Changes between Version 105 and Version 106 of GeoDjango

12/08/2007 09:59:47 PM (13 years ago)

Updated roadmap


  • GeoDjango

    v105 v106  
    2323=== Pending Features ===
    2424The 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.
    25  * Distance queries, calculations, and related utilities.  Status:
    26    * Robert Coup has contributed the excellent [ 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)
    27    * 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.
    28  * Support for a mapping framework (''e.g.'', Google Maps/Earth, Yahoo Maps, MS Live, etc.)
     25 * Distance Queries
     26   * Aggregate distance function and distance lookup types added as of r6886.
     27   * Improve support for non-projected coordinate systems.
     28 * Support for a mapping framework (''e.g.'', Open Layers, Google Maps/Earth, Yahoo Maps, MS Live, etc.)
    2929   * Admin fields and forms (WKT field currently as of r4884, but we want widgets to view and manipulate geographic objects).
     30   * 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.
    3031 * WMS views.
    3132 * Add as much from the PostGIS API as possible.
Back to Top