Descendants of 85675757
-
Semri —
this is a locality
Repo whosonfirst-data-admin-in/134/416/684/1/1344166841.geojson
ID 1344166841
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
51130 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/007/538924007.geojson
ID 538924007
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
51490 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/017/538924017.geojson
ID 538924017
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
52080 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/029/538924029.geojson
ID 538924029
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
53700 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/039/538924039.geojson
ID 538924039
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
55150 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/051/538924051.geojson
ID 538924051
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
56410 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/924/063/538924063.geojson
ID 538924063
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
73210 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/485/538923485.geojson
ID 538923485
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
75260 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/495/538923495.geojson
ID 538923495
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
76160 —
this is a postalcode
Repo whosonfirst-data-postalcode-pk/538/923/507/538923507.geojson
ID 538923507
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 3,054 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?