Error reading garminexpressimport.gpx file while starting BaseCamp or importing from

Former Member
Former Member
I use Basecamp 4.2.2 for a Nuvi 2595. It worked at first a few sessions: create, edit WPs, routes, and send to or receive from device, though I did not feel as comfortable as with MapSource. After creating several routes with tens of waypoints in BC, I sent them to 2595 device by specifying to send the list containing routs only, hoping WPs were not sent together with routes. But the result was disappointing: all waypoints I used are still sent to device as they were in other lists under “my collection” The unwanted WPs make the saved list in 2595 too long for its 5” screen.

Trying to find a way to avoid WPs, I decided to delete all data under “my collection” and start a new BC session from scratch (I do make a backup by exporting data to a gpx file before deleting). This was a bad decision: after this, if the device was connected, BC started with a warning: “An error occurred while reading file gpx/garminexpressimport.gpx”. If no device connected, no warning at start, but at importing from device, the same warning came, see attached screenshot. The result was: no routes but only WPs imported from the device.
Later, I found, by using “send selection to device”, WPs can be avoided, but it was too late. I can restore a BC session by importing the exported gpx, but cannot avoid the warning at import. Now I can still use BC, send data to device, but cannot receive data from device anymore.
I wonder, what triggered this error? What can I do now?
I checked Garmin device in Windows Explorer, there are two copies of the file, one within GPX folder under root of the internal storage, one within Garmin/gpx subfolder. What does this file do? I do have Garmin Express installed on the PC, and run it for couple of times. But the time-tag of the trouble-making gpx file is not the time when I used Garmin Express.

One suggestion: it sounds strange to me that the file menu of BC lack save, save as …, and open function that is routine of file menu for any software. No save/open but only export/import, backup/restore means BC is very rigid in one fixed session.
Compare to MapSource, it can save, open a new session, open more instances of MapSource windows at the same time and open different saved gdb files.
It sounds strange to me also: isn’t easier to expand functions of a mature MapSource than to develop a totally new BaseCamp with so many uncertainties and user complaining? This is out of topic of course.

Thanks for help in advance.
  • Former Member
    0 Former Member
    I apologize for the trouble.

    Can you attach a copy of gpx/garminexpressimport.gpx?

    You can probably just remove the file to see if the problems go away (back it up if you are worried removing it will cause issues), but I'd still like to see what's wrong with the file.

    Not getting into another MapSource discussion, but just as a quick explanation: there is no Save in BaseCamp because it's not a document-based application, but a database driven application. You are not supposed to worry about files.
  • Former Member
    0 Former Member
    Hi, FALAGAR, thanks for the quick response and suggestion.

    It seems the gpx file is the culprit. I removed the garminexpressimport.gpx file from 2595's internal storage/gpx folder. Now there is no complaint at start of BC even if the device is connected. When I use receive from device, no complaint either. But the received contain waypoints only, no routes, trips are received despite they are stored there under Apps/trip planner. I can't remember whether this is a normal behavior of BC's import or not. Or the lack of routes is due to lack of the gpx file.
    Without this gpx file in device, there is no problem in the 2595 device either, all saved wps, and routes, trips under trip planner are unaffected. It seems the file is only needed for exchange data between PC and device.

    Thanks to your explanation of BC. Now I begin to understand some "strange" behavior of BC as a database oriented software: such as automatically adding a number to a previous used wps, because a database cannot tolerate identical items.

    Attached please find the offensive gpx file.

    Thanks again for your help.
  • Former Member
    0 Former Member
    Thanks for sending the file, we'll investigate.

    I don't think trips get exposed by the device. You can send routes with BaseCamp to the device, it will convert them to trips internally and not show you again. That is certainly not the behavior I'd like the device to have, but that's what it does.
  • Former Member
    0 Former Member
    Hi, FALAGAR, thanks for the quick response and suggestion.

    It seems the gpx file is the culprit. I removed the garminexpressimport.gpx file from 2595's internal storage/gpx folder. Now there is no complaint at start of BC even if the device is connected. When I use receive from device, no complaint either. But the received contain waypoints only, no routes, trips are received despite they are stored there under Apps/trip planner. I can't remember whether this is a normal behavior of BC's import or not. Or the lack of routes is due to lack of the gpx file.
    Without this gpx file in device, there is no problem in the 2595 device either, all saved wps, and routes, trips under trip planner are unaffected. It seems the file is only needed for exchange data between PC and device.

    Thanks to your explanation of BC. Now I begin to understand some "strange" behavior of BC as a database oriented software: such as automatically adding a number to a previous used wps, because a database cannot tolerate identical items.

    Attached please find the offensive gpx file.

    Thanks again for your help.


    Sadly, the culprit is indeed the file itself. We have contacted the Garmin Express team about this issue and we are hoping they will have a resolution soon. Sorry for the trouble, and thank you for your feedback.
  • Former Member
    0 Former Member
    Problem still exists

    Just updated two Nuvi 2595's and had problem with both. Also deleted the file from the internal and able to now not receive the error. Thanks for the tip. Has there been any action by the Garmin programmers on this or do we need to bring it up differently?