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

Tool: Best examples based on custom elements? #23

Open
AmeliaBR opened this issue May 17, 2019 · 4 comments
Open

Tool: Best examples based on custom elements? #23

AmeliaBR opened this issue May 17, 2019 · 4 comments
Labels
bug: need info Important information or reference is missing. section: reference tools The "Reviewed JavaScript Tools" overview section

Comments

@AmeliaBR
Copy link
Member

@AmeliaBR AmeliaBR commented May 17, 2019

If we're proposing a markup-based map widget, it would be nice to have examples of existing tools that use an element and attribute API for embedding and customizing maps.

There is of course the community group's own custom element proposal, but it's circular logic to use it as an example!

I've found a few custom elements that are wrappers for the various major maps APIs, but not sure which ones would make a good reference:

@AmeliaBR AmeliaBR added the discussion: sample JS tool an existing web map tool: should we include it in the review? what should we say about it? label May 17, 2019
@prushforth
Copy link
Member

@prushforth prushforth commented May 18, 2019

@AmeliaBR AmeliaBR added bug: need info Important information or reference is missing. section: reference tools The "Reviewed JavaScript Tools" overview section and removed discussion: sample JS tool an existing web map tool: should we include it in the review? what should we say about it? labels May 25, 2019
@AmeliaBR
Copy link
Member Author

@AmeliaBR AmeliaBR commented Aug 31, 2019

Thanks to some data from Brian Kardell's analysis of HTTPArchive content, it looks like the most popular map viewer custom elements (searching for elements with "map" in the name and excluding sitemap, pagemap, etc.) are:

  • <ymaps>, which must be Yandex maps, probably via the React component? It's many times more common than any of the other <*map*> element names that are coming up. (Other than basic <map>.)
  • <dealeron-maps>, where DealerOn is a company that makes ready-to-wear websites for car dealerships. No documentation of what that actually looks like inside.
  • <ui-gmap-google-map> and <ng-map>, and <ang-map> which are all Angular modules wrapping Google maps in a declarative markup structure.

@Malvoz
Copy link
Member

@Malvoz Malvoz commented Aug 7, 2020

#23 (comment):

No mapping frameworks or elements use URLs for content, except ours. This
is the next frontier in showing that maps can be standardized, in my
opinion.

FWIW <leaflet-map>'s <leaflet-tilelayer> does support the url attribute to display data from external WMS services:
https://leaflet-extras.github.io/leaflet-map/demo.html#layerwms

@prushforth
Copy link
Member

@prushforth prushforth commented Aug 7, 2020

Although those look like URLs, they require further processing, and require that the client 'know' that {x} means tile column, and so on. These are assumptions, or coupling that need to be specified or else a mechanism needs to be specified in the media type spec on how to define what those variables 'mean'. This is baked into MapML processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: need info Important information or reference is missing. section: reference tools The "Reviewed JavaScript Tools" overview section
Projects
None yet
Development

No branches or pull requests

3 participants