[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58701] [octave-forge] (mapping) gpxread time

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #58701] [octave-forge] (mapping) gpxread time parsing error with decimal seconds
Date: Tue, 4 Aug 2020 07:43:52 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #12, bug #58701 (project octave):

Yep you're right.
Do you think that with that last mod we can close this bug report? The
original issue has been fixed.

What I couldn't test was a "real" file w/o time and ele subnodes. I just
created one by regexprep'ing out the time nodes from "COURSE_19341403.gpx"
(easily done in notepad++) but then you get an artificial file, not one made
by GPS devices or googleearth or so. It worked fine though.

There will come a moment when I look into time subnodes for waypoints (it's on
the ToDo list), but that is another issue than the subject of this bug report
(which has already drifted somewhat).


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]