Manual Route Plannung

Settings > Routeplanner > Hamburger Menu (top right) > Routemenu > Settings > Via Point as standard: Unselect

Via points as standard is unselected, but still additional points on manual segments are created.

3 Points/segment extra ? Strange

Can you share an example result by an exported gpx file ? (attach here)

Share a screen record (dropbox share or other service) of your precise actions in the routeplanner ?

Sorry, it is actually not 3 points per segment, but many points depending on the length of the segment. In my first tries I only used short segments causing on interior point. For longer tracks/segments there are more interior points per segment.

I will upload an example later today.

Hi,

the route in manual mode is divided into interpolated segments due to calculation of its elevation profile. These segments number can be reduced in Locus expert settings (https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings). What problems do the segments cause?

best regards

Michal, Locus team

Aha Michal, maybe you've indicated a possible issue. (Let's wait that example gpx file).

Can it be Malte that you expect to create a route(rte) by only few reference rtept's connected by straight lines ?

Export as (rte)gpx ? So the external (Garmin) gps or application (Mapsource_Basecamp) does the routing "by recalculate" for you ?

While playing around with the routing, I noticed that the intermediate points are used and needed for the elevation profile.

@0709, you are right. My idea was to create basic tracks (or routes) for routing on a garmin device. The intermediate points (not beeing on any road) destroy the routing.

@Michal, thank you for pointing to the expert settings. This certainly helps. Setting the route interpolation step value to a large number like 10 km avoids intermediate points. But, for segments shorter than this value the blue line is not drawn during routing. Only after saving the track all segments are shown. This is also true for the default setting of 100 m, here it is not so obvious as segments shorter than 100m are not often used (see attached screenshot).

Do you still want to see an example gpx file or screencast? For me the original question is fully answered. The missing segment line is a different issue, maybe a bug or a feature....

Thanks for your help,

Malte

Hi Malte. (No example file necessary)

Nice..that was however an unexpected use case. OMG ...Oh My Garmin ;-)

The missing connect lines ? I noticed too. Locus team sure will pick up this issue and correct ;-)

Advise..to avoid unexpected track_route 'glitches' in the recalculated results.

Put the rtept's reference points always a little away from road_street junctions !

Find more: https://ridewithgps.com/help/incorrect-cue-sheet-entries

(Locus does not generate you a warning as the RWGPS web routing service does)

Hi Malte, I suppose constructing "New Idea" would be attractive.

Produce design inclusive resulting track path view in the Locus planner.

@ export select service (1) usefull for Garmin gps.

Your Opinion ?

@ Export Select:

1. Track as (rte) Route. (Both Start and Finish Point are Via Points !) (Flag)

The export contains ONLY the rtept (Info) Via Points.

The Via Points are attached into the rtept's.

OR:

2. Export as "Direct" (rte) Route. (Both Start and Finish Point are Via Points !) (Flag)

a. (Un)set: Inclusive Nav Points ? Y/N.

The export has the same point density as a track !

Via Points AND Navigation points are attached into the rtept's.

1. Usefull for (Garmin gps) use cases. (Results can be different because of other routing profile)

2. *Optimalised for Locus to Locus transfers. (WYSIWYG)

1. Calculate by Locus: https://youtu.be/P0POD0d6uOY

1. Calculate by Mapsource: https://youtu.be/C9A5RHpsS4Y

Example files attached.

* https://forum.locusmap.eu/index.php?topic=5953.msg49519#msg49519

Hello Malte,

thanks for pointing on this "issue".

I'm thinking about the current solution and to be true, can't say that it's bad. In the case of manual drawing, app really interpolate new points along the segment in the defined interval. These points are useful for more precise chart and also helps during navigation.

Diss-advantage?

- increased the size of the database because points are stored in internal database

- some problems as you describe: well, can't say that your issue is something we may care about because exporting routes created in Locus Map to other devices is definitely a rare use-case compare to its advantages.

So not sure if there is any better solution for now.

@Menion, I am absolutely happy with the option to define the interpolation density. I did not know about it and was hoping for such a solution to control the behaviour depending on the use case.

Thanks for your help, everybody!