You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: sly [Added to the original trac issue at 9.17pm, Sunday, 8th May 2011]
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.
Reporter: magic_doc
[Submitted to the original trac issue database at 10.24am, Friday, 18th February 2011]
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:
1970-00-00T00:00:00.000ZUploading 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 tag.
which is of cause not correct!
1970-00-00T00:00:00.000ZWhen I remove all lines with the Elevation-Tag, that it looks like this here:
then the import works flawlessly.
The text was updated successfully, but these errors were encountered: