49 attribute fields, profiled from the October 2023 vintage.
Columns in Scotland County
| Field | Type | Filled | Distinct | Example values |
|---|---|---|---|---|
| objectid | OFTReal | 21.2k | 21128.0, 6765.0, 6766.0 | |
| no_match | OFTString | 4 | 74 behind LHA / CITYnocar, no card, no card | |
| acres | OFTReal | 6.3k | 0.011, 0.126, 0.159 | |
| pinid | OFTString | 21.8k | 0100010300101, 01000101015, 01000101016 | |
| recno | OFTString | 21.3k | PE012908, PE012909, PE012910 | |
| update1 | OFTString | 474 | 2007/04/13, 2010/02/03, 2010/02/03 | |
| pin | OFTString | 21.8k | 010001 0300101, 010001 01015, 010001 01016 | |
| accountnum | OFTReal | 14.6k | 907974.0, 7071030.0, 7071030.0 | |
| address1 | OFTString | 6.9k | PATTERSON DICIE M, W BROOKS JR & WF. SUMA R., TRANSPORT INC | |
| address2 | OFTString | 8.9k | 13401 WESLEYAN DR, 1304 SHEPHERD AVE, 107 W RAILROAD ST | |
| address3 | OFTString | 4.4k | P O BOX 249, P O BOX 249, 106 N GILL ST | |
| assessedva | OFTInteger | 1.3k | 0, 0, 0 | |
| buildingva | OFTInteger | 8.5k | 4550, 0, 0 | |
| city | OFTString | 859 | LAURINBURG, LAURINBURG, LAURINBURG | |
| citycode | OFTString | 5 | L, L, L | |
| countytaxc | OFTString | 1 | C, C, C | |
| deedbook | OFTString | 1.9k | 1715, 1559, 1610 | |
| deeddate | OFTInteger | 5.5k | 20210601, 20170911, 20190205 | |
| deedpage | OFTReal | 967 | 109.0, 109.0, 130.0 | |
| deedstamps | OFTInteger | 455 | 0, 0, 0 | |
| deferredva | OFTInteger | 1.3k | 0, 0, 0 | |
| exemptionc | OFTString | 2 | EDAV, EDAV, ELD | |
| firetaxcod | OFTString | 1 | FIRE, FIRE, FIRE | |
| legaldescr | OFTString | 20.7k | PT 201-205 MAIN ST-PARC 2, 102 S. GILL ST, 129 W. RAILROAD ST | |
| legallandu | OFTReal | 2.9k | 1.0, 1.0, 1.0 | |
| legallan_1 | OFTString | 5 | LT, LT, LT | |
| marketland | OFTInteger | 4.6k | 2430, 8650, 11010 | |
| marketvalu | OFTInteger | 11.0k | 6980, 9060, 11550 | |
| name | OFTString | 13.6k | MIRABAL DAIMEL, LAURINBURG CITY, LAURINBURG CITY | |
| obxfvalue | OFTInteger | 1.7k | 0, 410, 540 | |
| parcelnumb | OFTString | 21.7k | 010001 0300101, 010001 01015, 010001 01016 | |
| parcelnu_1 | OFTReal | 1.4k | 30.01694444, 10.25, 10.26666667 | |
| parcelnu_2 | OFTReal | 199 | 1.00027778, 1.00027778, 1.00027778 | |
| propertyad | OFTString | 13.9k | FAIRLY ST, 102 RAILROAD ST, 129 RAILROAD ST | |
| saleinstru | OFTString | 41 | WD, WD, WD | |
| schooltaxc | OFTString | 1 | SCH, SCH, SCH | |
| state | OFTString | 46 | NC, NC, NC | |
| zipcode | OFTInteger | 7.0k | 283521815, 283530000, 283530000 | |
| field30 | OFTString | — | ||
| zipcode_1 | OFTString | — | ||
| shape_star | OFTReal | 21.8k | 497.903747559, 5494.50622559, 6941.03112793 | |
| shape_stle | OFTReal | 21.8k | 91.1644000464, 309.37623489, 338.31826099 | |
| shape__are | OFTReal | 21.8k | 497.90380859375, 5494.50628662109, 6941.03112792969 | |
| shape__len | OFTReal | 21.8k | 91.1644000539558, 309.376234889292, 338.318260997351 | |
| globalid | OFTString | 21.8k | d3b1be44-9abf-4f0b-80a6-e74afc567817, 90c08b8c-5fe7-4e19-ab93-0e133e1060e9, feb2a26d-73de-4ad0-a210-12f00da7f3d3 | |
| creationda | OFTString | 10 | 2022-09-27, 2022-09-27, 2022-09-27 | |
| creator | OFTString | 2 | krivera_laurinburg, krivera_laurinburg, krivera_laurinburg | |
| editdate | OFTString | 25 | 2022-09-27, 2022-09-27, 2022-09-27 | |
| editor | OFTString | 2 | krivera_laurinburg, krivera_laurinburg, krivera_laurinburg |
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.