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: Display multiple point locations on a single map #78

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

Use Case: Display multiple point locations on a single map #78

NickFitz opened this issue Jun 14, 2019 · 2 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

@NickFitz
Copy link
Contributor

@NickFitz NickFitz commented Jun 14, 2019

This issue is for discussion of the use case “Display multiple point locations on a single map”, its examples & list of required capabilities.

@NickFitz NickFitz added discussion: use case a possible use case: should it be included? what should it say? 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
@prushforth
Copy link
Member

@prushforth prushforth commented Jun 17, 2019

MapML proposal

@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented Jul 5, 2019

This is one of a number of use cases for the API that end up mirroring use cases for the static widget. It should probably be worded in a way that emphasizes changes that need to happen on the client-side. E.g., "Add locations from a dynamic data set to the map".

The examples in Nick's draft are good at capturing this idea, just need to express that in the heading:

Example uses of such a map include search results (e.g. restaurants), traffic information (e.g. locations of roadworks), or the locations where photographs in a gallery were taken.

@AmeliaBR AmeliaBR removed the section: client-side API Capabilities & use cases for client-side APIs label Jul 25, 2019
@Malvoz Malvoz added status: editor's draft there's a draft section in the report that corresponds to this discussion and removed status: placeholder there's a matching section heading / some text in the report, but it's far from complete labels Sep 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

4 participants