28 Transfer Trip to the SD Card

  Contents First Previous Next

Using the Memory Card is different

If the same operation is carried out but data is sent to the Memory Card instead of to Internal Storage, then each Trip saved as a separate gpx file in the Garmin / GPX folder. As in the image below:



When transferred to the XT from Basecamp, Waypoints are saved in a single file called Waypoints.gpx.


Importing Trips, Tracks and Waypoints from the SD Card

Any data - Trips, tracks, Waypoints - needs to be imported before it can be used by the Zumo for navigation. Waypoints will not show up as available for import if there are none in internal memory.

It is not possible to delete Trips that have been transferred to SD Card using the Zumo screen, it can only be done using a file explorer on your PC with the Zumo connected by USB cable.

Transferred Trips from Basecamp to the SD Card cannot be deleted or changed by the Zumo XT.

Limits

Practically, 100 Trips can be transferred and imported into the XT. It is actually much more, but since it will only display 100, it starts to get tricky gaining access to any more than that.

If you edit the current Trip (eg change the vehicle type), it changes the imported copy. So stopping a Trip and loading it again will give you the edited version. But if you delete the Trip and import it again gives you the original.

Trips etc which are transferred to memory card are not affected if the USB connection is re-connected.

When Trips are transferred to the memory card
  • The Zumo XT gives no indication that there are new Trips to be imported when the Zumo is started
  • Waypoints have to be imported manually when sent tot he SD card - it doesn’t happen automatically.
  • The XT will allow import of the same Trip multiple times - each version will have a sequence number appended
  • The Zumo XT will not delete any of the original transferred Trips if transferred in different USB sessions.
  • Basecamp will allow you to transfer the same Trip twice, but stores it on the Zumo just once.
  • If you transfer a Trip to the Zumo, and then modify it in Basecamp and transfer it again, the Zumo stores this as a separate Route99.gpx file.
  • If the same Trip name is used, Zumo shows that with a sequence number added.
  • Imported (or Saved) Trips can be deleted from Trip planner on the XT.
  • Any or all of the original Trips can be re-imported.
  • GPX files of Trips from other sources can be saved to the memory card for import to Zumo.
  • Any GPX files must be stored in the folder Garmin / GPX - case sensitive.
  • Most of the above also applies to Tracks - except tracks cannot be altered in the Zumo.
    •

    Issues with Data on Memory Cards

    These are not big issues, but they can create problems.

    • Waypoints are not automatically added to Favourites. They have to be imported manually.

    • It is up to you to manage the list of GPX files on the memory card. (eg manually delete old routes)

    • Zumo cannot find Favourites / Waypoints on the SD Card unless it has at least one Favourite in internal memory.

    • Routes and Favourites in Internal Memory are listed before those on the SD Card

    • Routes stored on the SD Card do not have the issues that I described for internal memory.

    Note that I have sneaked in that third bullet point. Go back and read it again. It will catch you out at some point.
    You know that you transferred the Trips and Waypoints, but it tells you there aren’t any. It is lying.
    Display the map, tap on it (it may need two taps) to position a blue/white flag. Click on the flag or the name and tap Save.
    Now go back and find your Waypoints. Magic, isn’t it ?

      Contents First Previous Next

    The information on these pages has been acquired from personal experience of using and testing the behaviour of Basecamp and my Zumo XT. I have no links with Garmin, and these pages should not be regarded as instructions. They are presented for interest only. The contents of these pages must not be shared, copied, transmitted, redistributed or re-published in any form without my permission. (C) JHeath 2021.