-
Notifications
You must be signed in to change notification settings - Fork 16
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
Would it be useful to allow and enable more than one <extent units="...">
per layer
#439
Comments
Maybe the layer control could designate one summary/details per |
I think the suggestion to have a separate summary for the different |
We should have a way to label an extent, which is clear for authors and implementers. I suggest adding a |
Sounds reasonable.
Not being able to differentiate between them seems problematic, there's a related issue in terms of what to do when a name/label hasn't been provided: #319. |
@Malvoz a multiple-extent layer could provide access to the individual extents' settings via the settings button you proposed. Each child extent could be considered an individual "setting" of the parent, each with its own settings button that exposes the same settings structure below / inside it, (except there would be no more levels of settings - settings buttons, that is) , just the settings controls themselves i.e. opacity slider, check input, remove button, etc. (those could each be inside a details/summary, as you've shown). WDYT? cc @Anshpreet8 |
Yes I think that'd form a logical structure.
I only kept |
One advantage might be that you could put several different projections in a single layer / mapml file and the client could pick the one that suits the map at the time.
Another possibility is that it could provide a scope for link templates and template variable names, which might help decrease error rates when editing them by hand / copying pasting+modifying (a standard coding method!).
Idea / question for discussion, pros and cons and so on.
The text was updated successfully, but these errors were encountered: