Code

Changes between Version 15 and Version 16 of GeoDjangoDatabaseAPI


Ignore:
Timestamp:
03/09/08 20:44:30 (6 years ago)
Author:
springmeyer
Comment:

Small grammatical changes in the geodjango wiki

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjangoDatabaseAPI

    v15 v16  
    44'''Note:''' All !GeoDjango queries are performed via the `GeoQuerySet`, a modified version of Django's `QuerySet` that enables the construction of spatial SQL.  
    55 
    6 !GeoDjango's lookup types can only be used with on geographic fields with `filter()`.  Filters on 'normal' fields (e.g. `CharField`) may be chained with those on geographic fields.  Thus, geographic queries take the following form (assuming the `Zip` model used in the [wiki:GeoDjangoModelAPI GeoDjango Model API docs]): 
     6!GeoDjango's lookup types can only be used on geographic fields with `filter()`.  Filters on 'normal' fields (e.g. `CharField`) may be chained with those on geographic fields.  Thus, geographic queries take the following form (assuming the `Zip` model used in the [wiki:GeoDjangoModelAPI GeoDjango Model API docs]): 
    77{{{ 
    88#!python 
     
    332332 
    333333= Extra Instance Methods = 
    334 '''Update:''' All of the extra instance methods haave been deprecated as of r6467 because lazy geometry support includes all of their functionality (including OGR geometries and OSR spatial references with the `ogr` and `srs` properties, respectively).  In other words, these properties may be directly accessed as attributes from the geometry field. 
     334'''Update:''' All of the extra instance methods have been deprecated as of r6467 because lazy geometry support includes all of their functionality (including OGR geometries and OSR spatial references with the `ogr` and `srs` properties, respectively).  In other words, these properties may be directly accessed as attributes from the geometry field.