Opened 8 years ago

Closed 8 years ago

#3548 closed defect (fixed)

Anonymous Timestamps + Elevation in gpx-File causes GPX Import Failure

Reported by: Michael Roesch Owned by: Tom Hughes
Priority: minor Milestone:
Component: website Version:
Keywords: gpx upload website import failure Cc:

Description

I always used the anonymous-timestamp-function in the gpxedit-plugin in JOSM and uploaded many tracks without issues.

Now my GPS-Software started adding elevation-tags in the tracks like this:

<trkpt lat="29.00017" lon="-13.490498">

<time>1970-00-00T00:00:00.000Z</time>

<ele>41.00</ele>

</trkpt>

Uploading that track causes the following error:

failed to import. Here's the error:

Found no good GPX points in the input data. At least 75% of the trackpoints lacked a <time> tag.

which is of cause not correct! When I remove all lines with the Elevation-Tag, that it looks like this here:

<trkpt lat="29.00017" lon="-13.490498">

<time>1970-00-00T00:00:00.000Z</time>

</trkpt>

then the import works flawlessly.

Change History (3)

comment:1 Changed 8 years ago by Michael Roesch

Resolution: invalid
Status: newclosed

sorry my failure- the problem was not the <ele>-Tags but the invalid date-format produced by the editgpx-Plugin in JOSM: substituting

1970-00-00T00:00:00.000

by

1970-01-01T00:00:00.00

does the trick!

So it is no OSM-related issue I must contact the author of the plugin!

comment:2 Changed 8 years ago by sly

Resolution: invalid
Status: closedreopened

After a bit of digging, I re-open this bug as the syntax YYYY-MM-DDThh:mm:ss.fffz for the gpx time tag is possible.

Of course, in the osm context milliseconds are irrelevant, but since it is supported by the gpx specs, some gpx generator might add millisecond and cause the gpx import to fail.

comment:3 Changed 8 years ago by Tom Hughes

Resolution: fixed
Status: reopenedclosed

This was fixed some time ago.

Note: See TracTickets for help on using tickets.