[Octave-bug-tracker] [bug #58701] [octave-forge] (mapping) gpxread time parsing error with decimal seconds

[Philip Nienhuis]

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

Well, I had another idea, a bit simpler but at the cost of some performance.
Maybe a kludge but it seems to work reliably for me:
http://hg.code.sf.net/p/octave/mapping/rev/de81ba0397f6

Please try attached new gpxread.m (with this fix) and report back.

I also had a go at reading time nodes for waypoints but that is a headache as
such nodes may be missing for some waypoints.

(file #49613)
    _______________________________________________________

Additional Item Attachment:

File name: gpxread.m                      Size:8 KB
    <https://file.savannah.gnu.org/file/gpxread.m?file_id=49613>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58701>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/