Descendants of 85672209
-
Repo whosonfirst-data-admin-cn/129/385/745/9/1293857459.geojson
ID 1293857459
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-in/129/341/851/9/1293418519.geojson
ID 1293418519
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-in/129/341/854/5/1293418545.geojson
ID 1293418545
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-in/129/341/855/9/1293418559.geojson
ID 1293418559
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Intwa —
this is a locality
Repo whosonfirst-data-admin-in/129/341/857/9/1293418579.geojson
ID 1293418579
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-in/129/341/860/1/1293418601.geojson
ID 1293418601
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Timli —
this is a locality
Repo whosonfirst-data-admin-in/129/341/891/3/1293418913.geojson
ID 1293418913
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Balori —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/341/893/7/1293418937.geojson
ID 1293418937
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Rithar —
this is a locality marked as current
Repo whosonfirst-data-admin-in/129/341/895/7/1293418957.geojson
ID 1293418957
Inception date unknown Cessation date unknown
It was last modified April 30, 2023.
-
Repo whosonfirst-data-admin-in/129/342/540/5/1293425405.geojson
ID 1293425405
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 2,412 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?