Descendants of 85675733
-
Repo whosonfirst-data-admin-ir/120/973/351/7/1209733517.geojson
ID 1209733517
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
24480 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/922/867/538922867.geojson
ID 538922867
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
37660 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/009/538923009.geojson
ID 538923009
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
38860 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/011/538923011.geojson
ID 538923011
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
39120 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/017/538923017.geojson
ID 538923017
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
39170 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/019/538923019.geojson
ID 538923019
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
39420 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/021/538923021.geojson
ID 538923021
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
39540 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/023/538923023.geojson
ID 538923023
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
40230 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/027/538923027.geojson
ID 538923027
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
40310 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/029/538923029.geojson
ID 538923029
Inception date unknown Cessation date unknown
It was last modified September 22, 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,558 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?