[mapserver-users] How reproduce a false color NDVI.

2015-03-01 Thread Andrea Peri
Hi, we have a set of tiffs georef with 4th bands of color RGB and Infrared. We need to activate a wms with the color from the NDVI index NDVI = Normalized Difference Vegetation Index NIR - RED NDVI = - NIR + RED Where NIR is the 4th band, RED s the 1th band. We

Re: [mapserver-users] How reproduce a false color NDVI.

2015-03-01 Thread Even Rouault
Le dimanche 01 mars 2015 10:17:34, Andrea Peri a écrit : > Hi, > we have a set of tiffs georef with 4th bands of color RGB and Infrared. > We need to activate a wms with the color from the NDVI index > > NDVI = Normalized Difference Vegetation Index > > NIR - RED > NDVI = -

Re: [mapserver-users] WFS filter creates a query using a number instead of text

2015-03-01 Thread Steve . Toutant
Mapserver 7 beta solved this issue.At least for my use cases.. with and without using gml_[item name]_type John Abraham @lists.osgeo.org Envoyé par : mapserver-users-boun...@lists.osgeo.org 2015-02-27 09:05 A "Rahkonen Jukka (MML)" cc "mapserver-users@lists.osgeo.org" , "bte...@gmail

Re: [mapserver-users] WFS filter creates a query using a number instead of text

2015-03-01 Thread bte...@gmail.com
Thanks Jukka - I'll try your suggestion for OGR connection-type first, since that's easy for me to test on our existing platform. I have tried the "PropertyIsLike" and that definitely works. It'll take me a little bit longer to "spin up" a more recent version of the software packages... Regards,

Re: [mapserver-users] WFS filter creates a query using a number instead of text

2015-03-01 Thread bte...@gmail.com
Hi Jukka - I've tried testing your other suggestion: OK - I've tried using the OGR CONNECTIONTYPE - it no longer generates an error message, but comes back with a null result set. Checking the logs reveals that the error is now apparently being pushed further back up the stack - eg the Postgres l

Re: [mapserver-users] Getcapabilities extremely slow in version 6.4.1

2015-03-01 Thread aabhayas
After profiling version 6.0.4 and 6.2.2 MapServer we were able to isolate the issue. It seems that the issues is related to “OWS_LAYER_GROUP” under LAYER>METADATA in our map files. When “OWS_LAYER_GROUP” is not used in the map file, GetCapabilities request on version 6.2.2 is significantly faster