Places that have a concordance with frgov:epci_code= (Open Data France)
-
Repo whosonfirst-data-admin-fr/404/356/151/404356151.geojson
ID 404356151
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Fye —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/356/381/404356381.geojson
ID 404356381
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Cherval —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/356/393/404356393.geojson
ID 404356393
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Nonza —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/355/955/404355955.geojson
ID 404355955
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Ussel —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/356/413/404356413.geojson
ID 404356413
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-fr/404/355/975/404355975.geojson
ID 404355975
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Glere —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/355/985/404355985.geojson
ID 404355985
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Connangles —
this is a localadmin marked as current
Repo whosonfirst-data-admin-fr/404/356/445/404356445.geojson
ID 404356445
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-fr/404/357/009/404357009.geojson
ID 404357009
Inception date unknown Cessation date unknown
It was last modified September 28, 2023.
-
Repo whosonfirst-data-admin-fr/404/357/021/404357021.geojson
ID 404357021
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,529 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?