Hi, I was also reading this unresolved one http://jira.codehaus.org/browse/GEOS-2199 and this too http://jira.codehaus.org/browse/GEOS-1987 and was not sure about what was the Geoserver/Geotools developers conclusion. What srsName to use as default if the native is different from the requested and srsName is not given for a filter. I believe that now the srsName used in query is applied to filter, too.
-Jukka Rahkonen- > -----Alkuperäinen viesti----- > Lähettäjä: [email protected] > [mailto:[email protected]] Puolesta Andrea Aime > Lähetetty: 10. kesäkuuta 2011 16:12 > Vastaanottaja: Rahkonen Jukka > Kopio: [email protected] > Aihe: Re: [Geoserver-users] Trouble with using a WFS data store > > On Fri, Jun 10, 2011 at 2:44 PM, Rahkonen Jukka > <[email protected]> wrote: > > 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/x > ml; > subtype=gml/3.1.1&SERVICE=WFS&REQUEST=GetFeature&FILTER=<ogc:F > ilter xmlns:ogc="http://www.opengis.net/ogc"; > xmlns:gml="http://www.opengis.net/gml";><ogc:BBOX><ogc:Property > Name>way</ogc:PropertyName><gml:Envelope><gml:lowerCorner>2627 58.6981286632 > 6629345.598547233</gml:lowerCorner><gml:upperCorner>325373.872 > 2497568 > 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? > > The srsName is not mandatory so TinyOWS should learn to default to the > srs declared in its capabilties. > That said I see no harm in always expressing the srs > > Who's going to perform the change? The code is in GeoTools, in > unsupported land btw: > http://svn.osgeo.org/geotools/trunk/modules/unsupported/wfs/ > > Cheers > Andrea > > > -- > ------------------------------------------------------- > Ing. Andrea Aime > GeoSolutions S.A.S. > Tech lead > > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584 962313 > fax: +39 0584 962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.youtube.com/user/GeoSolutionsIT > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ------------------------------------------------------- > ------------------------------------------------------------------------------ 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
