Usage question: is it possible to combine information from wandrer.earth with info in these maps?

[cleeland]

The end result I'm seeking is the ability to combine the information from wandrer-generated OSM maps with the information provided by this tool. I don't know the technical detail about how OSM works or how this tool works, and maybe if I did the answers would be obvious.

Wandrer.earth allows a user to download OSM maps with road/path shading changed to reflect roads on which the user has previously traveled. These maps are then sideloaded onto the wahoo device (although a different process from described here) and get displayed on the map page.

Obviously this would be a per-user action, but I'd like to explore what would be necessary to make this happen.

[treee111]

Hi, I also have wandrer.earth connected to my rides but am not a paying user so do not know about maps they create.

During generating the maps we are doing a lot with different OSM "parts". Splitting and merging of land, sea, streets, street names etc. Theoretically, there are a lot of possibilities depending how readable and open source files are.

In the end on the device our generated maps are simple. There is one set of generated maps loaded at a time. No switching, sideloading etc. We "just" replace the original maps with our generated ones.

Do you - in the end - want maps on your device to see where you have not been travelled yet? Assuming this would work, would your usage scenario be the following?
Create maps, go outside ride these roads, have the activity synced to wander.earth and then again: create maps (if it is for the same region), ...

If yes, that would be a per-user and after-some rides action.

[cleeland]

I am also not (yet) a paying user for wandrer; non-paying users can download maps for a limited number of areas a limited number of times to see how it works. I've done that.

We "just" replace the original maps with our generated ones.

That's what wandrer does as well; I was using the term "sideload" to describe that the process of getting the map onto the device doesn't use the wahoo download-through-the-companion-app process.

Do you - in the end - want maps on your device to see where you have not been travelled yet?

Yes, that is exactly the scenario. At some future time I would update the maps to include "the latest" information.

The key is that I would also like to combine the "roads I have traveled" information with the additional information added by the tools in this project.

[treee111]

We have the same understanding, 👍

That's what wandrer does as well; I was using the term "sideload" to describe that the process of getting the map onto the device doesn't use the wahoo download-through-the-companion-app process.

Alright, this is how we add e.g. POIs to the "basic" map.

The key is that I would also like to combine the "roads I have traveled" information with the additional information added by the tools in this project.

I understood and like written in my initial reply, if the wandrer-downloaded files are readable and equal to the files we handle actually, this could be done.

If I got some free hours I might try to download wandrer maps for my area and try to include them.

Do you have a screenshot, pictures or any other information on how wandrer makes the "not-travellled-to" roads visible on the device?

[cleeland]

If I got some free hours I might try to download wandrer maps for my area and try to include them.

I have a zip file of my area that I downloaded in October. I can share that with you if you like, though the zip is large (5Mb) so I'm not sure if it would be good as an attachment.

Do you have a screenshot, pictures or any other information on how wandrer makes the "not-travellled-to" roads visible on the device?

I will try to do that this evening or tomorrow. I have a recent set that I haven't loaded into the bolt v2 yet. I can show you both the original elemnt and bolt v2 since I have both of those.

[Ebe66]

Very nice idea but I'm afraid that (in my opinion) it's not going to be possible.
I made a free account and watched a youtube video on how this "sideloading" works.
They create what we for the Wahoo devices would call cache/temp files. That means that these files are .map files, not some sort of osm files which is what would be needed. You basically can't do anything anymore with .map files.
The only opening I see atm is making a dump as a KMZ/KML and convert that somehow to OSM.

[Ebe66]

Some success already. When downloading the kmz/kml dump of my rides, I got a kmz file. I could rename this to a .zip (it's a zip file) and extract the kml in it. This kml I could convert to osm with gpsbabel. Adding the kay:value in the options dialog of highway:residential for ways. The resulting osm file I could open with Maperitive and, in my case, it contained only the roads I still had to "explore". So with an export and conversion with gpsbabel I would be able to take it further into the mapmaker.

[Ebe66]

The short answer is yes. But it would always entail a few manual steps. See my post above, the conversion to osm with gpsbabel results in a file with negative node/way id numbers that osmconvert does not "like". Solution in a (good) text editor search and replace the - sign with a very large positive number (see the issue on contour lines) after this the file can be converted to o5m with osmconvert and be taken along in the normal cutting and merging procedure. The screenshot below is from a test I did manually with my 50 free rides. This shows the roads still to travel as red (just as an example of course)
I like the idea but at 30 dollar a year...

[treee111]

Hi @Ebe66 thanks for checking that out and as always you found a solution :-)
From reading it, the replacement step might be doable in python as well... I might not dig into that now but rather release the next version with the contour lines, other features & breaking changes.

@cleeland are you still interested in this? If you know a little programming you could setup a developer environment and try to integrated the adjustments mentioned in the last comment. It doesn't need to be a perfect fitting version, I could do the rest of implementing it in the same style as the rest.

[Ebe66]

Hi @treee111 (and @cleeland) , you should know me a bit better by now ;-) I actually already fully integrated it in my version. I thought I had posted it already here but apparently not.
Take a look at my github https://github.com/Ebe66/Windows-Wahoo-Map-Creator-Osmosis The assumption is you generate an export on the Wandrer site in kml\kmz format with "only include roads you have not traveled" selected. Put the export file in the maps folder and you are ready to go.
However be warned that my version is the predecessor of treee111's version and is a lot less "user-friendly". Look at it as an "internal" version.
You can put multiple wandrer exports in the maps folder (for different/larger regions) but you yourself have to take care of removing older export files.

[cleeland]

I am still interested but haven’t had any time in the last month or so to try out setting up the environment to use this cool tool much less a dev environment. Hopefully life will throttle back in a few weeks and I’ll get a chance to try what’s already been implemented.

On Sat, Apr 1, 2023 at 10:08 AM Ebe66 ***@***.***> wrote: Hi @treee111 <https://github.com/treee111> (and @cleeland <https://github.com/cleeland>) , you should know me a bit better by now ;-) I actually already fully integrated it in my version. I thought I had posted it already here but apparently not. Take a look at my github https://github.com/Ebe66/Windows-Wahoo-Map-Creator-Osmosis The assumption is you generate an export on the Wandrer site in kml\kmz format with "only include roads you have not traveled" selected. Put the export file in the maps folder and you are ready to go. However be warned that my version is the predecessor of treee111's version and is a lot less "user-friendly". Look at it as an "internal" version. You can put multiple wandrer exports in the maps folder (for different/larger regions) but you yourself have to take care of removing older export files. — Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJQQR6FHPILAQRTLZ5AETDW7BOIVANCNFSM6AAAAAAUTBCNLA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Chris Cleeland