Import GPX track as route without calculation

[0709wiwiwi]

Proposal: Create a starter navtrack.

Import a normal track.
Menu Import > Overlay + route.
NEW !
Waypoints slider Left (0). Triggers no calculation !
The next slider step is the current minimum (2)
Expected result.
Add a sym pass_place plus type via in the first and last trackpoint.
Done.
A realisation is probably relatively simple.
What purpose should it serve ? TEST.
Find a more optimal track conversion into a TBT navtrk
It makes some test I want to do more easy.

[devemux86]

@0709wiwiwi Thanks for the suggestion.

GPX nav track is a file format, not to be confused with routes,
that can be used in navigation or other app purposes.

Import a track, not as overlay but as route, must produce a route,
that then can be exported in any format.

If routing step is skipped, then the only possible result would be a "route"
with 2 waypoints, geometry the track geometry and no turn instructions.

Do you mean something like that?

[0709wiwiwi]

correct.

[devemux86]

@0709wiwiwi

This process produces a route without turn instructions, so users may be confused by the result.
They will not understand that afterwards they need to run "Add shaping points" and "Recalculate route".

Should this type of import include these automatic steps?

• Add shaping points (with a fixed distance)
• Recalculate route
• Add a beeline to the sections of the route that cannot be calculated

So that in the end there is a result that users can understand as a real route?

[0709wiwiwi]

Agree with your suggestion Emux.

After more tests nicely staggered shaping points are fine.
Tests done by the tracks from Motortreffens
First I merged and bound the multi tracks into a single one segment track.
Calculations with 1 km distance shaping points run smoothly.
For cycling or hiking routes, closer is possibly more optimal?

The BRouter calculated sufficiently fast even with 400 shaping points.
Still errors do occur but these are more detectable

1. The standard RED u-turns.
   Activate the Misplaced Via Points tool to solve.
2. Other anomalies and so RED u-turns are more annoying.
   • If shaping points fall on the returning lane, the router sends you back and forth while at traffic circles an extra round can be calculated. The import section distance and the recalculated section distance is then significantly different.
     If a section distances is a significantly different then color the corresponding shaping points red ? Shifting a false red shaping position ensures a correction by recalculation.
3. Beelines for non routable sections ? Still no idea how to automate this.
   Alex may be able to give some input. Cruiser performs what the BRouter offers.

[devemux86]

@0709wiwiwi

Beelines for non routable sections ? Still no idea how to automate this.

This can be possible if route is calculated section by section (like in BRouter website).
But then the correct misplaced waypoints cannot work.

So the whole process becomes a bit complicated.

[devemux86]

A better alternative than selecting a fixed number of waypoints (like now 2-200),
is offering an additional selection with distance between the added waypoints in the import screen.

Like the existing slider in the "Add shaping points" screen.
And then let the import do its calculations as it does now.

[devemux86]

Or replace the existing slider with the max number of waypoints,
with a new slider with the distance between the added waypoints (in the import screen).

[devemux86]

Waypoints slider Left (0). Triggers no calculation !
The next slider step is the current minimum (2)

@0709wiwiwi Let's try this idea in the next update and see if there is interest.

• Import a GPX track
• Set the waypoints slider to the far left and label "Without route calculation" appears
• The track is imported without calculation as a simple route with the exact track line

Then we can add shaping points manually or using the "Add shaping points" function,
calculate only the sections we like and start navigation on the track.

[DolomitesTom]

Sounds useful

[devemux86]

• Available in Cruiser 5.5.2 #820