61 attribute fields, profiled from the April 2021 vintage.
Columns in Cullman County
| Field | Type | Filled | Distinct | Example values |
|---|---|---|---|---|
| objectid | OFTInteger | 50.0k | 442, 443, 2186 | |
| parcelid | OFTString | 50.0k | 3109290000004001, 3109290000004002, 3109290000004004 | |
| pin | OFTReal | 50.0k | 72120.0, 73344.0, 83999.0 | |
| owner | OFTString | 42.4k | CHASTEEN TAMMY, CHASTEEN TAMMY, CHASTEEN TAMMY | |
| mailadd1 | OFTString | 31.4k | 385 COUNTY RD 4, 385 COUNTY RD 4, 385 COUNTY RD 4 | |
| mailadd2 | OFTString | 292 | SUITE 200, SUITE 200, SUITE 300 | |
| mailadd3 | OFTString | — | ||
| mailcity | OFTString | 1.1k | BREMEN, BREMEN, BREMEN | |
| mailstate | OFTString | 50 | AL, AL, AL | |
| mailzip1 | OFTString | 1.4k | 35033, 35033, 35033 | |
| mailzip2 | OFTString | 1.6k | 1549, 5105, -503 | |
| previousow | OFTString | 40.4k | HAMM, RONNIE, HAMM, RONNIE A & FRANCES R, HAMM, RONNIE A & FRANCES R | |
| neighborho | OFTString | 15 | E, E, E | |
| propertycl | OFTString | — | ||
| propertysu | OFTString | — | ||
| timberacre | OFTReal | 851 | 25.0, 40.0, 26.0 | |
| uservalue | OFTInteger | 4.4k | 10625, 48468, 48468 | |
| taxdist | OFTString | 12 | 01, 01, 01 | |
| flag1 | OFTString | — | ||
| flag2 | OFTString | — | ||
| flag3 | OFTString | — | ||
| flag4 | OFTString | — | ||
| flag5 | OFTString | — | ||
| flag6 | OFTString | — | ||
| situsaddid | OFTInteger | — | ||
| situsaddna | OFTString | 5.1k | COUNTY RD 4, COUNTY RD 4, COUNTY RD 4 | |
| situsaddnu | OFTInteger | 6.3k | 0, 0, 0 | |
| situsaddci | OFTInteger | — | ||
| impdescrip | OFTString | 1.4k | ,, Res/Com, Pool, Barn, Utility, Barn, , | |
| sublot | OFTString | 1.0k | 5 & 6, 4, 1 | |
| subblock | OFTString | 152 | 002, 002, 002 | |
| deededacre | OFTReal | 1.1k | 39.95, 7.59, 0.0 | |
| calcacres | OFTReal | 2.3k | 39.95, 8.59, 2.4 | |
| pin_pid | OFTString | 50.0k | 72120.00000000, 3109290000004001, 73344.00000000, 3109290000004002, 83999.00000000, 3109290000004004 | |
| neighbor_1 | OFTString | 15 | E, E, E | |
| legaldescr | OFTString | 50.0k | 39.95 AC- NW 1/4 OF SW 1/4, 78 ACRES E 1/2 SE 1/4 LESS ROW, 40 ACRES SW 1/4 SW 1/4 | |
| taxyeardue | OFTInteger | 2 | 2021, 2021, 2021 | |
| totaltaxdu | OFTReal | 16.2k | 346.32, 951.32, 26.0 | |
| cimpvalue | OFTReal | 4.9k | 0.0, 343800.0, 0.0 | |
| clandvalue | OFTReal | 8.3k | 133200.0, 39300.0, 9900.0 | |
| area | OFTReal | 50.0k | 231270.914724, 45318.813125, 14037.77351 | |
| len | OFTReal | 50.0k | 1924.606418, 976.636364, 677.738035 | |
| ttv | OFTReal | 11.9k | 133200.0, 383100.0, 9900.0 | |
| tav | OFTReal | 4.6k | 13320.0, 38320.0, 1000.0 | |
| join_count | OFTInteger | 1 | 1, 1, 1 | |
| target_fid | OFTInteger | 50.0k | 442, 443, 2186 | |
| oid_1 | OFTInteger | — | ||
| subdivisio | OFTString | 1.1k | UNION GROVE ACRES SUB, UNION GROVE ACRES SUB, UNION GROVE ACRES SUB | |
| deedbook | OFTString | 1.3k | 691, 691, 691 | |
| deedpage | OFTString | 1.3k | 424, 424, 424 | |
| deedrecord | OFTString | 8.1k | 2019-12-26, 2019-12-26, 2019-12-26 | |
| deedsigned | OFTString | 1.5k | 2019-11-27, 2019-11-27, 2019-11-27 | |
| join_cou_1 | OFTInteger | 4 | 1, 1, 1 | |
| target_f_1 | OFTInteger | 50.0k | 442, 443, 2186 | |
| orig_fid | OFTInteger | 50.0k | 442, 443, 2186 | |
| str | OFTString | 792 | 29-13S-04W, 29-13S-04W, 29-13S-04W | |
| section_ | OFTString | 36 | 29, 29, 29 | |
| township | OFTString | 7 | 13S, 13S, 13S | |
| range | OFTString | 8 | 04W, 04W, 04W | |
| point_x | OFTReal | 50.0k | -86.987493, -86.988993, -86.988596 | |
| point_y | OFTReal | 50.0k | 33.879311, 33.881646, 33.88241 |
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.