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

Capability: Control which layers are included in a map #63

Open
NickFitz opened this issue Jun 14, 2019 · 2 comments
Open

Capability: Control which layers are included in a map #63

NickFitz opened this issue Jun 14, 2019 · 2 comments
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete

Comments

@NickFitz
Copy link
Contributor

@NickFitz NickFitz commented Jun 14, 2019

This issue is for discussion of the required API capability “Control which layers are included in a map”.

@NickFitz NickFitz added discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? status: placeholder there's a matching section heading / some text in the report, but it's far from complete section: client-side API Capabilities & use cases for client-side APIs labels Jun 14, 2019
@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented Jul 5, 2019

The current draft lists separate capabilities for add a layer (#61), remove a layer (#62), display a layer (this issue), & hide a layer (#64). I think we can probably collapse that set. Display & hide could be "toggle visibility of a layer", while "add" can probably be re-focused to talk about the specific type of layer you are initiating & adding (e.g., a vector set vs an image vs a tile set).

@AmeliaBR AmeliaBR changed the title Capability: Display a layer on a map Capability: Control which layers are included in a map Feb 7, 2020
@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented Feb 7, 2020

OK, in the current draft the capabilities have been merged as suggested above, so the title of this issue has been updated to match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete
Projects
None yet
Development

No branches or pull requests

2 participants