[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: Sun, 2 Aug 2020 11:47:54 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

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

Yeah, mixed time format fields are going to be a big PITA.
That is because Octave's datenum function (like Matlab's) isn't smart enough
to parse a date string vector with varying formats.
I have an idea on how to tackle this but I'm afraid it's going to be a kludge
at first; an IMO satisfactory solution may need a little bit more time.
Hopefully you'll stay with this bug report until a/the final fix is
Good that you uploaded a test file, thanks.

BTW I have plans to make a new mapping release soon, hopefully before
Octave-6.1.0 is released (I guess within 4-6 weeks). As to gpxread.m, the
current fixed version as it stands now is the bottom line so to say. Improved
versions might come after a new release.


Reply to this item at:


  Message sent via Savannah

reply via email to

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