Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7232 closed defect (fixed)

KML file locks ogrinfo, QGIS

Reported by: ndawson Owned by: warmerdam
Priority: normal Milestone: 2.2.4
Component: OGR_SF Version: 2.2.3
Severity: normal Keywords:
Cc:

Description

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.

Attachments (1)

doc.kml (3.4 KB ) - added by ndawson 6 years ago.
Faulty KML

Download all attachments as: .zip

Change History (9)

by ndawson, 6 years ago

Attachment: doc.kml added

Faulty KML

comment:1 by Jukka Rahkonen, 6 years ago

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

comment:2 by Even Rouault, 6 years ago

Resolution: fixed
Status: newclosed

In 41430:

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

comment:3 by Even Rouault, 6 years ago

In 41431:

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

comment:4 by Even Rouault, 6 years ago

Milestone: 2.2.4

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

comment:5 by Even Rouault, 6 years ago

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

comment:6 by Jukka Rahkonen, 6 years ago

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

comment:7 by Even Rouault, 6 years ago

In 41433:

Adjustment for refs #7232

comment:8 by Even Rouault, 6 years ago

In 41434:

Adjustment for refs #7232

Note: See TracTickets for help on using tickets.