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

Use case (website visitor): Show/hide map layers or feature sets #115

Open
AmeliaBR opened this issue Aug 10, 2019 · 0 comments
Open

Use case (website visitor): Show/hide map layers or feature sets #115

AmeliaBR opened this issue Aug 10, 2019 · 0 comments
Labels
discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion

Comments

@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented Aug 10, 2019

This issue is for discussion of the use case “Show/hide map layers or feature sets”, its examples & list of required capabilities.

This focuses on the use case for website end-users: is this available by default (or with minimal author configuration to enable it)?

Related to #82, which focuses on the developer/author's ability to restrict or replace/implement this type of control.

@AmeliaBR AmeliaBR added discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion labels Aug 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: use case a possible use case: should it be included? what should it say? status: editor's draft there's a draft section in the report that corresponds to this discussion
Projects
None yet
Development

No branches or pull requests

1 participant