Opened 16 years ago

Closed 14 years ago

#1897 closed defect (fixed)

KML driver output appears broken

Reported by: darkblueb Owned by: condit
Priority: normal Milestone:
Component: OGR_SF Version: svn-trunk
Severity: major Keywords: kml
Cc: condit, Mateusz Łoskot

Description

KML output from ogr2ogr does not open in GoogleEarth

KML SoC driver, nor KML driver 1.4.2

remove the <Multipolygon> tag, file can be opened,

though the polys are filled rather than outlines

Note that the SoC KML driver internally uses a v2.0 spec that is no longer on the web

related ticket #1766

GoogleEarth v4.2.0180.1134 (beta), 20Aug07, Mac OSX

Change History (10)

comment:1 by Even Rouault, 16 years ago

To be more precise, <Multipolygon> is not in v2.1 spec.

comment:2 by warmerdam, 16 years ago

Cc: condit added
Severity: blockermajor

Chris,

Do you have any thoughts on this?

Does it make sense to upgrade generation to KML 2.1 if 2.0 seems not well supported?

in reply to:  2 comment:3 by condit, 16 years ago

Owner: changed from warmerdam to condit
Status: newassigned

I actually think this is a display bug with Google Earth because it does parse / display everything else in KML 2.0 correctly. But it is part of a larger issue - and we should switch the KML output to at least 2.1 if not 2.2. I'm sure that 2.2 will go in as an OGC spec, but the question is when. So perhaps for now I'll just update the driver to output 2.1...

Replying to warmerdam:

Chris,

Do you have any thoughts on this?

Does it make sense to upgrade generation to KML 2.1 if 2.0 seems not well supported?

comment:4 by Mateusz Łoskot, 16 years ago

Cc: Mateusz Łoskot added

comment:5 by condit, 16 years ago

I've updated SVN to support KML 2.2 and would like to test this defect again. Could you attach the original problematic file?

comment:6 by jvdvegt, 15 years ago

I noticed other noncompliances in the KML output from ogr2ogr in FWTools 2.2.6:

  • <schema> element is added to <folder>, should be attached to <document>.
  • <schema> element has no 'id' nor 'type' attribute.
  • <SchemaData> uses the 'schemaURL' attribute, should be 'schemaUrl'.

in reply to:  6 comment:7 by darkblueb, 15 years ago

Replying to jvdvegt:

I noticed other noncompliances in the KML output from ogr2ogr in FWTools 2.2.6:

  • <schema> element is added to <folder>, should be attached to <document>.
  • <schema> element has no 'id' nor 'type' attribute.
  • <SchemaData> uses the 'schemaURL' attribute, should be 'schemaUrl'.

Is <document> formally required?

comment:8 by jvdvegt, 15 years ago

No, <Document> is not required (see spec here http://schemas.opengis.net/kml/2.2.0/ogckml22.xsd ). <kml> contains either NetworkLinkControl, AbstractFeatureGroup, KmlSimpleExtensionGroup or KmlObjectExtensionGroup. Both <Document> and <Folder> implement a AbstractContainerGroup, which implement a AbstractFeatureGroup.
Note that this seems quite different from the 2.1 spec.

comment:9 by condit, 15 years ago

Corrected the latter two problems (id and case of schemaUrl). This is checked in. The schema change is slightly more extensive. I'll have a look at that next...

comment:10 by Even Rouault, 14 years ago

Resolution: fixed
Status: assignedclosed

Schema writing has been implemented (some issues though : #2858, #2868)

Note: See TracTickets for help on using tickets.