Skip to content
This repository has been archived by the owner on Jul 17, 2024. It is now read-only.

Upload error for external WMTS ressources #5229

Closed
skitourenguru opened this issue Mar 6, 2021 · 10 comments
Closed

Upload error for external WMTS ressources #5229

skitourenguru opened this issue Mar 6, 2021 · 10 comments
Assignees

Comments

@skitourenguru
Copy link

Since 5. March 2021 its not possible anymore to import external WMTS ressources to map.geo.admin.ch. When you try to add one of the 2 following external GetCap-Links, there is an upload error:
https://map.skitourenguru.ch/ATHM_GetCapabilities.xml
https://map.slf.ch/public/mapcache/wmts/1.0.0/WMTSCapabilities.xml

Was there an update last friday?

Tested with Chrome and Firefox on Win.

@skitourenguru
Copy link
Author

There is a problem with CORS at Swisstopo (#5227)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://map.slf.ch/public/mapcache/wmts/1.0.0/WMTSCapabilities.xml. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing)

@davidoesch
Copy link
Contributor

we look into that on monday

@davidoesch
Copy link
Contributor

AFAIK: we did not deploy on fridays
CORS Issues can be reproduced

@davidoesch
Copy link
Contributor

Thx

@skitourenguru
Copy link
Author

The problem applies as well to the accidents of the SLF (Swisstopo-iFrame with referenced KML) under this link:
https://www.slf.ch/de/lawinen/unfaelle-und-schadenlawinen/toedliche-lawinenunfaelle-aktuell.html#tabelement1-tab2

@davidoesch
Copy link
Contributor

Update:
Looks like the provider of the KML/WMTS changed on their side infra setup.
We will look on how to adapt no our infra--

@cype
Copy link

cype commented Mar 8, 2021

hey there. CORS-problem also with KML-imports, see example here: http://www.uvek-gis.admin.ch/BFE/storymaps/WK_SpeicherbareEnergie/

@davidoesch
Copy link
Contributor

-root cause identified
-Issue solved (a bug on our side)

  • all systems back to normal

@skitourenguru
Copy link
Author

All works fine now... Thanks a lot for the fast fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants