Descendants of 85687051
-
Repo whosonfirst-data-postalcode-nl/891/261/157/891261157.geojson
ID 891261157
Inception date unknown Cessation date unknown
It was last modified December 14, 2017.
-
Repo whosonfirst-data-postalcode-nl/891/263/435/891263435.geojson
ID 891263435
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/447/891263447.geojson
ID 891263447
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/459/891263459.geojson
ID 891263459
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/503/891263503.geojson
ID 891263503
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/515/891263515.geojson
ID 891263515
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/525/891263525.geojson
ID 891263525
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/581/891263581.geojson
ID 891263581
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/605/891263605.geojson
ID 891263605
Inception date unknown Cessation date unknown
It was last modified July 28, 2016.
-
Repo whosonfirst-data-postalcode-nl/891/263/627/891263627.geojson
ID 891263627
Inception date unknown Cessation date unknown
It was last modified July 28, 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,398 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?