Ticket #1897 (closed defect: fixed)

Opened 5 years ago

Last modified 3 years ago

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, mloskot

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

  Changed 5 years ago by rouault

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

follow-up: ↓ 3   Changed 5 years ago by warmerdam

  • cc condit added
  • severity changed from blocker to major

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   Changed 5 years ago by condit

  • owner changed from warmerdam to condit
  • status changed from new to assigned

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?

  Changed 5 years ago by mloskot

  • cc mloskot added

  Changed 4 years ago by condit

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

follow-up: ↓ 7   Changed 4 years ago by 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'.

in reply to: ↑ 6   Changed 4 years ago by darkblueb

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?

  Changed 4 years ago by jvdvegt

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.

  Changed 4 years ago by condit

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...

  Changed 3 years ago by rouault

  • status changed from assigned to closed
  • resolution set to fixed

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

Note: See TracTickets for help on using tickets.