@urbankitstudio/atlas 0.6.35 → 0.6.37

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -245,9 +245,9 @@ read `addedAt` and fall back to the oldest `lastVerified` only when it is absent
245
245
 
246
246
  ## Coverage today
247
247
 
248
- The atlas bundles **395 counties across all 50 US states and DC** (413 verified endpoints), covering the largest counties in each state, and every county in Mississippi. Call `listStates()` to enumerate the full set.
248
+ The atlas bundles **479 counties across all 50 US states and DC** (494 verified endpoints), covering the largest counties in each state, every county in Mississippi and 98 of North Carolina's 100. Call `listStates()` to enumerate the full set.
249
249
 
250
- Every state has at least one county on record, and 386 of the 395 carry a verified endpoint. The other 9 have `hasPublicRest: false` and an empty `endpoints` array, with `notes` recording the reason and who to contact. Those reasons vary: a subscription-only regional GIS partner, a statewide server that requires an auth token, a state with no county-level parcel authority, a county viewer with no public query API, a county that does not publish owner names online. They ship rather than being omitted, so `findCounty()` still resolves them. **Check `hasPublicRest`** rather than assuming every county has an endpoint; `totals.countiesWithEndpoint` gives the queryable count directly.
250
+ Every state has at least one county on record, and 467 of the 479 carry a verified endpoint. The other 12 have `hasPublicRest: false` and an empty `endpoints` array, with `notes` recording the reason and who to contact. Those reasons vary: a subscription-only regional GIS partner, a statewide server that requires an auth token, a state with no county-level parcel authority, a county viewer with no public query API, a county that does not publish owner names online. They ship rather than being omitted, so `findCounty()` still resolves them. **Check `hasPublicRest`** rather than assuming every county has an endpoint; `totals.countiesWithEndpoint` gives the queryable count directly.
251
251
 
252
252
  The city registries cover 30 cities with code-violation or building-permit datasets, 19 with zoning-case datasets. Call `listCities()` for the current set.
253
253
 
@@ -261,6 +261,20 @@ The live, browseable atlas lives at [urbankitstudio.com/parcel-atlas](https://ur
261
261
 
262
262
  Socket also flags `unpopularPackage` — a download-count signal, not a code issue, that install growth resolves on its own.
263
263
 
264
+ ## Attribution
265
+
266
+ The parcel layers the atlas points to belong to their publishers. These publishers require or request credit when their data is reused, and each record listed here ends its `notes` with the same `Credit:` line.
267
+
268
+ | Records | Publisher's terms | Credit |
269
+ |---|---|---|
270
+ | `co-el-paso`, `co-jefferson`, `co-arapahoe`, `co-adams`, `co-douglas`, `co-larimer`, `co-boulder`, `co-weld`, `co-mesa`, `co-park` (the State of Colorado's `Colorado_Public_Parcels` service) | The service's copyright text names this statement as sufficient | State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel |
271
+ | `md-montgomery` | Reuse allowed, attribution requested | Montgomery County Planning Department (M-NCPPC) |
272
+ | `md-prince-georges` | Reuse allowed, attribution requested | Prince George's County Planning Department (M-NCPPC) |
273
+ | `nc-wake` | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) | Wake County (Wake County GIS, Wake County Revenue) |
274
+ | `ca-sonoma` | [CC BY-SA 3.0 US](https://creativecommons.org/licenses/by-sa/3.0/us/legalcode) | County of Sonoma |
275
+ | `ca-sacramento` | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) in the county's catalog (the item itself says public domain) | Sacramento County GIS |
276
+ | `dc-district-of-columbia` | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) | District of Columbia |
277
+
264
278
  ## License
265
279
 
266
280
  MIT — see [LICENSE](./LICENSE). © 2026 UrbanKit Studio.
@@ -91,7 +91,7 @@
91
91
  "url": "https://data-sacramentocounty.opendata.arcgis.com/",
92
92
  "email": null
93
93
  },
94
- "notes": "22 fields confirmed: OBJECTID, APN, LOT_SIZE, NEIBRHC, JURISDICTION, STREET_NBR, STREET_NAM, CITY, ZIP, TRA, SUBDIVISIO, LOT, LANDUSE, LU_GENERAL, LU_SPECIF, LU_DETAIL, LU_USE, LU_SEC_USE, PRCL_KEY, PRCL_TYPE, Shape__Area, Shape__Length. Live query confirmed: JURISDICTION='CITRUS HEIGHTS' returns real Sacramento County parcels. NOTE: Owner name is NOT on this public layer. APN is the 14-character Sacramento County parcel number. Land use fields are detailed (LU_GENERAL, LU_SPECIF, LU_DETAIL). ArcGIS item ID: 8d011b99aebc46d48060b2e5bdd7f4a0. Hosted on ArcGIS Online (services1.arcgis.com/5NARefyPVtAeuJPU). Capabilities: Query, Extract. maxRecordCount=2000."
94
+ "notes": "22 fields confirmed: OBJECTID, APN, LOT_SIZE, NEIBRHC, JURISDICTION, STREET_NBR, STREET_NAM, CITY, ZIP, TRA, SUBDIVISIO, LOT, LANDUSE, LU_GENERAL, LU_SPECIF, LU_DETAIL, LU_USE, LU_SEC_USE, PRCL_KEY, PRCL_TYPE, Shape__Area, Shape__Length. Live query confirmed: JURISDICTION='CITRUS HEIGHTS' returns real Sacramento County parcels. NOTE: Owner name is NOT on this public layer. APN is the 14-character Sacramento County parcel number. Land use fields are detailed (LU_GENERAL, LU_SPECIF, LU_DETAIL). ArcGIS item ID: 8d011b99aebc46d48060b2e5bdd7f4a0. Hosted on ArcGIS Online (services1.arcgis.com/5NARefyPVtAeuJPU). Capabilities: Query, Extract. maxRecordCount=2000. Credit: Sacramento County GIS. The county's open-data catalog lists this layer under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0), while its ArcGIS item reads \"This work is licensed under a Creative Commons Public Domain Dedication License\"; crediting the county satisfies either."
95
95
  },
96
96
  {
97
97
  "id": "ca-sonoma",
@@ -129,7 +129,7 @@
129
129
  "url": "https://gis-sonomacounty.hub.arcgis.com/",
130
130
  "email": null
131
131
  },
132
- "notes": "Sonoma County (county seat Santa Rosa, pop. 490,000) publishes parcels through the OWTSPublic Cities_GIS_Parcel_Base FeatureServer. APN format is XXX-XXX-XXX with hyphens (e.g. '029-201-001'). Owner name is NOT exposed on this public layer; for ownership, use the county Assessor. (Why California counties differ on this is explained on the California state page.) The Sonoma County Assessor's parcel search is at sonomacounty.ca.gov/assessor. The address schema on this layer was refactored in 2026: the prior single SitusAddress string field was replaced by two formatted address lines (SitusFormatted1, SitusFormatted2) plus fully structured components, SitusStreetNo, SitusDirection, SitusStreetName, SitusStreetType, SitusUnitNumber, SitusCity, SitusState, SitusZip. Queries on the old SitusAddress field name will fail against the current layer; use SitusFormatted1 or SitusStreetName instead. The endpoint is hosted on the county's own ArcGIS server (socogis.sonomacounty.ca.gov). The Sonoma County GIS open-data hub is at gis-sonomacounty.hub.arcgis.com."
132
+ "notes": "Sonoma County (county seat Santa Rosa, pop. 490,000) publishes parcels through the OWTSPublic Cities_GIS_Parcel_Base FeatureServer. APN format is XXX-XXX-XXX with hyphens (e.g. '029-201-001'). Owner name is NOT exposed on this public layer; for ownership, use the county Assessor. (Why California counties differ on this is explained on the California state page.) The Sonoma County Assessor's parcel search is at sonomacounty.ca.gov/assessor. The address schema on this layer was refactored in 2026: the prior single SitusAddress string field was replaced by two formatted address lines (SitusFormatted1, SitusFormatted2) plus fully structured components, SitusStreetNo, SitusDirection, SitusStreetName, SitusStreetType, SitusUnitNumber, SitusCity, SitusState, SitusZip. Queries on the old SitusAddress field name will fail against the current layer; use SitusFormatted1 or SitusStreetName instead. The endpoint is hosted on the county's own ArcGIS server (socogis.sonomacounty.ca.gov). The Sonoma County GIS open-data hub is at gis-sonomacounty.hub.arcgis.com. The layer's description says its “primary difference” from the county's ‘Parcels Public’ layer is “the inclusion of additional attributes licensed for internal use ONLY”; on 2026-10-17 the only columns it had that Parcels Public lacks were editor-tracking fields (GlobalID, created_user, created_date, last_edited_user), and this record serves none of them, only the APN and situs columns Parcels Public also publishes. Credit: County of Sonoma. The layer's copyright text says: \"You must source attribution “County of Sonoma” when distributing this data\", and the service metadata (Cities_GIS_Parcel_Base MapServer, info/metadata) names the licence as the “Attribution-ShareAlike” 3.0 United States (CC BY-SA 3.0 US), https://creativecommons.org/licenses/by-sa/3.0/us/legalcode."
133
133
  },
134
134
  {
135
135
  "id": "ca-orange",
@@ -34,7 +34,7 @@
34
34
  "orderField": "File_Date",
35
35
  "streetNumberType": "number",
36
36
  "latestRecordDate": "2026-10-13",
37
- "coverage": "Fort Worth development permits, about 1.6 million records filed 2001 to present. Trade permits (electrical, mechanical, plumbing, backflow) are included alongside building permits. The street is split across columns: with a house number, '8653 Funtier Ct' is matched as 8653 on Addr_No and 'Funtier' on Street_Name (one leading direction and one common street type are dropped). Without a house number the name alone gets the same trimming, so 'Funtier Ct' is matched as 'Funtier' on Street_Name.",
37
+ "coverage": "Fort Worth development permits, about 1.6 million records filed 2001 to present. Trade permits (electrical, mechanical, plumbing, backflow) are included alongside building permits. The street is split across columns: with a house number, '8653 Funtier Ct' is matched as 8653 on Addr_No and 'Funtier' on Street_Name (one leading direction and one common street type are dropped; a street named South or North keeps its name, so '2600 South Blvd' is matched as 'South'; a lettered street keeps its letter, so '1700 E Q St' is matched as 1700 on Addr_No and 'Q' on Street_Name; a house number plus one stray word with no street type, such as '100 E' or '100 %', is searched as typed against Street_Name and finds no rows). Without a house number the name alone gets the same trimming, so 'Funtier Ct' is matched as 'Funtier' on Street_Name.",
38
38
  "recordLabel": "Permit",
39
39
  "openedLabel": "Filed",
40
40
  "fields": {
@@ -16,7 +16,7 @@
16
16
  "orderField": "adddttm",
17
17
  "streetNumberType": "text",
18
18
  "latestRecordDate": "2026-10-09",
19
- "coverage": "Open LADBS code-enforcement cases only, about 29,000, opened 1995 to present. Closed cases are published in a separate dataset (rken-a55j) that this tool does not search. The street is split across columns: with a house number, '139 W 88th St' is matched as 139 on stno and '88th' on stname (one leading direction and one common street type are dropped). Without a house number the name alone gets the same trimming, so '88th St' is matched as '88th' on stname.",
19
+ "coverage": "Open LADBS code-enforcement cases only, about 29,000, opened 1995 to present. Closed cases are published in a separate dataset (rken-a55j) that this tool does not search. The street is split across columns: with a house number, '139 W 88th St' is matched as 139 on stno and '88th' on stname (one leading direction and one common street type are dropped; a street named South or North keeps its name, so '2600 South Blvd' is matched as 'South'; a lettered street keeps its letter, so '1700 E Q St' is matched as 1700 on stno and 'Q' on stname; a house number plus one stray word with no street type, such as '100 E' or '100 %', is searched as typed against stname and finds no rows). Without a house number the name alone gets the same trimming, so '88th St' is matched as '88th' on stname.",
20
20
  "recordLabel": "Case",
21
21
  "openedLabel": "Opened",
22
22
  "fields": {
@@ -16,7 +16,7 @@
16
16
  "orderField": "DateComplaintReceived",
17
17
  "streetNumberType": "number",
18
18
  "latestRecordDate": "2026-10-09",
19
- "coverage": "Scottsdale code complaints received since 2021-09, about 18,900 rows. Closed complaints only: open complaints are not published, and every row's status begins with CLOSED. No result means no closed complaint on file, not that the property has no open violation. The street is split across columns: with a house number, '4201 N Hayden Rd' is matched as 4201 on StreetNumber and 'Hayden' on StreetName (one leading direction and one common street type are dropped). Without a house number the name alone gets the same trimming, so 'Hayden Rd' is matched as 'Hayden' on StreetName.",
19
+ "coverage": "Scottsdale code complaints received since 2021-09, about 18,900 rows. Closed complaints only: open complaints are not published, and every row's status begins with CLOSED. No result means no closed complaint on file, not that the property has no open violation. The street is split across columns: with a house number, '4201 N Hayden Rd' is matched as 4201 on StreetNumber and 'Hayden' on StreetName (one leading direction and one common street type are dropped; a street named South or North keeps its name, so '2600 South Blvd' is matched as 'South'; a lettered street keeps its letter, so '1700 E Q St' is matched as 1700 on StreetNumber and 'Q' on StreetName; a house number plus one stray word with no street type, such as '100 E' or '100 %', is searched as typed against StreetName and finds no rows). Without a house number the name alone gets the same trimming, so 'Hayden Rd' is matched as 'Hayden' on StreetName.",
20
20
  "recordLabel": "Complaint",
21
21
  "openedLabel": "Received",
22
22
  "closedLabel": "Closed",
@@ -173,7 +173,7 @@
173
173
  "url": "https://gis.colorado.gov/",
174
174
  "email": null
175
175
  },
176
- "notes": "El Paso County (Colorado Springs metro, pop. 730,000, county seat Colorado Springs) is the second-most populous Colorado county and home to Fort Carson, Peterson Space Force Base, and Schriever Space Force Base. Like all Colorado counties, it uses the Colorado Governor's OIT statewide composite endpoint, query by countyName='El Paso' or countyFips='041' (the statewide layer uses the 3-digit county FIPS, not the full 5-digit '08041'). Owner query confirmed live with real Colorado Springs results (e.g., 'SMITH CHERYL LYNNE'). The composite layer exposes parcel_id, owner/owner2, ownerAdd/ownAddCty/ownAddStt/ownAddZip, situsAdd/sitAddCty/sitAddZip, legalDesc, landSqft/landAcres, zoningCode/zoningDesc, landUseCde/landUseDsc, saleDate, salePrice, apprValTot, asedValTot, and dateReceived (currency indicator for when each county's data was loaded). The El Paso County Assessor at assessor.elpasoco.com handles formal reassessment disputes. Colorado assesses on a biennial cycle, unlike Illinois or California, which use triennial or annual schedules.",
176
+ "notes": "El Paso County (Colorado Springs metro, pop. 730,000, county seat Colorado Springs) is the second-most populous Colorado county and home to Fort Carson, Peterson Space Force Base, and Schriever Space Force Base. Like all Colorado counties, it uses the Colorado Governor's OIT statewide composite endpoint, query by countyName='El Paso' or countyFips='041' (the statewide layer uses the 3-digit county FIPS, not the full 5-digit '08041'). Owner query confirmed live with real Colorado Springs results (e.g., 'SMITH CHERYL LYNNE'). The composite layer exposes parcel_id, owner/owner2, ownerAdd/ownAddCty/ownAddStt/ownAddZip, situsAdd/sitAddCty/sitAddZip, legalDesc, landSqft/landAcres, zoningCode/zoningDesc, landUseCde/landUseDsc, saleDate, salePrice, apprValTot, asedValTot, and dateReceived (currency indicator for when each county's data was loaded). The El Paso County Assessor at assessor.elpasoco.com handles formal reassessment disputes. Colorado assesses on a biennial cycle, unlike Illinois or California, which use triennial or annual schedules. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
177
177
  "capabilityOverrides": {
178
178
  "owner_name": {
179
179
  "status": "not_published",
@@ -299,7 +299,7 @@
299
299
  "url": "https://gis.colorado.gov/",
300
300
  "email": null
301
301
  },
302
- "notes": "Jefferson County (Denver's west-side suburbs, Lakewood, Arvada, Wheat Ridge, Evergreen, Golden; pop. 582,000, county seat Golden) is a mixed urban-mountain county extending from the Denver metro edge into the foothills and lower Rockies. Like all Colorado counties, it uses the Colorado Governor's OIT statewide composite endpoint, query by countyName='Jefferson' or countyFips='059' (3-digit county portion; full 5-digit is '08059'). Owner query confirmed live: returns real Jefferson County results (e.g., 'SMITH STEVEN W' at '7347 W FREMONT DR LITTLETON'). The composite layer exposes parcel_id, owner/owner2 (owner name fields), ownerAdd/ownAddCty/ownAddStt/ownAddZip (owner mailing address), situsAdd/sitAddCty/sitAddZip (situs address), legalDesc, landSqft/landAcres, zoningCode/zoningDesc, landUseCde/landUseDsc, saleDate/salePrice, apprValTot/asedValTot, and dateReceived. The Jefferson County Assessor at jeffco.us/1304/Assessor administers biennial reassessments (Colorado assesses on a two-year cycle, not triennial). Open-data downloads available at jeffco.us/GIS."
302
+ "notes": "Jefferson County (Denver's west-side suburbs, Lakewood, Arvada, Wheat Ridge, Evergreen, Golden; pop. 582,000, county seat Golden) is a mixed urban-mountain county extending from the Denver metro edge into the foothills and lower Rockies. Like all Colorado counties, it uses the Colorado Governor's OIT statewide composite endpoint, query by countyName='Jefferson' or countyFips='059' (3-digit county portion; full 5-digit is '08059'). Owner query confirmed live: returns real Jefferson County results (e.g., 'SMITH STEVEN W' at '7347 W FREMONT DR LITTLETON'). The composite layer exposes parcel_id, owner/owner2 (owner name fields), ownerAdd/ownAddCty/ownAddStt/ownAddZip (owner mailing address), situsAdd/sitAddCty/sitAddZip (situs address), legalDesc, landSqft/landAcres, zoningCode/zoningDesc, landUseCde/landUseDsc, saleDate/salePrice, apprValTot/asedValTot, and dateReceived. The Jefferson County Assessor at jeffco.us/1304/Assessor administers biennial reassessments (Colorado assesses on a two-year cycle, not triennial). Open-data downloads available at jeffco.us/GIS. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient)."
303
303
  },
304
304
  {
305
305
  "id": "co-arapahoe",
@@ -399,7 +399,7 @@
399
399
  "url": "https://gis.colorado.gov/",
400
400
  "email": null
401
401
  },
402
- "notes": "Arapahoe County, Colorado (Denver's southeast suburbs (Aurora, Centennial, Littleton, Englewood); FIPS 08005) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Arapahoe' to scope to Arapahoe County; the stored countyFips value is '005' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Arapahoe' counts 231,438 rows, owner populated on 98%, situs address on 93% and owner mailing address on 98%, and an owner-name SMITH search matches 1,495 rows. This is a state roll-up, not the county's own layer: every Arapahoe row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
402
+ "notes": "Arapahoe County, Colorado (Denver's southeast suburbs (Aurora, Centennial, Littleton, Englewood); FIPS 08005) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Arapahoe' to scope to Arapahoe County; the stored countyFips value is '005' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Arapahoe' counts 231,438 rows, owner populated on 98%, situs address on 93% and owner mailing address on 98%, and an owner-name SMITH search matches 1,495 rows. This is a state roll-up, not the county's own layer: every Arapahoe row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
403
403
  "addedAt": "2026-10-10"
404
404
  },
405
405
  {
@@ -500,7 +500,7 @@
500
500
  "url": "https://gis.colorado.gov/",
501
501
  "email": null
502
502
  },
503
- "notes": "Adams County, Colorado (Denver's north and east suburbs (Thornton, Westminster, Commerce City, Brighton); FIPS 08001) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Adams' to scope to Adams County; the stored countyFips value is '001' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Adams' counts 188,474 rows, owner populated on 99%, situs address on 93% and owner mailing address on 99%, and an owner-name SMITH search matches 826 rows. This is a state roll-up, not the county's own layer: every Adams row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
503
+ "notes": "Adams County, Colorado (Denver's north and east suburbs (Thornton, Westminster, Commerce City, Brighton); FIPS 08001) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Adams' to scope to Adams County; the stored countyFips value is '001' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Adams' counts 188,474 rows, owner populated on 99%, situs address on 93% and owner mailing address on 99%, and an owner-name SMITH search matches 826 rows. This is a state roll-up, not the county's own layer: every Adams row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
504
504
  "addedAt": "2026-10-10"
505
505
  },
506
506
  {
@@ -601,7 +601,7 @@
601
601
  "url": "https://gis.colorado.gov/",
602
602
  "email": null
603
603
  },
604
- "notes": "Douglas County, Colorado (the Denver-Colorado Springs corridor (Highlands Ranch, Parker, Castle Rock, Lone Tree); FIPS 08035) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Douglas' to scope to Douglas County; the stored countyFips value is '035' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Douglas' counts 164,818 rows, owner populated on over 99.9%, situs address on 88% and owner mailing address on over 99.9%, and an owner-name SMITH search matches 1,152 rows. This is a state roll-up, not the county's own layer: every Douglas row carries dateReceived 2026-04-21, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
604
+ "notes": "Douglas County, Colorado (the Denver-Colorado Springs corridor (Highlands Ranch, Parker, Castle Rock, Lone Tree); FIPS 08035) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Douglas' to scope to Douglas County; the stored countyFips value is '035' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Douglas' counts 164,818 rows, owner populated on over 99.9%, situs address on 88% and owner mailing address on over 99.9%, and an owner-name SMITH search matches 1,152 rows. This is a state roll-up, not the county's own layer: every Douglas row carries dateReceived 2026-04-21, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
605
605
  "addedAt": "2026-10-10"
606
606
  },
607
607
  {
@@ -702,7 +702,7 @@
702
702
  "url": "https://gis.colorado.gov/",
703
703
  "email": null
704
704
  },
705
- "notes": "Larimer County, Colorado (northern Colorado (Fort Collins, Loveland, Estes Park); FIPS 08069) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Larimer' to scope to Larimer County; the stored countyFips value is '69' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Larimer' counts 180,960 rows, owner populated on 99%, situs address on 88% and owner mailing address on 99%, and an owner-name SMITH search matches 1,063 rows. This is a state roll-up, not the county's own layer: every Larimer row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
705
+ "notes": "Larimer County, Colorado (northern Colorado (Fort Collins, Loveland, Estes Park); FIPS 08069) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Larimer' to scope to Larimer County; the stored countyFips value is '69' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Larimer' counts 180,960 rows, owner populated on 99%, situs address on 88% and owner mailing address on 99%, and an owner-name SMITH search matches 1,063 rows. This is a state roll-up, not the county's own layer: every Larimer row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
706
706
  "addedAt": "2026-10-10"
707
707
  },
708
708
  {
@@ -803,7 +803,7 @@
803
803
  "url": "https://gis.colorado.gov/",
804
804
  "email": null
805
805
  },
806
- "notes": "Boulder County, Colorado (the Boulder Valley (Boulder, Longmont, Louisville, Lafayette); FIPS 08013) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Boulder' to scope to Boulder County; the stored countyFips value is '013' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Boulder' counts 144,551 rows, owner populated on 99%, situs address on 99% and owner mailing address on 99%, and an owner-name SMITH search matches 829 rows. This is a state roll-up, not the county's own layer: every Boulder row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
806
+ "notes": "Boulder County, Colorado (the Boulder Valley (Boulder, Longmont, Louisville, Lafayette); FIPS 08013) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Boulder' to scope to Boulder County; the stored countyFips value is '013' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Boulder' counts 144,551 rows, owner populated on 99%, situs address on 99% and owner mailing address on 99%, and an owner-name SMITH search matches 829 rows. This is a state roll-up, not the county's own layer: every Boulder row carries dateReceived 2026-04-23, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
807
807
  "addedAt": "2026-10-10"
808
808
  },
809
809
  {
@@ -904,7 +904,7 @@
904
904
  "url": "https://gis.colorado.gov/",
905
905
  "email": null
906
906
  },
907
- "notes": "Weld County, Colorado (northern Colorado (Greeley, Evans, Windsor); FIPS 08123) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Weld' to scope to Weld County; the stored countyFips value is '123' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Weld' counts 163,491 rows, owner populated on 99%, situs address on 81% and owner mailing address on 99%, and an owner-name SMITH search matches 825 rows. This is a state roll-up, not the county's own layer: every Weld row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
907
+ "notes": "Weld County, Colorado (northern Colorado (Greeley, Evans, Windsor); FIPS 08123) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Weld' to scope to Weld County; the stored countyFips value is '123' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Weld' counts 163,491 rows, owner populated on 99%, situs address on 81% and owner mailing address on 99%, and an owner-name SMITH search matches 825 rows. This is a state roll-up, not the county's own layer: every Weld row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
908
908
  "addedAt": "2026-10-10"
909
909
  },
910
910
  {
@@ -1005,7 +1005,7 @@
1005
1005
  "url": "https://gis.colorado.gov/",
1006
1006
  "email": null
1007
1007
  },
1008
- "notes": "Mesa County, Colorado (the Western Slope (Grand Junction, Fruita, Palisade); FIPS 08077) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Mesa' to scope to Mesa County; the stored countyFips value is '77' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Mesa' counts 78,984 rows, owner populated on 99%, situs address on 92% and owner mailing address on 98%, and an owner-name SMITH search matches 556 rows. This is a state roll-up, not the county's own layer: every Mesa row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. 650 parcels carry the owner 'Confidential Owner', a county placeholder rather than a name (445 carry it in owner2, some repeated), and 649 of those 650 still show a situs address. The atlas withholds any row whose owner, mailing or situs reads as a redaction marker, so those parcels return no owner or address.",
1008
+ "notes": "Mesa County, Colorado (the Western Slope (Grand Junction, Fruita, Palisade); FIPS 08077) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Mesa' to scope to Mesa County; the stored countyFips value is '77' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Mesa' counts 78,984 rows, owner populated on 99%, situs address on 92% and owner mailing address on 98%, and an owner-name SMITH search matches 556 rows. This is a state roll-up, not the county's own layer: every Mesa row carries dateReceived 2026-03-27, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. 650 parcels carry the owner 'Confidential Owner', a county placeholder rather than a name (445 carry it in owner2, some repeated), and 649 of those 650 still show a situs address. The atlas withholds any row whose owner, mailing or situs reads as a redaction marker, so those parcels return no owner or address. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
1009
1009
  "addedAt": "2026-10-10"
1010
1010
  },
1011
1011
  {
@@ -1106,7 +1106,7 @@
1106
1106
  "url": "https://gis.colorado.gov/",
1107
1107
  "email": null
1108
1108
  },
1109
- "notes": "Park County, Colorado (the South Park basin (Fairplay, Bailey, Alma); FIPS 08093) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Park' to scope to Park County; the stored countyFips value is '093' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Park' counts 43,241 rows, owner populated on 99%, situs address on 85% and owner mailing address on 99%, and an owner-name SMITH search matches 289 rows. This is a state roll-up, not the county's own layer: every Park row carries dateReceived 2026-05-19, the day the state loaded the county's data, so ownership can trail the Assessor's live roll.",
1109
+ "notes": "Park County, Colorado (the South Park basin (Fairplay, Bailey, Alma); FIPS 08093) is served by the Colorado OIT statewide parcel composite, Colorado_Public_Parcels FeatureServer/0. Filter countyName='Park' to scope to Park County; the stored countyFips value is '093' (the layer keeps a county-only code, not the 5-digit FIPS). Same schema and endpoint as El Paso and Jefferson counties. Verified 2026-10-10 with an Origin: https://urbankitstudio.com header: countyName='Park' counts 43,241 rows, owner populated on 99%, situs address on 85% and owner mailing address on 99%, and an owner-name SMITH search matches 289 rows. This is a state roll-up, not the county's own layer: every Park row carries dateReceived 2026-05-19, the day the state loaded the county's data, so ownership can trail the Assessor's live roll. Credit: State of Colorado Public parcels were accessed on 2026-10-17 from https://gis.colorado.gov/public/rest/services/Address_and_Parcel (the attribution statement the State's service copyright text names as sufficient).",
1110
1110
  "addedAt": "2026-10-10"
1111
1111
  }
1112
1112
  ]
@@ -46,7 +46,7 @@
46
46
  "url": "https://opendata.dc.gov/datasets/DCGIS::common-ownership-lots",
47
47
  "email": null
48
48
  },
49
- "notes": "The District of Columbia is one county-equivalent (FIPS 11001) with no counties inside it. Layer 40, Owner Polygons (Common Ownership Layer), is the District's general ownership layer: 137,400 lot polygons merged from the Record, Tax, Parcel, Reservation and Air Rights lot layers and regenerated daily from the Office of Tax and Revenue's Integrated Tax System Public Extract (ITSPE). Layers 49 (District Land) and 50 (Federal Land) on the same service are narrower views of it. The parcel ID is the SSL (square, suffix, lot), written either as 'SQUARE SUFFIX LOT' (e.g. '1929 7056') or as 'PAR NNNNNNNN' for Parcel-type lots; both answer an SSL LIKE prefix search. The owner mailing address (ADDRESS1, ADDRESS2, CITYSTZIP) is separate from the premise address (PREMISEADD). Verified 2026-09-26: OWNERNAME LIKE 'SMITH%' returns 939 lots, and a PREMISEADD search returns individual homeowners alongside institutions.\n\nCoverage: the layer maps land, one polygon per lot. A condominium building is a single lot on it, and 3,921 of its 4,142 condominium lots carry no owner name, so an owner search finds lot owners, not unit owners. The tax extract published on the same service lists 221,622 records; unit-level condominium data sits in separate tables there, which this layer does not join. The service's ArcGIS Online item (Common Ownership Lots, item 1f6708b1f3774306bef2fa81e612a725, owner DCGISopendata) licenses the data under Creative Commons Attribution 4.0 International, so reuse credits the District of Columbia; the District's open-data terms apply CC0 only where no other license is noted, and this item notes one. OTR's Real Property Public Extract is a different product: a bulk file restricted to mortgage companies."
49
+ "notes": "The District of Columbia is one county-equivalent (FIPS 11001) with no counties inside it. Layer 40, Owner Polygons (Common Ownership Layer), is the District's general ownership layer: 137,400 lot polygons merged from the Record, Tax, Parcel, Reservation and Air Rights lot layers and regenerated daily from the Office of Tax and Revenue's Integrated Tax System Public Extract (ITSPE). Layers 49 (District Land) and 50 (Federal Land) on the same service are narrower views of it. The parcel ID is the SSL (square, suffix, lot), written either as 'SQUARE SUFFIX LOT' (e.g. '1929 7056') or as 'PAR NNNNNNNN' for Parcel-type lots; both answer an SSL LIKE prefix search. The owner mailing address (ADDRESS1, ADDRESS2, CITYSTZIP) is separate from the premise address (PREMISEADD). Verified 2026-09-26: OWNERNAME LIKE 'SMITH%' returns 939 lots, and a PREMISEADD search returns individual homeowners alongside institutions.\n\nCoverage: the layer maps land, one polygon per lot. A condominium building is a single lot on it, and 3,921 of its 4,142 condominium lots carry no owner name, so an owner search finds lot owners, not unit owners. The tax extract published on the same service lists 221,622 records; unit-level condominium data sits in separate tables there, which this layer does not join. The service's ArcGIS Online item (Common Ownership Lots, item 1f6708b1f3774306bef2fa81e612a725, owner DCGISopendata) licenses the data under Creative Commons Attribution 4.0 International, so reuse credits the District of Columbia; the District's open-data terms apply CC0 only where no other license is noted, and this item notes one. OTR's Real Property Public Extract is a different product: a bulk file restricted to mortgage companies. Credit: District of Columbia, under Creative Commons Attribution 4.0 International (https://creativecommons.org/licenses/by/4.0/)."
50
50
  }
51
51
  ]
52
52
  }
package/data/index.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "version": "0.3.0",
3
- "lastUpdated": "2026-10-14",
3
+ "lastUpdated": "2026-10-17",
4
4
  "totals": {
5
5
  "states": 51,
6
- "counties": 395,
7
- "endpoints": 413,
8
- "countiesWithEndpoint": 386,
6
+ "counties": 479,
7
+ "endpoints": 494,
8
+ "countiesWithEndpoint": 467,
9
9
  "countiesUnprobeable": 1
10
10
  },
11
11
  "states": [
@@ -214,7 +214,7 @@
214
214
  "name": "Missouri",
215
215
  "abbrev": "MO",
216
216
  "countyCount": 4,
217
- "endpointCount": 4,
217
+ "endpointCount": 3,
218
218
  "populated": true
219
219
  },
220
220
  {
@@ -277,8 +277,8 @@
277
277
  "slug": "north-carolina",
278
278
  "name": "North Carolina",
279
279
  "abbrev": "NC",
280
- "countyCount": 15,
281
- "endpointCount": 15,
280
+ "countyCount": 98,
281
+ "endpointCount": 98,
282
282
  "populated": true
283
283
  },
284
284
  {
@@ -293,7 +293,7 @@
293
293
  "slug": "ohio",
294
294
  "name": "Ohio",
295
295
  "abbrev": "OH",
296
- "countyCount": 8,
296
+ "countyCount": 9,
297
297
  "endpointCount": 8,
298
298
  "populated": true
299
299
  },
@@ -350,7 +350,7 @@
350
350
  "name": "Tennessee",
351
351
  "abbrev": "TN",
352
352
  "countyCount": 5,
353
- "endpointCount": 5,
353
+ "endpointCount": 4,
354
354
  "populated": true
355
355
  },
356
356
  {
@@ -2,7 +2,7 @@
2
2
  "stateSlug": "kentucky",
3
3
  "stateName": "Kentucky",
4
4
  "stateAbbrev": "KY",
5
- "lastUpdated": "2026-10-12",
5
+ "lastUpdated": "2026-10-17",
6
6
  "counties": [
7
7
  {
8
8
  "id": "ky-fayette",
@@ -15,69 +15,25 @@
15
15
  "hasPublicRest": true,
16
16
  "endpoints": [
17
17
  {
18
- "url": "https://services.arcgis.com/f4rR7WnIfGBdVYFd/arcgis/rest/services/Tax_Parcels/FeatureServer/0",
18
+ "url": "https://services1.arcgis.com/Mg7DLdfYcSWIaDnu/arcgis/rest/services/Parcel/FeatureServer/0",
19
19
  "serviceType": "FeatureServer",
20
20
  "layerIndex": 0,
21
- "layerName": "Tax_Parcels",
21
+ "layerName": "Parcel",
22
22
  "supportsQuery": true,
23
- "corsEnabled": null,
23
+ "corsEnabled": true,
24
24
  "searchFields": [
25
- {
26
- "name": "PAN",
27
- "label": "Parcel Account Number (Parcel ID)",
28
- "searchable": true
29
- },
30
- {
31
- "name": "Owner1",
32
- "label": "Owner Name 1",
33
- "searchable": true
34
- },
35
- {
36
- "name": "Owner2",
37
- "label": "Owner Name 2",
38
- "searchable": false
39
- },
40
- {
41
- "name": "Owner3",
42
- "label": "Owner Name 3",
43
- "searchable": false
44
- },
45
- {
46
- "name": "Mailing_Address",
47
- "label": "Mailing Address",
48
- "searchable": false
49
- },
50
- {
51
- "name": "PARCEL_SUB",
52
- "label": "Parcel Sub-Identifier",
53
- "searchable": false
54
- },
55
- {
56
- "name": "PARCEL_BLOCK",
57
- "label": "Block",
58
- "searchable": false
59
- },
60
- {
61
- "name": "PARCEL_LOT",
62
- "label": "Lot",
63
- "searchable": false
64
- },
65
- {
66
- "name": "PARCEL_TYPE",
67
- "label": "Parcel Type",
68
- "searchable": false
69
- },
70
- {
71
- "name": "RecordDate",
72
- "label": "Record Date",
73
- "searchable": false
74
- }
25
+ { "name": "PVANUM", "label": "PVA Parcel Number", "searchable": true },
26
+ { "name": "ADDRESS", "label": "Site Address", "searchable": true },
27
+ { "name": "UNIT", "label": "Unit", "searchable": false },
28
+ { "name": "CLASS", "label": "Property Class Code", "searchable": false },
29
+ { "name": "PVA_ACRE", "label": "PVA Acres", "searchable": false }
75
30
  ],
76
- "sampleQuery": "https://services.arcgis.com/f4rR7WnIfGBdVYFd/arcgis/rest/services/Tax_Parcels/FeatureServer/0/query?where=UPPER(Owner1)+LIKE+UPPER('%25SMITH%25')&outFields=PAN,Owner1,Mailing_Address,PARCEL_TYPE&returnGeometry=false&f=json&resultRecordCount=10",
31
+ "maxRecordCount": 2000,
32
+ "sampleQuery": "https://services1.arcgis.com/Mg7DLdfYcSWIaDnu/arcgis/rest/services/Parcel/FeatureServer/0/query?where=PVANUM+%3D+%2720636950%27&outFields=PVANUM,ADDRESS,UNIT,CLASS,PVA_ACRE&returnGeometry=false&f=json",
77
33
  "license": "public",
78
- "licenseUrl": "https://data-lfucg.hub.arcgis.com/",
34
+ "licenseUrl": "https://www.arcgis.com/home/item.html?id=e4a525d8772741468205e82fc173db22",
79
35
  "status": "live",
80
- "lastVerified": "2026-05-15",
36
+ "lastVerified": "2026-10-17",
81
37
  "verifiedBy": "manual"
82
38
  }
83
39
  ],
@@ -86,7 +42,17 @@
86
42
  "url": "https://data-lfucg.hub.arcgis.com/",
87
43
  "email": null
88
44
  },
89
- "notes": "Fayette County (Lexington, pop. 322,000; consolidated city-county) Tax Parcels FeatureServer hosted on ArcGIS Online (LFUCG org). Fayette County is a merged urban county government, the Lexington-Fayette Urban County Government (LFUCG). Fields confirmed: PAN (numeric parcel account number), PARCEL_SUB, PARCEL_BLOCK, PARCEL_LOT, LRM_GEOM_DOC, RecordDate, LRM_GEOM_DOC_AREA/UNITS, PARCEL_TYPE, PARCEL_POLY_NAME, Owner1/2/3, Mailing_Address. Note: PARCEL_POLY_NAME may be null; PAN is the numeric parcel identifier. Mailing_Address is a single concatenated field. Verified 2026-05-15: Owner1 SMITH returns Lexington-area addresses (e.g., '3875 GEIST RD STE E469', '4951 E JOHN JOHN CT'). A separate Parcels FeatureServer exists at the same org but has no owner fields, Tax_Parcels is the correct service. Note: distinct from Jefferson County KY (Louisville, FIPS 21111) already in atlas."
45
+ "notes": "Lexington-Fayette Urban County Government (LFUCG) publishes Fayette County's parcels on its own ArcGIS Online organization: the Parcel FeatureServer (item e4a525d8772741468205e82fc173db22, credited to LFUCG GIS, LFUCG Addressing, LFUCG Planning and the Fayette County Property Valuation Administrator) holds 114,433 parcels inside the county (extent about 84.66 to 84.28 W, 37.84 to 38.21 N). It publishes no owner name and no owner mailing address. PVANUM is the PVA parcel number, 8 characters on 114,280 rows and blank on 14; ADDRESS is the full site address (blank on 17), with its parts in NUM1, NUM2, DIR, NAME and TYPE; UNIT is filled on 6,795 rows; CLASS is a one-letter property class (R on 101,590 rows, C on 6,156, blank on 301); PVA_ACRE is the PVA acreage. The server answers any origin (Access-Control-Allow-Origin: *), pages results and returns up to 2,000 rows per request. The item's licence field is LFUCG's Terms of Use: the data is provided \"as is\" and used at the user's sole risk (section V.B), and section VI.B reads: \"To the fullest extent permitted by law, You shall indemnify and save harmless the LFUCG, from any claim, loss, damage, injury or liability of any kind, nature and description (including, without limitation, incidental and consequential damages, court costs, attorney’s fees and costs of investigation), that arise directly or indirectly, in whole or in part, from Your use of the Data, including without limitation Your use of the Data in a Derivative Work. In addition to Your obligation to indemnify the LFUCG, You specifically acknowledge and agree that You have an immediate and independent obligation to defend the LFUCG from any claim which actually or potentially falls within this indemnification provision, even if the allegations are or may be groundless, false or fraudulent, which obligation arises at the time such claim is tendered to You by LFUCG and continues at all times thereafter.\" LFUCG's open data hub is data-lfucg.hub.arcgis.com. Until 2026-10-17 this record pointed at services.arcgis.com/f4rR7WnIfGBdVYFd Tax_Parcels, which belongs to the Fairbanks North Star Borough, Alaska: 63,924 parcels around 64.24 to 65.44 N, 143.85 to 148.73 W.",
46
+ "capabilityOverrides": {
47
+ "owner_name": {
48
+ "status": "not_published",
49
+ "basis": {
50
+ "type": "endpoint_schema",
51
+ "note": "LFUCG's public parcel layer for Fayette County carries the PVA parcel number, site address, unit, property class and acreage only; it has no owner-name column.",
52
+ "sourceUrl": "https://services1.arcgis.com/Mg7DLdfYcSWIaDnu/arcgis/rest/services/Parcel/FeatureServer/0"
53
+ }
54
+ }
55
+ }
90
56
  },
91
57
  {
92
58
  "id": "ky-boone",
@@ -81,7 +81,7 @@
81
81
  "url": "https://www.montgomerycountymd.gov/gis/",
82
82
  "email": null
83
83
  },
84
- "notes": "Montgomery County is Maryland's most populous county (pop. 1.06 million; county seat Rockville) and one of the wealthiest in the US. The MCAtlas_Property_Points FeatureServer on mcmaps.org (mcmaps.org/server11) is the county's ArcGIS Server backing the MCAtlas web viewer; it exposes 97 fields as point geometry. Live query confirmed 351,703 parcels. Owner-name search uses UPPER() LIKE on OWNERS_NAME. Key fields: TAX_NO (Maryland 8-digit tax account number), OWNERS_NAME, OWNERS_NAME2, OWNERS_ADDR1/ADDR2/ADDR3, OWNERS_CITY/STATE/ZIP (full mailing address), PREMISE_ADDR_HOUSENO/STREET/STREET_TYPE/CITY/ZIP (situs address components), LAND_ASSMT, IMPROV_ASSMT, LEGAL_DESC, TRANSFER_DATE, SALES_PRICE, YEAR_BUILT, LANDUSE_CODE. The county uses Maryland SDAT (State Department of Assessments and Taxation) as the authoritative property record; mcmaps.org mirrors a subset of that data. Note: property points are centroid-located, not parcel polygons. For polygon geometry, Maryland's statewide parcel boundary layer is at geodata.md.gov/imap/rest/services/PlanningCadastre/MD_ParcelBoundaries/MapServer but does not expose owner data directly.",
84
+ "notes": "Montgomery County is Maryland's most populous county (pop. 1.06 million; county seat Rockville) and one of the wealthiest in the US. The MCAtlas_Property_Points FeatureServer on mcmaps.org (mcmaps.org/server11) is the county's ArcGIS Server backing the MCAtlas web viewer; it exposes 97 fields as point geometry. Live query confirmed 351,703 parcels. Owner-name search uses UPPER() LIKE on OWNERS_NAME. Key fields: TAX_NO (Maryland 8-digit tax account number), OWNERS_NAME, OWNERS_NAME2, OWNERS_ADDR1/ADDR2/ADDR3, OWNERS_CITY/STATE/ZIP (full mailing address), PREMISE_ADDR_HOUSENO/STREET/STREET_TYPE/CITY/ZIP (situs address components), LAND_ASSMT, IMPROV_ASSMT, LEGAL_DESC, TRANSFER_DATE, SALES_PRICE, YEAR_BUILT, LANDUSE_CODE. The county uses Maryland SDAT (State Department of Assessments and Taxation) as the authoritative property record; mcmaps.org mirrors a subset of that data. Note: property points are centroid-located, not parcel polygons. For polygon geometry, Maryland's statewide parcel boundary layer is at geodata.md.gov/imap/rest/services/PlanningCadastre/MD_ParcelBoundaries/MapServer but does not expose owner data directly. The layer is the county's own, not a statewide one: on 2026-10-17, 351,930 of its 351,954 points fell inside the county's bounding box, and the other 24 shared one placeholder coordinate in West Virginia (about 37.58 N, 81.53 W) while their situs cities are Montgomery County towns, which is why the layer's extent reads about 4.6 degrees wide. Credit: Montgomery County Planning Department (M-NCPPC). The service's ArcGIS item (MCAtlas_Property_Points, 32172f03689f47818a7fbfb2d2a34adc) says: \"You can copy, modify, distribute, and perform analysis on the data, even for commercial purposes, all without asking permission, but please provide attribution to the Montgomery County Planning Department.\"",
85
85
  "ownerFieldNote": null,
86
86
  "capabilityOverrides": null
87
87
  },
@@ -177,7 +177,7 @@
177
177
  "url": "https://www.princegeorgescountymd.gov/665/Geographic-Information-Systems-GIS",
178
178
  "email": null
179
179
  },
180
- "notes": "Prince George's County is Maryland's second-most populous county (pop. 910,000; county seat Upper Marlboro). The Property_Flattened MapServer on gis.princegeorgescountymd.gov (ArcGIS Server 11.5) is the county's canonical public property layer with 112 fields and 352,791 parcels. Live query confirmed OWNER_NAME exposure. Key fields: ACCOUNT (county account number, 7 digits), PROPERTY_ID (prefixed as '12' + ACCOUNT for the full 9-digit SDAT account number), OWNER_NAME, ICO_NAME (in-care-of), HOUSE_NUMBER (zero-padded 6-digit, e.g. '002909'), STREET_NAME, STREET_TYPE, STREET_DIRECTION, MAIL_STREET/CITY/STATE/ZIP5 (owner mailing address), ASSESS_DIST (assessment district), LAND_AREA_ACRE, LAND_AREA_SQFT, LIBER, FOLIO, SUB_NAME, CONDO_UNIT_NUMBER, TAXMAPGRID. The situs address is split across HOUSE_NUMBER + STREET_NAME + STREET_TYPE. There is no single combined site address field on this layer. The county belongs to the M-NCPPC (Maryland-National Capital Park and Planning Commission) planning region and uses Maryland SDAT for the authoritative ownership record. Prince George's County borders DC and contains the University of Maryland (College Park) and Joint Base Andrews. 2026-10-03: the registered endpoint moved from the county MapServer to the Planning Department's hosted ArcGIS Online copy of the same layer (Property_Flattened_Py FeatureServer on services1.arcgis.com, owner Planning_PGCO_MD, CORS open, maxRecordCount 2000, 353,381 parcels). The reason is a county-side defect, not a schema change: gis.princegeorgescountymd.gov is load-balanced and one backend node lacks the layers, so about every second request to any service on the host (Property_Flattened, Property_Centroids, Property, AddressPoints) answers HTTP 200 with a Layer not found error body, metadata and queries alike, whatever the where clause. The liveness cron does not retry an HTTP 200 error body, so the county flapped between live and degraded. The hosted copy has the same field names (every declared searchField present, plus MAIL_STATE) and returned the same first row as the county host on its good turns, with 18 of 18 probes answering. The old host is deliberately not kept as a second endpoint, because the cron grades a county by its worst endpoint. Caveat: the hosted copy is a periodic refresh by the Planning Department (stamped Updated 20260923), so its freshness is days, not minutes; switch back once the county host answers consistently."
180
+ "notes": "Prince George's County is Maryland's second-most populous county (pop. 910,000; county seat Upper Marlboro). The Property_Flattened MapServer on gis.princegeorgescountymd.gov (ArcGIS Server 11.5) is the county's canonical public property layer with 112 fields and 352,791 parcels. Live query confirmed OWNER_NAME exposure. Key fields: ACCOUNT (county account number, 7 digits), PROPERTY_ID (prefixed as '12' + ACCOUNT for the full 9-digit SDAT account number), OWNER_NAME, ICO_NAME (in-care-of), HOUSE_NUMBER (zero-padded 6-digit, e.g. '002909'), STREET_NAME, STREET_TYPE, STREET_DIRECTION, MAIL_STREET/CITY/STATE/ZIP5 (owner mailing address), ASSESS_DIST (assessment district), LAND_AREA_ACRE, LAND_AREA_SQFT, LIBER, FOLIO, SUB_NAME, CONDO_UNIT_NUMBER, TAXMAPGRID. The situs address is split across HOUSE_NUMBER + STREET_NAME + STREET_TYPE. There is no single combined site address field on this layer. The county belongs to the M-NCPPC (Maryland-National Capital Park and Planning Commission) planning region and uses Maryland SDAT for the authoritative ownership record. Prince George's County borders DC and contains the University of Maryland (College Park) and Joint Base Andrews. 2026-10-03: the registered endpoint moved from the county MapServer to the Planning Department's hosted ArcGIS Online copy of the same layer (Property_Flattened_Py FeatureServer on services1.arcgis.com, owner Planning_PGCO_MD, CORS open, maxRecordCount 2000, 353,381 parcels). The reason is a county-side defect, not a schema change: gis.princegeorgescountymd.gov is load-balanced and one backend node lacks the layers, so about every second request to any service on the host (Property_Flattened, Property_Centroids, Property, AddressPoints) answers HTTP 200 with a Layer not found error body, metadata and queries alike, whatever the where clause. The liveness cron does not retry an HTTP 200 error body, so the county flapped between live and degraded. The hosted copy has the same field names (every declared searchField present, plus MAIL_STATE) and returned the same first row as the county host on its good turns, with 18 of 18 probes answering. The old host is deliberately not kept as a second endpoint, because the cron grades a county by its worst endpoint. Caveat: the hosted copy is a periodic refresh by the Planning Department (stamped Updated 20260923), so its freshness is days, not minutes; switch back once the county host answers consistently. Credit: Prince George's County Planning Department (M-NCPPC). The Planning Department's open-data page (https://gisdata.pgplanning.org/opendata/) says: \"You can copy, modify, distribute, and perform analysis on the data, even for commercial purposes, all without asking permission, but please provide attribution to the Prince George's County Planning Department.\""
181
181
  },
182
182
  {
183
183
  "id": "md-baltimore",
@@ -2,7 +2,7 @@
2
2
  "stateSlug": "missouri",
3
3
  "stateName": "Missouri",
4
4
  "stateAbbrev": "MO",
5
- "lastUpdated": "2026-10-10",
5
+ "lastUpdated": "2026-10-17",
6
6
  "counties": [
7
7
  {
8
8
  "id": "mo-jackson",
@@ -12,44 +12,14 @@
12
12
  "county": "Jackson",
13
13
  "countySlug": "jackson-county",
14
14
  "countyFips": "29095",
15
- "hasPublicRest": true,
16
- "endpoints": [
17
- {
18
- "url": "https://gis.mijackson.org/countygis/rest/services/RealEstate/RealEstateParcels/FeatureServer/0",
19
- "serviceType": "FeatureServer",
20
- "layerIndex": 0,
21
- "layerName": "RealEstateParcels",
22
- "supportsQuery": true,
23
- "corsEnabled": null,
24
- "searchFields": [
25
- { "name": "PIN", "label": "Parcel Identification Number", "searchable": true },
26
- { "name": "OWNER", "label": "Owner Name", "searchable": true },
27
- { "name": "OWNER2", "label": "Owner Name 2", "searchable": false },
28
- { "name": "O_ADDRESS", "label": "Owner Address", "searchable": false },
29
- { "name": "O_CITY", "label": "Owner City", "searchable": false },
30
- { "name": "O_STATE", "label": "Owner State", "searchable": false },
31
- { "name": "O_ZIP", "label": "Owner ZIP", "searchable": false },
32
- { "name": "P_FULLADD", "label": "Property Full Address", "searchable": true },
33
- { "name": "P_CITY", "label": "Property City", "searchable": false },
34
- { "name": "P_STATE", "label": "Property State", "searchable": false },
35
- { "name": "P_ZIP", "label": "Property ZIP", "searchable": false },
36
- { "name": "P_ACREAGE", "label": "Acreage", "searchable": false },
37
- { "name": "LIBERPAGE", "label": "Liber/Page (deed reference)", "searchable": false }
38
- ],
39
- "sampleQuery": "https://gis.mijackson.org/countygis/rest/services/RealEstate/RealEstateParcels/FeatureServer/0/query?where=UPPER(OWNER)+LIKE+UPPER('%25SMITH%25')&outFields=PIN,OWNER,OWNER2,O_ADDRESS,O_CITY,P_FULLADD,P_CITY&returnGeometry=false&f=json&resultRecordCount=10",
40
- "license": "public",
41
- "licenseUrl": "https://gis.mijackson.org/",
42
- "status": "live",
43
- "lastVerified": "2026-06-20",
44
- "verifiedBy": "automated"
45
- }
46
- ],
15
+ "hasPublicRest": false,
16
+ "endpoints": [],
47
17
  "contact": {
48
- "department": "Jackson County GIS (Assessed Services Division)",
49
- "url": "https://jacksongov.org/residents/property-information",
18
+ "department": "Jackson County GIS Department",
19
+ "url": "https://jcgis.jacksongov.org/parcelviewer/",
50
20
  "email": null
51
21
  },
52
- "notes": "Jackson County MO (Kansas City metro; county seat Kansas City; FIPS 29095; pop. 715,000, largest county in MO) provides parcel data via gis.mijackson.org. The RealEstate/RealEstateParcels/FeatureServer/0 layer exposes 20 fields: PIN (parcel ID), LIBERPAGE, O_CITY, OWNER, OWNER2, O_STATE, O_ADDRESS, O_ZIP, P_CITY, P_FULLADD, P_STATE, P_ZIP, P_STATUS, P_ACREAGE, P_ASSMBOR1-4, P_HPERCENT. Owner search via UPPER(OWNER) LIKE works well. Verified 2026-06-20: SMITH returns Kansas City-area addresses. Jackson County MO includes Kansas City proper and inner suburbs (Independence, Lee's Summit, Blue Springs). Do not confuse with Jackson County in other states. The GIS portal is at gis.mijackson.org."
22
+ "notes": "No public ArcGIS REST layer with owner names was found for Jackson County, Missouri (Kansas City metro; FIPS 29095) as of 2026-10-17. The county's own current parcel layer, ParcelViewer/ParcelsAscendRelate FeatureServer layer 1 on jcgis.jacksongov.org, holds 311,163 parcels inside the county (extent about 94.61 to 94.11 W, 38.83 to 39.24 N) but carries ids only: parcel_id, the dashed parcel number in Name, PropertyID, and TCA and School code columns. It has no owner, situs or mailing column. The same service's Ascend_GisInfo table (layer 2) adds situs address, land use and values but no owner name, and it has no geometry. Owner names appear only on the county's PastYearParcels layers for 2017 to 2019, which are not current and are not used. The county's Parcel Viewer (jcgis.jacksongov.org/parcelviewer) shows parcels in the browser. Until 2026-10-17 this record pointed at gis.mijackson.org RealEstateParcels, which is Jackson County, Michigan: 78,038 parcels around 42.07 to 42.42 N, 84.13 to 84.72 W, with property state MI on 74,650 rows."
53
23
  },
54
24
  {
55
25
  "id": "mo-st-louis",