BRouter: viaX-position not mapped

[WolfgangZ42]

A strange behavior of BRouter.
First my BRouter mapping - updated today:

Import this file into Cruiser: F_1-a1b.zip
Moving any waypoint (without actually moving it) then results in:

Routing-Service = **BRouter(offline)** Routing-Service = **BRouter**

Any Idea?

[devemux86]

@WolfgangZ42 thanks for the report.

Moving any waypoint (without actually moving it)

This is a nice trick that forces the app to recalculate the route!
So it tries to recalculate it with the selected profile + service + settings.

As we discussed in #169, the message from BRouter (offline):
"BRouter: via3-position not mapped in existing datafile"
means that the mentioned waypoint cannot be attached to the nearest road.

In case of BRouter website the result seems the same.

What routing profile and settings do you use?
Have you tried to zoom in and move slightly the waypoint?

[WolfgangZ42]

Have you tried to zoom in and move slightly the waypoint?

Sure I did that with waypoint 3 - unsuccesfully.

[WolfgangZ42]

My pref: #T.zip

[0709wiwiwi]

"motor" or "car".brf does not correspond with

highway track
track type grade3
https://www.openstreetmap.org/way/129757725

It needs this extra:
motor_vehicle yes
motor vehicle yes
motorbike yes
https://www.openstreetmap.org/way/40109540#map=15/46.4967/12.7962

[WolfgangZ42]

Willy, both of the OSM parts you mentioned are accepted in the whole route: Christians_Alpentour.zip
My example above is just an extract of this route.

The whole story is:

• Christian gave me his route with over 100 waypoints and the BRouter message
• He wanted two parts bridged by direct line
• I erased unnecessary waypoints in kurviger.de to ~20 to save the enormous calculation time
• Then I inserted the "beeline" parts
• After that the BRouter message was gone
• But still there even in parts of the original route

My (or better: Christians) Problem is solved - but I thought it's worth investigating. My pref: #T.zip

[0709wiwiwi]

It will possibly be more comfortable by multi profiles per track section.

Except for a beeline section currently a default profile applies to the entire track :-((

You could then probably overcome difficult parts in a traject without "must" use beeline(s).

Provided, of course, that a path is already drawn in osm.

The Zossebart reroute profile that I am just testing is attached
reroute.brf.txt
I have assigned it in the Brouter app to Foot shortest.

[devemux86]

I asked @afischerdev and as always he is very helpful! 👍

There is the profile parameter waypointCatchingRange with default 250.

[devemux86]

Next Cruiser will allow to change the BRouter waypointCatchingRange parameter inside Cruiser settings.
Local tests with a range > 250 m show successful routes with waypoints far from the road network.

What maximum do you think we can have, 1 km or more?

[devemux86]

Next Cruiser will also allow to change the BRouter correctMisplacedViaPointsDistance parameter (to avoid u-turns) in Cruiser settings.

What maximum do you think we can have, 100 m or more?

[0709wiwiwi]

correctMisplacedViaPointsDistance

100m max ok.
@WolfgangZ42 ok?

[WolfgangZ42]

I think my (or better: Christian's) problem had nothing to do with this distance. Rather, kurviger.de has allowed a route that is rejected by BRouter when recalculating - until now I thought Kurviger was more restrictive. Should the situation arise again, we will work consequently without recalculation.
So the default of 250 m for WaypointCatchingRange seems to me to be sufficient.

[devemux86]

@WolfgangZ42 your report seems indeed like a tags issue.

However it is convenient to have a more flexible range for waypoints.
It happens to place waypoints far from the road network and BRouter then complains.

[WolfgangZ42]

Short supplement: the route Sauris.gpx.txt works if use_tracks is enabled in options. After disabling it the error message appears again "... viaxx-position not mapped ..."
Hint: if you ride on gravel roads don't forget to switch on use_tracks ❗

[0709wiwiwi]

Nice example of a gpx navigation track. By avg speed 70.1 kmh.
Anyway I noticed that at Shaping Point 11 the U-turn is missing
When I recalculate with the Brouter offline the U-turn is attached.

[devemux86]

BRouter settings for "Waypoints search range" and "Correct misplaced waypoints" are available in Cruiser 3.0.20.

Available in "Settings | Routing | BRouter | Advanced" or search settings for "brouter".

[Cer-o]

Murcia - Mojácar.gpx.zip
Good morning. I have also suffered this problem when importing different routes, such as the one I attached.
After reading the thread, the cause and possible solution to the problem have not been clear to me.

[Cer-o]

I have repositioned point 48 in the center of the road and the error has been reproduced again.
I have increased the setting you have indicated to me to 500 and the error has disappeared.
Thank you so much.

[devemux86]

@Cer-o

I have repositioned point 48 in the center of the road and the error has been reproduced again.

There is probably a barrier / gate / seasonal closure on the road of point 48?

You can enable the following BRouter setting and try again:

[Cer-o]

I have reverted the distance to 300 meters and checked the ignore barriers, but the error has reproduced.
I have redialed the distance of 500 meters and the error has disappeared.

[Cer-o]

La pista gpx presentada es una pista simple grabada. En algunos lugares allí donde se grabaron algunas salidas y vueltas. Esta pista simple grabada no contiene instrucciones de giro. Por lo tanto, debe limpiar y reconstruir una pista de navegación y, por lo tanto, mostrar la pista simple grabada como referencia visual para afinar su diseño final.Si te gusta el resultado puedes guardarlo como un gpx navtrack. En el conjunto de exportación gpx, la navegación inclusiva.En una importación posterior de gox navtrack, seleccione automático.

Se adjunta un gpx navtrack importable. Cero_20230604_134039.gpx.txt

Quitar el .txt

Hello and thanks for your help.
Due to my limited knowledge and the translation, I cannot understand you.

[0709wiwiwi]

Ok nuevo intento.

1. El track gpx que has mostrado es un simple track record gpx.
2. Un track gpx simple no contiene instrucciones de navegación.
3. El track grabado contiene errores en los que te metes en una carretera falsa, que luego se corrigen con un retorno.
4. El track probablemente también indica algunas rutas a miradores seguidas de un retorno.

Utilice este track grabado como ejemplo visual para diseñar un NUEVO track de navegación.
Cruiser puede hacer esto parcialmente de forma automática para usted, pero no 100% perfecto.
Por lo que debe comprobar el resultado de algunos errores y corregirlos manualmente.

Una vez que el NUEVO diseño esté a tu gusto, puedes usarlo para navegar.
O puedes exportarlo como un archivo .kurviger o archivo navtrack gpx para su posterior reutilización.

Traducción realizada con la versión gratuita del traductor www.DeepL.com/Translator

[0709wiwiwi]

For example, if we set it to 500m then the import works: (perhaps we need to set a larger value as default)

A higher tolerance for motorcyclists could potentially be practical.
For pedestrian routing, you would better check why a position has been refused.

Note:
Presets can perfectly take care of such individual transportation or vehicle distinction rules.

[devemux86]

Important is that all other routers operate with large waypoint search ranges.
BRouter seems to be more restrictive and this is causing problems to users.

We definitely need to think about the user convenience with a larger range.