Descendants of 85687059
-
Repo whosonfirst-data-postalcode-nl/891/272/039/891272039.geojson
ID 891272039
Inception date unknown Cessation date unknown
It was last modified December 14, 2017.
-
9907 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/571/538958571.geojson
ID 538958571
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9913 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/581/538958581.geojson
ID 538958581
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9925 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/605/538958605.geojson
ID 538958605
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9956 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/641/538958641.geojson
ID 538958641
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9993 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/713/538958713.geojson
ID 538958713
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9503 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/962/055/538962055.geojson
ID 538962055
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9644 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/962/067/538962067.geojson
ID 538962067
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9674 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/962/079/538962079.geojson
ID 538962079
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
-
9734 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/962/123/538962123.geojson
ID 538962123
Inception date unknown Cessation date unknown
It was last modified December 15, 2017.
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,660 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?