[Gdal-dev] GDAL/OGR and Postgres
Ethan Alpert
ealpert at digitalglobe.com
Wed Oct 12 13:30:15 EDT 2005
poSpatialFilter is for Layers and doesn't apply to an entire datasource.
When you're calling ExecuteSQL you're calling the datasource directly
hence you must include your spatial filter into the where clause of you
SQL statement. At least that's my understanding.
-e
-----Original Message-----
From: gdal-dev-bounces at lists.maptools.org
[mailto:gdal-dev-bounces at lists.maptools.org] On Behalf Of Marc Florisson
Sent: Wednesday, October 12, 2005 10:39 AM
To: gdal-dev at lists.maptools.org
Subject: [Gdal-dev] GDAL/OGR and Postgres
Hi,
I wonder how to filter reults with ExecuteSQL (from OGRDataSource class)
- With mif/mid files I don't have any trouble.
- But with Postgres 8.0.4 (installed with Postgis extension and GDAL has
been compiled with Postgres support),
ExecuteSQL doesn't read the second parameter (poSpatialFilter) and I get
too much results./
/What should I do to make it work ?/
//
/
_______________________________________________
Gdal-dev mailing list
Gdal-dev at lists.maptools.org
http://lists.maptools.org/mailman/listinfo/gdal-dev
More information about the Gdal-dev
mailing list