Just noticed that the geotools and geoapi do not share the same
understanding of the BBOX filter.
[EMAIL PROTECTED] SpatialOperator Spatial operator} that evaluates to [EMAIL PROTECTED]
true} when the bounding
box of the feature's geometry overlaps the bounding box provided in this
object's properties.
An implementation may choose to throw an exception if one attempts to test
features that are in a different SRS than the SRS contained here.
Our geotools implementations check the geometry for not disjoint with
the literal envelope. This does agree with our recent review of the
Filter specification ....
The <BBOX> element is defined as a convenient and more compact way of
encoding the very common bounding box constraint based on the gml:Box
geometry. It is equivalent to the spatial operation <Not><Disjoint> …
</Disjoint></Not> meaning that the <BBOX> operator should identify all
geometries that spatially interact with the box in some manner.
So I am figuring that GeoAPI needs a javadoc fix ... shall I make a Jira?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
