Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#7231 closed defect (fixed)

LIBKML driver on Windows doesn't properly detect x, y, z coordinates

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

Description

On Windows 10, LIBKML doesn't properly read xyz coordinates probably due to whitespace.

From Even Rouault:

From testing, it appears that the presence of newline+tabulations without spaces between coordinate triplets is the cause of the issue, where libkml doesn't detect properly the start of the x coordinate of the new triplet and mangles it with the z of the previous one.

I attached a file for testing.

Attachments (1)

flight1.kml​ (1.1 KB ) - added by annakrat 7 years ago.
kml for testing

Download all attachments as: .zip

Change History (4)

by annakrat, 7 years ago

Attachment: flight1.kml​ added

kml for testing

comment:1 by Even Rouault, 7 years ago

Resolution: → fixed
Status: new → closed

In 41418:

LIBKML: workaround Windows specific issue with libkml (at least the version used by OSGeo4W at time of writing), where tabulations as coordinate separators aren't properly handled (fixes #7231)

comment:2 by Even Rouault, 7 years ago

In 41419:

LIBKML: workaround Windows specific issue with libkml (at least the version used by OSGeo4W at time of writing), where tabulations as coordinate separators aren't properly handled (fixes #7231)

comment:3 by Even Rouault, 7 years ago

Milestone: → 2.2.4
Note: See TracTickets for help on using tickets.