|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #58701] [octave-forge] (mapping) gpxread time parsing error with decimal seconds |
Date: | Sat, 1 Aug 2020 07:11:47 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 |
Update of bug #58701 (project octave): Status: Need Info => Ready For Test _______________________________________________________ Follow-up Comment #3: I've pushed a fix here: http://hg.code.sf.net/p/octave/mapping/rev/cd4ece3dd87e and attached a new gpxread.m here. Please try it and report if it fixes your problem. [Slightly OT] I also had a look at uncovering Time values from Waypoint nodes (these are currently not read). ATM that isn't possible w/o incurring a severe performance penalty. In case someone wants that functionality please open a new bug report / feature request for it. (file #49596) _______________________________________________________ Additional Item Attachment: File name: gpxread.m Size:8 KB <https://file.savannah.gnu.org/file/gpxread.m?file_id=49596> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58701> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |