Descendants of 85675763
-
12160 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/609/538920609.geojson
ID 538920609
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
12210 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/619/538920619.geojson
ID 538920619
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
12320 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/631/538920631.geojson
ID 538920631
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
12460 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/651/538920651.geojson
ID 538920651
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
12600 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/673/538920673.geojson
ID 538920673
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
22100 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/809/538920809.geojson
ID 538920809
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
22590 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/831/538920831.geojson
ID 538920831
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
23310 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/853/538920853.geojson
ID 538920853
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
24700 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/899/538920899.geojson
ID 538920899
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
26220 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/920/921/538920921.geojson
ID 538920921
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,524 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?