[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: Geoff Warne
Subject: [Octave-bug-tracker] [bug #58701] [octave-forge] (mapping) gpxread time parsing error with decimal seconds
Date: Mon, 3 Aug 2020 04:38:22 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36

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

Have tested successfully with about 100 files and found a couple with an
Here is the Warning.

warning: your pattern caused PCRE to hit its MATCH_LIMIT; trying harder now,
but this will be slow
warning: called from
    gpxread at line 219 column 19

I will attach an example file.

Also looking at your fix I think the second regexprep is not needed as datenum
will match with 1, 2 or 3 decimal places filled.

>> datenum('2020-08-03T18:05:29.001Z','yyyy-mm-ddTHH:MM:SS.FFFZ')
ans =  738006.75381
>> datenum('2020-08-03T18:05:29.01Z','yyyy-mm-ddTHH:MM:SS.FFFZ')
ans =  738006.75381
>> datenum('2020-08-03T18:05:29.1Z','yyyy-mm-ddTHH:MM:SS.FFFZ')
ans =  738006.75381
>> datenum('2020-08-03T18:05:29.Z','yyyy-mm-ddTHH:MM:SS.FFFZ')
ans =  738006.75381
>> datenum('2020-08-03T18:05:29Z','yyyy-mm-ddTHH:MM:SS.FFFZ')
error: ds(0): subscripts must be either integers 1 to (2^63)-1 or logicals
error: called from
    datevec>__date_str2vec__ at line 268 column 12
    datevec at line 144 column 54
    datenum at line 113 column 46


Reply to this item at:


  Message sent via Savannah

reply via email to

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