Descendants of 85688753
-
79903 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/819/554783819.geojson
ID 554783819
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
78352 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/789/549/554789549.geojson
ID 554789549
Inception date unknown Cessation date unknown
It was last modified December 04, 2016.
-
78579 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/789/615/554789615.geojson
ID 554789615
Inception date unknown Cessation date unknown
It was last modified December 05, 2016.
-
79920 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/789/653/554789653.geojson
ID 554789653
Inception date unknown Cessation date unknown
It was last modified December 03, 2016.
-
79989 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/966/751/538966751.geojson
ID 538966751
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
79163 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/966/879/538966879.geojson
ID 538966879
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
79991 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/966/901/538966901.geojson
ID 538966901
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
75164 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/776/351/554776351.geojson
ID 554776351
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
75489 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/776/543/554776543.geojson
ID 554776543
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
75849 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/776/643/554776643.geojson
ID 554776643
Inception date unknown Cessation date unknown
It was last modified December 04, 2016.
There are so many results for this query that the Spelunker database can't do page1, page2, page3... style pagination without getting sad. There are actually 1,364 pages worth of results for this query but as of this writing there is only the "next page" of results. We all have our limits, right? Speaking of limits, these query results have a pretty short shelf life. As long as you are paging through the results everything will be okay but if left idle for too long (about 5 minutes) they will expire and you'll need to perform a new query. It's good to have constraints to work against, right?