Opened 11 years ago

Closed 8 years ago

#11999 closed New feature (wontfix)

Support for Google Maps encoded geometries

Reported by: Robert Coup Owned by: Robert Coup
Component: GIS Version:
Severity: Normal Keywords: gmaps
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


When displaying polygons and polylines with GMaps, performance can be massively improved by using encoded geometries. It would be great for GeoDjango to support this:

  • a module to encode geometries and return a dictionary, so people can JSON-encode and send to the client, embed in templates, etc.
  • use encoded geometries in GoogleGeoAdmin


Change History (7)

comment:1 Changed 11 years ago by Robert Coup

Owner: changed from nobody to Robert Coup
Status: newassigned

I've built a Python port of Mark McClure's Javascript encoder. There's also a matching C extension which has the same signature (think cStringIO vs StringIO). Other upsides: clean, pythonic, BSD licensed, unit tests. :)

Will be on Google Code somewhere in the next few days, or part of the gmaps-utility-library project.

comment:3 Changed 11 years ago by Russell Keith-Magee

Triage Stage: UnreviewedDesign decision needed

comment:4 Changed 9 years ago by Peter Baumgartner

Severity: Normal
Type: New feature

comment:5 Changed 9 years ago by Aymeric Augustin

UI/UX: unset

Change UI/UX from NULL to False.

comment:6 Changed 9 years ago by Aymeric Augustin

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:7 Changed 8 years ago by Aymeric Augustin

Resolution: wontfix
Status: assignedclosed

This ticket has a large scope, the problems it describes are covered by an external library, and I don't see a good reason to merge it in Django.

Note: See TracTickets for help on using tickets.
Back to Top