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: Technical drawings (panning, zooming, layers, etc.) #1

Open
prushforth opened this issue Oct 31, 2018 · 7 comments
Open

Use case: Technical drawings (panning, zooming, layers, etc.) #1

prushforth opened this issue Oct 31, 2018 · 7 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

@prushforth
Copy link
Member

prushforth commented Oct 31, 2018

This issue is for discussion of the use case “Display drawings or schematics without geographic coordinates”, its examples & list of required capabilities.


Per discussions with @satakagi at TPAC, an important level of progressive enhancement of the <map> element could be "deep zooming" of non-georeferenced technical drawings, such as schematics of microprocessors etc.

Recently the "WGS84" projection in MapML was extended to support tile resolutions at different zoom levels. Is this projection adequate for this use case?

@AmeliaBR AmeliaBR changed the title Panning and zooming of technical drawings Use case: technical drawings (panning, zooming, layers, etc.) Apr 18, 2019
@AmeliaBR AmeliaBR added the discussion: use case a possible use case: should it be included? what should it say? label Apr 18, 2019
@AmeliaBR
Copy link
Member

AmeliaBR commented Apr 18, 2019

Based on the strategy in the new report, there are two ways of thinking about this use case:

  • Panning & zooming are low-level capabilities that could be implemented in CSS/HTML separate from a map viewer, so they can be reused for other types of content.

  • Within the map viewer, a potential capability is the ability to draw and layer graphics that use non-geographic coordinate systems.

I think that both have benefits. For something like "zoom in on a product photo", you maybe don't want all the extra UI and complexity of a map viewer. But for complex technical drawings or architectural blueprints, you may want more than just panning & zooming, you want layers & markers with pop-ups & lots of the other capabilities from the map viewer — everything except connecting the drawing to specific latitude and longitude.

@prushforth
Copy link
Member Author

prushforth commented Apr 18, 2019

As chance would have it, there is some discussion of incubating infinite scrolling recently on WICG. Somebody did note in a GitHub issue for that project that 2D stuff including map tiles is of interest, not just text. It doesn't look like the authors of virtual-scroller took that suggestion to heart yet, though.

@AmeliaBR AmeliaBR added the status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft label Apr 20, 2019
@prushforth prushforth changed the title Use case: technical drawings (panning, zooming, layers, etc.) Use case: Technical drawings (panning, zooming, layers, etc.) Apr 25, 2019
@AmeliaBR AmeliaBR added 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 and removed status: suggestion this issue discusses a suggested addition to the report, that is not yet in the draft labels May 26, 2019
@prushforth
Copy link
Member Author

prushforth commented Jul 20, 2019

Twitter never disappoints. There is a standard API for non-georeferenced imagery, with a number of viewers , which perhaps use the API.

@AmeliaBR AmeliaBR removed the section: map viewer Capabilities & use cases for declarative map viewer widgets label Jul 25, 2019
AmeliaBR pushed a commit that referenced this issue Aug 24, 2019
@AmeliaBR
Copy link
Member

AmeliaBR commented May 5, 2020

Here's a lovely example of using GIS software for non-geographic data: https://twitter.com/pokateo_/status/1186620601949134849

@prushforth
Copy link
Member Author

prushforth commented Oct 23, 2020

I just noticed that the examples for Leaflet and OpenLayers use the TMS convention of tile matrix origin at the lower left position and the y axis positive upwards; this is conveyed to them through the use of the {-y} url template variable. I view the whole token to be a template variable reference, and as with other URL template variables in Leaflet, it 'understands' the meaning of the variable by its name '-y', which embeds the client-server coupling that we must avoid.

So, either we have to include support for TMS, taking it into account in these UCRs (we probably could define a TCRS this way, but not sure it's a good idea for an obsolete and niche spec such as TMS), or potentially migrate our examples towards origin-at-top-left examples.

@shepazu
Copy link
Member

shepazu commented Nov 18, 2020

This use case is a good candidate to be broken out into a more generalized functionality. It doesn't seem to be a map use case per se, but rather a valid use case that can only be solved with mapping software because the primitive infrastructure functionality (zoom, pan, sometimes tiling, layers, annotation, etc.) isn't available in browsers.

The distinction may be important, because there is a larger set of applications of which maps are only one:

  • maps (note: there are many different types of maps)
  • technical schematics
  • floorplans / blueprints
  • data charts
  • flow charts (including “mind maps”)
  • high-resolution art images (paintings, manuscripts, etc.)
  • medical imaging
  • XR (augmented/virtual reality) spaces
  • games

Each of these things may have different sets of additional functionality above and beyond the core shared functionality.

@Malvoz
Copy link
Member

Malvoz commented Oct 5, 2021

There's a relevant proposal from WebKit: the <model> element.

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