Opened 11 years ago

Closed 11 years ago

Last modified 9 years ago

#4347 closed defect (fixed)

KMLSuperoverlay files cannot be read by Google Earth 6.1.0.5001

Reported by: Even Rouault Owned by: Even Rouault
Priority: normal Milestone:
Component: GDAL_Raster Version: unspecified
Severity: normal Keywords: kml kmlsuperoverlay
Cc: warmerdam, Kyle Shannon

Description

See http://lists.osgeo.org/pipermail/gdal-dev/2011-November/030893.html

"""Possible issue with output (from http://earth.google.com/support/bin/answer.py?answer=40901):

To conform more closely with the OGC KML 2.2 standard, we've made the parsing of the <coordinates> tag more strict in version 6.1. Spaces must only be used to separate the (longitude,latitude,altitude) triplets which specify the coordinates of a single point. It is invalid to add spaces between individual coordinates. We understand that previous versions of the client were more lenient, so if your KML files contain spaces beween coordinates in coordinate triplets, an easy workaround is to remove all whitespace located immediately before or after commas inside a <coordinates> tag."""

Change History (4)

comment:1 by Even Rouault, 11 years ago

Resolution: fixed
Status: newclosed

r23385 /trunk/gdal/frmts/kmlsuperoverlay/kmlsuperoverlaydataset.cpp: KMLSuperoverlay: remove spaces between coordinates in coordinate triplets as mandated by KML 2.2 spec, to restore compatibility with Google Earth 6.1.0.5001 (#4347)

r23386 /branches/1.8/gdal/frmts/kmlsuperoverlay/kmlsuperoverlaydataset.cpp: KMLSuperoverlay: remove spaces between coordinates in coordinate triplets as mandated by KML 2.2 spec, to restore compatibility with Google Earth 6.1.0.5001 (#4347)

comment:2 by warmerdam, 11 years ago

Cc: warmerdam added

comment:3 by Even Rouault, 9 years ago

Milestone: 1.8.2

Milestone 1.8.2 deleted

comment:4 by Kyle Shannon, 9 years ago

Cc: Kyle Shannon added
Note: See TracTickets for help on using tickets.