KML file locks ogrinfo, QGIS

[ndawson]

The attached KML file locks ogrinfo. It was apparently created in Google Earth. The issue comes from the LineString with name "test", which contains an empty coordinates element.

[ndawson]

Faulty KML

[Jukka Rahkonen]

I have no problem at all with GDAL 2.3.0dev from yesterday. Both KML and LIBKML driver shows the feature with an empty geometry this way:

OGRFeature(Proposed infrastructure.kml):2
  Name (String) = test
  tessellate (Integer) = 1
  extrude (Integer) = 0
  visibility (Integer) = -1
  Style = @m_ylw-pushpin0
  LINESTRING EMPTY

[Even Rouault]

In 41430:

LIBML: workaround Windows specific issue if the content of <coordinates> is non-empty and does not contain any digit (fixes #7232)

[Even Rouault]

In 41431:

LIBML: workaround Windows specific issue if the content of <coordinates> is non-empty and does not contain any digit (fixes #7232)

[Even Rouault]

I could reproduce with OSGeo4W based builds. As there was also another Windows specific issue yesterday with #7231, I'm wondering if there's not an ABI issue with libkml in OSGeo4W being built with VS != 2015

[Even Rouault]

Withdrawing my above comment: libkml is built with VS2015, but I see warnings at GDAL build time about VS2015 not being supported when including the libkml headers

[Jukka Rahkonen]

The version I used for testing and that had no problem is built with MSVC 2017.

[Even Rouault]

In 41433:

Adjustment for refs #7232

[Even Rouault]

In 41434:

Adjustment for refs #7232