Osmand useless for GPX navigation? want return to missed waypoints

[limom...@gmail.com]

I was happy to find Osmand as a great navigation software. Worked well for hiking with gpx tracks.
But using tracks for the motorbike is a hassle. If I miss for several reasons a waypoint, it wants me allways to make a U-turn.

Is there any solution that a waypoint can be ignored?

Or maybe making the waypoint larger so it can´t get missed?

I use open street maps. Maybe it helps to use another map?

Would it help to have more waypoints in the track?

[Majka]

Even when navigating along the gpx, you can simply ignore the instructions and the navigation will sooner or later recalculate the remaining part of the route. Did you set OsmAnd as navigation software (in the navigation settings)? Even if you want to use predefined gpx routes only, set it up to allow for re-calculating.

What version of OsmAnd are you using? I did use the navigation along the gpx route in the past, but it is much easier and simpler to use the gpx just for setting the waypoints and leave the app do the navigating. With few exceptions (closed roads with conditional access), there isn't much reason for me to "force" an exact route. With the correct settings, I get almost always exactly the route I would choose for myself.

For me, the way to go would be less waypoints, not more, and leaving the app to navigate from waypoint to waypoint for the remaining ones. If you can ignore a waypoint when you missed it, it can be almost always left out from the route completely (leaving it to the navigation, if you go through or not).

Just as a note - I stopped using gpx route for navigation for hiking, bicycle and for car. With correct settings for each navigation mode, it was simply not necessary.

[limom...@gmail.com]

I open the OSMAND+ app and start navigation with my GPS track. I have 1 point about every 10 km to force the desired route. Osmand snaps the navigation on the road automaticly and the navigations works perfect.

Maybe I should create the route with more points? Will it ignore the missed point as soon it arrives at the next point? BTW, I create tracks with ITN converter.

[Majka]

On Thursday, 14 March 2019 11:27:39 UTC+1, limom...@gmail.com wrote:

I open the OSMAND+ app and start navigation with my GPS track. I have 1 point about every 10 km to force the desired route. Osmand snaps the navigation on the road automaticly and the navigations works perfect.

Maybe I should create the route with more points? Will it ignore the missed point as soon it arrives at the next point? BTW, I create tracks with ITN converter.

I repeat: you don't have to turn around and go back. Simply drive on the route you are currently, even if it is wrong. OsmAnd will recalculate the route. Putting more points is counterproductive if you want to ignore them. Or did I understand your problem completely wrong?

With more points, you are doing just the opposite - when you put point into your route, you are saying you want to get to this point, then to the end of the route. With more points, you are stacking the navigation: A > B (have to get there) > C (again, need to pass it) > .... > Finish.  Decide if it is necessary to pass the point (even if you miss it near it, and have to reroute). 

BTW, on the bike and if you have planned stops, it is easier to let OsmAnd navigate from point to point (start -> first stop; then first stop > next stop; next stop > finish). Or, when planning the route, put ONLY the points you want to drive by (no avoiding, if missed a turn, reroute there), meaning as FEW as you can. See here for an example (BRouter web). I set just the point I want to have in the route at all cost (have to pass, no avoiding it) and let the navigation decide the route there. If I miss a turn, OsmAnd would recalculate and navigate me to the next point on this route as fast as it can, and from there take the rest of the route again as planned.

[Bart Eisenberg]

This video is my take on how to navigate on the road with an imported GPX. See how my experience compares with yours.

https://youtu.be/mMcw4kYmfPk

(In the current version of OsmAnd, some of the Quick Actions button functions are not working for now, but it looks like that will be fixed.)

I do agree with Majka: if you can use OsmAnd's native navigation to replicate the GPX route, that's the best approach.  But that's more difficult if the GPX you're following is a scenic tour, as opposed to the fastest way to get from point A to point B.  So the best option depends on nature the route.   

[limom...@gmail.com]

For going from A to B fast I allways use Google Maps with traffic infos. I need Osmand only for planed routes (bike/hike).

I checked the video. I do it the same way, but I never had the issue with the instructions for every turn.
What was the distance between waypoints in this video? To many I guess.
There is a software available to clean a route with to many waypoints.
For a 100 mile trip I had maybe 10 waypoints in my planed GPX track. Osmand is choosing the closest road by itself.
Works perfect if I don´t miss a waypoint.
My worst problem was for example a ride through downtown Tallahassee.
Sitting on my bike I saw a bunch of crossing routes because Osmand wanted to go back to a missed waypoint all the time.
We had to stop with 6 bikes and I switched to google to continue.

[Martin Trautmann]

On 19-03-14 11:27, limom...@gmail.com wrote:
> I open the OSMAND+ app and start navigation with my GPS track. I have 1
> point about every 10 km to force the desired route. Osmand snaps the
> navigation on the road automaticly and the navigations works perfect.
> Maybe I should create the route with more points? Will it ignore the
> missed point as soon it arrives at the next point? BTW, I create tracks
> with ITN converter.

Do you have actual waypoints in between? Then Osmand will try to go
there, even if you passed it.

My worst case was a waypoint which I set on a highway in oder to ease
routing for more than 200 km distance.

Unfortunately, this waypoint ended up on the wrong side of the highway.
Thus osmand wanted me to leave on an exit after, return on the other
side, back to the next exit, then go on to my final destination.

Waypoints are removed only if you had reached them close enough. If you
missed then, you have to remove them manually.

But if you did use a GPS track to follow, it should remove older track
points once you are closer to your goal.

So it's not osmand's fault, but your mistake how to set and use waypoints?

- Martin

[limom...@gmail.com]

Yes I did continue the road, but following the route downtown was impossible when Osmand wanted to go back at every side street.
Thanks for the link. This is what I do. I agree with only as many waypoints as needed. Just so many to keep the desired route.
Going from point to point and press "next" is useless when sitting on a bike.
Can´t touch on my phone while driving with gloves and maybe raining.

Am Donnerstag, 14. März 2019 15:58:28 UTC+1 schrieb Bart Eisenberg:

[limom...@gmail.com]

Exactly this is my problem. What means "close enough". If Osmand would accept maybe 30 meter for accepting a waypoint the problem would be solved.

Yes, older trackpoints are removed after maybe 30 km. No setting in Osmand WHEN they are removed?

Looks to me like there can be a solution for vehicle navgation, as long a solution is available in the program.

[limom...@gmail.com]

In my opinion IT IS Osmands fault, if there is no way to avoid this.
Maybe I drive on a 2-lane highway on the left and I miss the waypoint by 1 meter on the right lane.
It is my mistake?

[Bart Eisenberg]

The video reflects my experience following GPXs with OsmAnd on foot and in a car. I've never had the problem you describe. I assume under settings you've disabled "pass along entire track".

[Harry van der Wolf]

Op vr 15 mrt. 2019 om 15:41 schreef Bart Eisenberg <bartei...@gmail.com>:

The video reflects my experience following GPXs with OsmAnd on foot and in a car. I've never had the problem you describe. I assume under settings you've disabled "pass along entire track".

Hi Bart,

Where can I find that? It is not in my Settings. Not directly in the (Navigation) settings and neither when I calculate the route based on the GPX routepoint track and choose the options.

Harry

[Martin Trautmann]

On 19-03-14 15:58, Bart Eisenberg wrote:> This video is my take on how

to navigate on the road with an imported
> GPX. See how my experience compares with yours.
> https://youtu.be/mMcw4kYmfPk

Thanks Bart,

that's an excellent video to demonstrate what you can do here.
Very well done, you put plenty of effort into it!

I feel it takes far too much effort to prepare a route the way you did.
However, is it possible to export this GPX track, including the GPX
waypoints and names? Then it might be helpful to give them others, e.g.
for bicycle routes and including special POIs.

Schönen Gruß
Martin

[limom...@gmail.com]

I do not find this setting, where is it?

[Bart Eisenberg]

The setting "Pass along the entire track" is from the Directions menu, but only seen if you're navigating a GPX route.  See screen capture.  This part of an earlier video shows the effect of the setting: https://youtu.be/bjbqrVkFEtY?t=439

Thanks Martin!  I'm afraid I no longer have the GPX track I used in the video demo. But adding GPX waypoints is straightforward.  And to your point regarding preparation time, the simplest way to follow a GPX is just to display it....and follow it.  (Just remember to watch the road, not the screen.)

[Harry van der Wolf]

OsmAnd is so smart!!

When I load a GPX file containing route points, I can calculate a route along the points. In that case I have an option "Calculate route between points". Absolutely great!

When I load a GPX file containing track points (most of the time a lot) I get the option "Pass along the entire track". Sometimes OsmAnd really amazes me for all the options and cleverly implemented relevant options for a certain functionality.

However, just by accident I found another bug. My default phone locale is Dutch. Even if I set OsmAnd to English (to test above options), it reverts to Dutch if I rotate my phone.

Harry

Op vr 15 mrt. 2019 om 21:02 schreef Bart Eisenberg <bartei...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bart Eisenberg]

@Harry: speaking of bugs, I'd be grateful if you'd try this in the interest of providing a sanity check: 

Set a single map maker near your location.

Press the directions key.

What do you see?

On 3.3.4 on three devices, I automatically start navigating from my current position to the map marker.  And that becomes the default navigation unless I delete the map marker. I can never get back to the full directions menu because a navigation is already in process.  I'm reluctant report this on GitHub because it seems so obvious that someone must have already done so.  Or is it a setting?  Much appreciated.

--Bart

[Harry van der Wolf]

When I set the map maker it is indeed automatically creating a route from my current position.

But when I enter a new destination it simply calculates a route to the new destination and no longer uses the map marker.

Same when I cancel the route, select a new destination and request directions.

Is there some setting to keep map markers also in the next route?

I'm still on 3.3.4 although I see others already on 3.3.5. It is not yet available for me.

Harry

Op vr 15 mrt. 2019 om 21:34 schreef Bart Eisenberg <bartei...@gmail.com>:

[Harry van der Wolf]

And 10 minutes later on 3.3.5. 

But everything remains the same.

Harry

Op vr 15 mrt. 2019 om 22:03 schreef Harry van der Wolf <hvd...@gmail.com>:

[Bart Eisenberg]

And if I've made a new route, and "cancel" it, OsmAnd navigates back to the map marker.  I don't know of a setting that would cause this. And you don't know.  And it persists in 3.3.5. I'll put on GitHub.  Thanks!

 

On Friday, March 15, 2019 at 2:03:17 PM UTC-7, Harry van der Wolf wrote

[Bart Eisenberg]

I just downloaded 3.3.6.  The Map Marker problem appears fixed. (Talk about service!)  

[Pere Pujal i Carabantes]

I wonder if the setting about "close to end" announcement is also used for close to waypoint?

--
Enviat des del meu dispositiu Android amb el K-9 Mail. Disculpeu la brevetat.

[Bart Eisenberg]

In navigating with a GPX, it would be helpful here to know whether we're  talking about a track (a GPX recorded on a GPS or GPS app) or a route (a GPX plotted ahead of time and probably less precise).  And does "waypoint" refer to a GPX waypoint, which is part of the GPX?  Or to an intermediate destination, which is an intermediate goal associated with navigation, but not part of the GPX?  

[Bart Eisenberg]

And just noting that some GPX "routes" generated with mapping software only contain track points. Routes created on OsmAnd and saved as GPXs contain both track points that describe the path and route points that describe the directional turns. (I think I've got that right. Corrections welcome.)

[limom...@gmail.com]

As far as I know the GPX file format contains a list of waypoints (coordinates), nothing else.
A navigation software uses these waypoints to create a route, depending on settings. Osmand does it different for cars, bicycle or walking. For cars it can be set to snap the closest way from point to point on the matching road. Thats why not many waypoints are needed, just so many to stay on the desired roads.

I create my GPX files on the PC with "ITN CONVERTER" using Open Street Maps.

Very simple and free tool.

Then I use the GPX with Osmand, also with Open Street Maps.

Works perfect.

I disabled "Pass along the entire track" and I will test if this was the solution for my problem with the missed waypoints.

[Harry van der Wolf]

Hi,

I always use RouteConverter to create routes. It can create GPX files containing tracks, waypoints and routepoints.

https://www.routeconverter.com/home/en

If you create routes only on the points where you need the directions, you can still save them as track, waypoints or routepoints. OsmAnd can still create a route from all three.

Mostly I create a route and save it 3x: some_route_rp.gpx, some_route_wp.gpx and some_route_tr.gpx.

I always try to use the some_route_rp.gpx

The "problem" with real tracks containing track points is that they sometimes contain thousands of points. To create a route for hiking, cycling or car you mostly only need 10-30 points.

Harry

Op za 16 mrt. 2019 om 17:14 schreef Bart Eisenberg <bartei...@gmail.com>:

--

[Bart Eisenberg]

@Harry's and @limom's description of how OsmAnd handles routes (as opposed to tracks) was news to me, so I did some experimenting with RouteConverter using v. 3.3.6--creating one GPX route for roads and a second for hiking trails, and followed both. Some observations, based on this small sample:

Overally, both worked well.  Using just the routepoints, OsmAnd filled in the rest and gave completely accurate directions for the roads, and mostly accurate ones for the trails. (The problem could have been the OSM data being imprecise.) Audio instructions also included the routepoints themselves, which were announced as intermediate destinations.  But these were not shown on the screen, and I couldn't add additional intermediate destinations the usual way.  

I never encountered the problem discussed here of coming close to a routepoint and it not being recognized.  In a few places, I deliberately took a different route, and OsmAnd sometimes didn't reroute as quickly as I might have expected.  But soon enough so as not to be a problem.  

Under options, "Calculate route between points" must be checked.  The setting I noted above--"Pass along entire track"--wasn't available.  (Harry also noted this.)  So I guess the first indicates the presence of routepoints, the second of trackpoints.  GPXs created by OsmAnd itself, by saving a route, contain both.  

The only disadvantage I can think of in using a route rather than a track is that the former doesn't fully specify the path you take, because OsmAnd does the final calculation.  Whereas a track specificies it completely because it doesn't use the underlying map. Seems to me that  OsmAnd-generated GPXs work best on OsmAnd. But routes generated elsewhere are a close second.  

[Helmut Jarausch]

Hi,

I'm using OSMAND 3.3.7 on my Android phone.

I've followed the video by Bart Eisenberg on the Quick Action button.

When he uses this button to add a map marker he's given the choice to move the map to place the marker precisely at a specific pont on the map. 

When I do the same, OSMAnd just places the marker anywhere without giving me the choice to move it at a point of my choice. 

Since this happens on my phone running Android 6.1 as well as on my tablet running Android 8.1, I must be missing something. 

Many thanks for some hints, 

Helmut 

--