your welcome

Found another issue reading linestrings.
The coordinates seem to be produced in 2 ways.
1 separated by spaces
2 separated by linefeeds

have changed line 97 to
lines = strsplit (strtrim (coords), {" ","\n"});

an example file with linefeeds is "greaterhobarttrails-hobart-hobart-to-the-pinnacle.kml"

After this fix all my kml's passed.

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:

:
          <Placemark>
            <TimeSpan>
              <begin>2010-01-01T00:00:00Z</begin>
              <end>2010-01-01T00:00:00Z</end>
            </TimeSpan>
            <Style>
              <IconStyle>
              <scale>0.9</scale>
              <Icon>
                <href>http://connect.garmin.com/image/main/icons/kml/grn-play.png</href>
              </Icon>
            </IconStyle>
            </Style>
            <Point>
              <altitudeMode>clampToGround</altitudeMode>
              <coordinates>138.83341203443706,-34.710941025987267,346</coordinates>
            </Point>
          </Placemark>
:

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 work.

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.

Another file I have has points without elevation data. It uses the <altitudeMode>clampToGround</altitudeMode> method.

This fails on line 72 as xyz doesn't have a 3rd entry for elevation.

attached file is "COURSE_20667693.kml"

Better take this kmlread.m (forgot to move some cell2mat code into if blocks).

(file #49623)

I've pushed some fixes here:
http://hg.code.sf.net/p/octave/mapping/rev/35aca628cc6b
and attached the resulting kmlread.m.
Please report if this fixes reading other kml files you have lying around.

From what I can see in ParraWirra.kml the XYZ coordinates of the individual Placemarks and those in the LineString section are identical.

Anyway, based on your findings in comment #4 I'll probably postpone further fixes. Which doesn't mean I won't work at it, or someoe else might, it's just that I have no time & priority for it in the coming months.

Have tested kmlread on a few files with id tags and name subnodes and it works well

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)

the part of kmlread that tries to parse the placemark text does not handle the case when the placemark has an id or the following point/linestring/polygon has an id.

eg the kml syntax for placemark and point are

<Placemark>
Syntax
<Placemark id="ID">
  <!-- inherited from Feature element -->
  <name>...</name>                      <!-- string -->
  <visibility>1</visibility>            <!-- boolean -->
  <open>0</open>                        <!-- boolean -->
  <atom:author>...<atom:author>         <!-- xmlns:atom -->
  <atom:link href=" "/>                <!-- xmlns:atom -->
  <address>...</address>                <!-- string -->
  <xal:AddressDetails>...</xal:AddressDetails>  <!-- xmlns:xal -->
  <phoneNumber>...</phoneNumber>        <!-- string -->
  <Snippet maxLines="2">...</Snippet>   <!-- string -->
  <description>...</description>        <!-- string -->
  <AbstractView>...</AbstractView>      <!-- Camera or LookAt -->
  <TimePrimitive>...</TimePrimitive>
  <styleUrl>...</styleUrl>              <!-- anyURI -->
  <StyleSelector>...</StyleSelector>
  <Region>...</Region>
  <Metadata>...</Metadata>              <!-- deprecated in KML 2.2 -->
  <ExtendedData>...</ExtendedData>      <!-- new in KML 2.2 -->

  <!-- specific to Placemark element -->
  <Geometry>...</Geometry>
</Placemark>


<Point>
Syntax
<Point id="ID">
  <!-- specific to Point -->
  <extrude>0</extrude>                        <!-- boolean -->
  <altitudeMode>clampToGround</altitudeMode>
        <!-- kml:altitudeModeEnum: clampToGround, relativeToGround, or absolute -->
        <!-- or, substitute gx:altitudeMode: clampToSeaFloor, relativeToSeaFloor -->
  <coordinates>...</coordinates>              <!-- lon,lat[,alt] -->
</Point>



I have it working by changing line 58 to
 pnam = cell2mat (regexp (xml(max (1, il - 1000):il+7), ...
                               '<Placemark.*?<name>(.+?)</name>.*?<Point', "tokens")){end};

lines 81 and 116 could be changed similarly.

I have not tested this extensively