Descendants of 85672239
-
Bargabodi —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/996/5/1293429965.geojson
ID 1293429965
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Rampuri —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/997/7/1293429977.geojson
ID 1293429977
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Bhonda —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/998/9/1293429989.geojson
ID 1293429989
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Ahrora —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/999/9/1293429999.geojson
ID 1293429999
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/343/003/9/1293430039.geojson
ID 1293430039
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/343/005/1/1293430051.geojson
Inception date unknown Cessation date unknown
It was last modified April 30, 2023. This record is deprecated.
-
Pandri —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/343/007/3/1293430073.geojson
ID 1293430073
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Garra —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/343/009/3/1293430093.geojson
ID 1293430093
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/343/012/3/1293430123.geojson
ID 1293430123
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Chhayen —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/343/013/3/1293430133.geojson
ID 1293430133
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
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 8,340 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?