Changes between Version 123 and Version 124 of GeoDjango

Timestamp:

Mar 11, 2009, 2:42:31 PM (16 years ago)

Author:

jbronn

Comment:

question about GeoQ is irrelevant now

GeoDjango

@@ -101 +101 @@
  * '''Q:''' Why are the OGRGeometry methods `transform` and `transform_to` separate?
    * 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.
- * '''Q:''' Why don't `Q` objects work?
-   * `Q` object functionality is for use with models that use `QuerySet`.  Because !GeoDjango models use `GeoQuerySet`, use the `GeoQ` object instead:
-{{{
->>> from django.contrib.gis.db.models import GeoQ
->>> from geoapp.models import City, Country, State # See django.contrib.gis.tests.geoapp
->>> tx = Country.objects.get(name='Texas')
->>> ks = State.objects.get(name='Kansas')
->>> City.objects.filter(GeoQ(point__within=tx.mpoly) | GeoQ(point__within=ks.poly))
-[<City: Houston>, <City: Dallas>, <City: Lawrence>]
-}}}
 
 == Example ==