Changes between Version 128 and Version 129 of GeoDjango


Ignore:
Timestamp:
05/10/2010 08:02:12 PM (5 years ago)
Author:
pbx
Comment:

Links to GIS branch were producing 500 errors; removed them from the page and added a note/link under News.

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v128 v129  
    22
    33[[TOC(GeoDjangoBackground, GeoDjango, GeoDjangoInstall, GeoDjangoModelAPI, GeoDjangoDatabaseAPI, GEOSGeometry, GeoDjangoExtras)]]
    4 The [http://code.djangoproject.com/browser/django/branches/gis GIS] branch intends to be a world-class geographic web framework.  Our goal is to make it as easy as possible to build GIS web applications and harness the power of spatially enabled data.
     4The GIS branch intends to be a world-class geographic web framework.  Our goal is to make it as easy as possible to build GIS web applications and harness the power of spatially enabled data.
    55
    66''News:''
     7 * Having been merged to trunk, the !GeoDjango branch is now in [browser:django/branches/attic the Attic]; direct links to it have been removed from this page.
    78 * !GeoDjango is featured in the [http://www.geoconnexion.com/uploads/opensource_14_intv7i9.pdf October 'Open Sources' Column] by contributer Dane Springmeyer in [http://www.geoconnexion.com/geo.php GeoConnexion International Magazine]
    89 * !GeoDjango was merged to trunk on 5th August 2008!
     
    2425The wiki documentation is woefully behind, please use the [http://geodjango.org/docs/ 1.0 documentation]. 
    2526
    26 When in doubt, use `help` on the feature in question, as most [browser:django/branches/gis/django/contrib/gis GeoDjango modules] and routines have docstrings.
     27When in doubt, use `help` on the feature in question, as most GeoDjango modules and routines have docstrings.
    2728
    2829== Roadmap ==
     
    4748 * 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].
    4849 * r5529: Added utilities for importing vector data (e.g., SHP files) directly into !GeoDjango models. 
    49      * 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].
     50     * The !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].
    5051
    5152
    52  * 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]
     53 * r5397: Added a `ctypes` interface for [http://www.gdal.org/ogr/ogr_arch.html GDAL/OGR] in django.contrib.gis.gdal
    5354   * `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()`).
    5455   * `SpatialReference`: Wraps [http://www.gdal.org/ogr/classOGRSpatialReference.html OGR Spatial Reference] objects, may be used to transform OGR geometries.
    5556   * `DataSource`: Wraps [http://www.gdal.org/ogr/classOGRDataSource.html OGR Data Source] objects, may be used to explore GDAL-supported data sources
    56  * r5008: Added a `ctypes` interface for [http://geos.refractions.net/ GEOS] in [source:django/branches/gis/django/contrib/gis/gdal django.contrib.gis.geos].
     57 * r5008: Added a `ctypes` interface for [http://geos.refractions.net/ GEOS] in django.contrib.gis.geos.
    5758   * `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.
    5859 * r4851: Added PostGIS indexing capability.
     
    6263=== Design Issues ===
    6364 * Client JS/Flash framework.  The `maps` module will be added soon, support for the following APIs will be implemented, or is being considered
    64    * [browser:django/branches/gis/django/contrib/gis/maps/google django.contrib.gis.maps.google]: Contains the `GoogleMap` object, which generates basic Google Maps API !JavaScript from customizable templates.  Automatic zoom-level determination is included.
     65   * django.contrib.gis.maps.google: Contains the `GoogleMap` object, which generates basic Google Maps API !JavaScript from customizable templates.  Automatic zoom-level determination is included.
    6566   * `django.contrib.gis.maps.openlayers`: Similar plans are in place for a [http://www.openlayers.org/ OpenLayers] module, which is ''the'' open source web mapping framework.  Well-tested, BSD-licensed, and includes multitudes of features; for example, !OpenLayers supports WMS/WFS/tiles as well as Google, MS Virtual Earth, and Yahoo layers.  ''See also'' ticket #5472.
    6667   * [http://developer.yahoo.com/maps/ Yahoo!] , [http://platform.mapquest.com/specs-free.html MapQuest], and [http://www.mapstraction.com/ Mapstraction] are all possibilities for API hooks.
Back to Top