[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: Sat, 1 Aug 2020 08:31:02 -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:                    None => Need Info              
             Assigned to:                    None => philipnienhuis         
                 Release:                   5.2.0 => other                  


Follow-up Comment #2:

Thanks for this bug report and your analysis.

Rather than "Hubert_100_social_training_run.kml" you supplied
"KoziClassic.kml" but that also gives some insight :-)

That KoziClassic.kml file shows that many more nodes can have an id tag; e.g.,
the Point, LineString and Polygon subnodes. So the regexp format strings will
have to be adapted a bit more than you suggest.
I provisionally fixed the latter issue by omitting the last ">" from the
regexp format strings because the id tags can have arbitrary length and
consequently, that last ">" could fall of the substring selected in the regexp
call anyway.

A first draft of a kmlread.m fixed for the id tags is attached, please try.

Can you still upload that Hubert_100_social_training_run.kml? than I can look
into the missing "name" subnodes as well.

(file #49597)

Additional Item Attachment:

File name: kmlread.m                      Size:7 KB


Reply to this item at:


  Message sent via Savannah

reply via email to

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