Missed waypoint, reroute takes me back to the beginning.

[Douglas Furlong]

I used the attached GPX file, and used OSMAnd+ to decide the routes between the points, to go on a bike ride.

About 10km's in, I missed one of the waypoints, when I checked my phone, the new route it had calculated took me all the way back to the beginning, forcing me to redo the entire track.

Previously there were options to 'pass along entire track', which I think would have solved my issue. However for the life of me I could not find that option and for the life of me I couldn't find that option in Osmand+ 1.8.

To be honest for me at least, it would be nice to be able to mark way points/route points as visited (ideally automatically).

Does any one have any thoughts about this?

[rhian g]

I have noticed something similar a couple of times on long routes where I had to change due to diversions for road works, Osmand then recalculates including all the waypoints whether passed or not. At one point it took 40 minutes to recalculate a route even though I was, after 5 minutes, back on the original route, and kept insisting I turn around and visit all the waypoints again. 

I solve it by deleting waypoints that are passed forcing recalculations to be from present position to next unpassed waypoint.

[Poutnik Fornntp]

Great trekking application Trekbuddy*  uses for GPX file navigation** feature of forward/backward waypoint stepping, and - this I am not so sure - also to choose closest or user chosen WP as a current one ( then eventually stepped ).

* -  raster maps, originally in Java, controlled by keyboard. Ported to Android as well, where I did not get used to touch control yet.
** - great if Trekbuddy is used with computer screen with arrow graphics and distance to next WP.

Dne pondělí, 8. září 2014 12:22:05 UTC+2 rhian g napsal(a):

[awmross]

I use OSMAnd to follow gpx routes on my bike, and I have had the exact same issue you are experiencing. I posted a message on this previously but didn't get much of a response.

See here: https://groups.google.com/d/topic/osmand/Ttr53SRbm8E/discussion (the second point)

In my experience, "pass along entire track" seemed to make the problem worse; so I'm not sure that is a solution.

The gpx navigation used to work fine in OSMAnd 1.6. I don't know why they changed it. I have considered 'downgrading' to 1.6. There may be issues with doing that though, as the osmand map format changed around that time? (I could be wrong)

In 1.6, it 'just worked'. I never had problems picking up a route halfway.

[EmmEff]

On Sunday, September 7, 2014 8:51:06 AM UTC-4, Douglas Furlong wrote:

About 10km's in, I missed one of the waypoints, when I checked my phone, the new route it had calculated took me all the way back to the beginning, forcing me to redo the entire track.

Previously there were options to 'pass along entire track', which I think would have solved my issue. However for the life of me I could not find that option and for the life of me I couldn't find that option in Osmand+ 1.8.

To be honest for me at least, it would be nice to be able to mark way points/route points as visited (ideally automatically).

Does any one have any thoughts about this?

We are having a related discussion here:

https://groups.google.com/d/topic/osmand/NzlJ5HNTfcM/discussion

Unfortunately, the author(s) have yet to comment on a possible fix. I am not savvy enough to remember features/functionality from previous versions of OsmAnd, but somebody posted that the capability of stepping through a route used to exist and now it no longer does.

Hope this helps,

Mike. 

[Sabra Sharaya]

But after the route is calculated, there is an icon near the bottom that looks like a street sign. If you touch that then you can go through the route one step at a time.

[Mike Frisch]

Thanks. Is this documented somewhere? I still would like to see an option for auto-rerouting similar to what a Garmin navigation device supports.

On Sat, Sep 13, 2014 at 9:33 PM, Sabra Sharaya <sabras...@gmail.com> wrote:

But after the route is calculated, there is an icon near the bottom that looks like a street sign. If you touch that then you can go through the route one step at a time.

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/ShXYkXOiu-c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Douglas Furlong]

On Sunday, 14 September 2014 02:33:24 UTC+1, Sabra Sharaya wrote:

But after the route is calculated, there is an icon near the bottom that looks like a street sign. If you touch that then you can go through the route one step at a time.

I don't see how that is helpful in my situation.

I'm going on an 80km bike ride, I'm not going to memorise each turning to get to my destination, if I were to do that, there are many online tools that I could use.

If I come off the route for a few hundred meters, i would expect the routing engine to take me back to the way point I just missed (or simply the closest one), and then continue routing from there, not to take me back to the very begining.

[Douglas Furlong]

On Monday, 8 September 2014 11:22:05 UTC+1, rhian g wrote:

I have noticed something similar a couple of times on long routes where I had to change due to diversions for road works, Osmand then recalculates including all the waypoints whether passed or not. At one point it took 40 minutes to recalculate a route even though I was, after 5 minutes, back on the original route, and kept insisting I turn around and visit all the waypoints again. 

I solve it by deleting waypoints that are passed forcing recalculations to be from present position to next unpassed waypoint.

That i suppose is an option, I'd need to look at how I've done my routes, as deleting all passed waypoints, would be problematic simply due to the number I'd need to delete (I want to control my cycle route down quiet roads etc).

It would ruin the rhythm of the cycle ride if every 20/40 minutes I had to stop, and delete 5 or 10 or 20 way points.

[Douglas Furlong]

Looks interesting, if way-points could some how be marked as visited (if you've gone over them), and effectively turned off that would be great for me I think.

If that calculation isn't 100% i don't mind having to stop every so often to delete a problematic way point.

I'll keep an eye on that.

[Douglas Furlong]

On Tuesday, 9 September 2014 09:51:33 UTC+1, awmross wrote:

I use OSMAnd to follow gpx routes on my bike, and I have had the exact same issue you are experiencing. I posted a message on this previously but didn't get much of a response.

See here: https://groups.google.com/d/topic/osmand/Ttr53SRbm8E/discussion (the second point)

In my experience, "pass along entire track" seemed to make the problem worse; so I'm not sure that is a solution.

The gpx navigation used to work fine in OSMAnd 1.6. I don't know why they changed it. I have considered 'downgrading' to 1.6. There may be issues with doing that though, as the osmand map format changed around that time? (I could be wrong)

In 1.6, it 'just worked'. I never had problems picking up a route halfway.

 

I believe the routing has been improved by quite a margin, I can now provide a minimal set of waypoints and the software calculates how to make it's way between them, I don't believe that was the case before.

That being said, for me, having the option to either pass along all way points, or pass along waypoints from here (as opposed to pass along entire track/ pass along way points from here) would possibly fix my issue.

Do we know if the developers spend much time looking on these forums?