6 attribute fields, profiled from the September 2017 vintage.
Columns in Stark County
| Field | Type | Filled | Distinct | Example values |
|---|---|---|---|---|
| PPID | OFTString | 10.9k | 36000006751000, 36000006706000, 36000006705000 | |
| PID | OFTString | 10.5k | 36000006751000, 36000006706000, 36000006705000 | |
| OWNERNAME | OFTString | 4.7k | SWENSON, KRIS ALLEN, SWENSON, KRIS, SWENSON, KRIS | |
| OWNERADDRE | OFTString | 4.2k | 5117 132ND AVE SW, BELFIELD ND 58622, 5117 132ND AVE SW, BELFIELD ND 58622, 5117 132ND AVE SW, BELFIELD ND 58622 | |
| PROPERTYAD | OFTString | 3.4k | 0, 0, 0 | |
| LEGALDESC | OFTString | 10.5k |
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.