[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: Tue, 4 Aug 2020 09:43:02 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

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

That Nan thing is a very old bug :-) thx forspotting that. I'll fix it.

<altitudeMode>clampToGround</altitudeMode> doesn't quite rule out elevation
data. The elevations are behind the Lat/Lon coordinates, see e.g., first
Placemark in ParraWirra.kml:


The last ",346" in the coordinates subnode is the elevation. I think the
"clamptoground" option usually does need an elevation as the processing
application undoubtedly needs to know the ground level elevation to clamp to
in the first place, doesn't it.
But yes in COURSE_20667693.kml they're lacking. I guess to cater for that
requires testing for nr. of commas (field separators) in the coordinates
subnode and based on that perform the reshape and Z assignment.
Needs to be done elsewhere in kmlread.m as well, I'm afraid. Could be a bit of

As I said in comment #6 I'll put this aside for the next period; if you can
suggest fixes or upload patches I'll happily review them.


Reply to this item at:


  Message sent via Savannah

reply via email to

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