Descendants of 85688543
-
Repo whosonfirst-data-admin-ca/132/652/720/9/1326527209.geojson
ID 1326527209
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
11424 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/786/357/554786357.geojson
ID 554786357
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
11736 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/393/554786393.geojson
ID 554786393
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
11969 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/417/554786417.geojson
ID 554786417
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
14241 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/431/554786431.geojson
ID 554786431
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
14276 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/455/554786455.geojson
ID 554786455
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
16553 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/477/554786477.geojson
ID 554786477
Inception date unknown Cessation date unknown
It was last modified August 03, 2016.
-
21264 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/786/497/554786497.geojson
ID 554786497
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
21283 —
this is a postalcode marked as current
Repo whosonfirst-data-postalcode-us/554/786/519/554786519.geojson
ID 554786519
Inception date unknown Cessation date unknown
It was last modified January 20, 2021.
-
21843 —
this is a postalcode
Repo whosonfirst-data-postalcode-us/554/786/543/554786543.geojson
ID 554786543
Inception date unknown Cessation date unknown
It was last modified August 03, 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,399 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?