Code

Changes between Version 98 and Version 99 of GeoDjango


Ignore:
Timestamp:
10/15/07 13:50:12 (7 years ago)
Author:
jbronn
Comment:

updated roadmap, got rid of the phases.

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v98 v99  
    2020'''Note:''' In order to minimize confusion, please don't modify the official roadmap below.  If you have a suggestion, place it in the [wiki:GeoDjango#Suggestions suggestion section] or ask your question in the [wiki:GeoDjango#FAQ FAQ].  If your request is urgent, submit a ticket requesting your feature or bugfix (make sure to specify the component as 'GIS').  Thanks for your cooperation! 
    2121 
    22 === Phase 1 === 
    23  * Create Geometry-enabled fields and manager.  Status: complete as of r4788. 
    24  * Allow for Geometry-enabled queries.  Status: complete as of r4788. 
    25  
    26 === Phase 2 === 
    27  * '''Pending''' 
    28    * Distance queries, calculations, and related utilities.  Status:  
    29      * 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) 
    30      * 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. 
    31    * Support for a mapping framework (''e.g.'', Google Maps/Earth, Yahoo Maps, MS Live, etc.) 
    32      * Admin fields and forms (WKT field currently as of r4884, but we want widgets to view and manipulate geographic objects). 
    33    * WMS views. 
    34    * Add as much from the PostGIS API as possible. 
    35  * '''Complete''' 
    36    * PostGIS indexing capability. 
    37    * As of r5008, added a {{{ctypes}}} interface for [http://geos.refractions.net/ GEOS] in [source:django/branches/gis/django/contrib/gis/gdal django.contrib.gis.geos]. 
    38      * {{{GEOSGeometry}}}: Wraps [http://geos.refractions.net/ro/doxygen_docs/html/classgeos_1_1geom_1_1Geometry.html GEOS geometries]; all accessed geometry fields are returned as {{{GEOSGeometry}}} instances. 
    39    * As of r5397, added a {{{ctypes}}} interface for [http://www.gdal.org/ogr/ogr_arch.html GDAL/OGR] in [source:django/branches/gis/django/contrib/gis/gdal django.contrib.gis.gdal].   
    40      * {{{OGRGeometry}}}: Wraps [http://www.gdal.org/ogr/classOGRGeometry.html OGR geometries], may be accessed with an extra instance method (''e.g.'', {{{z.get_poly_ogr()}}}). 
    41      * {{{SpatialReference}}}: Wraps [http://www.gdal.org/ogr/classOGRSpatialReference.html OGR Spatial Reference] objects, may be used to transform OGR geometries. 
    42      * {{{DataSource}}}: Wraps [http://www.gdal.org/ogr/classOGRDataSource.html OGR Data Source] objects, may be used to explore GDAL-supported data sources  
    43    * As of r5529, there are utilities for importing vector data (''e.g.'', SHP files) directly into !GeoDjango models.   
    44      * The [source:django/branches/gis/django/contrib/gis/utils/LayerMapping.py LayerMapping] class will import vector data from GDAL-supported data sources.  This is still 'beta', and requires installation of the [wiki:GeoDjango#GDAL GDAL library]. 
    45    * As of r5657, "Lazy-Geometry" support was added (courtesy of Robert Coup's excellent patch in #4322) -- deprecating most of the  [wiki:GeoDjangoDatabaseAPI#ExtraInstanceMethods extra instance methods]. 
    46    * As of of r6497, the `GeoMixin` was completely deprecated. 
    47  
    48 === Phase 3 === 
     22=== Pending Features === 
     23The 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.  
     24 * Distance queries, calculations, and related utilities.  Status:  
     25   * 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) 
     26   * 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. 
     27 * Support for a mapping framework (''e.g.'', Google Maps/Earth, Yahoo Maps, MS Live, etc.) 
     28   * Admin fields and forms (WKT field currently as of r4884, but we want widgets to view and manipulate geographic objects). 
     29 * WMS views. 
     30 * Add as much from the PostGIS API as possible. 
    4931 * Support additional spatial databases, in the following order of priority. 
    5032   * Oracle Spatial (spatial support is included in Oracle's Express Edition) 
     
    5436     * MySQL is last because its spatial offerings are not compliant with either the OGC and SQL/MM specifications.  Specifically, all operations are limited to the bounding boxes of the geometries. 
    5537 * Geocoding framework. 
     38=== Milestones === 
     39Significant !GeoDjango changesets are mentioned below: 
     40 * r4851: Added PostGIS indexing capability. 
     41 * r5008: Added a {{{ctypes}}} interface for [http://geos.refractions.net/ GEOS] in [source:django/branches/gis/django/contrib/gis/gdal django.contrib.gis.geos]. 
     42   * {{{GEOSGeometry}}}: Wraps [http://geos.refractions.net/ro/doxygen_docs/html/classgeos_1_1geom_1_1Geometry.html GEOS geometries]; all accessed geometry fields are returned as {{{GEOSGeometry}}} instances. 
     43 * r5397: Added a {{{ctypes}}} interface for [http://www.gdal.org/ogr/ogr_arch.html GDAL/OGR] in [source:django/branches/gis/django/contrib/gis/gdal django.contrib.gis.gdal].   
     44   * {{{OGRGeometry}}}: Wraps [http://www.gdal.org/ogr/classOGRGeometry.html OGR geometries], may be accessed with an extra instance method (''e.g.'', {{{z.get_poly_ogr()}}}). 
     45   * {{{SpatialReference}}}: Wraps [http://www.gdal.org/ogr/classOGRSpatialReference.html OGR Spatial Reference] objects, may be used to transform OGR geometries. 
     46   * {{{DataSource}}}: Wraps [http://www.gdal.org/ogr/classOGRDataSource.html OGR Data Source] objects, may be used to explore GDAL-supported data sources  
     47 * r5529: Added utilities for importing vector data (''e.g.'', SHP files) directly into !GeoDjango models.   
     48     * The [source:django/branches/gis/django/contrib/gis/utils/LayerMapping.py LayerMapping] class will import vector data from GDAL-supported data sources.  This is still 'beta', and requires installation of the [wiki:GeoDjango#GDAL GDAL library]. 
     49 * r5657: "Lazy-Geometry" support was added (courtesy of Robert Coup's excellent patch in #4322) -- deprecating most of the  [wiki:GeoDjangoDatabaseAPI#ExtraInstanceMethods extra instance methods]. 
     50 * r6497: the `GeoMixin` was completely deprecated. 
    5651 
    5752== Implementation ==