Use case: Mashup multiple layers of map tile data or features in a map

[prushforth]

This issue is for discussion of the map viewer use case “Mashup multiple layers of map tile data or features in a map”, its examples & list of required capabilities.

---

The ability to add and remove layers to yhe map is a fundamental use case, common to most Web map libraries. OTOH, most map libraries don't use URLs to refer to layers, because there is no commonly understood layer representation.

[caseymm]

Hoping I can get a bit of clarification on this... The title of this issue, "Use case: Combine multiple layers of map tile data or features," suggests to me that you're suggesting combining all map layers that contain data (points, polylines, other overlays, etc.) into one single layer. I also asked @zcorpan about this and he said that he thought it meant including the ability for a map to show multiple layers (as opposed to my understanding of all layers being flattened into one). Are either of these interpretations correct?

[prushforth]

you're suggesting combining all map layers that contain data (points, polylines, other overlays, etc.) into one single layer. I also asked @zcorpan about this and he said that he thought it meant including the ability for a map to show multiple layers

Simon is correct, but I can appreciate the confusion.

[prushforth]

@caseymm I renamed the issue, hopefully that is clearer. The intent is per Simon's interpretation; of course it's hard to tell how something is interpreted, language being what it is.

[Malvoz]

@prushforth We'd want to change the title in the document as well. Though I think the new title too can be interpreted as merging/fusing tile data and features into 1 layer, is "Display features or title data from multiple layers" clearer perhaps?