@urbankitstudio/atlas 0.6.15 → 0.6.17
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 +11 -2
- package/data/florida.json +67 -67
- package/data/index.json +6 -6
- package/data/michigan.json +1 -1
- package/data/new-jersey.json +122 -42
- package/data/new-york.json +88 -1
- package/data/oklahoma.json +1 -1
- package/dist/index.cjs +285 -118
- package/dist/index.d.cts +6 -0
- package/dist/index.d.ts +6 -0
- package/dist/index.js +285 -118
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -142,11 +142,20 @@ Treat both as *unknown*. Neither should render as "up".
|
|
|
142
142
|
|
|
143
143
|
Omit `?fips=` to get every tracked county in one call.
|
|
144
144
|
|
|
145
|
+
## `addedAt` is the one date that never moves
|
|
146
|
+
|
|
147
|
+
A county may carry `addedAt` (YYYY-MM-DD): the date it entered the atlas. It is
|
|
148
|
+
optional, because counties added before 2026-10-05 carry none, and it is the
|
|
149
|
+
only date here that is not re-stamped: `lastVerified` moves on every
|
|
150
|
+
re-verification, so a county verified yesterday can look brand new. When you
|
|
151
|
+
need to know whether a county is new to the atlas rather than recently checked,
|
|
152
|
+
read `addedAt` and fall back to the oldest `lastVerified` only when it is absent.
|
|
153
|
+
|
|
145
154
|
## Coverage today
|
|
146
155
|
|
|
147
|
-
The atlas bundles **
|
|
156
|
+
The atlas bundles **247 counties across all 50 US states and DC** (259 verified endpoints), covering the largest counties in each. Call `listStates()` to enumerate the full set.
|
|
148
157
|
|
|
149
|
-
Every state has at least one county on record, and
|
|
158
|
+
Every state has at least one county on record, and 241 of the 247 carry a verified endpoint. The other 6 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.
|
|
150
159
|
|
|
151
160
|
Counties are added as their public REST endpoints are verified. Package versions bump when data refreshes — pin to a minor range (`^0.x`) to receive new counties without breaking changes.
|
|
152
161
|
|