Descendants of 890508877
-
Dhuta —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/882/5/1293428825.geojson
ID 1293428825
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/342/961/7/1293429617.geojson
ID 1293429617
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Shivpur —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/342/963/1/1293429631.geojson
ID 1293429631
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/342/981/1/1293429811.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/400/7/1293434007.geojson
Inception date unknown Cessation date unknown
It was last modified April 30, 2023. This record is deprecated.
-
Repo whosonfirst-data-admin-in/131/014/565/7/1310145657.geojson
ID 1310145657
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/129/343/397/1/1293433971.geojson
Inception date unknown Cessation date unknown
It was last modified April 30, 2023. This record is deprecated.
-
Gujarpur —
this is a locality marked as current
Repo whosonfirst-data-admin-in/131/014/505/1/1310145051.geojson
ID 1310145051
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/131/014/506/9/1310145069.geojson
ID 1310145069
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/131/014/573/5/1310145735.geojson
ID 1310145735
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 1,305 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?