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: Add a marker or multiple markers to a map #56

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

Capability: Add a marker or multiple markers to a map #56

NickFitz opened this issue Jun 14, 2019 · 3 comments
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? duplicate 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 “Add a marker or multiple markers to 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
@prushforth
Copy link
Member

@prushforth prushforth commented Jun 21, 2019

Adding (and displaying) markers is by far the most common need, but it is specialization of a more general capability, which is to allow the user to input (any) simple features geometry. Multiple markers might be a "multipoint" type geometry, or it might be multiple points. This capability also leads into a discussion of how <form> elements might work in a map browsing context. We have had that discussion on and off in the MapML world e.g. <input type=location subtype=polygon> , but we need to actually implement something that experiments with ideas, to evaluate what's feasible. To do that, I believe we need to get some Web map developers from OpenLayers (for example), and/or OpenStreetMap etc., say, to help us with the user experience and so on.

@NickFitz
Copy link
Contributor Author

@NickFitz NickFitz commented Nov 12, 2019

It seems to me that this capability is likely to duplicate much of what is said at https://maps4html.github.io/HTML-Map-Element-UseCases-Requirements/#capability-marker-points if it attempts to get into definitions of “marker” and so on, so I intend to link to that capability for background, and restrict this one to consideration of the API-related aspects of adding markers. Does that seem reasonable?

@Malvoz
Copy link
Member

@Malvoz Malvoz commented Nov 12, 2019

Moving the current definition of "marker" ("A map marker is a small icon that marks a point feature.") from #capability-marker-points to the glossary section makes the most sense, to me at least.

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? duplicate 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

3 participants