Hi, Can it really be so that in WFS 1.1.0 the meaning of BBOX given without projection is different when using http GET Key Value Pair (&BBOX=...) than when using http POST and BBOX given inside a Filter? I have understood that in the latter case if BBOX is given without srsName the default is the same than the default srsName of the FeatureType. Now I have been reading from the standard that if the BBOX is given withour crsuri as a KVP then the default is WGS84. If this is the case I feel it is a bit odd but because it is WFS standard I would not be surprised.
Excerpt from the OGC WFS 1.1.0 standard (OGC 04-094) 14.3.3 Bounding box The bounding box parameter, BBOX, is included in this specification for convenience as a shorthand representation of the very common a bounding box filter which would be expressed in much longer form using XML and the filter encoding described in [3]. A BBOX applies to all feature types listed in the request. The KVP encoding for a bounding box is defined in subclause 10.2.3 of normative reference [15]. The general form of the parameter is: BBOX=lcc1,lcc2,...,lccN,ucc1,ucc2,...uccN[,crsuri] where lcc means Lower Corner Coordinate, ucc means Upper Corner Coordinate and crsuri means the URI reference to the coordinate system being used. This encoding allows N coordinates for each corner listed in the order of the optional crsuri. If the crsuri is not specified then the 2-D coordinates shall be specified using decimal degrees and WGS84 as described in [15]. -Jukka Rahkonen- ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
