Skip navigation
edkatibah
edkatibah Calculating status...
Currently Being Moderated

Problem with GPX file rendering

Jun 11, 2012 8:17 PM

Tags: #map #lr4 #lightroom4 #gpx #track_log #gpx_file

I'm having an issue with Lightroom 4.1 GPX file rendering (Load Track Log).  The GPX files were generated from a Garmin eTrex GPS unit.  The Garmin GPS tracks were downloaded to Garmin Basecamp Version 3.3.1 from which the GPX files were exported. All software is being executed on a MacBook Pro running OS X 10.6.8.

 

Esri's ArcGIS Explorer Online renders the GPX file correctly:

Screen shot Esri ArcGIS Explorer GPS Track.jpg

Here is how the same data is incorrectly rendered in Lightroom 4.1:

Screen shot Lightroom 4.1 GPS Track.jpg

I have placed a copy of the GPX file used above at:

 

http://sdrv.ms/Only2R

 

Note: this is not an isolated issue - I have 40 additional GPX files which all suffer the same rendering issues in Lightroom 4.1.

 

Thanks for looking into this issue.

 

- Ed

 

Ed Katibah

ed@katibah.net

1343 Views   11 Replies   Latest reply: edkatibah, Jun 12, 2012 1:36 PM
 
Replies
  • cppasm
    Currently Being Moderated
    1. cppasm,
    Jun 12, 2012 12:03 AM   in reply to edkatibah
    Report

    Your GPX file contains extensions to GPX specification describing in what color to display your track and other additional information.

    Try converting it to basic GPX file using GPSBabel (just load your GPX and convert to GPX) and see if this helps.

     
    |
    Mark as:
  • edkatibah
    Currently Being Moderated
    2. edkatibah,
    Jun 12, 2012 7:58 AM   in reply to cppasm
    Report

    @1.cppasm

     

    Thanks for the pointer to GPSBabel.  I did as you suggested but GPSBabel did not remove the extensions sections you pointed out:

     

            <extensions>

                <gpxx:TrackExtension>

                    <gpxx:DisplayColor>Green</gpxx:DisplayColor>

                </gpxx:TrackExtension>

            </extensions>

     

    So I opened the GPX file in TextWrangler and removed the <extensions> section, saved the GPX file and re-opened it as a track log in Lightroom.  And no joy, the rendering issue still persists...

     
    |
    Mark as:
  • edkatibah
    Currently Being Moderated
    3. edkatibah,
    Jun 12, 2012 8:41 AM   in reply to edkatibah
    Report

    I just opened the GPX file in GPSBabel and displayed over Google Maps.  GPSBabel has no issue with this GPX file...

    Screen shot 2012-06-12 at 8.35.21 AM.jpg

     
    |
    Mark as:
  • Dorin Nicolaescu-Musteață
    Currently Being Moderated
    4. Dorin Nicolaescu-Musteață,
    Jun 12, 2012 11:48 AM   in reply to edkatibah
    Report

    A similar issue. http://forums.adobe.com/message/4459571

     

    And just like yours, the other tracklog did not have timestamps. I guess that is what's confusing Lightroom. Not sure it's a bug or a design limitation.

     
    |
    Mark as:
  • edkatibah
    Currently Being Moderated
    5. edkatibah,
    Jun 12, 2012 12:37 PM   in reply to Dorin Nicolaescu-Musteață
    Report

    @ Dorin Nicolaescu-Musteață

     

    ;-) That's my post, too.  I was searching everywhere looking for someone who could give me some insight into the issue.  Based on your comments, I did, however, open the GPX file in TextWrangler and performed a Search and Replace,

     

    replacing

     

         </ele>

     

    with

     

         </ele><time>2012-06-12T14:44:24Z</time>

     

    The time is a non-changing, static value which I took from the time tag earlier in the GPX file. With this modification, Lightroom correctly rendered (!!finally!!) the GPX file. 

     

    I did try an even simpler

     

    replace

     

      </ele>

     

    with

     

      </ele><time></time>

     

    tags but Lightroom choked on this structure.

     

    Here is the GPX track correctly rendered in Lightroom 4.1:

    Screen shot 2012-06-12 at 12.19.11 PM.jpg

    Quite a difference, eh?

     

    Now, let's hope that Adobe developement reads this post and fixes this issue.

     
    |
    Mark as:
  • CR Henderson
    Currently Being Moderated
    6. CR Henderson,
    Jun 12, 2012 12:54 PM   in reply to Dorin Nicolaescu-Musteață
    Report

    Dorin Nicolaescu-Musteață wrote:

     

    A similar issue. http://forums.adobe.com/message/4459571

     

    And just like yours, the other tracklog did not have timestamps. I guess that is what's confusing Lightroom. Not sure it's a bug or a design limitation.

    It should be noted that Garmin GPS units will remove the date/time information from a track point that was not created directly by a GPS fix in the unit. 

     

    This means that any track that is uploaded to the Garmin GPS from a PC or is the result of compressing--called saving in some Garmin units--the track will not contain date/time information.

     
    |
    Mark as:
  • Ian Lyons
    Currently Being Moderated
    7. Ian Lyons,
    Jun 12, 2012 12:57 PM   in reply to edkatibah
    Report

    You're not helping yourself by double posting, just confusing the hell out of folk who are trying to help.

     

    As others have already mentioned, your GPX file is messed up with a bunch of info that Lr can't use or understand. Also, the lack of timestamps doesn't help.

     

    If file is still on your Etrex try copying it across to your hard drive again, but don't use BaseCamp. Instead connect the Etrex to your Mac via USB then set it up as a USB Mass Storage Device (i.e. choose Interface from Etrex Setup menu)

     
    |
    Mark as:
  • CR Henderson
    Currently Being Moderated
    8. CR Henderson,
    Jun 12, 2012 1:11 PM   in reply to Ian Lyons
    Report

    Ian Lyons wrote:

     

    <...>

     

    As others have already mentioned, your GPX file is messed up with a bunch of info that Lr can't use or understand. Also, the lack of timestamps doesn't help.

     

    I suspect that the extraneous information isn't the problem.  His file is a syntatically correct .gpx file and as such should be read without problem by LR.  However, without the benefit of a time stamp there is no valid method of determining the order of the data points.  The order of the points in the file is a normally accepted method, but it is not standardized.  I write my own .gpx files using my own software.  My files contain lots of added information and LR reads them without a problem.

     

     

    Ian Lyons wrote:

     

    <...>

     

    If file is still on your Etrex try copying it across to your hard drive again, but don't use BaseCamp. Instead connect the Etrex to your Mac via USB then set it up as a USB Mass Storage Device (i.e. choose Interface from Etrex Setup menu)

    I don't believe the eTrex communicates via USB mass storage--at least the early ones didn't, they required communication be via the Garmin Interface Specification which was originally applied only to RS232.  Later the spec was 'wrapped' by further information and Garmin used it for USB.  The use of the USB mass storage method arrived with the nuvi series and has prevailed since then.  So it is possible that your suggestion doesn't apply.

     
    |
    Mark as:
  • edkatibah
    Currently Being Moderated
    9. edkatibah,
    Jun 12, 2012 1:18 PM   in reply to Ian Lyons
    Report

    Interesting about the "double posting" since I clearly referenced this post in the other forum.  Additionally, I was led to believe that the other forum (http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_1_in correctly_renders_gpx_track_logs) was for reporting defects in Lightroom.  My mistake.

     
    |
    Mark as:
  • Ian Lyons
    Currently Being Moderated
    10. Ian Lyons,
    Jun 12, 2012 1:30 PM   in reply to edkatibah
    Report

    The post Dorin linked to above was at http://forums.adobe.com/message/4459571#4459571 not the Community Feedback forums. If you'd followed his link you'd see it a different user name, a different GPS device, but same problem, and missing the same info.

     
    |
    Mark as:
  • edkatibah
    Currently Being Moderated
    11. edkatibah,
    Jun 12, 2012 1:36 PM   in reply to edkatibah
    Report

    @CR Henderson

     

    Your observations on the older eTrex units are right on.  The particular unit that I am using, eTrex Summit HC, is indeed an older unit and while quite accurate, apparently drops the timestamp under certain conditions.  The Garmin BaseCamp software, in any event, does drop the timestamp associated with individual point locations in a track.

     

    It's noteworthy that the new Garmin Forerunner 910XT, which I will now use in place of the eTrex, does not drop the timestamp, even when used with Garmin BaseCamp software and produces GPX files which can be consumed with Lightroom successfully.  Here is sample clip from the GPX file produced by the 910XT:

     

    ...

        <trk>

            <name>2012-04-20T15:26:48Z</name>

            <extensions>

                <gpxx:TrackExtension>

                    <gpxx:DisplayColor>DarkGray</gpxx:DisplayColor>

                </gpxx:TrackExtension>

            </extensions>

            <trkseg>

                <trkpt lat="37.864622538909316" lon="-122.088304460048676">

                    <ele>156.799987799999997</ele>

                    <time>2012-04-20T15:26:48Z</time>

                    <extensions>

                        <gpxtpx:TrackPointExtension>

                            <gpxtpx:hr>65</gpxtpx:hr>

                        </gpxtpx:TrackPointExtension>

                    </extensions>

                </trkpt>

    ...

            </trkseg>

        </trk>

    ...

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)