Opened 16 years ago
Closed 15 years ago
#2181 closed defect (fixed)
KML: Encoding issue and mixed container
| Reported by: | lhahne | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.6.1 |
| Component: | OGR_SF | Version: | 1.5.0 |
| Severity: | normal | Keywords: | kml |
| Cc: |
Description
Ogr2ogr and ogrinfo fail to open a KML file which has no problems opening with Google Earth.
Attachments (1)
Change History (3)
by , 16 years ago
comment:1 by , 16 years ago
| Component: | Utilities → OGR_SF |
|---|---|
| Keywords: | kml added |
| Summary: | Ogr2ogr and ogrinfo fail to open a KML file → KML: Encoding issue and mixed container |
comment:2 by , 15 years ago
| Milestone: | → 1.6.1 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
In trunk (r16908) and branches/1.6 (r16909) : "KML: Add support for reading MultiGeometry and layers with mixed geometry type. Avoid quadratic complexity when reading KML files. Advertize 25D geometry type when relevant"
Test improved in r16910
Note:
See TracTickets
for help on using tickets.
I've improved a bit in r13623 the reporting of XML parsing error of the KML driver. Here the first problem is that the "Windows-1252" encoding of the XML file that is not handled by the Expat library out of the box. See the section "Encoding issues" of the GPX driver http://www.gdal.org/ogr/drv_gpx.html, that also uses the Expat library. I think that supporting other encodings is possible, but require additionnal work from the application.
I've replaced "Windows-1252" by "ISO-8859-1", but the reading stops with "KML: We have a mixed container here" (message reported in debug mode), which is an issue already reported as #1803 and #1853.
I took the liberty to rename the summary to reflect both issues