Web-Route-Planner

Hello Oliver,

I am unclear about the problem you're encountering. I used Komoot to plan and save a route with multiple waypoints. The route was exported as a GPX file, which I then imported into the Locus web planner. However, I didn't observe any points detected during the import process. The GPX file checked afterwards only showed track geometry, not waypoints.

Could you attach a sample of your GPX file for my review? I greatly appreciate your assistance.

Best regards, Ondrej.

No points here ...

Please read my description! The problem does not occur after I have imported the GPX file - everything is still OK. It only occurs AFTER I have changed the route in the LM web planner.

I have already explained this several times - don't you want to understand me?

First of all, thank you very much for your patience and effort in understanding my problem!

Once you have understood it, I am sure it will be improved - even if it takes a while (good things take time).

Just to better understand why I use Komoot for planning - firstly, I have had a lot of planned tours since 2019 that I simply imported into LM. As long as I don't change anything, everything is fine, otherwise... I have already described it.

On the other hand, when it comes to displaying CYCLE PATHS, BRouter and Komoot are really better in this regard! If I set cycling as the sport, I am not interested in hiking trails! Then I want to see cycle paths and *rideable* paths! Depending on the sport, for gravel, gravel (field path, forest path, goods path), for racing bikes only asphalt, for MTB it can also be a trail.

For trekking, preferably cycle paths, asphalt and gravel, then roads, but no trails and never hiking trails, steps or similar!

For clarification, I have attached three screenshots of the web route planners LM, Komoot and BRouter.

It is also quite annoying that a cycle path in LM cannot be used if cycling is set because LM thinks it is a hiking trail... You then have to change the sport to hiking in order to set a waypoint on this path and hope that this will reroute the rest of the route from the cycle path to hiking trails....

If you have set cycling, all routes where cycling is permitted are normally used. Of course, it is possible that something is entered incorrectly in OSM. But then Komoot should not use it either.
You can share such a location here and test the same location with Komoot.

Hm .... and why am I then denied a path that I want to choose - with a waypoint - as long as I have chosen cycling, which can very well be chosen in Komoot? Maybe I'm just confused by all the paths displayed with their colors, which I don't actually want to see.

Hi Olliz,

Thank you for reaching out and sharing such a detailed description with us. I appreciate the effort you put into outlining the issues. Going forward, it would be more efficient to create separate tickets for each concern, as it helps us address each issue more effectively and ensures better readability and maintenance.

1) Routing Issue for Cycling:
The problem you're experiencing with cycling routes not being properly planned sounds like it could be related to the OSM data set or possibly a rare issue on our side. To investigate this further, we would need a specific example. If you could share a planner link or GPX file along with a description of the expected vs. actual routing, it would greatly help us in diagnosing the issue.

2) Hiking Trails Visibility on the Map:
Currently, we offer a combined hiking/biking map theme. In the offline vector maps, you can toggle hiking and cycling routes on or off as needed. However, in the web planner, we use raster tiles, which do not currently support this feature. There are plans to transition to vector tiles for the web planner as well, though this isn't something that will be happening immediately.

I hope you find this information helpful. If you have any further questions or need additional assistance, feel free to reach out.

Kind regards,
Ondrej

First of all, thank you for taking care of my problem. In fact, this is in the web planner, as I only use it to plan, or import planned routes from Komoot or BRouter and change them in the LM web planner if necessary (which unfortunately doesn't work so well at the moment).
Attached are the GPX files and screenshots of an imported route to show what I mean.

Apparently the problem only occurs with imported routes. Because if I create the route directly in the web planner and move waypoint 2, the route is calculated completely correctly.

Hi Olliz,

I apologize for the delay in getting back to you. The issue you're encountering with imported tracks is a well-known one. When dealing with imported routes, such as those from GPX files, we don't have access to the original waypoints used to plan the route. This information is only available when planning directly within Locus Map.

Currently, when recalculating the route, the system does not consider the current path between waypoints. Instead, the router calculates the best route between two waypoints based on the selected routing profile. For imported GPX tracks, we only know the final geometry of the route, not the waypoints themselves. We use a basic algorithm to estimate waypoints, but as you've noticed, this doesn’t always work as expected. We are aware of the limitation, and it’s challenging to resolve in a way that aligns with human expectations.

There’s a related discussion on this issue, which you might find helpful: https://help.locusmap.eu/topic/28008-cant-edit-existing-track-in-webplanner-without-triggering-recalculate-all-2.

For now, some manual adjustments are necessary. You can:

1. Keep the imported track visible on the map or pin it using the eye icon.
2. Open the track/route in the web planner.
3. Select the appropriate routing profile and recalculate the entire route.
4. If needed, manually adjust the route by adding waypoints.

I hope this helps. If you have any further questions, feel free to reach out.

Best regards,
Ondrej

Thanx!

I am glad that I could help :). Can I mark this ticket as "Solved"? Thanks O.

Thanx - yes.