Descendants of 85633345
-
3996 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/347/538927347.geojson
ID 538927347
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4816 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/369/538927369.geojson
ID 538927369
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4817 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/373/538927373.geojson
ID 538927373
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4818 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/375/538927375.geojson
ID 538927375
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4470 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/379/538927379.geojson
ID 538927379
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4471 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/381/538927381.geojson
ID 538927381
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4474 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/383/538927383.geojson
ID 538927383
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4475 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/385/538927385.geojson
ID 538927385
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4476 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/387/538927387.geojson
ID 538927387
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
4477 —
this is a postalcode
Repo whosonfirst-data-postalcode-nz/538/927/391/538927391.geojson
ID 538927391
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,098 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?