Code

Changes between Version 5 and Version 6 of GeoDjango1.2


Ignore:
Timestamp:
12/14/09 17:25:19 (5 years ago)
Author:
jbronn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango1.2

    v5 v6  
    1010 
    1111These tickets and features are a high priority for inclusion into `django.contrib.gis` for the Django 1.2 release. 
     12 
     13If you want a preview, clone the [http://geodjango.org/hg/gis-1.2/ gis-1.2] repository from the !GeoDjango mercurial. 
    1214 
    1315=== Multiple Database Support  === 
     
    2729 * #12154: `OGRGeometry` coordinate dimension change upon transform 
    2830 * Need more robust KML serialization to better support 3D (see below) 
     31 * What about the admin? 
    2932 
    3033=== Map Widgets === 
     
    3336   * #9806: `GeometryField` crashes the geographic admin 
    3437   * #11002: Map widgets for databrowse 
     38 * Related projects: 
     39   * Charles !DeTar's [http://github.com/yourcelf/olwidget olwidget]. 
    3540 
    3641=== PostGIS Geography Support === 
    37  * Add support for the PostGIS 1.5 geography type. 
     42 * Add support for the PostGIS 1.5 [http://postgis.refractions.net/documentation/manual-svn/ch04.html#PostGIS_Geography geography] type.   
     43 * Current API in testing is to set `geography` keyword on the geometry field (only SRID of 4326 supported): 
     44{{{ 
     45from django.contrib.gis.db import models 
     46 
     47class City(models.Model): 
     48    point = models.PointField(geography=True) 
     49    objects = models.GeoManager() 
     50 
     51}}} 
     52 * API limited to subset of supported [http://postgis.refractions.net/documentation/manual-svn/ch08.html#PostGIS_GeographyFunctions geography functions]. 
    3853 
    3954=== KML === 
     
    4661 * Upgrade KML templates to use 2.2 
    4762 
     63=== Geometry Backend === 
     64 * Backend Information: 
     65   * Was necessary to decouple from database; makes it possible to swap out geometry representation used within the rest of !GeoDjango 
     66   * Set `GEOMETRY_BACKEND` to change from GEOS (default) to a different included backend, or with the module name of the user's choice. 
     67   * Requirements: 
     68     * `Geometry` and `GeometryException` objects 
     69     * `Geometry` objects require: 
     70       * Serialization properties: `wkb`, `wkt`, `ewkt`, `ewkb` 
     71       * Attribute properties: `coord_dim`, `geom_type` (string), `srid` 
     72 
     73 * Initial Backends (housed in `django.contrib.gis.geometry.backend`): 
     74   * `geos`: default, uses `GEOSGeometry` 
     75   * `gdal`: uses `OGRGeometry` (actually faster at parsing than GEOS) 
     76   * `ogr`: thin wrapper over [http://trac.osgeo.org/gdal/wiki/GdalOgrInPython GDAL's SWIG bindings] 
     77   * `shapely` subclass of or thin wrapper over [http://trac.gispython.org/lab/wiki/Shapely Shapely] 
     78 
    4879=== GEOS === 
    4980 * #10923: Use thread-safe GEOS API 
    5081 * #12010: Add `ewkb` and `hexewkb` properties and document the GEOS IO Classes 
     82 * Add support for the [http://trac.gispython.org/lab/wiki/PythonGeoInterface Python Geo Interface] 
     83   * Create a `__geo_interface__` property that returns a dictionary containing the `type`, `coordinates`, and `crs` of the `GEOSGeometry` 
     84   * Use the interface to create GeoJSON when GDAL not available, e.g., `simplejson.dumps(self.__geo_interface__)` 
     85   * Be able to initialize arbitrary Python objects that implement the `__geo_interface__` protocol 
     86 
     87=== GDAL === 
     88 * #12154: `OGRGeometry` coordinate dimension change upon transform 
     89 * Add serialization properties for compatibility as geometry backend: `ewkb`, `hexewkb`, `ewkt` 
     90 * Add support for the Python Geo Interface 
     91   * Same as above, but will be easier to implement 
    5192 
    5293=== `GeoQuerySet` Methods === 
     
    5495 * #11854: Add support for PostGIS `ST_Azimuth` 
    5596   * Also considering: `ST_GeoHash`, `ST_ForceRHR`, `ST_MinimumBoundingCircle` 
    56  * `GeoQuerySet` method "in-place" option? 
     97 * `GeoQuerySet` method `in-place` keyword option? 
    5798 
    5899=== Google Maps === 
     
    67108 
    68109=== Google Maps === 
    69  * #11211: Add `GMarkerOptions`: `clickable`, `bouncy`, `dragCrossMove`, `bounceGravity`, `autoPan` and `hide`. 
     110 * #11211: Add `GMarkerOptions`: `clickable`, `bouncy`, `dragCrossMove`, `bounceGravity`, `autoPan` and `hide` 
    70111 * #11458: Add `GPolylineOptions` and `GPolygonOptions` to `django.contrib.gis.maps.google.overlays` 
    71112 * #11999: Support for Google Maps encoded geometries