-
-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Change IGN urls #3591
Comments
Additional information see : https://www.ign.fr/geoplateforme/debrief/accompagner-la-bascule-vers-la-geoplateforme |
Made some tests this day (2023-10-27) some layers are not available As explained in https://geoservices.ign.fr/services-geoplateforme-diffusion
summary with example URL :
Note : the sheet linked in the IGN page don't describe the "MAPS" layer |
Thanks a lot for working on this subjet |
Update : "Cartes" and "Plan" still not available
|
GEOGRAPHICALGRIDSYSTEMS.PLANIGNV2 is now ✅ |
Thanks @nworr for checking, I have added Orthophoto and Plan by default in 3liz/lizmap-plugin#523 |
There is also the builtin search address in LWC using the API : https://geoservices.ign.fr/documentation/services/services-geoplateforme/autocompletion |
GEOGRAPHICALGRIDSYSTEMS.MAPS now available with authentification : sample with temporary key |
Both branch (3.6 & 3.7) now use the "IGN geoplateforme" URLs. |
Search and WMS services are now using the "new" geoplateforme URL from IGN in 3.6, 3.7, and master branch |
What is the bug?
Following the news in IGN website : https://geoservices.ign.fr/actualites/2023-01-23-geoplateforme
Linked to 3liz/lizmap-plugin#471
===Edit===
Today, they have published this link as well comparing features and giving some end of life dates : https://geoservices.ign.fr/bascule-vers-la-geoplateforme
Steps to reproduce the issue
Follow the blog post
Versions
Not relevant
Check Lizmap plugin
QGIS server version, only if the section above doesn't mention the QGIS Server version
No response
Operating system
Not relevant
Browsers
Firefox
Browsers version
Not relevant
Relevant log output
No response
The text was updated successfully, but these errors were encountered: