Descendants of 85633789
-
18632 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/483/025/421483025.geojson
ID 421483025
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25223 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/011/421484011.geojson
ID 421484011
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25226 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/015/421484015.geojson
ID 421484015
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25227 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/017/421484017.geojson
ID 421484017
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25230 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/019/421484019.geojson
ID 421484019
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25231 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/021/421484021.geojson
ID 421484021
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25234 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/023/421484023.geojson
ID 421484023
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25244 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/025/421484025.geojson
ID 421484025
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25245 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/027/421484027.geojson
ID 421484027
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
25246 —
this is a postalcode
Repo whosonfirst-data-postalcode-se/421/484/029/421484029.geojson
ID 421484029
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 4,388 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?