Code

Changes between Version 17 and Version 18 of GeoDjango


Ignore:
Timestamp:
02/26/07 10:35:56 (7 years ago)
Author:
Jeremy Dunck <jdunck@…>
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v17 v18  
    2525 
    2626=== GeoTypes === 
    27   GeoTypes supports only psycopg1, which is dead.  Porting it to Psycopg2 doesn't look too terrible.  Upside is conversion from type params to SQL.  Simplifies (avoids?) QuerySet modification. 
     27  GeoTypes supports only psycopg1, which is dead.  Porting it to Psycopg2 doesn't look too terrible.  Upside is conversion from type params to SQL.  Simplifies (avoids?) QuerySet modification.  Maintainer of GeoTypes has been responsive as of Feb 26 2007 on the psycopg mailing list. 
     28  Example code, where point and box are types from GeoTypes: 
     29{{{ 
     30Schools.objects.geo_near(point=x, radius=1.0) 
     31Schools.objects.geo_within(bound_box=box) 
     32}}} 
    2833 
    2934=== Geos === 
    3035  I'm not sure how we can use GEOS without also doing something like GeoTypes down in the QuerySet.  Ideas? 
    3136 
    32 {{{ 
    33  
    34 Schools.objects.geo_near(point=x, radius=1.0) 
    35 Schools.objects.geo_within(bound_box=box) 
    36 }}} 
    3737 
    3838