Free Parcel Data

North Dakota Mountrail County

Field dictionary

GEOID38061
Aged

15 attribute fields, profiled from the January 2021 vintage.

Columns in Mountrail County

Field Type Filled Distinct Example values
objectid OFTInteger 100% 16.9k 55, 74, 75
gis_parcel OFTString 100% 15.9k 550001527, 550001526, 550001522
gis_acreag OFTReal 100% 3.2k 160.0, 160.0, 160.0
tsc_parcel OFTString 100% 15.9k 550001527, 550001526, 550001522
tsc_owner1 OFTString 100% 4.9k NO DOCUMENTS RECORDED, NO DOCUMENTS RECORDED, NO DOCUMENTS RECORDED
tsc_owne_1 OFTString 100% 4.2k 00000, 00000, 00000
tsc_acreag OFTInteger 100% 1 0, 0, 0
tsc_legal_ OFTString 85% 5.2k SW, NW, NE
tsc_sec_tw OFTString 100% 1.9k 22 150 093, 22 150 093, 21 150 093
tsc_townsh OFTString 100% 62 UNORG TWP 150-93, UNORG TWP 150-93, UNORG TWP 150-93
tsc_plat OFTString 31% 170 ORIGINAL TOWNSITE, ORIGINAL TOWNSITE, ORIGINAL TOWNSITE
tsc_block OFTString 100% 43 000, 000, 000
tsc_lot OFTString 21% 447 6, 16, 7
shape__are OFTReal 100% 16.2k 1433342.757812, 1433744.296875, 1432484.6875
shape__len OFTReal 100% 16.8k 4788.908886, 4789.587356, 4787.471826

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.