Descendants of 101751893
-
1022 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/749/538958749.geojson
ID 538958749
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
1034 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/771/538958771.geojson
ID 538958771
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
1043 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/783/538958783.geojson
ID 538958783
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
1051 —
this is a postalcode
Repo whosonfirst-data-postalcode-nl/538/958/793/538958793.geojson
ID 538958793
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/229/890574229.geojson
ID 890574229
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/235/890574235.geojson
ID 890574235
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/267/890574267.geojson
ID 890574267
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/279/890574279.geojson
ID 890574279
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/301/890574301.geojson
ID 890574301
Inception date unknown Cessation date unknown
It was last modified April 11, 2017.
-
Repo whosonfirst-data-postalcode-nl/890/574/367/890574367.geojson
ID 890574367
Inception date unknown Cessation date unknown
It was last modified April 11, 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,574 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?