Andrea Aime wrote: > On Tue, Mar 29, 2011 at 9:03 PM, Rahkonen Jukka > <jukka.rahko...@mmmtike.fi> wrote: > > Hi, > > > > I noticed that the demo request of Geoserver 2.0.2 is using filter > > > > <wfs:Query typeName="topp:states"> > > <Filter> > > <Intersects> > > <PropertyName>the_geom</PropertyName> > > <gml:Point > srsName="http://www.opengis.net/gml/srs/epsg.xml#4326";> > > <gml:coordinates>-74.817265,40.5296504</gml:coordinates> > > </gml:Point> > > </Intersects> > > </Filter> > > </wfs:Query> > > </wfs:GetFeature> > > > > The WFS GetCapabilities of the same server is listing in > the capabilities > > <ogc:Filter_Capabilities> > > ?<ogc:Spatial_Capabilities> > > ?<ogc:Spatial_Operators> > > <ogc:Intersect/> > > > > Why the demo request is using "Intersects"? I had a try > with that demo request and Geoserver seems to accept both > > Intersect and Intersects but the result is different. I've > been told that uDig is creating requests with "Intersects" > and Mapserver does not accept those but I have not checked > that myself. > > The Filter specification 1.0 states: > > <xsd:element name="Intersects" type="ogc:BinarySpatialOpType" > substitutionGroup="ogc:spatialOps"/> > > however filtercapabilties.xsd, referred by wfs 1.0 caps states: > > <xsd:element name="Intersect"> > <xsd:complexType/> > </xsd:element> > > and Filter 1.1 states: > > <xsd:element name="Intersects" > type="ogc:BinarySpatialOpType" > substitutionGroup="ogc:spatialOps"/> > > while wfs 1.1 caps states: > > <xsd:simpleType name="SpatialOperatorNameType"> > <xsd:restriction base="xsd:string"> > <xsd:enumeration value="BBOX"/> > <xsd:enumeration value="Equals"/> > <xsd:enumeration value="Disjoint"/> > <xsd:enumeration value="Intersects"/> > > As far as I can see GeoServer respects all by the letter, even the > inconsistency in WFS 1.0/Filter 1.0 between the caps name and the > actual filter name.
Amazing, I love all versions of WFS standard. So WFS 1.0.0 GetCapabilities is advertising "Intersect" but users should not care and use "Intersects" instead? That's what I have done but I got baffled because of somewhat misleading GetCapabilities. I am still confused with "Intersect". The query above with "Intersects" against topp:states returns one state. If I edit the query to use "Intersect" it returns all the states. Is this what it is supposed to do? -Jukka Rahkonen- ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
