Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Disk & Database›.dbf
THE FILE FIELD GUIDE
.dbf

DBF data table

Disk & Database

DBF is an xBase table, also used for Shapefile attributes. It does not by itself contain map geometry. Check encoding, memo companions and row correspondence before editing.

Main use
Storing tables or geographic attributes
Data type
Binary data / document
All sections, questions and sources

Content reviewed： · Editor：Kai

Example: a practical checking sequence

Example: independently sorting a Shapefile DBF can break attributes. Check the original complete dataset and edit through GIS. For garbled Japanese, establish the correct encoding before export; do not overwrite undecoded text.

Opening steps

Choose your environment or purpose to see its steps.

DBF belonging to a Shapefile

Keep SHP, SHX and encoding companions together.

  1. Copy matching SHP, SHX, DBF, CPG and other companions.
  2. Open the Shapefile in compatible GIS and display its attribute table.
  3. Check encoding and feature-to-row correspondence.
A standalone DBF table

Check DBF variant and memo support.

  1. Identify producer, table variant and memo companions.
  2. Open a copy in compatible database/table software.
  3. Compare row counts, text, dates, numbers and memos.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Japanese text is garbled: inspect CPG and source encoding.
  • No map: DBF holds attributes; obtain geometry companions.
  • Empty memos: check companions and variant support.
  • Wrong map attributes: isolated sorting/deletion may break correspondence.
  • Truncated fields: inspect format limits for names, types and widths.

DBF → CSV or a complete GIS format

  1. Preserve source and companions.
  2. Export standalone tables to appropriately encoded CSV or complete geographic data to supported GIS formats.
  3. Verify rows, fields, text, coordinates and attribute correspondence.

CSV does not preserve all memo/type/spatial structure; do not independently reorder a Shapefile DBF and replace it.

Attributes versus geometry

Shapefiles combine geometry and attributes across companion files; edit through GIS to preserve their correspondence.

Source for these steps：GDAL · ESRI Shapefile / DBF driver

Check encoding before export

Saving garbled text can destroy original characters. Decode correctly before creating a new export.

  • Keep encoding companions.
  • Compare dates, numbers and nulls.
  • Check destination field-name limits.

Source for these steps：GDAL · ESRI Shapefile / DBF driver / QGIS · Vector general algorithms

Related-format differences

Related-format differences
Format / purposeUse and preserved information
DBFTyped table data.
SHPShapefile geometry.
CSVText table with different type/structure semantics.

Handling and security

Tables/maps can contain customer and location data; inspect before sharing and back up the complete set.

Questions and answers

Does DBF contain the map?

Not generally; geometry is separate.

Can I sort it externally and put it back?

Use GIS editing to avoid breaking correspondence.

Does garbling mean corruption?

Check encoding first.

Why are memos missing?

Check companions and format support.

Does CSV preserve everything?

No; types, memos and spatial structure differ.

Format facts: name, steward and MIME type
Formal name
dBASE / xBase table
Steward / specification
dBASE / xBase / GIS implementations
MIME type
Check the producer or implementation; do not assume a single universal MIME value.

Primary and official sources