360 Photos Support

[mahmoudadel54]

Description

As per issue title, it is requested the integration of a support for 360° photos in MS. This issue is coming from a preliminary investigation aimed to evaluate the feasibility of this task by establishing also an acceptable perimeter for a first implementation.

Main intervention area have been evaluated for this purpose:

• Data conversion
• Integration inside MapStore of a photo viewer based on a set of points taking into account the current implementation of Google Street API
• Interaction inside the 360 Photo viewer
• Overlap of vector layer data on the 360 Photo

Visualization in MapStore

• Integration in MapStore extending the configuration of the Street View plugin. This includes:
  • Review o/refactor of design and interactions with the plugin components
  • Extend localConfig.json configuration of the plugin to support multiple provider: Google Street View and Mapillary
  • Generalize action to support multiple providers and components
  • Review map icon
• [2D/3D] Add mapillary.js as an alternative viewer configurable to access custom data provider (images output generated in the previous step)
  • New components to visualize the mapillary.js viewer
  • Workflow to apply correct layers on map. Data conversion has been focused on small tracks using GeoJSON files, in case of large datasets we will need a different approach.
  • Add map support to control layers
• [2D] Add mapillary.js with the default provider:
  • Api key support and search on map
  • (Optional) Layer support: from the documentation mapillary allows to use coverage vector tiles with an access token (only Web Mercator seems supported). Openlayers allow to use vector tiles but we need to implement them on MapStore2. For a first implementation we propose to consider this optional and leave the user simply click on map without layer reference. After this we will be able to better consider that point and maybe evaluate if a valid alternative also i nterma os performances could be to use the mapillary apis to fetch layer content within the view and render points/path using a vector layer client side (this could be a future POC). This point is not included in the current estimate
  • No implementation for 3D

Acceptance criteria

• [ ] Be able to process 360° pictures. Photos and coordinates must be converted in a format that MapStore could handle
• [ ] Be able to visualize 360° pictures in MS using OS software
• [ ] Be able to interact with rendered 360° pictures and possibly overlay vector layers on them (optional)

Other useful information