Incorrect boundedBy in FeatureCollection
----------------------------------------

                 Key: GEOS-3020
                 URL: http://jira.codehaus.org/browse/GEOS-3020
             Project: GeoServer
          Issue Type: Bug
          Components: WFS
    Affects Versions: 1.7.4
         Environment: Windows 2003 Server, Tomcat 5.5.27, Java 1.6.13
            Reporter: Gerhard Sommer
            Assignee: Andrea Aime
            Priority: Minor


If WFS is configured not to include bounding boxes, the bounding box for the 
complete result is null:

<wfs:FeatureCollection xmlns="http://www.opengis.net/wfs"; 
xmlns:wfs="http://www.opengis.net/wfs"; 
xmlns:vienna="http://www.wien.gv.at/ows/wfs/gml"; 
xmlns:gml="http://www.opengis.net/gml"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://ntsdeadv1:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd 
http://www.wien.gv.at/ows/wfs/gml 
http://ntsdeadv1:8080/geoserver/wfs?service=WFS&amp;version=1.0.0&amp;request=DescribeFeatureType&amp;typeName=vienna:MZK_SITFE";>
        <gml:boundedBy>
                <gml:null>unknown</gml:null>
        </gml:boundedBy>
        <gml:featureMember>
...

I think this is bug, as it should display the bounding box around all the 
features in this FeatureCollection.

If WFS is configured to include bounding boxes, all bounding boxes, even for 
each Feature are included, as can be expected. But the bounding box at the 
FeatureCollection level shows a much bigger bounding box:

<wfs:FeatureCollection xmlns="http://www.opengis.net/wfs"; 
xmlns:wfs="http://www.opengis.net/wfs"; 
xmlns:vienna="http://www.wien.gv.at/ows/wfs/gml"; 
xmlns:gml="http://www.opengis.net/gml"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://ntsdeadv1:8080/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd 
http://www.wien.gv.at/ows/wfs/gml 
http://ntsdeadv1:8080/geoserver/wfs?service=WFS&amp;version=1.0.0&amp;request=DescribeFeatureType&amp;typeName=vienna:MZK_SITFE";>
        <gml:boundedBy>
                <gml:Box 
srsName="http://www.opengis.net/gml/srs/epsg.xml#31256";>
                        <gml:coordinates xmlns:gml="http://www.opengis.net/gml"; 
decimal="." cs="," ts=" ">-1221.41100000031,334744.782 
4249.51400000043,340498.812999999</gml:coordinates>
                </gml:Box>
        </gml:boundedBy>
        <gml:featureMember>
..

The selection in both cases included the following BBOX filter:

      <ogc:BBOX>
        <ogc:PropertyName>SHAPE</ogc:PropertyName>
        <gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#31256";>
          <gml:coordinates>1600,337000 3000,338150</gml:coordinates>
        </gml:Box>
      </ogc:BBOX>

and there is not one single negative coordinate in the result (which should be 
the case, if the lower left corner of the bounding box starts with -1221!).

So what does this bounding box describe?

I think, that in any case it should be a box, which encloses all features in 
the result. It makes sense to configure GeoServer, so that it does not output 
the boundedBy Element for each feature. But it makes also much sense to always 
include the correct bounding box for all the features in the result. Maybe this 
is the reason, why gml:boundedBy is not optional in the 
AbstractFeatureCollectionBaseType. To output gml:null instead of the 
coordinates will validate against the schema, but it would be more useful to 
output the correct bounding box.

Best Regards,
Gerhard


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to