Ticket #1766 (closed defect: fixed)

Opened 10 months ago

Last modified 10 months ago

OGR KML Driver - writes v2.0, reads only v2.1

Reported by: darkblueB Assigned to: Didge
Priority: normal Milestone: 1.5.0
Component: OGR_SF Version: svn-trunk
Severity: normal Keywords: kml
Cc: warmerdam, mloskot

Description

the new KML driver for OGR requires KML v2.1 when reading. KML Files produced by the driver via ogr2ogr are set as v2.0.

This is a problem (at least) because many real world work flows would call for making changes to KML iteratively.

KML driver v15 from Google SoC site GDAL 1.4.2 otherwise

Change History

08/27/07 12:40:07 changed by warmerdam

  • keywords set to kml.
  • owner changed from warmerdam to Didge.
  • version changed from unspecified to svn-trunk.
  • cc set to warmerdam, mloskot.
  • milestone set to 1.5.0.

Jens,

What is needed to relax the KML reading code so it supports KML 2.0 as well as 2.1? Ideally also older and newer KML variants. The general rule of thumb is that OGR drivers should be as flexible as practical in the versions of a format that they can read.

08/30/07 07:36:30 changed by Didge

  • status changed from new to closed.
  • resolution set to fixed.

I added two more lines to also detect 2.0 and 2.2 (beta). That's just done by parsing the kml-tag for the xml namespace. There is no documentation for 2.0 so I don't know what the differences are. But I think they will not affect the parsing of kml in ogr.