Descendants of 85633105
-
Repo whosonfirst-data-admin-at/129/379/545/5/1293795455.geojson
ID 1293795455
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Repo whosonfirst-data-admin-at/124/326/559/7/1243265597.geojson
ID 1243265597
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Doksany —
this is a locality marked as current
Repo whosonfirst-data-admin-cz/112/604/770/7/1126047707.geojson
ID 1126047707
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Kosel —
this is a neighbourhood
Repo whosonfirst-data-admin-cz/112/606/116/5/1126061165.geojson
ID 1126061165
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Volfířov —
this is a locality marked as current
Repo whosonfirst-data-admin-cz/112/605/283/1/1126052831.geojson
ID 1126052831
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Praský —
this is a neighbourhood
Repo whosonfirst-data-admin-cz/112/606/415/9/1126064159.geojson
ID 1126064159
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Repo whosonfirst-data-admin-cz/112/606/741/5/1126067415.geojson
ID 1126067415
Inception date unknown Cessation date unknown
It was last modified August 25, 2019.
-
Vaclavovice —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-cz/112/607/283/5/1126072835.geojson
ID 1126072835
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Sebuzín —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-cz/112/608/338/7/1126083387.geojson
ID 1126083387
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-cz/112/608/342/1/1126083421.geojson
ID 1126083421
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,794 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?