[Octave-bug-tracker] [bug #58854] [octave forge] (mapping) kmlread does not handle id tags when trying to parse placemark text

[Geoff Warne]

Follow-up Comment #9, bug #58854 (project octave):

Found a problem with a kml file that had a mixed time format in the <when>
</when> field.

It happened that when the time ticked over midnight there was one entry with
only the date, no time.

I will attach the file its called "2020-50km-Course.kml"

This grab from a KML Reference indicates that it is valid.



Elements Specific to TimeStamp
<when>
Specifies a single moment in time. The value is a dateTime, which can be one
of the following:
dateTime gives second resolution
date gives day resolution
gYearMonth gives month resolution
gYear gives year resolution
The following examples show different resolutions for the <when> value:

gYear (YYYY)
<TimeStamp>
  <when>1997</when>
</TimeStamp>

gYearMonth (YYYY-MM)
<TimeStamp>
  <when>1997-07</when>
</TimeStamp> 

date (YYYY-MM-DD)
<TimeStamp>
  <when>1997-07-16</when>
</TimeStamp> 

dateTime (YYYY-MM-DDThh:mm:ssZ)
Here, T is the separator between the calendar and the hourly notation of time,
and Z indicates UTC. (Seconds are required.)
<TimeStamp>
  <when>1997-07-16T07:30:15Z</when>
</TimeStamp>

dateTime (YYYY-MM-DDThh:mm:sszzzzzz)
This example gives the local time and then the ± conversion to UTC.
<TimeStamp>
  <when>1997-07-16T10:30:15+03:00</when>
</TimeStamp>

    _______________________________________________________

Reply to this item at:

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

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