Opened 16 years ago

Last modified 5 years ago

#12416 new New feature

Improve KML Serialization

Reported by: jbronn Owned by:
Component: GIS Version: dev
Severity: Normal Keywords: gis kml 3d style rhr
Cc: Tyler Erickson Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by jbronn)

Currently, there are several problems with the way KML is generated inside GeoDjango:

  1. Now that 3D is supported, there is no way to specify the following element tags, which are important to displaying them in Google Earth: <altitudeMode>, <extrude>, and <tessellate>.
  1. A Z value of 0 needs to be omitted for geometries that are purely 2D (this primarily affects the GEOSGeometry.kml property)
  1. Allow specification of an id for geometries, so that styling rules may be easily applied by the user.
  1. For polygons: "the <coordinates> for polygons must be specified in counterclockwise order. Polygons follow the "right-hand rule," which states that if you place the fingers of your right hand in the direction in which the coordinates are specified, your thumb points in the general direction of the geometric normal for the polygon." ​KML Reference. I'm not sure about implementing this within the 'dumb' kml properties of GEOSGeometry and OGRGeometry, rather GeoQueryset.kml should wrap ST_AsKml in the necessary routines, e.g., ST_Reverse(ST_ForceRHR(ST_AsKml(the_geom))).

Attached is an initial idea for a write_kml routine.

Attachments (1)

write_kml.diff​ (2.1 KB ) - added by jbronn 16 years ago.

Download all attachments as: .zip

Change History (12)

by jbronn, 16 years ago

Attachment: write_kml.diff​ added

comment:1 by jbronn, 16 years ago

Description: modified (diff)

comment:2 by Tyler Erickson, 16 years ago

Cc: Tyler Erickson added

comment:3 by jbronn, 16 years ago

(In [12349]) Added reverse and force_rhr methods to GeoQuerySet. Refs #12416.

comment:4 by Russell Keith-Magee, 16 years ago

Triage Stage: Unreviewed → Accepted

comment:5 by James Bennett, 16 years ago

milestone: 1.2 → 1.3

This doesn't seem to be an actual bug, so I'm punting it off the milestone.

comment:6 by jbronn, 15 years ago

milestone: 1.3 → 1.4
Status: new → assigned

Punting again.

comment:7 by Matt McClanahan, 15 years ago

Severity: → Normal
Type: → New feature

comment:8 by Jacob, 14 years ago

milestone: 1.4

Milestone 1.4 deleted

comment:2 by Aymeric Augustin, 14 years ago

UI/UX: unset

Change UI/UX from NULL to False.

comment:3 by Aymeric Augustin, 14 years ago

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:4 by Mariusz Felisiak, 5 years ago

Owner: jbronn removed
Status: assigned → new
Note: See TracTickets for help on using tickets.
Back to Top