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: Support hyperlinks from markers or vector features #142

Open
Malvoz opened this issue Sep 9, 2019 · 5 comments
Open

Capability: Support hyperlinks from markers or vector features #142

Malvoz opened this issue Sep 9, 2019 · 5 comments
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: map viewer Capabilities & use cases for declarative map viewer widgets status: editor's draft there's a draft section in the report that corresponds to this discussion

Comments

@Malvoz
Copy link
Member

Malvoz commented Sep 9, 2019

This issue is for discussion of the map viewer capability “Support hyperlinks from markers or vector features”.

@Malvoz Malvoz added discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: map viewer Capabilities & use cases for declarative map viewer widgets status: editor's draft there's a draft section in the report that corresponds to this discussion labels Sep 9, 2019
@Malvoz
Copy link
Member Author

Malvoz commented May 24, 2021

Because markers and vectors can overlap, it is important to consider the problems that may cause about interacting with these links, especially for users with a pointing/touch-enabled device. See: Maps4HTML/MapML-Proposal#41.

@pvgenuchten
Copy link

One can now link a map-properties value to a remote location, in this way one can link from a feature to remote source

<map-properties>
        <table>
          <thead>
            <tr>
              <th role="columnheader" scope="col">Property name</th>
              <th role="columnheader" scope="col">Property value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <th scope="row">Name</th>
              <td itemprop="amenity"><a href="https://en.wikipedia.org/wiki/Ottawa">Ottawa</a></td>
            </tr>
        </table>
<map-properties>

Reverse link could be more challenging?

https://example.com/index.html#mapml=example&feature=Ottowa

@prushforth
Copy link
Member

Reverse link could be more challenging?

https://example.com/index.html#mapml=example&feature=Ottowa

By 'reverse link', can we clarify, is "https://example.com/index.html" a page that has a/some map(s) on it, and what behaviour are you expecting from the mapml #fragment?

@Malvoz
Copy link
Member Author

Malvoz commented Jun 28, 2022

By 'reverse link', can we clarify, is "https://example.com/index.html" a page that has a/some map(s) on it

That's how I interpret it as well.

what behaviour are you expecting from the mapml #fragment?

We did discuss such behavior briefly in Maps4HTML/Web-Map-Custom-Element#378, IMO:

This is essentially Text Fragments, but for maps

I think the appropriate capability to hold the discussion is #146, because the supported use case #41 mentions:

  • bookmark a view/location so you can come back to it the next time you visit the webpage

@pvgenuchten
Copy link

pvgenuchten commented Jun 28, 2022

By 'reverse link', can we clarify, is "https://example.com/index.html" a page that has a/some map(s) on it, and what behaviour are you expecting from the mapml #fragment?

correct, the self link (permalink) would have a reference to a map instance on a page, (probably a layer reference) and an object reference

expected behaviour for example that the map is centered on the feature, maybe a balloon is opened with details on the feature

but these are just wild ideas, probably hard to implement

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: map viewer Capabilities & use cases for declarative map viewer widgets 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

3 participants