how can I transfer a track from one device to another, avoid "Unknown street" navpoints?
I want to create a track on a tablet (larger screen) and transfer it to a phone for actual navigation. I am using compute source BRouter (offline route calculation) without compute instructions then edit the track and add navigation points at important turns. If I navigate on the same device I have created/ edited the track, then the top line "navigation panel" is correctly hidden. This change was made in V3.9.0 "chg: navigation panel with streets is now hidden if route do not have any streets values". Previously the navigation panel always displayed "Unknown street". But if I export the track as a TCX file, and then import the track, whether onto same device or another, the navigation panel now again displays "Unknown street" for each navigation point. The imported track is different to the original track. I want to hide the "navigation panel" if it just displays "Unknown street". I've tried deleting the coursepoint "<name>XXX</name>" from the TCX file but makes no difference. Can the TCX file format be improved to fix this?
The same question
Hello Andrew,
if you create a precise navigation route in one Locus version, that best, and only supported format that should export and later import all instructions, is GPX v 1.1. No other. Support for TCX format was added later mainly on requests of Willy (user 0709), but it's support for precise navigation is limited compare to support in GPX.
So please try to do this with GPX format. If there still be a problem, please share with me your exported GPX and I'll check it on my own device. Thanks
Hello Andrew,
if you create a precise navigation route in one Locus version, that best, and only supported format that should export and later import all instructions, is GPX v 1.1. No other. Support for TCX format was added later mainly on requests of Willy (user 0709), but it's support for precise navigation is limited compare to support in GPX.
So please try to do this with GPX format. If there still be a problem, please share with me your exported GPX and I'll check it on my own device. Thanks
Yes, that seems to work - brilliant, thanks. I thought (wrongly) the TCX format was implemented mainly for course points, and I couldn't see course points written when I exported to GPX V1.0 which I had been using for BaseCamp compatibility, but now I'll archive all tracks as GPX V1.1 instead.
Yes, that seems to work - brilliant, thanks. I thought (wrongly) the TCX format was implemented mainly for course points, and I couldn't see course points written when I exported to GPX V1.0 which I had been using for BaseCamp compatibility, but now I'll archive all tracks as GPX V1.1 instead.
I'm still little bit confuse from TCX ... do not know what to wants from this format. Anyway GPX files exported from Locus has own extension that should keep all required information generated for navigation. So track re-imported back should be absolutely equal.
During last months we discuss a lot similar topics and I'm aware that in GPX is potential risk on some incorrect placing of orders in case, track is over exactly same trackpoints (same way there and back). Anyway if any problem appear, feel free to create an issue here because it is definitely a problem.
I'm still little bit confuse from TCX ... do not know what to wants from this format. Anyway GPX files exported from Locus has own extension that should keep all required information generated for navigation. So track re-imported back should be absolutely equal.
During last months we discuss a lot similar topics and I'm aware that in GPX is potential risk on some incorrect placing of orders in case, track is over exactly same trackpoints (same way there and back). Anyway if any problem appear, feel free to create an issue here because it is definitely a problem.
Sure I know a confusing situation. Remember official .tcx (Garmin) only supports limited 16 PointTypes !
Locus in a previous history version had only tcx export. While reporting export bug, I asked tcx import support. Why ? As .tcx is THE only used track file format (with strictly timed Navigation instructions), as generated by popular RWGPS, BRT websites and others ! Why tcx ? Pushed by the popularity and supporting of A LOT of Garmins very popular specific bike gps hardware I suppose. If we like it or not, thats reality.
I think very strict Navigation functionality can also be offered by gpx and not limited to only 16 (strange) PointTypes. See idea:
http://help.locusmap.eu/topic/autodedect-and-select-navigation-points-from-simple-waypoints-in-a-trackfile
This should "free" users for more alternative (pc) editors, now mainly using Garmin (pc) software or online web to generate strict timed Navigation tracks.
Locus Navigation and simple trackediting.
A file (with merged instructions), using extra Locus instructions, is incompatible with Garmin norm, or cannot be exported correctly by official tcx. Example: Bear, Sharp Left or Right are unknown in official tcx and replaced by Locus export into accepted official PointType Left or Right.
Menion solution: Track transfer using gpx V 1.1 into another Locus system. OK for simple A to B trackcircuit.
And I noticed "Strict Navigation" failures in tests with complex outward and returning (MTB) tracks.
Sure I know a confusing situation. Remember official .tcx (Garmin) only supports limited 16 PointTypes !
Locus in a previous history version had only tcx export. While reporting export bug, I asked tcx import support. Why ? As .tcx is THE only used track file format (with strictly timed Navigation instructions), as generated by popular RWGPS, BRT websites and others ! Why tcx ? Pushed by the popularity and supporting of A LOT of Garmins very popular specific bike gps hardware I suppose. If we like it or not, thats reality.
I think very strict Navigation functionality can also be offered by gpx and not limited to only 16 (strange) PointTypes. See idea:
http://help.locusmap.eu/topic/autodedect-and-select-navigation-points-from-simple-waypoints-in-a-trackfile
This should "free" users for more alternative (pc) editors, now mainly using Garmin (pc) software or online web to generate strict timed Navigation tracks.
Locus Navigation and simple trackediting.
A file (with merged instructions), using extra Locus instructions, is incompatible with Garmin norm, or cannot be exported correctly by official tcx. Example: Bear, Sharp Left or Right are unknown in official tcx and replaced by Locus export into accepted official PointType Left or Right.
Menion solution: Track transfer using gpx V 1.1 into another Locus system. OK for simple A to B trackcircuit.
And I noticed "Strict Navigation" failures in tests with complex outward and returning (MTB) tracks.
Sorry, but a lot of similar topics are mixed up now over a lot of similar treads. What a mess. I stay here. OK ?
V 3.9.1.5
1. Locus auto Screen On/Off. = OK !
My settings: (Full functional Gesture control !)
-Android system auto screen turn off: 2 minutes.
-Always Screen on: Disabled.
-Disable lock screen
-Locus Gesture: Wave once and "turn_on_screen_by_gesture_disable_auto_screen_off=1" (config.cfg)
-Locus Screen turn on: A single activation 13 seconds before turn.(config.cfg).
-Locus auto screen turn off: *15 sec.
2. Export using gpx V1.1 and strict Navigation.
Answered: Wait to next version and lets see.
3. Direct Locus generated Navigation. Export can be optimised both in tcx and gpx !
Detailled street info from the routing engine is available.
Proof: See the resulting wpt tagging in the gpx files. Unfortunately the street details are in the <name> tag !
But the optimal place for such extra details is in <desc> tag if using gpx or in <Notes> tag in tcx !
The exported tcx file cuts this usefull information, as a <Name> tag is generated from the Locus xx.tts file !
And so this usefull information is lost because not using the description <Notes> tag.
Examples see the zip. Same traject ! Routing engine: MapQuest.
File 1 tcx: tcx file generated from BRT website. See <Name> tag and the informative <Notes> tag containing the detailled street info.
File 2 tcx: Export of above file from Locus database into .tcx file format. The <Name> tag is changed according to Locus language xx.tts file, the <Notes> tag is unchanged.
File 3 tcx. Same traject generated by Locus MapQuest, export to tcx file. Name tag according to language xx.tts file. No <Notes> tag and so the detailed street info from MapQuest routing is lost.
File 4 gpx v1.0. Same traject generated by Locus MapQuest, export to gpx v1.0 file. Detailled street info is in the <name> tag ! Why not in the description <desc> tag ?
File 5 gpx v1.1. Same traject generated by Locus MapQuest, export to gpx v1.1 file. Detailled street info is in the <name> tag ! Why not in the description <desc> tag ?
Willy.
Sorry, but a lot of similar topics are mixed up now over a lot of similar treads. What a mess. I stay here. OK ?
V 3.9.1.5
1. Locus auto Screen On/Off. = OK !
My settings: (Full functional Gesture control !)
-Android system auto screen turn off: 2 minutes.
-Always Screen on: Disabled.
-Disable lock screen
-Locus Gesture: Wave once and "turn_on_screen_by_gesture_disable_auto_screen_off=1" (config.cfg)
-Locus Screen turn on: A single activation 13 seconds before turn.(config.cfg).
-Locus auto screen turn off: *15 sec.
2. Export using gpx V1.1 and strict Navigation.
Answered: Wait to next version and lets see.
3. Direct Locus generated Navigation. Export can be optimised both in tcx and gpx !
Detailled street info from the routing engine is available.
Proof: See the resulting wpt tagging in the gpx files. Unfortunately the street details are in the <name> tag !
But the optimal place for such extra details is in <desc> tag if using gpx or in <Notes> tag in tcx !
The exported tcx file cuts this usefull information, as a <Name> tag is generated from the Locus xx.tts file !
And so this usefull information is lost because not using the description <Notes> tag.
Examples see the zip. Same traject ! Routing engine: MapQuest.
File 1 tcx: tcx file generated from BRT website. See <Name> tag and the informative <Notes> tag containing the detailled street info.
File 2 tcx: Export of above file from Locus database into .tcx file format. The <Name> tag is changed according to Locus language xx.tts file, the <Notes> tag is unchanged.
File 3 tcx. Same traject generated by Locus MapQuest, export to tcx file. Name tag according to language xx.tts file. No <Notes> tag and so the detailed street info from MapQuest routing is lost.
File 4 gpx v1.0. Same traject generated by Locus MapQuest, export to gpx v1.0 file. Detailled street info is in the <name> tag ! Why not in the description <desc> tag ?
File 5 gpx v1.1. Same traject generated by Locus MapQuest, export to gpx v1.1 file. Detailled street info is in the <name> tag ! Why not in the description <desc> tag ?
Willy.
I had a look at your above suggested gpx export method. Such exported navigation track does not look very nice in another viewer. No better alternative gpx export solution available in future ?
See also: https://www.dropbox.com/s/892u91szx45816q/Short.zip?dl=0
I had a look at your above suggested gpx export method. Such exported navigation track does not look very nice in another viewer. No better alternative gpx export solution available in future ?
See also: https://www.dropbox.com/s/892u91szx45816q/Short.zip?dl=0
Replies have been locked on this page!