Opened 17 years ago
Closed 17 years ago
#1766 closed defect (fixed)
OGR KML Driver - writes v2.0, reads only v2.1
| Reported by: | darkblueB | Owned by: | Didge |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.5.0 |
| Component: | OGR_SF | Version: | svn-trunk |
| Severity: | normal | Keywords: | kml |
| Cc: | warmerdam, Mateusz Łoskot |
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 (2)
comment:1 by , 17 years ago
| Cc: | added |
|---|---|
| Keywords: | kml added |
| Milestone: | → 1.5.0 |
| Owner: | changed from to |
| Version: | unspecified → svn-trunk |
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
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.
Note:
See TracTickets
for help on using tickets.
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.