Routing over online/internal BRouter

[0709]

I understand  the request Erelen. But guess what. In the Kurviger (motorbiking) forum some users do explicitely ask to be able to do NOT.
Because they want to prepair and  plan routes in wintertime  to be used than for the next summer holiday bike tours. As recently in France and Italy there where severe damages on roads by bad wetter conditions (completely destroyed even not existing roads anymore) where a user planner than does hope will be repaired sooner or later. Users that want to take some planning risk and when summer finally arrives double check if in the meanwhile the conditions are changed yes or maybe not. In my country we are constantly repairing, a nicely finished road is more and more just to become an exception ;-)  The trenches that were so many in our area in WW1 have now been spread all over our country.

[Radim V]

Please, block routing thru highway=construction in all profiles.

I see, will do also another lifecycle tags, thanks :-)

[0709]

@ Radim V
U- turn navigation instruction generation through Locus (B)Router missing command

Non-directional navigation instruction U-turn instruction delivered by the GraphHopper (-98) router has been nicely supported in most recent Kurviger.
After a non-directional U-turn you return over exactly the same out and return path and thus make a perfect 180 ° trackpoint turn.
In Kurviger you so do find the combination of a Shaping or Via Point together with the U-turn command sharing the same identical track point.

Notification Difference:
With a Shaping Point you only have a U-turn command message.
Example TTS: After 60m Return
With a Via Point you have a combined message: Via Point <name> followed by U-turn command.
Example TTS: After 60m Nice Viewpoint, Return.

Locus does not generate nor use, not even by using the online GraphHopper Router service.
And BRouter does not generate the non directional U-turns.
Question:
Is there a possibility in Locus LM4 with the internal Brouter to generate this as such and to use it?
In picture: See Icon difference. Non-directional U-turn is without arrow, directional U-turns with arrow.
On the left the Locus <sym> command, on the right the corresponding GraphHopper command.

[Radim V]

@ Radim V
U- turn navigation instruction generation through Locus (B)Router missing command

Non-directional navigation instruction U-turn instruction delivered by the GraphHopper (-98) router has been nicely supported in most recent Kurviger.
After a non-directional U-turn you return over exactly the same out and return path and thus make a perfect 180 ° trackpoint turn.
In Kurviger you so do find the combination of a Shaping or Via Point together with the U-turn command sharing the same identical track point.

Notification Difference:
With a Shaping Point you only have a U-turn command message.
Example TTS: After 60m Return
With a Via Point you have a combined message: Via Point <name> followed by U-turn command.
Example TTS: After 60m Nice Viewpoint, Return.

Locus does not generate nor use, not even by using the online GraphHopper Router service.
And BRouter does not generate directional U-turns.
Question:
Is there a possibility in Locus LM4 with the internal Brouter to generate this as such and to use it?
In picture: See Icon difference. Non-directional U-turn is without arrow, directional U-turns with arrow.
On the left the Locus <sym> command, on the right the corresponding GraphHopper command.

Hi, this is something to look into, but currently, there are much more pressing issues to cope with, sadly.   

[zossebart]

May I ask where the Lo* - profiles originate from? Clearly, they are not all from brouter default profiles? I assume some of them are based on poutniks profiles? Or did you create them all from scratch?

Do you plan to create issues and/or pullrequests in the corresponding source github repos for changes users suggest here? Or do you plan to maintain your own (proprietary) modified versions? Because if the former, other users could benefit as well from improved profiles.

And while you are at it: could you please reconsider (optionally) supporting ALL profile parameters instead of only your whitelist? I wrote this before: I think it's ok to use the whitelist as a default. But you could add a setting in expert settings to enable support for all parameters (for power users). I think it is ok to display the description texts from the profile instead of the translations Locus offers for the whitelisted parameters.
I recently enhanced my profile with yet another (non-whitelisted)parameter which significantly changes routing when altered. Without this parameter supported by Locus (unlike e.g. brouter-web), I'm forced to create even more variants of the profile with this parameter set to different values.

I hope you get my point.

regards,
zossebart