This object is in archive!
Start & end of route not using the obvious road
Not a Problem
See video here.. When I add a second routing point #2 with BRouter car profile (although any profile has same problem) the router proposes an off-road straight line track instead of following the obvious road. It only seems to happen if the route is on a small road. This never used to happen in versions before the new Route Planner. It means I can't properly create a full end-to-end route when starting and/or finishing on smaller roads.
The same problem 
Hi Andrew
it seems BRouter (or other OSM based router) car profile considers the small route impassable by car. Locus doesn't calculate routes on its own, it always uses calculations of external services so it's not a matter of Route planner.
best regards
Michal
Hi Andrew
it seems BRouter (or other OSM based router) car profile considers the small route impassable by car. Locus doesn't calculate routes on its own, it always uses calculations of external services so it's not a matter of Route planner.
best regards
Michal
Hi Michal. I don't think this is true. As I said A) the routing used to work before Route Planner was implemented B) any BRouter profile shows same problem, not just car. Menion has also mentioned in the beta forum some dirty hack related to this issue i.e. it is a known issue. So I want to "kick it along". Here is BRouter web link: http://brouter.de/brouter-w....
Hi Michal. I don't think this is true. As I said A) the routing used to work before Route Planner was implemented B) any BRouter profile shows same problem, not just car. Menion has also mentioned in the beta forum some dirty hack related to this issue i.e. it is a known issue. So I want to "kick it along". Here is BRouter web link: http://brouter.de/brouter-w....
Hello,
I also don't think, this is related to Route planner. You will get same result when using "Navigate to" function.
What Locus do incorrectly on your video, is that it connects requested start point with returned start point of BRouter routing. Fact that it ignores small road is more a problem of combination of used profile & BRouter version & it's data. Suggest to try it with later Locus Map Beta version (where are now after more then year updated internal BRouter profiles) and also suggest to download latest BRouter and it's routing data.
Hello,
I also don't think, this is related to Route planner. You will get same result when using "Navigate to" function.
What Locus do incorrectly on your video, is that it connects requested start point with returned start point of BRouter routing. Fact that it ignores small road is more a problem of combination of used profile & BRouter version & it's data. Suggest to try it with later Locus Map Beta version (where are now after more then year updated internal BRouter profiles) and also suggest to download latest BRouter and it's routing data.
Here is a funny one in 3.27.1.4 with latest BRouter & data. Points #1 and 2 are only 100m apart but BRouter decides to go direct from #1 to A6 highway over longer distance, and direct from B64 main road to final point #2 over even longer distance. Possible with helicopter but not even 4WD ;-)
The correct route is calculated for non-car profiles and the slope coloring is working very nicely!
Here is a funny one in 3.27.1.4 with latest BRouter & data. Points #1 and 2 are only 100m apart but BRouter decides to go direct from #1 to A6 highway over longer distance, and direct from B64 main road to final point #2 over even longer distance. Possible with helicopter but not even 4WD ;-)
The correct route is calculated for non-car profiles and the slope coloring is working very nicely!
Nice Andrew, thanks.
When you disable Locus-based routing profiles and use BRouter default profiles, it works correctly. So it seems that it's something in Poutnik's profiles.
Libor, is there any reason why your latest "Car-FastEco" profile completely ignore this route https://www.openstreetmap.org/way/88775762 ? I'm no expert in these OSM stuff.
Nice Andrew, thanks.
When you disable Locus-based routing profiles and use BRouter default profiles, it works correctly. So it seems that it's something in Poutnik's profiles.
Libor, is there any reason why your latest "Car-FastEco" profile completely ignore this route https://www.openstreetmap.org/way/88775762 ? I'm no expert in these OSM stuff.
I Will look at it at home.
But for now, I highly suggest the new Arndt's standard car fast and eco profiles, based on kinematic model. They seem to me very good. I have just added the toll free modification I will upload later.
I Will look at it at home.
But for now, I highly suggest the new Arndt's standard car fast and eco profiles, based on kinematic model. They seem to me very good. I have just added the toll free modification I will upload later.
Replies have been locked on this page!