Places that have a concordance with eg:gisco_id= (EuroGeographics)
-
Repo whosonfirst-data-admin-ch/404/568/547/404568547.geojson
ID 404568547
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-ch/404/568/555/404568555.geojson
ID 404568555
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-ch/404/568/609/404568609.geojson
ID 404568609
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Avenches —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/615/404568615.geojson
ID 404568615
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Kloten —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/627/404568627.geojson
ID 404568627
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-ch/404/568/697/404568697.geojson
ID 404568697
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Vollèges —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/717/404568717.geojson
ID 404568717
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Oberbüren —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/723/404568723.geojson
ID 404568723
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Corgémont —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/731/404568731.geojson
ID 404568731
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Niederbipp —
this is a localadmin marked as current
Repo whosonfirst-data-admin-ch/404/568/751/404568751.geojson
ID 404568751
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 7,406 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?