Descendants of 85632429
-
Repo whosonfirst-data-admin-jp/122/648/752/9/1226487529.geojson
ID 1226487529
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/649/112/1/1226491121.geojson
ID 1226491121
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Jike —
this is a locality
Repo whosonfirst-data-admin-jp/122/649/406/1/1226494061.geojson
ID 1226494061
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/649/664/3/1226496643.geojson
ID 1226496643
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/649/879/5/1226498795.geojson
ID 1226498795
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/650/113/9/1226501139.geojson
ID 1226501139
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/650/116/1/1226501161.geojson
ID 1226501161
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/650/118/5/1226501185.geojson
ID 1226501185
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Hino —
this is a locality
Repo whosonfirst-data-admin-jp/122/650/120/7/1226501207.geojson
ID 1226501207
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-jp/122/650/356/1/1226503561.geojson
ID 1226503561
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
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 16,113 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?