Opened 6 years ago

Closed 3 years ago

#11999 closed New feature (wontfix)

Support for Google Maps encoded geometries

Reported by: rcoup Owned by: rcoup
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 6 years ago by rcoup

  • Needs documentation unset
  • Needs tests unset
  • Owner changed from nobody to rcoup
  • Patch needs improvement unset
  • Status changed from new to assigned

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 6 years ago by russellm

  • Triage Stage changed from Unreviewed to Design decision needed

comment:4 Changed 5 years ago by baumer1122

  • Severity set to Normal
  • Type set to New feature

comment:5 Changed 4 years ago by aaugustin

  • UI/UX unset

Change UI/UX from NULL to False.

comment:6 Changed 4 years ago by aaugustin

  • Easy pickings unset

Change Easy pickings from NULL to False.

comment:7 Changed 3 years ago by aaugustin

  • Resolution set to wontfix
  • Status changed from assigned to closed

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