Use shaping points by default

[0709wiwiwi]

Concerns specifically the BRouter Essbee web version.

@EssBee59 cc @afischerdev

The Brouter web essbee version most simply offers an export by the new Locus_Cuiser TBT track format.
Great ! Anyway one item can still simply be optimized.

• Do not by default set trkpt <sym>pass_place **<type>via** but **<type>shaping**
  Except for the first and the last tkrpt or if planned as announced via point in the navigation.

• A <sym>pass_place <type>via is announced in the navigation.

• A <sym>pass_place <type>shaping is not announced in the navigation.

• Example a by Brouter essbee web converted track into a TBT navtrack.

Wellen - 162.5km.gpx.txt

The multiple <sym>pass_place <type>via are all announced without any use.

The next TBT navtrack provides the optimized version.

Wellen - 162.5km_shaping.gpx.txt

Navigates without multiple unnecessary annoying announcements.

Update.
Please stick to the question asked. The prefered reference web version to test is the Essbee web version.
The Essbee version is the only one that fully respects the set export mode. Simply put, you cannot press the wrong button.
The optimization will probably have to take place in the BRouter core. That is why Alex is in cc.

[devemux86]

BRouter website also exports GPX navigation tracks.

Press the cloud button in the export route screen:

[EssBee59]

If I understand right: the request concerns the "Export track" function of a Brouter-web using the option "turnInstructionMode=Locus-style (new-mode)?
I think, there is no difference there between the "brouter-web" and the "essbee" instances of brouter-web!
(both are using the same brouter as backend and the gpx+ turn-instruction are generated by the brouter backend.

Did you checked (or compared gpx) a track-export using brouter-web?

[devemux86]

brouter-core module generates the GPX files and all other formats.

[EssBee59]

And brouter-core is part of the brouter backend there! Emux ***@***.***> schrieb am Mo., 20. Okt. 2025, 13:09:

…

*devemux86* left a comment (abrensch/brouter#847) <#847 (comment)> brouter-core module generates the GPX files and all other formats. — Reply to this email directly, view it on GitHub <#847 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL75PSDLJNXSHNXXMFTQNCD3YS7H5AVCNFSM6AAAAACJVC5Q22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRRGYZDCMZQGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[0709wiwiwi]

You have to use that cloud button, and then you have to deal with that pop-up, so not ideal.

In the Bikerouter, you can't even export the mode by the cloud button. It is so not correctly applied. (Reported, without result)

Only the Essbee version deserves praise in this regard.

@EssBee59

• Regarding the actual question and request.
  The BRouter.de version also exports these multiple trkpt type via, instead of the prefered type shaping.

[afischerdev]

Lets go back to the core BRouter lib and the main idea.
We could change this for the Locus export (export number 2) like this

• start/end point get a via
• BRouter via points get a shaping
• points with a name or a marker 'visite this' get a get a via
• voice hints get the same marker as before

@devemux86 @menion
This affected Locus and Cruiser. What do the developers think about this?

[devemux86]

@afischerdev Good plan. 👍

a marker 'visit this'

What is this?

[afischerdev]

@devemux86
These are other words for via points
In BRouter internal logic all points are via points,
but the meaning is shaping points and so they can moved by the misplaced function.
At the moment incoming points with names are handled as - in your words - via point and so they are not moved.
But we already discussed unnamed points the should work as - in your words - unmoved via point. Please see here

[menion]

I have nothing against it, thanks.

I do not know if @devemux86 uses a similar system in Cruiser, but I may confirm this solution.

Just to summarise it:

• Points that are important to the user should be marked as "via point". The app should notify them during navigation and deal with them also during recalculation.
• Points that help "shape" the route and where navigation announcement is not needed during the ride should be marked as "shaping".

Minor info: in the case of Locus Map, also the start and end points may be marked as "shaping". It is not important and the result should be identical.

[0709wiwiwi]

In Locus Map, also the start and end points may be marked as "shaping". It is not important and the result should be identical.

Also in Cruiser the start and end points may be marked as "shaping" just as well. The result should be identical.
In the Cruiser app exports the start and end points are usually marked as "via". Add a name or none is optional.

To know.
The current Locus map app only detects a via or shaping point by using the Locus specific sym pass_place.
Unlike Cruiser the via or shaping point in a trkpt sym u-turn type via_shaping combination is skipped by Locus. :-((

• You can navigate using even the most simple TBT navigation track.

TBT_only.gpx.txt

Without any route planner via or shaping point references, do not recalculate ! ! !
If you trigger a recalculation (manually or automatically), that round trip could be VERY short.

[afischerdev]

I would like to stay with the type via point for start and end point.

As you see here, the sharping points are corrected to the next junction, via points stay at its origin position.

[afischerdev]

And the GPX for this - with export way point and export corrected points

testtrack0.gpx.txt

[afischerdev]

Here a GPX file using beelines at start, end and in between. And the other point types as well.

testtrack0.locus.gpx.txt