[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58854] [octave forge] (mapping) kmlread does

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #58854] [octave forge] (mapping) kmlread does not handle id tags when trying to parse placemark text
Date: Sun, 2 Aug 2020 12:07:34 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Update of bug #58854 (project octave):

                  Status:               Need Info => In Progress            


Follow-up Comment #5:

Thanks for Parrawirra.kmz, let's see what can be done.
The upload limit here is small (16 MB) and I never know if that is before or
after 7-bit encoding which tends to expand files by sometimes 30 % :-)
But zipped and esp. 7-zipped or bzipped files may make it within the limits.

Looking TL;DR tru the file I see a few more things that "need attention".
TimeSpan rather than Time nodes, MultiGeometry (although that just duplicates
the Lon/Lat coordinates), to name a few.
.kml files (actually .xml) are read using regular expressions (XML gurus
probably frown here). Now, regexps, while usually much faster than XML
parsers, expect a fairly rigid file layout. For complicated and much varying
file formats like .kml it is very hard to be able to catch all file layouts.
On top of that Octave has no options for XML I/O (see a.o., bug #58004).

And disclaimer: kmlread.m has been marked "experimental" for a reason.

But I'll have a look. As with gpxread.m a fix may not be in time for a next
mapping package release though.


Reply to this item at:


  Message sent via Savannah

reply via email to

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