Collaboration with eCamp3
Opened this issue · 2 comments
As mentioned in ecamp/ecamp3#5169, there is some interest in integrating our tool with the eCamp3 project. As one of the primary maintainers of this project, I'm happy to help with such an integration. Thus, this issue was created to discuss the scope of such an integration and track any progress on our side.
What can we contribute?
As discussed in ecamp/ecamp3#5169, there is no plan to add support for storing files as appendices directly inside the eCamp tool. Therefore, an integration consists of storing a reference to our tool instead (e.g., a link or uuid). This reference allows the route to be re-retrieved later. The PDF data could be re-generated on the fly via an API call and included in the eCamp export.
Needed prerequisites on our side?
The above integration implies that we implement an option to store routes within our tool. There are multiple options for such data storage:
- This could be as simple as the storage option on map.geo.admin.ch, where you can share any drawing with a link. Everyone with the link can modify the data behind that link. One year after the last modification, the data gets deleted.
- A more complex option would include a full-blown user-based system, where users must register with CeviDB or MiData login to store, edit and manage their routes. Routes can then be shared via links in view-only mode.
What are our plans for the future?
-
One of our big dreams is to provide the ability to draw and modify routes directly within our tool (similar to Schweiz Mobil and the Swisstopo App), including the ability to use magnetic paths (i.e., your route automatically follows any paths on the map). Thus, we must find a solution to store the drawn paths to provide such a feature.
-
We also dream of providing solutions to use our tool to create a safety concept, alternative routes, etc.
for updates, see ecamp/ecamp3#5169 (comment)