-
Notifications
You must be signed in to change notification settings - Fork 3
Ability to use custom WMS/WMTS layers inside app #2269
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- Improved UI strings handling - Use a separate panel to select
8beea19
to
221a558
Compare
… fixes the problem, not sure why)
63d7a6a
to
6ea3cc4
Compare
Thanks for your comments @bprusinowski , all very useful. I have solved the majority of them. I think now that we have this foundation for custom layers, I will potentially port the code from https://github.com/geoadmin/web-mapviewer/blob/b32e10b678a00fd5e9df79ba1f98b32fd6684f01/packages/mapviewer/src/api/layers/WMSCapabilitiesParser.class.js#L48 since it tries to handle more cases than the default WMS/WMTS parsers. I can do that this afternoon to see if it unblocks more providers. I would still like to merge this PR since it brings the new UI and already some providers are working. What do you think ? |
Of course, sounds like a good approach 💯 |
This PR uses the custom WMTS chooser that was previously done only in Storybook and integrate it into the app.
How to test
TODO