Descendants of 85682567
-
Wyhlen —
this is a neighbourhood
Repo whosonfirst-data-admin-ch/139/440/775/3/1394407753.geojson
ID 1394407753
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-ch/112/589/135/7/1125891357.geojson
Inception date unknown Cessation date unknown
It was last modified August 10, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-ch/101/842/023/101842023.geojson
ID 101842023
Inception date unknown Cessation date unknown
It was last modified August 10, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-ch/112/531/040/9/1125310409.geojson
ID 1125310409
Inception date unknown Cessation 2017-05-19
It was last modified August 10, 2019.
-
Nattheim —
this is a locality marked as current
Repo whosonfirst-data-admin-de/101/761/793/101761793.geojson
ID 101761793
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Notzingen —
this is a locality marked as current
Repo whosonfirst-data-admin-de/101/761/813/101761813.geojson
ID 101761813
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Ohmden —
this is a locality marked as current
Repo whosonfirst-data-admin-de/101/761/823/101761823.geojson
ID 101761823
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-de/101/761/831/101761831.geojson
ID 101761831
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-de/101/761/849/101761849.geojson
ID 101761849
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-de/101/761/903/101761903.geojson
ID 101761903
Inception date unknown Cessation date unknown
It was last modified August 01, 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 2,274 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?