Descendants of 85672213
-
Bataua —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/821/9/1293428219.geojson
ID 1293428219
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/342/823/1/1293428231.geojson
ID 1293428231
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/129/343/244/7/1293432447.geojson
Inception date unknown Cessation date unknown
It was last modified April 30, 2023. This record is deprecated.
-
Repo whosonfirst-data-admin-in/129/343/245/9/1293432459.geojson
ID 1293432459
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Purabdiha —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/343/246/7/1293432467.geojson
ID 1293432467
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Surda —
this is a locality marked as current
Repo whosonfirst-data-admin-in/131/014/422/1/1310144221.geojson
ID 1310144221
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Mahubona —
this is a locality marked as current
Repo whosonfirst-data-admin-in/131/014/423/3/1310144233.geojson
ID 1310144233
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Kushi —
this is a locality
Repo whosonfirst-data-admin-in/131/014/424/3/1310144243.geojson
ID 1310144243
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Nebhi —
this is a locality
Repo whosonfirst-data-admin-in/129/343/476/9/1293434769.geojson
ID 1293434769
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/129/344/117/3/1293441173.geojson
ID 1293441173
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 4,190 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?