Code

Changes between Version 4 and Version 5 of GeoDjango1.2


Ignore:
Timestamp:
12/14/09 15:53:04 (4 years ago)
Author:
jbronn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango1.2

    v4 v5  
    44 
    55== Overview == 
     6 
     7This document details the features that are forthcoming to !GeoDjango in the 1.2 release. 
    68 
    79== High Priority == 
     
    2022 
    2123=== 3D Geometries === 
    22  * Complete! 
     24 * #11433: Complete support for 3D Geometries 
     25   * Complete! 
    2326   * PostGIS only, but considering support for !SpatiaLite 2.4 
    24  * #11433: Complete support for 3D Geometries 
    2527 * #12154: `OGRGeometry` coordinate dimension change upon transform 
    26  
    27  
    28 === PostGIS Geography Support === 
    29  * Add support for the PostGIS 1.5 geography type. 
     28 * Need more robust KML serialization to better support 3D (see below) 
    3029 
    3130=== Map Widgets === 
     
    3534   * #11002: Map widgets for databrowse 
    3635 
    37 === GEOS API Thread Safety === 
     36=== PostGIS Geography Support === 
     37 * Add support for the PostGIS 1.5 geography type. 
    3838 
     39=== KML === 
     40 * Come up with a more robust method to serialize KML from geometries 
     41   * Need to have way to set `clampToGround`, `relativeToGround`, and `absolute` tags (important for 3D KML) 
     42   * Other tags? 
     43   * Styles? 
     44   * Put in `django.contrib.gis.utils.kml`? 
     45   * Class-based or method-based? 
     46 * Upgrade KML templates to use 2.2 
     47 
     48=== GEOS === 
    3949 * #10923: Use thread-safe GEOS API 
     50 * #12010: Add `ewkb` and `hexewkb` properties and document the GEOS IO Classes 
    4051 
    4152=== `GeoQuerySet` Methods === 
     
    5061 
    5162== Other Tickets and Features == 
    52  
    5363These tickets/features will be considered for inclusion into !GeoDjango for 1.2, but there are no guarantees as core developer time is scarce.  To increase chances of being accepted, the ticket should have a patch, tests, and as much documentation as possible. 
    5464 
    5565=== Miscellaneous === 
    56  
    5766 * #11948: Linear referencing 
    5867 
    5968=== Google Maps === 
    60   * #11211: Add `GMarkerOptions`: `clickable`, `bouncy`, `dragCrossMove`, `bounceGravity`, `autoPan` and `hide`. 
    61   * #11458: Add `GPolylineOptions` and `GPolygonOptions` to `django.contrib.gis.maps.google.overlays` 
    62   * #11999: Support for Google Maps encoded geometries 
     69 * #11211: Add `GMarkerOptions`: `clickable`, `bouncy`, `dragCrossMove`, `bounceGravity`, `autoPan` and `hide`. 
     70 * #11458: Add `GPolylineOptions` and `GPolygonOptions` to `django.contrib.gis.maps.google.overlays` 
     71 * #11999: Support for Google Maps encoded geometries