@urbankitstudio/atlas 0.6.34 → 0.6.36
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 +15 -5
- package/data/city-property/fort-worth.json +1 -1
- package/data/city-property/los-angeles.json +1 -1
- package/data/city-property/orlando.json +5 -3
- package/data/city-property/scottsdale.json +1 -1
- package/data/city-zoning/orlando.json +2 -1
- package/data/index.json +5 -5
- package/data/tennessee.json +56 -1
- package/dist/index.cjs +186 -31
- package/dist/index.d.cts +25 -5
- package/dist/index.d.ts +25 -5
- package/dist/index.js +186 -31
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -143,12 +143,22 @@ for (const ds of cityDatasets(dallas.slug, "permits")) {
|
|
|
143
143
|
Three lookup modes appear in `dataset.lookup`. `address` is a case-insensitive substring match
|
|
144
144
|
on `dataset.addressField` (the common case); the street is escaped for the provider's SQL by
|
|
145
145
|
`buildCityQuery`, which is why an address lookup carries no paste-in template, and the LIKE
|
|
146
|
-
wildcards `%` and `_` stay active as they do on the site.
|
|
146
|
+
wildcards `%` and `_` stay active as they do on the site. A dataset that sets `houseNumberSpaceRuns`
|
|
147
|
+
(only Orlando's, whose tables store two or three spaces after the house number: `4274 TATUM ST`)
|
|
148
|
+
also matches the space after a leading house number as a run of one to four spaces, or the spacing
|
|
149
|
+
as typed, and nothing else, so `4274 Tatum St` finds them but not `4274 OLD TATUM ST`; every other
|
|
150
|
+
dataset matches the spacing as typed. When `dataset.addressParts` lists more
|
|
147
151
|
columns than `addressField` (Dallas violations store `str_num`, `str_prefix`, `str_nam`,
|
|
148
152
|
`str_suffix`), the name column holds the street name alone, so `buildCityQuery` matches the
|
|
149
153
|
derived name: the typed house number comes off, then a leading directional when the table has a
|
|
150
|
-
direction column, then one trailing street type when it has a type column
|
|
151
|
-
|
|
154
|
+
direction column, then one trailing street type when it has a type column (a strip that would leave
|
|
155
|
+
a lone letter, no letter or digit, or only a direction or type word a leading directional exposed,
|
|
156
|
+
as `N St` would become `St`, is not applied past the house number: `100 N St` sends `N St`, `100 %` and `100 E` are sent as typed,
|
|
157
|
+
while `100 Court St` sends `Court`, and `2600 South Blvd` sends `South` where the table has a type column); `streetForDataset`
|
|
158
|
+
returns that name, and every row on the street comes back for you to filter by house number. A dataset
|
|
159
|
+
that keeps the house number in its own column (`streetNumberField`: Los Angeles violations, Fort Worth
|
|
160
|
+
permits, Scottsdale violations) matches the number on that column and the name on `addressField`; a street
|
|
161
|
+
typed without a number gets the same trimming, so `Funtier Ct` is matched as `Funtier` and `South St` as `South`. `location` means the docket is published on parcel
|
|
152
162
|
shapes with no address column (Denver, Charlotte): geocode the address yourself and put the
|
|
153
163
|
WGS84 point into `queryTemplate` where `{LON},{LAT}` stands. `parcel` (New York) is keyed by
|
|
154
164
|
parcel id; `queryNote` spells out the two joins. `scopeWhere`, when present, is part of the
|
|
@@ -235,9 +245,9 @@ read `addedAt` and fall back to the oldest `lastVerified` only when it is absent
|
|
|
235
245
|
|
|
236
246
|
## Coverage today
|
|
237
247
|
|
|
238
|
-
The atlas bundles **
|
|
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.
|
|
239
249
|
|
|
240
|
-
Every state has at least one county on record, and
|
|
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.
|
|
241
251
|
|
|
242
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.
|
|
243
253
|
|
|
@@ -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
|
|
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
|
|
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": {
|
|
@@ -10,13 +10,14 @@
|
|
|
10
10
|
"datasets": {
|
|
11
11
|
"violations": {
|
|
12
12
|
"kind": "violations",
|
|
13
|
+
"houseNumberSpaceRuns": 4,
|
|
13
14
|
"tabLabel": "Code Violations",
|
|
14
15
|
"type": "socrata",
|
|
15
16
|
"url": "https://data.cityoforlando.net/resource/k6e8-nw6w.json",
|
|
16
17
|
"orderField": "casedt",
|
|
17
18
|
"where": "case_type in ('Housing','Lot','Zoning','Abatement','Commercial')",
|
|
18
19
|
"latestRecordDate": "2026-09-23",
|
|
19
|
-
"coverage": "Orlando code-enforcement cases of the housing, lot, zoning, abatement and commercial types, about 147,000 opened 1994 to present. Business-tax, ticket, sign and other case types in the same table are left out. Lags the calendar: on 2026-10-14 the newest case in the table was opened 2026-09-23.
|
|
20
|
+
"coverage": "Orlando code-enforcement cases of the housing, lot, zoning, abatement and commercial types, about 147,000 opened 1994 to present. Business-tax, ticket, sign and other case types in the same table are left out. Lags the calendar: on 2026-10-14 the newest case in the table was opened 2026-09-23. 99,433 of the 146,669 case addresses carry two spaces after the house number ('4274 TATUM ST'); the search matches that gap as a run of one to four spaces, or the spacing as typed, and nothing else, so '4274 Tatum St' finds the case.",
|
|
20
21
|
"recordLabel": "Case",
|
|
21
22
|
"openedLabel": "Opened",
|
|
22
23
|
"closedLabel": "Resolved",
|
|
@@ -31,13 +32,14 @@
|
|
|
31
32
|
},
|
|
32
33
|
"permits": {
|
|
33
34
|
"kind": "permits",
|
|
35
|
+
"houseNumberSpaceRuns": 4,
|
|
34
36
|
"tabLabel": "Building Permits",
|
|
35
37
|
"type": "socrata",
|
|
36
38
|
"url": "https://data.cityoforlando.net/resource/ryhf-m453.json",
|
|
37
39
|
"orderField": "processed_date",
|
|
38
40
|
"where": "processed_date IS NOT NULL",
|
|
39
41
|
"latestRecordDate": "2026-09-23",
|
|
40
|
-
"coverage": "Orlando permit applications of every type (building, electrical, plumbing, mechanical, engineering, fire and more), about 1.1 million on record. Lags the calendar: on 2026-10-14 the newest application in the table was processed 2026-09-23. About 5% of permit addresses (
|
|
42
|
+
"coverage": "Orlando permit applications of every type (building, electrical, plumbing, mechanical, engineering, fire and more), about 1.1 million on record. Lags the calendar: on 2026-10-14 the newest application in the table was processed 2026-09-23. About 5% of permit addresses (55,657 of 1,105,323) carry two or three spaces after the house number; the search matches that gap as a run of one to four spaces, or the spacing as typed, and nothing else, so a typed full address finds them.",
|
|
41
43
|
"recordLabel": "Permit",
|
|
42
44
|
"openedLabel": "Processed",
|
|
43
45
|
"closedLabel": "Finaled",
|
|
@@ -58,6 +60,6 @@
|
|
|
58
60
|
"url": "https://data.cityoforlando.net/",
|
|
59
61
|
"license": "Public record (City of Orlando)",
|
|
60
62
|
"portalLabel": "Orlando Open Data (Socrata)",
|
|
61
|
-
"currentRecordsNote": "Code-enforcement cases and permit applications are both published on the City of Orlando's open-data portal. On 2026-10-14 the newest record in both tables was dated 2026-09-23, although the portal reported a same-day refresh. Most code-case addresses carry two spaces after the house number (\"4274 TATUM ST\")
|
|
63
|
+
"currentRecordsNote": "Code-enforcement cases and permit applications are both published on the City of Orlando's open-data portal. On 2026-10-14 the newest record in both tables was dated 2026-09-23, although the portal reported a same-day refresh. Most code-case addresses carry two spaces after the house number (\"4274 TATUM ST\"); the search matches that gap as a run of one to four spaces, or the spacing as typed, and nothing else, so a full address (\"4274 Tatum St\") finds them."
|
|
62
64
|
}
|
|
63
65
|
}
|
|
@@ -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
|
|
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",
|
|
@@ -11,6 +11,7 @@
|
|
|
11
11
|
"type": "socrata",
|
|
12
12
|
"url": "https://data.cityoforlando.net/resource/bhxy-4rji.json",
|
|
13
13
|
"orderField": "application_date",
|
|
14
|
+
"houseNumberSpaceRuns": 4,
|
|
14
15
|
"where": "application_description='Zoning' AND application_date IS NOT NULL",
|
|
15
16
|
"latestRecordDate": "2026-09-18",
|
|
16
17
|
"fields": {
|
|
@@ -31,7 +32,7 @@
|
|
|
31
32
|
"url": "https://data.cityoforlando.net/",
|
|
32
33
|
"license": "Public record (City of Orlando)",
|
|
33
34
|
"portalLabel": "Orlando Open Data (Socrata)",
|
|
34
|
-
"currentRecordsNote": "Zoning cases come from the city's Planning Applications dataset, scoped to the Zoning application type (about 450 cases since 2002; the same table also holds annexations, variances and master plans). Existing and proposed zoning appear only inside each case's comments, not as columns, and the status is Open or Closed without saying approved or denied. About half the case addresses carry two spaces after the house number, so a
|
|
35
|
+
"currentRecordsNote": "Zoning cases come from the city's Planning Applications dataset, scoped to the Zoning application type (about 450 cases since 2002; the same table also holds annexations, variances and master plans). Existing and proposed zoning appear only inside each case's comments, not as columns, and the status is Open or Closed without saying approved or denied. About half the case addresses (221 of 407) carry two or three spaces after the house number; the search matches that gap as a run of one to four spaces, or the spacing as typed, and nothing else, so a full address finds them as well as a street name alone does.",
|
|
35
36
|
"datasetUrl": "https://data.cityoforlando.net/d/bhxy-4rji"
|
|
36
37
|
}
|
|
37
38
|
}
|
package/data/index.json
CHANGED
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
"lastUpdated": "2026-10-14",
|
|
4
4
|
"totals": {
|
|
5
5
|
"states": 51,
|
|
6
|
-
"counties":
|
|
7
|
-
"endpoints":
|
|
8
|
-
"countiesWithEndpoint":
|
|
6
|
+
"counties": 395,
|
|
7
|
+
"endpoints": 413,
|
|
8
|
+
"countiesWithEndpoint": 386,
|
|
9
9
|
"countiesUnprobeable": 1
|
|
10
10
|
},
|
|
11
11
|
"states": [
|
|
@@ -349,8 +349,8 @@
|
|
|
349
349
|
"slug": "tennessee",
|
|
350
350
|
"name": "Tennessee",
|
|
351
351
|
"abbrev": "TN",
|
|
352
|
-
"countyCount":
|
|
353
|
-
"endpointCount":
|
|
352
|
+
"countyCount": 5,
|
|
353
|
+
"endpointCount": 5,
|
|
354
354
|
"populated": true
|
|
355
355
|
},
|
|
356
356
|
{
|
package/data/tennessee.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"stateSlug": "tennessee",
|
|
3
3
|
"stateName": "Tennessee",
|
|
4
4
|
"stateAbbrev": "TN",
|
|
5
|
-
"lastUpdated": "2026-10-
|
|
5
|
+
"lastUpdated": "2026-10-14",
|
|
6
6
|
"counties": [
|
|
7
7
|
{
|
|
8
8
|
"id": "tn-davidson",
|
|
@@ -235,6 +235,61 @@
|
|
|
235
235
|
"email": null
|
|
236
236
|
},
|
|
237
237
|
"notes": "Sullivan County, Tennessee (county seat Blountville; Kingsport and Bristol) has no county-run public REST parcel layer with owner names. Its parcels are carried on the City of Johnson City's regional ParcelPublishing/TaxParcels MapServer layer 0 (Tax Parcels), which also holds Washington, Carter, Unicoi and neighbouring counties. Filter with COUNTYNAME='Sullivan County' (78,958 of the layer's 183,538 rows on 2026-10-03); the plain value 'Sullivan' matches nothing. About 313 Sullivan parcels (GISLINK starting 082) carry a NULL or different COUNTYNAME and fall outside this scope, roughly 0.4 percent; COUNTY_ID=82 catches them but admits 314 rows from outside the county, so the name scope stays. The owner is OWNER (with OWNER2); the parcel ID is GISLINK (e.g. 082029B A 01600) with ID as the display form (029B A 016.00), and PARID is NULL for Sullivan rows. ADDRESS stores the street name first and the house number last (BRENTWOOD DR 377), so search on a street word: a number-first LIKE ('%377 BRENTWOOD DR%') returns nothing, and only 647 of 78,737 Sullivan addresses start with a digit, so the free tools' address auto-lookup will miss most Sullivan addresses until they retry number-last. The owner mailing address is MAILADDR with MAILCITY, STATE and ZIP. CARDURL links each parcel to the state's TPAD property card. CORS reflects the request Origin (Access-Control-Allow-Origin echoed back, credentials true); a request without an Origin gets no CORS header. maxRecordCount is 2000. LICENCE: RESTRICTED. The ArcGIS item's licence text reads: \"Read access only for all city staff. Delivered products are not to be resold by the purchaser for any reason and may not be reproduced without the written permission of the staff of the Johnson City GIS Division.\" The item and the REST endpoint are public, but the terms restrict resale and reproduction, so the atlas records only the query URL, stores no copy of the layer beyond the short-lived server cache every live query passes through, and serves this county by live query only; Leo reviewed and accepted that exposure on 2026-10-03. The data was last refreshed in October 2025. Sullivan County's own SULLIVAN service on ArcGIS Online has no owner field, and Tennessee publishes no statewide parcel REST layer. Verified live 2026-10-03: owner SMITH returned rows (first SMITH BETTY TRUSTEE, GISLINK 082029B A 01600, BRENTWOOD DR 377, mailing 377 BRENTWOOD DRIVE KINGSPORT)."
|
|
238
|
+
},
|
|
239
|
+
{
|
|
240
|
+
"id": "tn-montgomery",
|
|
241
|
+
"state": "TN",
|
|
242
|
+
"stateName": "Tennessee",
|
|
243
|
+
"stateSlug": "tennessee",
|
|
244
|
+
"county": "Montgomery",
|
|
245
|
+
"countySlug": "montgomery-county",
|
|
246
|
+
"countyFips": "47125",
|
|
247
|
+
"hasPublicRest": true,
|
|
248
|
+
"endpoints": [
|
|
249
|
+
{
|
|
250
|
+
"url": "https://gis.montgomerytn.gov/gisserver/rest/services/PublicParcels/MapServer/0",
|
|
251
|
+
"serviceType": "MapServer",
|
|
252
|
+
"layerIndex": 0,
|
|
253
|
+
"layerName": "PublicParcels",
|
|
254
|
+
"supportsQuery": true,
|
|
255
|
+
"corsEnabled": true,
|
|
256
|
+
"searchFields": [
|
|
257
|
+
{
|
|
258
|
+
"name": "ParcelNo",
|
|
259
|
+
"label": "Parcel Number (e.g. 066E A 00600 000)",
|
|
260
|
+
"searchable": true
|
|
261
|
+
},
|
|
262
|
+
{
|
|
263
|
+
"name": "GISLINK",
|
|
264
|
+
"label": "GIS Link (Parcel ID, e.g. 063066E A 00600)",
|
|
265
|
+
"searchable": true
|
|
266
|
+
},
|
|
267
|
+
{
|
|
268
|
+
"name": "PropertyAddress",
|
|
269
|
+
"label": "Situs Address",
|
|
270
|
+
"searchable": true
|
|
271
|
+
},
|
|
272
|
+
{
|
|
273
|
+
"name": "PropertyCity",
|
|
274
|
+
"label": "Situs City",
|
|
275
|
+
"searchable": false
|
|
276
|
+
}
|
|
277
|
+
],
|
|
278
|
+
"sampleQuery": "https://gis.montgomerytn.gov/gisserver/rest/services/PublicParcels/MapServer/0/query?where=UPPER(PropertyAddress)+LIKE+'%25MAIN%25'&outFields=ParcelNo,GISLINK,PropertyAddress,PropertyCity&returnGeometry=false&f=json",
|
|
279
|
+
"license": "unknown",
|
|
280
|
+
"licenseUrl": "http://montgomerytn.gov/assessor/public-parcels",
|
|
281
|
+
"status": "live",
|
|
282
|
+
"lastVerified": "2026-10-14",
|
|
283
|
+
"verifiedBy": "manual"
|
|
284
|
+
}
|
|
285
|
+
],
|
|
286
|
+
"contact": {
|
|
287
|
+
"department": "Montgomery County Assessor of Property",
|
|
288
|
+
"url": "http://montgomerytn.gov/assessor/gis",
|
|
289
|
+
"email": null
|
|
290
|
+
},
|
|
291
|
+
"notes": "Montgomery County, Tennessee (Clarksville; FIPS 47125). The county's public parcel layer, the one the Assessor of Property's Public Parcels page advertises, is PublicParcels MapServer layer 0 on the county GIS server (gis.montgomerytn.gov, ArcGIS Server): 99,863 rows on 2026-10-14. THIS LAYER PUBLISHES PARCEL IDS AND SITUS ADDRESSES BUT NO OWNER OR MAILING FIELDS, so owner lookups return nothing here; look a parcel up by parcel number, by street address or by point. The parcel id is ParcelNo (e.g. 066E A 00600 000) with GISLINK as the shorter link id (063066E A 00600); the situs is PropertyAddress with PropertyCity. The rows are one per building card, not one per parcel: a parcel with several buildings repeats its parcel id and situs on each row (one sampled parcel returned six), so counts of rows overstate counts of parcels. The layer also carries subdivision, lot and block, deed book and page, property type, taxing district, acreage, assessed and appraised values, building attributes and the last sale. The layer's name is PublicParcels, the wkid is 102736 (Tennessee State Plane, US feet; latestWkid 2274), and outSR=4326 returns longitude and latitude. maxRecordCount is 2000 with pagination. CORS: the server echoes the request Origin in Access-Control-Allow-Origin, so a probe without an Origin header reads it as closed. No license or terms are published on the layer or on the assessor's pages. Verified 2026-10-14: a count of 99,863, a situs LIKE query on MAIN (120 rows) and an outSR=4326 query.",
|
|
292
|
+
"addedAt": "2026-10-14"
|
|
238
293
|
}
|
|
239
294
|
]
|
|
240
295
|
}
|