Re: [mapserver-users] Is PropertyIsNull supported by MapServer?
Le mercredi 30 avril 2014 16:58:45, geographika a écrit : > Hello again! > > I'm trying to allow for any records with a NULL property to be returned > via a WFS 1.1 GetFeature request. > OpenLayers has a OpenLayers.Filter.Comparison.IS_NULL filter that > produces XML such as: > > > > YEAR > > > > MapServer (6.4) however doesn't support it, and logs the following > error: msWFSGetFeature(): WFS server error. Invalid or Unsupported > FILTER in GetFeature > Looking at the page http://mapserver.org/ogc/filter_encoding.html page > it seems all 8 tests fail for this filter: > > 1.3.4.10GetFeature PropertyIsNull filter > > And in the notes below "Test number 1.3.4.10: This property is not > supported in MapServer." > However several recent commits seem to reference this filter e.g. > https://github.com/mapserver/mapserver/commit/7c97d948645e3c04228e25ba2f533 > 3f0a23fd128 Is this for WFS version 2.0? Is so are there any plans to > implement PropertyIsNull for older WFS protocols? I've not tried, but the implementation of PropertyIsNull should also work with WFS 1.1.0 > > Regards, > > Seth > > -- > web:http://geographika.co.uk > twitter: @geographika -- Geospatial professional services http://even.rouault.free.fr/services.html ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Is PropertyIsNull supported by MapServer?
Hello again! I'm trying to allow for any records with a NULL property to be returned via a WFS 1.1 GetFeature request. OpenLayers has a OpenLayers.Filter.Comparison.IS_NULL filter that produces XML such as: YEAR MapServer (6.4) however doesn't support it, and logs the following error: msWFSGetFeature(): WFS server error. Invalid or Unsupported FILTER in GetFeature Looking at the page http://mapserver.org/ogc/filter_encoding.html page it seems all 8 tests fail for this filter: 1.3.4.10GetFeature PropertyIsNull filter And in the notes below "Test number 1.3.4.10: This property is not supported in MapServer." However several recent commits seem to reference this filter e.g. https://github.com/mapserver/mapserver/commit/7c97d948645e3c04228e25ba2f5333f0a23fd128 Is this for WFS version 2.0? Is so are there any plans to implement PropertyIsNull for older WFS protocols? Regards, Seth -- web:http://geographika.co.uk twitter: @geographika ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] MapServer Errors in APACHE logs.
http://mapserver.org/optimization/debugging.html if you set the error file to "stderr" then the logs will go to the apache error log, as others have pointed out. -- thomas On 29 April 2014 20:55, Basques, Bob (CI-StPaul) wrote: > All, > > > > Has anyone done any work with capturing MapServer errors in APACHE? > Specifically I want to be able to tell the difference between a MapServer > mis-config (textual error page) and a successful image response. The idea > is to somehow log those textual message responses in an automated way > through Apache. > > > > I’m pretty sure I could make my own custom logfile for MapServer (CGI) > calls, but not so sure about textual response vs raster response filters, at > least from the APACHE point of view . . .. Is a MapServer Text based error > page considered for inclusion in the Apache error log or?? > > > > Thanks. > > > > Bobb > > > > > > > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
