How to get a GPX file on GO Navigation App?
Dutch-Rider
Posts: 18 [Master Explorer]
It is not strange nowadays.
I receive a GPX from someone through Social media or mail. How do I get this GPX file in TomTom Go with my Smartphone.
There is no connection between TomTom Go and GPX. So my Smartphone says: "There is no app to open GPX". In my opnion TT Mydrive is THE app for this functionality. But it cannot do this. Only the Website version can import GPX files.
I receive a GPX from someone through Social media or mail. How do I get this GPX file in TomTom Go with my Smartphone.
There is no connection between TomTom Go and GPX. So my Smartphone says: "There is no app to open GPX". In my opnion TT Mydrive is THE app for this functionality. But it cannot do this. Only the Website version can import GPX files.
Tagged:
0
Best Answer
-
RoadRider
Posts: 684 [Revered Pioneer]
Not supported.
You have to upload the GPX file using MyDrive Web.
MyDrive Web is made for a desktop browser.
The correct way for sharing routes is using the Share option in MyDrive. This creates a route link and also works in the MyDrive App. Even non TomTom users can use this link to download the GPX. (Brand special options like Garmin shaping points are removed in this GPX file)
MyRoute App also has an upload option to MyDrive from mobile but this is not compatible with the Navigation App.
(It is not totally impossible to use MyDrive Web in the Android Chrome version. When you try you will see it’s a pain...)
When I find the time I will release a Load Track version for Android to solve this problem. But this is still a lot of work.5
Answers
You have to upload the GPX file using MyDrive Web.
MyDrive Web is made for a desktop browser.
The correct way for sharing routes is using the Share option in MyDrive. This creates a route link and also works in the MyDrive App. Even non TomTom users can use this link to download the GPX. (Brand special options like Garmin shaping points are removed in this GPX file)
MyRoute App also has an upload option to MyDrive from mobile but this is not compatible with the Navigation App.
(It is not totally impossible to use MyDrive Web in the Android Chrome version. When you try you will see it’s a pain...)
When I find the time I will release a Load Track version for Android to solve this problem. But this is still a lot of work.
Edit: probably just a temporarily hick.. it works again
Superuser
The latest versions of the Go Mobile App uses different maps to the old Apps which is why the Syncing of routes between the My Drive website or App is not currently possible. The NDS format maps are different to those used in the My Drive system and Tomtom have stated that they are working on the compatibility issue arising from this situation. They have indicated they hope to have the issue resolved soon and will then restore the syncing facility. They have not stated any specific timeline for this.
Doug
@MarcoGo TomTom changed something in the backend. Load Track now always does a retry. Tip you can click the progress bar at the end to speed up.
Currently I an very busy at work with certifications. I will try to fix this when I have the time.
I also have problems with the stability of syncing tracks to the NDS app lately and did see more complains in other fora. Maybe @lampard can investigate this syncing to NDS issue.
@MarcoGo Are you still having issues while syncing routes/tracks via MyDrive? Can you provide an exact timestamp when this issue occurred?
@RoadRider Can you elaborate some more on the above statement? What exactly you observed that seems to be changed now?
Regards, lampard
I did see some reports on other fora starting the end of last week.
Tracks do not always sync directly to the GO Navigation app. Some times you have to turn Sync off an on again.
Syncing some times has a long delay lately. I also had this problem on Saturday.
So I am not sure if both is the same problem (just the delay and a impatient user)
With my "Load Track" App I now get a error for the first call to the GOR REST API. Normally this happens when the GOR backend is to busy so this triggers a delay in my app. The retry after this delay still works.