48 attribute fields, profiled from the June 2022 vintage.
Columns in Escambia County
| Field | Type | Filled | Distinct | Example values |
|---|---|---|---|---|
| objectid | OFTInteger | 50.0k | 5666367, 5666368, 5666370 | |
| reference | OFTString | 50.0k | 014S331002390004, 014S331002250004, 014S331010000018 | |
| refnum | OFTString | 50.0k | 01-4S-33-1002-390-004, 01-4S-33-1002-250-004, 01-4S-33-1010-000-018 | |
| owner | OFTString | 50.0k | MGFB PROPERTIES INC, MGFB PROPERTIES INC, KEY WEST OF PERDIDO KEY | |
| mailaddres | OFTString | 50.0k | 17401 PERDIDO KEY DRIVE, 17401 PERDIDO KEY DRIVE, 224 KEY LARGO PL | |
| mailaddr_1 | OFTString | 599 | 165 FLANDERS RD, 3 POYDRAS ST STE 9D, REGIONAL CENTER | |
| mailcity | OFTString | 3.5k | PENSACOLA, PENSACOLA, PENSACOLA | |
| mailstate | OFTString | 64 | FL, FL, FL | |
| mailzip | OFTString | 9.1k | 32507, 32507, 32507 | |
| mailcountr | OFTString | 17 | CANADA, *, * | |
| year_ | OFTString | 1 | 2022, 2022, 2022 | |
| controlno | OFTString | 50.0k | 104637475, 104637020, 104649034 | |
| siteaddr | OFTString | 50.0k | 17348 PERDIDO KEY DR, PERDIDO KEY DR, 208 KEY LARGO PL | |
| city | OFTString | 7 | PENSACOLA, PENSACOLA, PENSACOLA | |
| zip | OFTString | 18 | 32507, 32507, 32507 | |
| subdivcond | OFTString | 1.8k | 743, 743, 743 | |
| subdivisio | OFTString | 1.7k | KEY WEST PB 15 P 65, KEY WEST PB 15 P 65, KEY WEST PB 15 P 65 | |
| legal1 | OFTString | 50.0k | COMMENCING AT THE INTERSECTION, COMMENCING AT THE INTERSECTION, PARCEL A PRIVATE PARK KEY WEST | |
| legal2 | OFTString | 50.0k | OFTHE NORTH RIGHT-OF-WAY LINE, OF THE NORTH RIGHT-OF-WAY LIN, PB 15 P 65 OR 5441 P 1358 | |
| legal3 | OFTString | 50.0k | OF FLORIDA STATE HIGHWAY NO., E OF FLORIDA STATE HIGHWAY NO., LA FLA ST LI N 77 DEG 2 MIN 0 | |
| legal4 | OFTString | 50.0k | 292 AND THE ALABAMA-FLORIDA ST, 292 AND THE ALABAMA-FLORIDA S, SEC E ALG ELY PROJ OF CENTER L | |
| legal5 | OFTString | 45.5k | ATE LINE; RUN THENCE N 76 DEG, TATE LINE; RUN THENCE N 76 DEG, I 268 47/100 FT CONT N 77 DEG | |
| legal6 | OFTString | 40.3k | 22 MIN 32 SEC E ALONG SAID NOR..., 22 MIN 32 SEC E ALONG SAID NO..., 2 MIN 0 SEC E ALG SAME COURSE ... | |
| confcd | OFTString | 2 | N, N, N | |
| citycd | OFTString | 5 | MSTU, MSTU, MSTU | |
| tifcd | OFTString | 22 | PKTF, PKTF, PKTF | |
| dorcd | OFTString | 110 | 1000, 1000, 0900 | |
| delinqcd | OFTString | 2 | N, N, N | |
| agexempt | OFTString | 2 | N, N, N | |
| currasdlan | OFTReal | 24.1k | 160000.0, 160000.0, 1.0 | |
| currasdbld | OFTReal | 50.0k | 0.0, 0.0, 0.0 | |
| currasdxf | OFTReal | 11.7k | 0.0, 0.0, 0.0 | |
| currmkt | OFTReal | 50.0k | 160000.0, 160000.0, 1.0 | |
| prevasdlan | OFTReal | 24.1k | 160000.0, 160000.0, 1.0 | |
| prevasdbld | OFTReal | 50.0k | 0.0, 0.0, 0.0 | |
| prevasdxf | OFTReal | 11.7k | 0.0, 0.0, 0.0 | |
| prevmkt | OFTReal | 50.0k | 160000.0, 160000.0, 1.0 | |
| sohyear | OFTInteger | 30 | 0, 0, 0 | |
| ownersplit | OFTInteger | 1 | 1, 1, 1 | |
| landapprai | OFTString | 2.0k | 6/6/2019, 6/6/2019, 6/24/2019 | |
| landtype | OFTString | 27 | WATERFRONT - WORKING, WATERFRONT - NON WORKING, RESIDENTIAL | |
| landsize | OFTReal | 13.9k | 0.5619, 0.5526, 0.0472 | |
| mapnum | OFTString | 1.0k | 01-4S-33, 01-4S-33, 01-4S-33 | |
| exemption | OFTString | 22 | HOMESTEAD EXEMPTION, HOMESTEAD EXEMPTION, HOMESTEAD EXEMPTION | |
| link | OFTString | 50.0k | http://www.escpa.org/cama/Detail_a.aspx?s=014S331002390004, http://www.escpa.org/cama/Detail_a.aspx?s=014S331002250004, http://www.escpa.org/cama/Detail_a.aspx?s=014S331010000018 | |
| cappedvalu | OFTReal | 50.0k | 160000.0, 160000.0, 1.0 | |
| starea() | OFTReal | 50.0k | 24478.116089, 24071.087921, 2055.882599 | |
| stlength() | OFTReal | 50.0k | 1113.158691, 1089.69276, 211.606156 |
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.