Importing GPX files into Base Camp

Former Member
Former Member
I have some feedback to hopefully improve your Base Camp application.

I have written an application to take our coordinate file and convert it to a waypoint or track GPX file. In my attempt to get the GPX file to import into Base Camp I discovered a couple problems I really wish you could address in a future version:
1) If there is an error importing the file it would be helpful to identify the line number and/or xml element where the error occured "Unknown error opening import file" is not useful to try to determine WHERE in the GPX file the error occurs.
2) This one took over an hour to figure out:
<gpxx:DisplayColor>green</gpxx:DisplayColor>
Notice that lower case "green" is one cause for unknown error. Your Base Camp application will generate an error unless it is proper case "Green". Please consider fixing the code in Base Camp to mitigate this error or identify the specific error when displaying error information to the user.

My experience with importing GPX files into Base Camp is that its really picky and just does not display enough diagonstic information. I do like the application however and it handles our basic needs.

Thanks,
Terry
  • I guess you could upload it to something like dropbox?
  • The information for a track point begins with <trkpt lat=&#8221; &#8220; lon=&#8221; &#8220;> and ends with </trkpt>. Copy and post a range that includes your offending point and 2 points above and below it. From this, we may be able to spot the problem (or perhaps the first problem &#8211; there may be many).
  • Former Member
    0 Former Member
    Thank you SUSSAMB,

    The file is about 3245 Kb and it appears that the uplod limit is 1 Mb. Any suggestions?

    Any help would be appreciated as I really need to track these trips.

    Thanks
    Don.


    You can zip the file down and attach it to another post here.

    Also....
    You can open 2 notepad files side by side on your screen.
    The corrupt file on one side and a file that you know works properly on the other.
    Be sure to do a Save As with a new name on the corrupt file before you start.
    You need to keep the original corrupt file in case things go sideways during the repair.
    Then compare the 2 files line by line correcting the corrupt one as you go.
  • Your problems begin at the very end of your attachment. Unfortunately, I need to see more in order to give good advice.

    Here is the end of your attachment with some formatting added to make things clearer:

    <trkpt lat="-27.238460" lon="153.006957">
    <ele>22.25</ele>
    <time>2012-06-19T06:29:19Z</time>
    <extensions>
    <gpxtpx:TrackPointExtension>
    <gpxtpx:speed>26.08</gpxtpx:speed>
    <gpxtpx:course>321.88</gpxtpx:course>
    </gpxtpx:TrackPointExtension>
    </extensions>
    </trkpt>

    <trkpt lat="-27.236401" lon="153.005499">
    <ele>24.65</ele>
    <time>2012-06-19T06:29:29Z</time>
    <extensions>
    <gpxtpx:TrackPointExtension>
    <gpxtpx:speed>27.45</gpxtpx:speed>
    <gpxtpx:course>333.18</gpxtpx:course>
    </gpxtpx:TrackPointExtension>
    </extensions>
    </trkpt>

    <trkpt lat="-27.233273" lon="153.00 <------ Problems start here

    <trk>
    <name>ACTIVE LOG: 06 Jun 2012 14:01</name>
    <trkseg>
    <trkpt lat="-27.071572"

    Where I have indicated, you have an incomplete track point. The following line starts a new track without terminating the pervious track. Even worse, this new track indicates a time (06 Jun 2012) that precedes your last valid track point (19 Jun 2012). It&#8217;s possible that you have a small section of old data and then your previous track will begin again (unfortunately, there will be missing points in your track). You need to look at the track points that follow to see if they are time stamped <time>2012-06-06&#8230; or change back to <time>&#8230; 2012-06-19 at some point. The track with the name &#8220;ACTIVE LOG: 06 Jun 2012 14:01&#8221; should continue all the way to the next </trkseg>.

    Let me know what you find. If possible, post a section of your file from <trkpt lat="-27.236401" lon="153.005499"> to and including a complete track point with a time stamp of <time>2012-06-19 or to the end of your file if it is small enough.
  • Former Member
    0 Former Member
    If you are still having trouble, try zipping up the file and attach it. It will probably be easier for some of these fine knowledgeable folks here to fix the file than having you poke around by yourself.

    Or, if you have trouble zipping the file or the attaching it still doesn't work, sign up on skydrive.com (it's free), upload the file there, share it, and post the URL address to the file here.
  • Somehow the device wrote some of the track logs to the file, and then started over again. Luckily there is nothing lost; the file just needed some clean up.
    See attachment.
  • You cannot download the Recent visits from your device, unless you save them on the nüvi as waypoints (needs to be done one by one...)
  • You have asked several other questions regarding the operation of your nuvi 1450T, unfortunately I don’t own one. But I will try to start things off and perhaps others will fill in the details for your particular unit.

    Based on your gpx file, a trip log is what I know as a track log. A track/trip log contains one or more tracks, tracks are made up of segments and segments are made up of track points. For example, if your unit loses lock it will make a segment break. On my model, a track will end when I turn off the unit or manually save it. The details of tracks will vary from model to model.

    On my model, there is a file called Current.gpx that collects the real time track data. It has a limit of 10000 track points. When this limit is reached, the unit will essentially copy the Current.gpx file to a folder called Archive and give it a name. I’m guessing that Nuvi’s do something similar and uses a number for the name. All models have memory limitations. There will be limit to how many archived files your unit will hold. When it reaches this limit, it will likely replace the oldest file (on your unit it might be called 1.gpx) with the latest archive.

    This is why a trip that begins in one file might end in the next file. It also explains why trips in file 5.gpx can occur at a later date than files in 6.gpx. I can assure you that within a file, all points are recorded in chronological order.

    When you look at a track log, you will see the track names in alphabetical order. How Garmin builds track names has varied quite a bit (from model to model as well as within the life time of a single model). If your model built the name with the date as 2012-06-09 instead of 09 Jun 2012 alphabetical order would also be chronological order. As I said, naming has changed within firmware updates of a particular model.

    I have no concept of Recent Visits. Perhaps it stores POIs used to create routes and the coordinates where you stop and turn off the unit. In any event, if you want to note a particular location on a trip, it should be done by creating a waypoint. How or if this can be done your model I do not know.

    By the way, your particular bad file appears to have been caused by the archiving process being interrupted. After the interruption, your unit rewrote all of the tracks in the real time log starting at the interruption point (i.e. you had part of the data followed by all of the data).

    I too would like to thank JAVAWA for taking the time to fix your file.
  • Former Member
    0 Former Member
    "Recent Finds" or "Recently Found" is an internal list of the things you have searched for. So, if you search for the nearest Krispy Kreme and then you search for a couple of other things, when you decide you really do want that donut you don't have to search for Krispy Kreme again. You can just go "Where To?" > "Recently Found" and your Krispy Kreme search will still be near the top of the list. That saves a bunch of typing any time you want to search for something you have already searched for recently.

    I'm pretty sure the list is just maintained somewhere in internal memory. To make something from the Recently Found list into a waypoint you would have to select it in the Recently Found list. Depending upon your Nuvi model you should then have some options. They would include tapping GO but should also include displaying it on the map. It might also include the option to add it to Favorites. If not, when you display it on the map you should be able to tap it and save it.

    Of course Krispy Kreme is a bad example. First, it's unhealthy. :-) Second, it's already in the POI database so making it a waypoint would be pointless (pardon the awful pun!). A better example is if you searched for an address. Recently Found list saves you a ton of work by not forcing you to go through the address search routine again to get that address back up so you can either navigate to it or save it to your Favorites.

    ...ken...
  • Any location that you enter somehow into your nuvi will appear it the recently found list. Pressing where am I will generate an entry. So will browsing to a part of the map and selecting a location.

    As already mentioned these are stored within the nuvis inaccessible memory. If you want access to them you need to save them as favorites.