After a lot of experimenting, my thinking (for the moment) is this: OsmAnd, and other routing software too, is in the business of creating efficient routes from point A to point B. Perhaps via points C, D, ... Whereas people who create GPXs are generally interested in trips that are scenic rather than efficient: preferring smaller roads to highways, detours to directness, and, in some cases, ending where they started. Your GPX looks like that.
Ideally, one would import a scenic GPX route into OsmAnd, which would create a route that duplicates it using OsmAnd map data. But the developers have posted (on Github) that this is a tough problem to solve. I'm unaware of any other GPS software that's solved it either: that takes a GPX from another source and fully duplicates it with a route providing turn-by-turn, road-by-road directions. So for the foreseeable future, "navigating the track without calculating the route between points" does seem like the best option. Following it takes more concentration. So for safety sake, keep your eyes (mostly) on the road. On Saturday, July 6, 2019 at 10:35:40 PM UTC-7, Peer wrote: > > Hello Bart, > > thanks for checking mt gpx route. I think it is normal that a calculated > route is OSmAnd wil be different from the track on an imported gpx-file. > The file is created in an other program thats probably uses different > navigation settings. > > I tried yesterday to create a route with OsmAnd alone, as Paul suggested. > I noticed that the intermediate points were shown by a flag on the map. > After saving the track/route and reloading it the intermediate points were > shown as a circle with a star in it. The imported gpx-file does not show > symbols on the map for the route points. So there must be a difference in > the saved OsmAnd gpx-file and the imported gpx-file. Perhaps thats can be a > cause for the routing problems. > > Creating a route in OsmAnd was not easy at first. But after a while I got > the hang of it. Creating a new intermediate point or a new destination > works ok. In the beginning I made a lot of mistakes so I started again many > times. For my purpose, creating a route (100km +) on smaller roads this > method does not work very good. To get an overview I have to zoom out. But > then the smaller roads are not displayed. So I have to zoom in to see the > smaller roads again And the zooming in and out has to been done many times. > OsmAnd also regarly moves the map back to the starting point which is > inconvenient. I find it difficult to place an intermediate point > accurately. During experimenting I experienced that OsmAnd sometimes > refuses to let me pass certain points and creates a detour. I do not know > why. I saved a route and oepned it again. The I wanted to make some changes > but I could not change te intermediate points (circle with star). Adding > intermediate points at the end of the route did not work properly. I > experienced similar strange route guidance as in my tests on the motorbike. > I also found out that I was able to add a new destination to the saved > route but I was not able to add a new intermediate point. I saw the flag on > the screen but this point was not part of the calculted route. > So my experience with adding intermedate points and new destination points > in OsmAnd is not good. I think the experience will be much better when you > create shorter routes. > > Navigating the track without calculating the route between point does work > very good for me. I think that will the way I navigate tracks for the > moment. But I hope there will be more progress in the future. > Thanks for the support!! > Peer > > Op zondag 7 juli 2019 01:28:10 UTC+2 schreef Bart Eisenberg: >> >> Correction: on closer inspection, my route, using "Calculate route >> between points", varies in several places from your GPX, although it goes >> in the general direction and gets the area of your screen capture right. >> Sorry for the confusion. >> >> On Saturday, July 6, 2019 at 4:05:34 PM UTC-7, Bart Eisenberg wrote: >>> >>> Here's a closeup of my routing near your screenshot: >>> >>> [image: Routing near Fluitenberg.png] >>> >>> >>> On Monday, July 1, 2019 at 4:43:39 AM UTC-7, Peer wrote: >>>> >>>> I created a track with waypoints on MyRouteApp.com and saved it to the >>>> tracks directory of OsmAnd. >>>> I choosed the track for navigating with the option 'Calculate route >>>> between Points'. >>>> >>>> At first the navigating was fine. After approximately one hour OsmAnd >>>> was starting to act strange when it should recalculate a route. The >>>> recalculated as not logical. >>>> example 1: >>>> I should take a turn right into a side street. But OsmAnd wants me to >>>> go straight ahead, make a u-turn on a roundabout 200 meters further and >>>> then make a left turn into the side straat. >>>> example 2: I have to drive straight ahead. But Osmand wants me to turn >>>> right into a side street, make a uturn after 100meters and then turn right >>>> again to follow the orginal route. >>>> >>>> This happened several times, always when recalculating a route. I do >>>> not know if this is problem in OsmAnd (version 3.3.8) or that my phone >>>> (Samsung trend, 6 years old) is just not strong enough for performing this >>>> calculations. >>>> >>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/7cce55b2-cc50-4420-9b68-341d070b2bd5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
