Places that have a concordance with hasc:id= (Statoids HASC)
-
Aruba —
this is a region marked as current
Repo whosonfirst-data-admin-aw/856/674/89/85667489.geojson
ID 85667489
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Aruba —
this is a country marked as current
Repo whosonfirst-data-admin-aw/856/322/95/85632295.geojson
ID 85632295
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Eckerö —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/49/85667849.geojson
ID 85667849
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Kumlinge —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/93/85667893.geojson
ID 85667893
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Geta —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/53/85667853.geojson
ID 85667853
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Brändö —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/99/85667899.geojson
ID 85667899
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Föglö —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/57/85667857.geojson
ID 85667857
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Saltvik —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/63/85667863.geojson
ID 85667863
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Sund —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/67/85667867.geojson
ID 85667867
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Mariehamn —
this is a region marked as current
Repo whosonfirst-data-admin-ax/856/678/71/85667871.geojson
ID 85667871
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,403 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?