[Geoserver-devel] 'bbox' parameter on WMS request

GeoServer GeoServer Developer
1

Should the 'bbox' parameter result in a bounding box query being issued to the datastore, assuming that the bbox values are smaller than the extents of the feature?

I'm seeing 'calling sql builder with filter null' in the log output. Should the datastore be telling someone that it can handle spatial queries?

Regards,
David

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.2.0 - Release Date: 2/21/2005

2

Hi David,

could you please provide the following information?:

- the complete request your're sending
- the stack trace
- tell what backend are you querying (postgis, arcsde, shapefile, etc)

best regards,

Gabriel.

On Tue, 2005-02-22 at 13:16 -0500, David Adler wrote:

Should the 'bbox' parameter result in a bounding box query being issued to
the datastore, assuming that the bbox values are smaller than the extents
of the feature?

I'm seeing 'calling sql builder with filter null' in the log
output. Should the datastore be telling someone that it can handle spatial
queries?

Regards,
David

3

Should the 'bbox' parameter result in a bounding box query being issued to
the datastore, assuming that the bbox values are smaller than the extents
of the feature?

Yes.

I'm seeing 'calling sql builder with filter null' in the log
output. Should the datastore be telling someone that it can handle spatial
queries?

Yeah, in the FilterCapabilities of the SQLEncoder. The Encoder should
turn the filter into the sql statements for the datastore, and it should
statically add what Filters it can handle. See
http://svn.geotools.org/geotools/trunk/gt/plugin/postgis/src/org/geotools/filter/SQLEncoderPostgisGeos.java
(all the capabils.addType()s - it is a bit messy, but it's how we do it.

Then the datastore will call the SQLUnpacker to split up the Filter and
figure out where to process it - in the datastore, encoding it, or
post-processing with Java. If you're datastore is a JDBC one then I think
this should all happen automatically, as long as you have the right
FilterCapabilities.

best regards,

Chris

Regards,
David

--

4

Chris answered my question - the SQLEncoder subclass for the specific data store needs to provide via
getFilterCapabilities the fact that AbstractFilter.GEOMETRY_BBOX is supported. After putting this in, it worked like magic.

At 02:25 PM 2/22/2005, Gabriel Roldán wrote:

Hi David,

could you please provide the following information?:

  • the complete request your’re sending
  • the stack trace
  • tell what backend are you querying (postgis, arcsde, shapefile, etc)

best regards,

Gabriel.

On Tue, 2005-02-22 at 13:16 -0500, David Adler wrote:

Should the ‘bbox’ parameter result in a bounding box query being issued to
the datastore, assuming that the bbox values are smaller than the extents
of the feature?

I’m seeing ‘calling sql builder with filter null’ in the log
output. Should the datastore be telling someone that it can handle spatial
queries?

Regards,
David

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.2.0 - Release Date: 2/21/2005


SPAM: ---------------------- Spamnix Spam Report ----------------------
SPAM: Spamnix identified this message as spam.
SPAM: Score: 52
SPAM: Action: Quarantine
SPAM: ------------------- End of Spamnix Spam Report ------------------