Free Parcel Data

Kentucky Trimble County

Field dictionary

GEOID21223
Aged

11 attribute fields, profiled from the January 2019 vintage.

Columns in Trimble County

Field Type Filled Distinct Example values
PARCEL_ID OFTString 97% 5.1k 004-00-00-004.00, 004-00-00-007.00, 004-00-00-007.00
SALE_PRICE OFTReal 100% 610 24500.0, 0.0, 0.0
LAND_COVER OFTString 100% 3.4k {"41": 43}, {"11": 90, "21": 2, "22": 3, "41": 68, "52": 3, "81": 12}, {"11": 106, "21": 6, "22": 1, "31": 1, "41": 113, "81": 21}
MUNI_ID OFTInteger64 100% 2 1936871, 1936871, 1936871
ACREAGE OFTReal 100% 2.1k 6.02, 30.33, 42.79
ZIP_CODE OFTString 100% 5 40006, 40006, 40006
AREA_METER OFTReal 100% 5.5k 24364.460834506, 122747.266331213, 173151.663920395
CALC_ACREA OFTReal 100% 5.5k 6.02070191681478, 30.332076983106, 42.7875076713688
COUNTY_NAM OFTString 100% 1 Trimble, Trimble, Trimble
COUNTY_FIP OFTInteger64 100% 1 21223, 21223, 21223
STATE_ABBR OFTString 100% 1 KY, KY, KY

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.