Hi, I had a try with Geoserver 2.1.0 and WFS datastore. However, the TinyOWS server I used as a remote server does not send any features for Geoserver. The reason is probably in the filter created by Geoserver, together with TinyOWS which does not do any brain work in that end.
The whole request sent by Geoserver is like MAXFEATURES=100&PROPERTYNAME=way&SRSNAME=urn:ogc:def:crs:EPSG::3067&TYPENAME=tows:osm_line&VERSION=1.1.0&OUTPUTFORMAT=text/xml; subtype=gml/3.1.1&SERVICE=WFS&REQUEST=GetFeature&FILTER=<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc"; xmlns:gml="http://www.opengis.net/gml";><ogc:BBOX><ogc:PropertyName>way</ogc:PropertyName><gml:Envelope><gml:lowerCorner>262758.6981286632 6629345.598547233</gml:lowerCorner><gml:upperCorner>325373.8722497568 6707012.497216768</gml:upperCorner></gml:Envelope></ogc:BBOX></ogc:Filter> See the envelope: <gml:Envelope> <gml:lowerCorner>262758.6981286632 6629345.598547233</gml:lowerCorner> <gml:upperCorner>325373.8722497568 6707012.497216768</gml:upperCorner> </gml:Envelope> The geometry is without srsName and TinyOWS takes it as unknown in that case. The PostGIS query that follows will always fail because of not-matching SRIDs. Would it have any negative effect to make Geoserver to include srsName in filters? Of course the WFS server could take the srsName used in the QUERY and pass it on, but wouldn't it be unambiguous and thus better to add srsName alto to geometries used in Filters? -Jukka Rahkonen- ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
