Since Explorer didn’t work for uploading the file, I used Garmin Drive to send it to my navigation device.
Garmin Explorer stuck when uploading large .gpx file
Re: Garmin Explorer stuck when uploading large .gpx file
I'm using https://gpx.studio to create routes, and it works great overall. However, the GPX file it generates is about 7MB in size. I can't upload it to Google Maps, and my Garmin Zumo device also refuses to accept it – it's simply too big with too many points.
Does anyone know how I can reduce the file size while keeping the route intact and making it compatible with my Zumo?
GPX https://www.upload.ee/download/17986689 ... 9/Trip.gpx
Does anyone know how I can reduce the file size while keeping the route intact and making it compatible with my Zumo?
GPX https://www.upload.ee/download/17986689 ... 9/Trip.gpx
- lkraus
- Subscriber
- Posts: 524
- Joined: Mon Aug 24, 2020 2:36 pm
- Location: Central Ohio, U.S.A.
- Has liked: 69 times
- Been liked: 189 times
Re: Garmin Explorer stuck when uploading large .gpx file
The TRACK in the .gpx contains over 18000 track points. Tracks for the XT cannot exceed 15000 track points.
I've never used gpx.studio, but I would look for a setting to restrict the number of points.
Or simply split the track into two shorter tracks. It looks like it is too long to comfortably complete in one day.
EDIT: gpx.studio has a tool to reduce track points called Minify
I've never used gpx.studio, but I would look for a setting to restrict the number of points.
Or simply split the track into two shorter tracks. It looks like it is too long to comfortably complete in one day.
EDIT: gpx.studio has a tool to reduce track points called Minify
____________________________________
2006 R1200RT
Galaxy S10<>Zumo XT<>Sena 20S
2006 R1200RT
Galaxy S10<>Zumo XT<>Sena 20S
-
- Posts: 3067
- Joined: Sat Oct 19, 2019 4:17 pm
- Location: West Yorkshire, Uk
- Has liked: 421 times
- Been liked: 921 times
Re: Garmin Explorer stuck when uploading large .gpx file
I'm not going to download the GPX file - because the link requires you to sign up for something else.
Basecamp does an excellent job of reading badly formed GPX files and tidying them up so that incorrect lines are discarded and the file contains only correctly form GPX tags. Often with dodgy routes or tracks loading them into basecamp and resaving them cures the problem.
But basecamp also has a facilty for reducing the number of points in a file.
Double click the track in Basecamp and a dialog box opens up, with a number of options at the bottom.
Filter, Invert, Create Route, Create Adventure, Print.
Choose 'Filter' and this pop-up appears
You can filter it in different ways - all of them mathematical.
Maximum Ponts - if it has 10,000 points and you specify that you want a maximum of 1,000 then it will keep one point and remove the next 9. and repate that all the way through the file.
Uisng this, you can easily half the number of points in the track.
On a route with straight roads, that might make a significant difference - so specifying a longer distance between legs might be a better option. It means that your track my chop off corners - but if you are specifying (say) 300 ft between points that isn't too bad.
Basecamp does an excellent job of reading badly formed GPX files and tidying them up so that incorrect lines are discarded and the file contains only correctly form GPX tags. Often with dodgy routes or tracks loading them into basecamp and resaving them cures the problem.
But basecamp also has a facilty for reducing the number of points in a file.
Double click the track in Basecamp and a dialog box opens up, with a number of options at the bottom.
Filter, Invert, Create Route, Create Adventure, Print.
Choose 'Filter' and this pop-up appears
You can filter it in different ways - all of them mathematical.
Maximum Ponts - if it has 10,000 points and you specify that you want a maximum of 1,000 then it will keep one point and remove the next 9. and repate that all the way through the file.
Uisng this, you can easily half the number of points in the track.
On a route with straight roads, that might make a significant difference - so specifying a longer distance between legs might be a better option. It means that your track my chop off corners - but if you are specifying (say) 300 ft between points that isn't too bad.
Have owned Zumo 550, 660 == Now have Zumo XT2, XT, 595, 590, Headache
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC . . . Navigating with Zumo Booklet
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC . . . Navigating with Zumo Booklet