Changes between Version 67 and Version 68 of GeoDjango


Ignore:
Timestamp:
04/15/2007 11:48:11 PM (8 years ago)
Author:
jbronn
Comment:

simplified some docs, added some links

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v67 v68  
    5757 * [http://mapserver.gis.umn.edu/ MapServer]: University of Minnesota (UMN) "open source development environment for building spatially-enabled internet applications."
    5858 * [http://www.mapnik.org/ Mapnik]: C++ and Python toolkit for developing mapping applications.  Claimed benefits over MapServer: "It uses the AGG library and offers world class anti-aliasing rendering with subpixel accuracy for geographic data. It is written from scratch in modern C++ and doesn't suffer from design decisions made a decade ago." ''See'' [http://www.mapnik.org/faq/ MapNik FAQ].
     59 * [http://code.google.com/p/pyproj/ pyproj]: Pyrex generated python interface to PROJ.4 library.
    5960 * Ruby on Rails
     61   * [http://rubyforge.org/projects/georuby/ GeoRuby]: Interface for PostGIS and MySQL spatial extensions, but not sure about spatial querying.
    6062   * [http://www.ivygis.org/ IvyGIS]: Google-maps type displays with RoR and UMN's MapServer
    6163   * [http://thepochisuperstarmegashow.com/ProjectsDoc/spatialadapter-doc/index.html Spatial Adapter for Rails]: A plugin for Rails which manages the MySql Spatial and PostGIS geometric columns in a transparent way (that is like the other base data type columns).  This might have some useful techniques for when we try to support other spatial extensions other than PostGIS.
     
    104106   * '''Update:''' As of r5008, GeoDjango has its own GEOS interface (via {{{ctypes}}})
    105107   * GEOS is no longer maintained by Sean Gillies.  ''See'' Sean Gillies, ''[http://zcologia.com/news/150/geometries-for-python/ Geometries for Python]'' (blog post explaining rationale for abandoning GEOS support); ''see also'' Sean's message on the [http://geos.refractions.net/pipermail/geos-devel/2007-March/002851.html GEOS-Devel Mailing List] (Mar. 5, 2007).
    106    * Might consider either using PCL or implement a {{{ctypes}}} wrapper for the routines that we need -- can't really port PCL code here because it is GPL (Django is licensed under BSD).
     108   * Might consider either ~~using PCL~~ or implement a {{{ctypes}}} wrapper for the routines that we need -- can't really port PCL code here because it is GPL (Django is licensed under BSD).
    107109 * WMS Server
    108110   * I'm not satisfied with any of the current WMS/WFS implementations.   One implemented in Django would be desirable, e.g., {{{django.contrib.gis.wms}}}.  Thoughts anyone?  (OWSLib looks good, see below)
     
    389391== Extra Instance Methods ==
    390392
    391 A model with geometry fields will get the following methods:
     393A model with geometry fields will get the following methods, substitute {{{GEOM}}} with the name of the geometry field:
    392394
    393395== get_GEOM_geos ==
    394 For every geometry field the model instance will have a {{{get_GEOM_geos}}} method, where {{{GEOM}}} is the name of the geometry field.  Returns a {{{GEOSGeometry}}} instance for the geometry.  For example (using the {{{District}}} model from above):
     396Returns a {{{GEOSGeometry}}} instance for the geometry.  For example (using the {{{District}}} model from above):
    395397
    396398{{{
     
    413415== get_GEOM_wkt ==
    414416
    415 For every geometry field, the model instance will have a {{{get_GEOM_wkt}}} method, where {{{GEOM}}} is the name of the geometry field.  For example (using the {{{School}}} model from above):
     417Returns the OGC WKT (Well Known Text) for the geometry.  For example (using the {{{School}}} model from above):
    416418
    417419{{{
     
    424426== get_GEOM_centroid ==
    425427
    426 For every geometry field, the model instance will have a {{{get_GEOM_centroid}}} method, where {{{GEOM}}} is the name of the geometry field.  This routine will return the centroid of the geometry.  For example (using the {{{District}}} model from above):
     428This routine will return the centroid of the geometry.  For example (using the {{{District}}} model from above):
    427429
    428430{{{
     
    435437== get_GEOM_area ==
    436438
    437 For every geometry field, the model instance will have a {{{get_GEOM_area}}} method, where {{{GEOM}}} is the name of the geometry field.  This routine will return the area of the geometry.
     439This routine will return the area of the geometry field.
    438440
    439441{{{
     
    444446}}}
    445447
    446 '''Note''': The units system needs to be figured out here, since I don't know what these units represent.
     448'''Note''': Units are in the projected units of the coordinate system.  In the example above, the units are in degrees since we're using WGS84.  ~~The units system needs to be figured out here, since I don't know what these units represent~~.
Back to Top