Skip to content
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

Re-design what mapml-viewer does with LegendURL / GetLegendGraphic links #524

Open
prushforth opened this issue Oct 5, 2021 · 0 comments · May be fixed by #763
Open

Re-design what mapml-viewer does with LegendURL / GetLegendGraphic links #524

prushforth opened this issue Oct 5, 2021 · 0 comments · May be fixed by #763

Comments

@prushforth
Copy link
Member

WMS and other OGC mapping services provide legend information via linked graphics, typically but not necessarily images.

In the original implementation of this custom element, I wasn't sure what to do with this information, but I wanted to expose it, so I included a <a href="LegendURL">Layer name/title/label</a> in the <details>' <summary> that represents the layer in the layer control.

It seems possible that browsers will in future disallow such interactive content in the <summary> elements, so this issue is where we can discuss and design what to do with the (set of possible) LegendURL or GetLegendGraphic links (or equivalents) that may be available for a map layer. Currently these can be represented by DOM elements such as

<map-link rel="legend" href="LegendURL"></map-link>

but the question remains as to how to expose them to the developer, if not the user, in an accessible manner.

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

Successfully merging a pull request may close this issue.

2 participants