Routing in the wrong direction
Quote from Clif on 10.09.2020, 04:22I created a circular route on Basecamp and imported into Scenic. On following this route anti clockwise I was forced to make a detour because of a road closure. I made my way to a point on the route much further along (I could not use 'recalculate' as the road closed was the only road in the area and the app continually tried to take me back to the beginning of the closure).
On re-joining the route the app tried to take me in a clockwise direction (ie back to the start) rather than anti-clockwise to continue my journey. I've had this problem several times before when a route crosses over itself - rather than continue on the route the app tries to take the other (wrong) option. Other times when I leave the route and come back onto it the app can take me in either direction. In a sense the app doesn't differentiate what direction I'm actually travelling.
Is it a problem with waypoints?
Can you help please. Thanks
I created a circular route on Basecamp and imported into Scenic. On following this route anti clockwise I was forced to make a detour because of a road closure. I made my way to a point on the route much further along (I could not use 'recalculate' as the road closed was the only road in the area and the app continually tried to take me back to the beginning of the closure).
On re-joining the route the app tried to take me in a clockwise direction (ie back to the start) rather than anti-clockwise to continue my journey. I've had this problem several times before when a route crosses over itself - rather than continue on the route the app tries to take the other (wrong) option. Other times when I leave the route and come back onto it the app can take me in either direction. In a sense the app doesn't differentiate what direction I'm actually travelling.
Is it a problem with waypoints?
Can you help please. Thanks
Quote from Guido on 10.09.2020, 08:56Hi Clif,
I'm afraid this is a know problem with the current routing provider, where, when the route crosses itself, it gets confused and usually assumes you are on that crossing the 'second' time. With full round trips (start and destination less than 300 meters apart) I tried to work around this by loading the first half of the route at the beginning and only when reaching the midway point the second half is loaded.
To completely resolve this, I'm currently working on Scenic 3. Scenic 3 will switch to a new routing provider which does not have this problem. Scenic 3 is planned for the start of next motorcycle season.
I know this is probably not the answer you were hoping for, but for now, this is the best I can do. What I can recommend for now is follow:
- Make two routes for round trips
- When running into a blocked road, use the 'blocked road' button in the navigation menu (big button menu).Best regards,
Guido
Hi Clif,
I'm afraid this is a know problem with the current routing provider, where, when the route crosses itself, it gets confused and usually assumes you are on that crossing the 'second' time. With full round trips (start and destination less than 300 meters apart) I tried to work around this by loading the first half of the route at the beginning and only when reaching the midway point the second half is loaded.
To completely resolve this, I'm currently working on Scenic 3. Scenic 3 will switch to a new routing provider which does not have this problem. Scenic 3 is planned for the start of next motorcycle season.
I know this is probably not the answer you were hoping for, but for now, this is the best I can do. What I can recommend for now is follow:
- Make two routes for round trips
- When running into a blocked road, use the 'blocked road' button in the navigation menu (big button menu).
Best regards,
Guido
