Hi,

I think that such check should be optional. The bounding box that gets saved 
when the layer is created may not stay valid if the data are updated and new 
features are added with WFS-T or just directly to the data source. And 
obviously the check should only stop the queries if BBOX is totally outside the 
data extents.


I do not know how expensive the out-of-range requests are but I guess that 
bounding box filter could only make things faster but not any slower. But if 
you decide to go that way, why to do the test with an inaccurate bounding box? 
About 50% of the BBOX of Finland is actually Sweden, Russia, Norway, or empty 
sea. How about making an additional configuration option "Bounding Polygon" and 
use that? A further development step would be to make the integrated GWC to 
utilize this Bounding Polygon as well.


-Jukka Rahkonen-


________________________________
Lingbo Jiang wrote:

Hi Geoserver community,
For every WMS layer that has latLongBoundingBox set up in the config, GeoServer 
may restrict the request to the configured latLongBoundingBox. At the moment, 
it doesn't, and this results in unnecessary query and wastes connections and 
cursors (for Oracle).
Thus I propose to add an option in the code for latLongBoundingBox range 
checking. the option will allow to filter the none result query which is out of 
latLongBoundingBox range and improve the performance.
If community reckon that it is the right way, I am willing to submit a code 
patch to implement it if necessary.
Thanks first,
Lingbo

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to