Descendants of 85632229
-
Repo whosonfirst-data-admin-af/129/353/051/5/1293530515.geojson
ID 1293530515
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Adraskan —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/178/1/1108561781.geojson
ID 1108561781
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Chamkani —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/190/1/1108561901.geojson
ID 1108561901
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Farah —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/200/1/1108562001.geojson
ID 1108562001
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Khakrez —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/214/1/1108562141.geojson
ID 1108562141
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Lal Por —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/222/7/1108562227.geojson
ID 1108562227
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Naw Zad —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/231/1/1108562311.geojson
ID 1108562311
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Rustaq —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/241/7/1108562417.geojson
ID 1108562417
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Shinkay —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/249/3/1108562493.geojson
ID 1108562493
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Turwo —
this is a county marked as current
Repo whosonfirst-data-admin-af/110/856/255/1/1108562551.geojson
ID 1108562551
Inception date unknown Cessation date unknown
It was last modified September 28, 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 3,243 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?