Descendants of 404227549
-
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/122/604/619/9/1226046199.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Lorch —
this is a locality marked as current
Repo whosonfirst-data-admin-de/101/761/949/101761949.geojson
ID 101761949
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-de/101/761/957/101761957.geojson
ID 101761957
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Hals —
this is a locality
Repo whosonfirst-data-admin-de/122/605/192/1/1226051921.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-de/122/605/193/1/1226051931.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-de/124/258/687/3/1242586873.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-de/122/615/234/5/1226152345.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
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,067 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?