Descendants of 85632347
-
Kago —
this is a locality
Repo whosonfirst-data-admin-id/130/982/181/9/1309821819.geojson
ID 1309821819
Inception date unknown Cessation date unknown
It was last modified March 01, 2021.
-
155 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/137/421519137.geojson
ID 421519137
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
156 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/139/421519139.geojson
ID 421519139
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
211 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/145/421519145.geojson
ID 421519145
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
213 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/147/421519147.geojson
ID 421519147
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
214 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/151/421519151.geojson
ID 421519151
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
215 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/153/421519153.geojson
ID 421519153
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
221 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/155/421519155.geojson
ID 421519155
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
222 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/157/421519157.geojson
ID 421519157
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
223 —
this is a postalcode
Repo whosonfirst-data-postalcode-pg/421/519/159/421519159.geojson
ID 421519159
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,100 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?