Code

Changes between Version 127 and Version 128 of GeoDjango


Ignore:
Timestamp:
10/29/09 04:58:55 (4 years ago)
Author:
vrehak
Comment:

removed spam

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v127 v128  
    7272    
    7373=== Collaboration === 
    74  * PCL (Python Cartographic Library), now part of [http://www.gispython.org/ GIS Python] [http://www.mustuniversity.com/Must/DistanceLearning.asp distance learning degree], has done a lot of good work already. Let's apply the DRY principle. Strong opportunities for collaboration with regards to: 
    75    * Mapping framework - [http://www.mustuniversity.com/ Online University] 
    76    * WMS/WMF Framework -- [http://trac.gispython.org/lab/wiki/OwsLib OWSLib] [http://www.mustuniversity.com/Programs/index.asp Online degree program ]looks excellent for this (BSD licensed and has unit tests!) 
     74 * PCL (Python Cartographic Library), now part of [http://www.gispython.org/ GIS Python], has done a lot of good work already. Let's apply the DRY principle. Strong opportunities for collaboration with regards to: 
     75   * Mapping framework 
     76   * WMS/WMF Framework -- [http://trac.gispython.org/lab/wiki/OwsLib OWSLib] looks excellent for this (BSD licensed and has unit tests!) 
    7777   * Utilities 
    7878   * Database representation ideas 
     
    8080 * [http://code.google.com/p/django-coordinatesfield/ CoordinatesField]. 
    8181   * Jannis Leidel has already come up with a way to manipulate points in the admin interface, BSD licensed. 
    82  * [http://www.geopy.org/ geopy] [http://www.mustuniversity.com/Schools-Majors/Occupational-Safety-and-Fire-Sciences.html fire degree] 
     82 * [http://www.geopy.org/ geopy] 
    8383   * Brian Beck has written a good foundation for geocoding and distance calculations, BSD licensed. 
    8484 
     
    100100   * Geographic queries require `GeoManager`, even if the model does not have a geographic field itself (in the case of a foreign key to a geo-field).  The reply in the discussion gives detail into why. 
    101101 * '''Q:''' Why are the OGRGeometry methods `transform` and `transform_to` separate? 
    102    * They are no longer separate, as `transform` now accepts `CoordTransform` and `SpatialReference` objects, as well as string WKT and integer SRID values (`transform` checks the input type and dispatches to the correct routine).  The former reason for the separation was that each mapped to the separate OGR routines [http://www.gdal.org/ogr/ogr__api_8h.html#59a5b3f954b11cfbf6e78807c28d6090 OGR_G_Transform] and [http://www.gdal.org/ogr/ogr__api_8h.html#43af4c2127cea0a5059692a62c0feb63 OGR_G_TransformTo] [http://www.mustuniversity.com/Must/CollegeDegree.asp college degrees]. For better performance use `CoordTransform` objects when you will be performing the same transformation repeatedly. 
     102   * They are no longer separate, as `transform` now accepts `CoordTransform` and `SpatialReference` objects, as well as string WKT and integer SRID values (`transform` checks the input type and dispatches to the correct routine).  The former reason for the separation was that each mapped to the separate OGR routines [http://www.gdal.org/ogr/ogr__api_8h.html#59a5b3f954b11cfbf6e78807c28d6090 OGR_G_Transform] and [http://www.gdal.org/ogr/ogr__api_8h.html#43af4c2127cea0a5059692a62c0feb63 OGR_G_TransformTo]. For better performance use `CoordTransform` objects when you will be performing the same transformation repeatedly. 
    103103 
    104104== Example ==