Free Parcel Data

Colorado Yuma County

Field dictionary

GEOID08125
Aged

11 attribute fields, profiled from the November 2022 vintage.

Columns in Yuma County

Field Type Filled Distinct Example values
objectid OFTInteger 100% 11.9k 4, 23, 53
gis_parcel OFTString 100% 11.5k R528090, R528086, R528085
tsc_parcel OFTString 100% 11.4k R528090, R528086, R528085
tsc_owner1 OFTString 100% 5.0k GREAT SCOTT, LTD NASSER, BASSAM ET AL, GREAT SCOTT, LTD NASSER, BASSAM ET AL, GREAT SCOTT, LTD
tsc_owne_1 OFTString 100% 3.8k 8487 COUNTY ROAD K JOES CO 808229518, 8487 COUNTY ROAD K JOES CO 808229518, 8487 COUNTY ROAD K JOES CO 808229518
tsc_site_a OFTString 0%
tsc_net_ac OFTString 100% 4.4k 320.0000, 320.0000, 320.0000
tsc_tax_di OFTString 0%
tsc_accoun OFTString 100% 10 Agricultural, Agricultural, Agricultural
shape__are OFTReal 100% 11.8k 2246883.66796875, 2221036.08203125, 2219929.98828125
shape__len OFTReal 100% 11.9k 6378.44776589966, 6329.1700617176, 6335.34430462936

Why this differs from the next county over

There is no national parcel schema. Every assessor's office built its own, usually decades ago, usually inside whatever CAMA system it bought at the time. One county's owner column is OWNER_NAME, the next one's is own1, and a third splits it across four fields. Shapefile's ten-character DBF limit truncated a generation of them into things like TOTLNDVAL.

Nothing here is renamed or remapped. The columns above are exactly what is in the file, because a normalisation layer that quietly guesses wrong is worse than no normalisation at all — and every guess it makes is one you cannot audit.

The Filled column is the share of rows with a real value. Placeholder text such as n/a counts as empty; a column that is 100% present but 90% placeholder is a column that will disappoint you, and the profiler treats it accordingly.