Descendants of 85688651
-
32509 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/785/885/554785885.geojson
ID 554785885
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32410 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/788/707/554788707.geojson
ID 554788707
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32151 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/125/538967125.geojson
ID 538967125
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
32589 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/143/538967143.geojson
ID 538967143
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
32890 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/538/967/687/538967687.geojson
ID 538967687
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
32086 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/781/185/554781185.geojson
ID 554781185
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32124 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/781/197/554781197.geojson
ID 554781197
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32137 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/781/207/554781207.geojson
ID 554781207
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32169 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/781/219/554781219.geojson
ID 554781219
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
32226 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/781/229/554781229.geojson
ID 554781229
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,459 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?