Changes between Version 105 and Version 106 of GeoDjango

Timestamp:

Dec 8, 2007, 9:59:47 PM (17 years ago)

Author:

jbronn

Comment:

Updated roadmap

GeoDjango

@@ -23 +23 @@
 === Pending Features ===
 The following is a discussion of features we hope to implement in !GeoDjango.  Unless stated otherwise, features in this list are not prioritized.  If you have a pet feature you may accelerate its development by submitting code yourself. 
- * Distance queries, calculations, and related utilities.  Status: 
-   * Robert Coup has contributed the excellent [http://code.djangoproject.com/browser/django/branches/gis/django/contrib/gis/measure.py measure] module (in {{{django.contrib.gis.measure}}}), allowing for easy comparison of distances in a variety of formats (currently supported: feet, meters, yards, kilometers, miles, and nautical miles)
-   * No support in the database API yet, but performing spatial queries using output from the [wiki:GEOSGeometry GEOS] {{{buffer()}}} function may tide you over until we implement full support.
- * Support for a mapping framework (''e.g.'', Google Maps/Earth, Yahoo Maps, MS Live, etc.)
+ * Distance Queries
+   * Aggregate distance function and distance lookup types added as of r6886.
+   * Improve support for non-projected coordinate systems.
+ * Support for a mapping framework (''e.g.'', Open Layers, Google Maps/Earth, Yahoo Maps, MS Live, etc.)
    * Admin fields and forms (WKT field currently as of r4884, but we want widgets to view and manipulate geographic objects).
+   * Progress has been made on this front by multiple parties; we are currently waiting for `newforms-admin` to merge before fully committing to a strategy.
  * WMS views.
  * Add as much from the PostGIS API as possible.