Descendants of 85672133
-
Jalala —
this is a locality marked as current
Repo whosonfirst-data-admin-in/131/008/421/1/1310084211.geojson
ID 1310084211
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/131/008/425/1/1310084251.geojson
Inception date unknown Cessation 2023-03-21
It was last modified April 30, 2023.
-
Burj —
this is a locality
Repo whosonfirst-data-admin-in/131/009/410/1/1310094101.geojson
ID 1310094101
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/131/009/902/3/1310099023.geojson
ID 1310099023
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-in/131/009/903/5/1310099035.geojson
Inception date unknown Cessation date unknown
It was last modified December 06, 2019. This record is deprecated.
-
Parail —
this is a locality marked as current
Repo whosonfirst-data-admin-in/131/009/904/7/1310099047.geojson
ID 1310099047
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/346/833/1/1293468331.geojson
Inception date unknown Cessation 2023-03-21
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/346/836/5/1293468365.geojson
ID 1293468365
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Katwa —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/347/847/5/1293478475.geojson
ID 1293478475
Inception date unknown Cessation date unknown
It was last modified June 07, 2023.
-
Repo whosonfirst-data-admin-in/129/347/848/5/1293478485.geojson
ID 1293478485
Inception date unknown Cessation date unknown
It was last modified December 30, 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,053 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?