If we can get a decent bug report together we should be able to patch the GeoTools WFS code with some map server specific functionality. Before you give up try changing some of the connection parameters; there is a "strict" mode that may work better with MapServer.
If the options are not available through the WFS wizard; try the GeoTools DataStore wizard instead; it lists all the options (even the non useful ones). -- Jody Garnett On Wednesday, 30 March 2011 at 7:12 PM, Joaquín Rodriguez-Guerra Urcelay wrote: > I think that maybe this is issue wont happen when using WFS 1.1.0. > The use of gml:box in the Intersects operation is not allowed in WFS 1.1.0 > and maybe geotools creates a different filter when querying a WFS 1.1.0 > server, but I have not been able to display any mapserver WFS 1.1.0 layer in > uDig, and then I could not test it. > http://www2.dmsolutions.ca/cgi-bin/mswfs_gmap?SERVICE=WFS&VERSION=1.1.0&REQUEST=getcapabilities > dont work in udig, right? > > Joaquín > ________________________________________ > De: Joaquín Rodriguez-Guerra Urcelay > Enviado el: miércoles, 30 de marzo de 2011 9:00 > Para: User-friendly Desktop Internet GIS > Asunto: [udig-devel] Info, Select tools not working with mapserver wfs layers > > Hello list, > > I just wanted to ask if someone is using uDig with mapserver. > Some tools, like info or select are not working for me. The info tool for > example, uses the wfs intersect spatial filter with gml:box, which is not > working well in mapserver ( I think the other tools use the same filter, is > it right?) > > Example Filter: > > http://localhost:8080/cgi-bin/mywfs?WIDTH=512&SERVICE=WFS&VERSION=1.0.0&request=getfeature&typename=PositionReal&Filter= > <Filter xmlns="http://www.opengis.net/ogc"; > xmlns:gml="http://www.opengis.net/gml";><Intersects><PropertyName>point</PropertyName> > <gml:Box srsName="WGS84(DD)"><gml:coordinates decimal="." cs="," ts=" > ">-100.0,-45.0 100.0,45.0</gml:coordinates> </gml:Box> </Intersects> </Filter> > > I asked in [mapserver-users], and they have confirmed the issue, opened the > bug, and fixed it in the development branch. > http://www.mail-archive.com/[email protected]/msg13831.html > > Have anyone found a way around this?? I guess there is no easy way to tell > udig to use the intersect filter with gml:polygon instead of gml:box, and my > best shot would be to create new tools for info and select, right? > > Thank you, > > Joaquín > > ______________________ > This message including any attachments may contain confidential > information, according to our Information Security Management System, > and intended solely for a specific individual to whom they are addressed. > Any unauthorised copy, disclosure or distribution of this message > is strictly forbidden. If you have received this transmission in error, > please notify the sender immediately and delete it. > > ______________________ > Este mensaje, y en su caso, cualquier fichero anexo al mismo, > puede contener informacion clasificada por su emisor como confidencial > en el marco de su Sistema de Gestion de Seguridad de la > Informacion siendo para uso exclusivo del destinatario, quedando > prohibida su divulgacion copia o distribucion a terceros sin la > autorizacion expresa del remitente. Si Vd. ha recibido este mensaje > erroneamente, se ruega lo notifique al remitente y proceda a su borrado. > Gracias por su colaboracion. > > ______________________ > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
