nogo points and custom routing profiles
Solved
When I use custom routing profile with LoRouter (for example, "shortest.brf" from Brouter added to category "Walking"), router avoid absolutely all nogo-points, even nogo allowing all usage.
I expect that if custom profile configured as "Walking" - it use only walking-blocked nogo, if configured as "Cycling" (as "MLD" on my screenshot) - only cycle-blocked nogo.
The same problem 
"Shortest" always delivers the same routing result, regardless of the category under which you add it. This is the shortest possible route when walking. You can also add the "car eco" profile under Walking, for example, but it remains "car eco" and does not route via footpaths.
No-go areas are therefore always regarded as a block, regardless of what is set there. I think that shortest does not differentiate between the categories (walking, cycling, car) and cannot take the no-go settings into account.
"Shortest" always delivers the same routing result, regardless of the category under which you add it. This is the shortest possible route when walking. You can also add the "car eco" profile under Walking, for example, but it remains "car eco" and does not route via footpaths.
No-go areas are therefore always regarded as a block, regardless of what is set there. I think that shortest does not differentiate between the categories (walking, cycling, car) and cannot take the no-go settings into account.
Imagine, that I use not "Shortest", but "My own best walking profile" (result will be the same).
Please, explain me, what I neet to do, to get this profile ignore car/cycle-avoided nogo-s?
Or you can just extract any internat brf-file from Locus, add it as custom profile - and get the same problem.
Now, all custom profiles allways avoid all nogo-s - regardless of profile / nogo settings. And that's a problem.
Imagine, that I use not "Shortest", but "My own best walking profile" (result will be the same).
Please, explain me, what I neet to do, to get this profile ignore car/cycle-avoided nogo-s?
Or you can just extract any internat brf-file from Locus, add it as custom profile - and get the same problem.
Now, all custom profiles allways avoid all nogo-s - regardless of profile / nogo settings. And that's a problem.
Hi Evgeny,
issue simulated, thanks for reporting it. Forwarded to the devs.
Hi Evgeny,
issue simulated, thanks for reporting it. Forwarded to the devs.
Fixed, please wait for a new version.
Fixed, please wait for a new version.
Replies have been locked on this page!