Descendants of 85688697
-
60667 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/966/685/538966685.geojson
ID 538966685
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
60398 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/245/538967245.geojson
ID 538967245
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
60297 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/397/538967397.geojson
ID 538967397
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
60125 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/791/538967791.geojson
ID 538967791
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
60025 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/155/554783155.geojson
ID 554783155
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
60043 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/169/554783169.geojson
ID 554783169
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
60056 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/179/554783179.geojson
ID 554783179
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
60091 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/207/554783207.geojson
ID 554783207
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
60160 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/231/554783231.geojson
ID 554783231
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
60411 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/783/271/554783271.geojson
ID 554783271
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
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,067 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?