Shapefile: Parcels Attributes (.dbf)
The parcel attribute table, joined to the .shp purely by record order: there is no key and no explicit link. Deleting a geometry without deleting its row shifts every subsequent attribute onto the wrong shape, silently.
| CODE | NAME | USE | AREA_HA |
|---|---|---|---|
| P-001 | Harbour Yard | commercial | 1.42 |
| P-002 | Mill Court | residential | 2.05 |
| P-003 | Holloway Glebe | agricultural | 3.31 |
Specifications
- Format
- Esri shapefile component
- Crs
- WGS 84 (EPSG:4326)
- Byte Order
- mixed: big-endian headers, little-endian records
- Sidecar Set
- .shp/.shx/.dbf/.prj/.cpg
- Records
- 3
- Fields
- 4
- Field Names
- CODE, NAME, USE, AREA_HA
- Field Types
- C(8), C(24), C(14), N(8,2)
- Date Stamp
- 2026-01-01 (fixed for reproducibility)
Testing contract
Expected to pass- Scenario
- Join the attributes to the geometry and verify that row order still matches record order.
- Expected result
- Row 2 (Mill Court) pairs with the two-ring polygon; the join is positional, so any reordering of either file is detectable as a mismatch.
What is a .dbf file?
A dBASE table (.dbf) is a legacy binary tabular format with a fixed-width header describing columns (name, type, length) followed by fixed-length records. It persists today as the attribute table of GIS shapefiles and in legacy database exchange.
How to use this file
Use an example .dbf file to test dBASE/xBase readers, shapefile attribute parsing, and DBF-to-CSV conversion.
How to use this file for testing
“Shapefile: Parcels Attributes (.dbf)” is a deterministic Testaroo fixture for Geospatial, Data import, Serialization testing. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks, for testing map tools, route parsers, and geo importers.
Documented properties for this file: 3 records · 4 fields · Esri shapefile component. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Generated by generation/geospatial.py. Free for any use, no attribution required, license.
Related files
- dbfShapefile: Roads Attributes (.dbf with a decimal field)The road attribute table, including a numeric field declared with two decimal places. DBF stores numbers as right-justified ASCII, so the declared width and decimal count are the only thing that says 9.40 is not 940.
- dbfShapefile: Towns Attributes (.dbf, dBase III)The attribute table as a dBase III file: fixed-width, space-padded, ASCII numerics. Field names are capped at ten characters and there is no type for dates-with-time or for nested values, which is why shapefile export loses so much of a modern schema.
- zipShapefile Bundle: Kestrel Bay Parcels (zipped component set)A zipped shapefile containing a three-file polygon set with no .cpg, so the DBF encoding is undeclared. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.
- zipShapefile Bundle: Kestrel Bay Towns (zipped component set)A zipped shapefile containing the full five-file point set: .shp, .shx, .dbf, .prj and .cpg. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.
- dbfShapefile DBF: Accented Attributes in CP1252The same four accented attribute rows written in CP1252. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.
- dbfShapefile DBF: Accented Attributes in UTF-8The same four accented attribute rows written in UTF-8. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.
