Descendants of 85632469
-
Repo whosonfirst-data-admin-bt/124/335/925/5/1243359255.geojson
ID 1243359255
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-bt/127/688/320/1/1276883201.geojson
ID 1276883201
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-bt/890/433/681/890433681.geojson
ID 890433681
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-bt/121/001/426/9/1210014269.geojson
ID 1210014269
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Nganglam —
this is a locality marked as current
Repo whosonfirst-data-admin-bt/890/455/907/890455907.geojson
ID 890455907
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Lalai —
this is a locality
Repo whosonfirst-data-admin-bt/134/375/153/7/1343751537.geojson
ID 1343751537
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-bt/136/010/302/3/1360103023.geojson
ID 1360103023
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-bt/127/631/786/1/1276317861.geojson
ID 1276317861
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Mago —
this is a locality
Repo whosonfirst-data-admin-bt/127/666/769/1/1276667691.geojson
ID 1276667691
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Gorjo —
this is a locality
Repo whosonfirst-data-admin-bt/129/292/162/7/1292921627.geojson
ID 1292921627
Inception date unknown Cessation date unknown
It was last modified August 24, 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 125,625 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?