Bug #9624

GPX reading: False complaints about <time> tag

Added by Torsten Bronger over 6 years ago. Updated over 4 years ago.

Map / Geolocation
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
git development version
hardware architecture:


When reading a GPX file with a <time> element inside a <metadata> element (I attached such a file), DT complaints on the command line:

broken gpx file, element 'time' found outside of trkpt.

However, as fas as I understand <;, this GPX file correct.

track.gpx (637 Bytes) track.gpx Torsten Bronger, 10/20/2013 04:55 PM

Related issues

Has duplicate darktable - Bug #10682: Dark table barfs at mygpx fileFixed10/23/2015


#1 Updated by Christian iuga over 6 years ago

I'm not sure if it's related (it's was long time age, arround 1year)

I was using same kind of gpx file and used them with a perl script (
as now, we can't do it on darktable, i was obligate to modify my gpx file (not a big deal)

darktable need to have at least two point (trkpt) & the image need to be on the interval of these both point.

#2 Updated by Torsten Bronger over 6 years ago

I use big GPX file created with a smartphone. I'm sure that the image's timestamp is surrounded by track points. Besides, if I remove the <time> from <metadata>, there is no complaint anymore.

#3 Updated by Tobias Ellinghaus over 6 years ago

  • System changed from Ubuntu to all
  • % Done changed from 0 to 20
  • Target version set to Future
  • Status changed from New to Triaged
  • Category set to Map / Geolocation

The problem is that the GPX parser we have isn't complete. I could add the missing stuff, but given how easy it is to fix (and how few people complained 'till now) i don't assign this a very high priority for myself. So if anyone wants to do it (it's mostly reading the specs and copy&pasting&changing some code in src/common/gpx.c) feel free to do it.

#4 Updated by Roman Lebedev over 4 years ago

  • Has duplicate Bug #10682: Dark table barfs at mygpx file added

#5 Updated by Roman Lebedev over 4 years ago

  • bitness set to 64-bit
  • % Done changed from 20 to 100
  • Status changed from Triaged to Fixed

Duplicate #10682 was fixed, so i guess this is also fixed?

Also available in: Atom PDF

Go to top