Can't select route segment
When I trying to use route planner with BRouter
sometimes happens situations when route segrents switched to a state, when it's impossible to select them.
Here is the steps to reproduce the issue:
1. Choose BRouter as route provider in the Settings.
2. Go to route planner
3. Select any car profile (fast or eco)
4. Choose first point
5. Choose second point. It should be pretty far from the first 1000 .... 2000km. (After this step, route planner will start route calculation for the first added segment.
6. While route calculation process is in progress: add thirt route point (by long-tap on the screen).
And here is to ways to reproduce the issue:
- Manually inperrupt route calculation by tapping (X) button on screen.
- First route segment must be very long more that 3000km, so BRouter will fail due to timeout.
In both cases. All route segments which was added while BRouter worked on calculation of first segment, will switched in state when user can't select them.
Here is the video which illustrate the issue.
Sorry for a long video.
The same problem 
We've modified the way Locus Map handles BRouter timeouts so the resulting behavior is improved, PLease wait for the next app version.
We've modified the way Locus Map handles BRouter timeouts so the resulting behavior is improved, PLease wait for the next app version.
Hi Andrey,
a route segment can be selected by tapping the segment point:
As for your routes - BRouter is not capable to calculate such long journeys. It is effective up to 200 km and is more suitable for cycling routes than for car or motorbike routes. I would prefer GraphHopper for this usecase.
best regards
Michal, Locus team
Hi Andrey,
a route segment can be selected by tapping the segment point:
As for your routes - BRouter is not capable to calculate such long journeys. It is effective up to 200 km and is more suitable for cycling routes than for car or motorbike routes. I would prefer GraphHopper for this usecase.
best regards
Michal, Locus team
Hi Michal,
No, the issue is there.
And here is video which shows how to reproduce it:
https://www.youtube.com/watch?v=6-aD04QpBAs
Andrey.
Sent from Mail for Windows
Hi Michal,
No, the issue is there.
And here is video which shows how to reproduce it:
https://www.youtube.com/watch?v=6-aD04QpBAs
Andrey.
Sent from Mail for Windows
Hi Andrey,
BRouter is not optimized for calculating distances thousands of kilometers long. The issue relates to this - BRouter ends up with "time-out" and blocks calculating other segments, resulting in the segment that is still on the map but can't be selected. Use GraphHopper instead or create shorter routes - max 200 km.
Michal
Hi Andrey,
BRouter is not optimized for calculating distances thousands of kilometers long. The issue relates to this - BRouter ends up with "time-out" and blocks calculating other segments, resulting in the segment that is still on the map but can't be selected. Use GraphHopper instead or create shorter routes - max 200 km.
Michal
I think here you just ignoring the problem.
Obviously it’s not a BRouter who locks and unlock segments.
Its only about now your code handle such case.
As you can notice from my recent video,
There was no BRouter fails due to timeout.
Each time I interrupted route calculation manually via pretty legal way “by tapping (X) button on the screen)”.
And after that I’m getting locked route-segments. And this is bug. Definitely.
I think here you just ignoring the problem.
Obviously it’s not a BRouter who locks and unlock segments.
Its only about now your code handle such case.
As you can notice from my recent video,
There was no BRouter fails due to timeout.
Each time I interrupted route calculation manually via pretty legal way “by tapping (X) button on the screen)”.
And after that I’m getting locked route-segments. And this is bug. Definitely.
We've modified the way Locus Map handles BRouter timeouts so the resulting behavior is improved, PLease wait for the next app version.
We've modified the way Locus Map handles BRouter timeouts so the resulting behavior is improved, PLease wait for the next app version.
Replies have been locked on this page!