Overlay Manager - Merge/Save proposals

Route planning
1

I have a couple of ideas for new functions in Overlay Manager:

:one: Merge overlays

Use Case: Sometimes I use more overlays than I actually need to manage individually, because the contents are either in different folders or originsting from different GPX files.
Solution proposal: add “Merge overlays” function to OM, which would merge contents of two or more overlays into one and free-up some of the 15 overlay entries.

:two: Save overlay

Use case: I have added several overlays on my laptop from GPX files, but I do not have the files on my mobile device. I need to free-up some of the 15 overlay entries for other use. If I delete the overlay, I will not be able to add it later again, since I do not have the file with me.
Solution proposal: add the ability to save existing overlay for later use. Either on the cloud or as a GPX file saved locally. The overlay could be loaded later when needed.

2

Thanks for providing these ideas :slight_smile:

I think this would be really nice, but could only work for GPX files, so it has limited usability.

Interesting idea. This could only really work with GPX overlays as well. As for cloud folders, the automatic sync would be lost with no way to restore it ever again.

3

You could “decouple” the data of the merged folder from its original source in cloud. It gets a new name and a short note appears that the merged overlay will not show updates from the folder.
I find it very useful, even if it would be for GPX only.

Missing the ability to save the GPX file is my initial use case, why I decided to open the topic. I did not have the file on my mobile device and I did not want to loose the overlay.

I do not think it is an issue, if you loose the sync to the cloud. When I save something, I usually expect it to retain the state I have saved. It’s just an overlay, so the original data is still in the cloud.

4

Yeah, I totally can relate. One downside is, that we can’t restore the original GPX, so this could lead to unexpected content :thinking:. We only store the relevant info for the overlay.

I am not sure this could lead to a misunderstanding. Overall this will add even more complexity to overlays.

5

I thought, overlays are just data containers in a suitable format to be displayed. If that is so, then manipulating that data (merging and saving) without format conversion should not be too complicated.
Saving in a Kurviger propriatory format should then be fairly easy, but not the best option in terms of portability to another GPX Viewer/Editor.

Not a top priority - the idea may need some more time to ripe and to hear opinions of other users - what is really needed if anything at all.