Open willpom opened 2 years ago
TRUE turn-by-turn track navigation by a Garmin tcx course file. Sources: RWGPS & Plotaroute web & others. (Oldest & well known & popular) A course and instructions in associated coursepoints. Locus tcx_course
TRUE turn-by-turn track navigation by a gpx track file. Sources: Plotaroute web. Select gpx export Track + Directions. A track and instructions in associated waypoints. Locus gpx_navwpt_trk
TRUE turn-by-turn track navigation by a gpx track file. Sources: RouteYou web. Select download Locus map gpx. Cruiser Android & Desktop. Export as gpx navigation track. A track and instructions in trackpoints. (no typo) Locus gpx_navtrk
This is a follow on from a previous discussion so please check for background https://github.com/osmandapp/Osmand/issues/1910
I think there was a misconception of what the different file types are for navigation when this was previously discussed.
From what I have seen OSMand handles the 2 GPX types differently for navigation.
Both track & route viewed.
Track navigation - the small squiggle where it first reaches the cemetery isn't usually routable by car but the closeness of track points forces OSMand to ignore.
Route navigation - this is just an example in driving mode to show how the routing between points is taken over.
Previous OP is asking if there is the possibility for TCX integration. This would provide the breadcrumb trail of the GPX track preventing OSMand from creating some interesting routing. The difference being sought is that OSMand then reads the TCX's navigational prompts (speech if activated) rather than creating them based on how the TCX interacts with the map. This is known as TRUE turn-by-turn navigation.
File examples all from the same RWGPS route. https://ridewithgps.com/routes/39209388?privacy_code=yF97lonCXplV6qMM Track, route & TCX files: Example.zip
Having organised cycling events for 20+yrs TCX course is the best format if it can be used for navigating a planned route. By integrating in OSMand one would benefit from the True turn-by-turn navigation and have all the benefits of the mapping. This is more to do with removing the spurious fluff often found from routing algorithms and potentially using just the user defined.
In this example I'd expect the following to be read - these won't relate to what is actually on the map if user authored: SO @ X - 0.0 km LEFT @ T $ Greenbank - 0.2 km RIGHT @ X - 0.4 km imm LEFT @ [x] - 0.7 km LEFT (1ex) @ mRBT into St. James St - 1.0 km
I believe the addition of this feature would enhance OSMand for those using pre-planned routes.