[mapserver-users] GetFeatureInfo Cascading WMS

[Berger, Cora]

Dear group,
normally it is possible to request more than one layer with one 
GetFeatureInfo-request. This doesn't work with cascading WMS. Is this a bug?

Here are some example request:

Query-Layer: nw_tim_h_inu (works fine)
https://www.wms.nrw.de/geobasis/wms_nw_tim?SERVICE=WMS=1.3.0=GetFeatureInfo=image/png=true_LAYERS=nw_tim_h_inu=nw_tim_h_inu_FORMAT=text/html=10=50=50=EPSG:25832==101=101=379495.5134930965,5625172.894819761,380460.5309751969,5626137.912301861

Query-Layer: nw_tim_m_inb (works fine)
https://www.wms.nrw.de/geobasis/wms_nw_tim?SERVICE=WMS=1.3.0=GetFeatureInfo=image/png=true_LAYERS=nw_tim_m_inb=nw_tim_h_inu_FORMAT=text/html=10=50=50=EPSG:25832==101=101=379495.5134930965,5625172.894819761,380460.5309751969,5626137.912301861

If I request both layers at the same time, I don't get a result:
Query-Layer: nw_tim_m_inb, nw_tim_h_inu
https://www.wms.nrw.de/geobasis/wms_nw_tim?SERVICE=WMS=1.3.0=GetFeatureInfo=image/png=true_LAYERS=nw_tim_m_inb,nw_tim_h_inu=nw_tim_m_inb,nw_tim_h_inu_FORMAT=text/html=10=50=50=EPSG:25832==101=101=379495.5134930965,5625172.894819761,380460.5309751969,5626137.912301861

Cheers Cora
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Baffled by a MapServer WCS

[Berger, Cora]

Dear Ari,

this request works fine:
http://nsidc.org/cgi-bin/atlas_north?SERVICE=WCS=1.0.0=GetCoverage=GeoTIFF=sea_ice_concentration_01=-3961770,-3961769,3961769,4362961=EPSG:32661_CRS=EPSG:32661=317=333

Cheers
Cora


>-Ursprüngliche Nachricht-
>Von: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] Im
>Auftrag von mapserver-users-requ...@lists.osgeo.org
>Gesendet: Dienstag, 14. November 2017 21:00
>An: mapserver-users@lists.osgeo.org
>Betreff: mapserver-users Digest, Vol 118, Issue 11
>
>Send mapserver-users mailing list submissions to
>   mapserver-users@lists.osgeo.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.osgeo.org/mailman/listinfo/mapserver-users
>or, via email, send a message with subject or body 'help' to
>   mapserver-users-requ...@lists.osgeo.org
>
>You can reach the person managing the list at
>   mapserver-users-ow...@lists.osgeo.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of mapserver-users digest..."
>
>
>Today's Topics:
>
>   1. Baffled by a MapServer WCS (Ari Jolma)
>
>
>--
>
>Message: 1
>Date: Tue, 14 Nov 2017 11:18:16 +0200
>From: Ari Jolma 
>To: mapserver-users@lists.osgeo.org
>Subject: [mapserver-users] Baffled by a MapServer WCS
>Message-ID: 
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>Hi,
>
>I'm trying to get the GDAL WCS client working and in the process trying
>different WCS servers.
>
>I just found this http://nsidc.org/cgi-bin/atlas_north and I'm trying to
>use its WCS
>
>I'm making WCS 1.0 and 1.1 GetCoverage calls on a dataset that seems to
>be natively served in EPSG:32661:
>
>http://nsidc.org/cgi-
>bin/atlas_north?SERVICE=WCS=GetCoverage=1.0.0
>VERAGE=sea_ice_concentration_01=GeoTIFF=-
>3961770.085,4312961.971,-
>3911770.085,4362961.971=2=2=EPSG:32661
>
>Error: Requested BBOX
>(-5336721.37969822,2086027.77164232,-5316625.78536214,2109378.29356774)
>is outside requested coverage BBOX
>(-3961770.085,-3961769.906,3961769.894,4362961.971)
>
>http://nsidc.org/cgi-
>bin/atlas_north?SERVICE=WCS=1.1.1=GetCoverage
>NTIFIER=sea_ice_concentration_01=image%2Ftiff=-
>3924270.085,4350461.971,-
>3949270.085,4325461.971,urn:ogc:def:crs:EPSG::32661=pixels
>DTH=2=2=urn:ogc:def:crs:EPSG::32661=urn:ogc
>:def:cs:OGC:0.0:Grid2dSquareCS=urn:ogc:def:method:WCS:1.1:2dGridIn
>2dCrs=-3949270.085,4350461.971=25000,25000
>
>Requested BBOX
>(-5335202.686558,2107853.71031472,-5335202.686558,2107853.71031472) is
>outside requested coverage BBOX
>(-3961770.085,-3961769.906,3961769.894,4362961.971)
>
>For the first one I'm making a fix on the GDAL side for the grid origin
>not being at the center of a pixel and for the second one I'm setting
>the offsets to positive values and leaving out the 0,0 in the middle.
>For the 2nd one I'm also making axis order inversion since EPSG::32661
>is N,E. That's why the GridOrigin in like it is. I'm not sure whether
>MapServer applies axis inversion in the 1.1 in this case.
>
>Anyway, the baffling thing is that MapServer reports in both cases the
>requested BBOX (the one I'm sending, I guess) to be outside coverage
>BBOX and changed from what I sent -- there is obviously a reprojection
>done. The values are strange and I can't find/think in what CRS they are.
>
>Any ideas?
>
>Thanks,
>
>Ari
>
>
>
>
>--
>
>Subject: Digest Footer
>
>___
>mapserver-users mailing list
>mapserver-users@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>--
>
>End of mapserver-users Digest, Vol 118, Issue 11
>
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Kernel Density maps and WMS Time

[Berger, Cora]

Dear Domenico,
I created a WMS with TIME-Parameter successfully for historical orthophotos. 
You find the documentation for the time-parameter in mapfiles here: 
http://mapserver.org/de/ogc/wms_time.html

In your second layer try to change this:
Instead of 
CONNECTIONTYPE KERNELDENSITY
CONNECTION "the_geom"
Try
TILEINDEX "the_geom"
TILEITEM "location" #if the name of the column with the information where 
the data is stored is called like this
FILTER (`[datetime]` = `2006-06-23T03:10:00Z`)

In my case only the tileindex is stored in postgis and the raster data is 
stored in a filesystem. The column "location" of the tileindex contains the 
path to the folder where the raster data is stored.
Have you set up a mapfile using raster data and tileindex before? Maybe it 
helps to read the tileindex-documentation, too to get a better understanding of 
how the tileindex works. The WCS documentation also contains a part about 
spatio-temporal-tileindexes 
http://mapserver.org/ogc/wcs_server.html#spatio-temporal-indexes

Cheers 
Cora

>--
>
>Message: 1
>Date: Tue, 6 Jun 2017 15:12:10 +0200
>From: Domenico Febbo 
>To: mapserver-users@lists.osgeo.org
>Subject: [mapserver-users] Kernel Density maps and WMS Time
>Message-ID:
>   q...@mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>Dear All,
>there is a way to pass TIME parameter using WMS Time protocol from Kernel
>Density map to the base layer connected to POSTGIS?
>
>I want to create an animated density map using TIME parameter.
>
>##  MAPFILE  Extract  ###
>
>LAYER
>CONNECTION "host=localhost port=5432 dbname=postgres user=postgres
>password=postgres"
>CONNECTIONTYPE POSTGIS
>DATA "the_geom from (select * from table) as foo using unique gid using
>srid=4326"
>NAME "the_geom"
>PROCESSING "CLOSE_CONNECTION=DEFER"
>PROJECTION
>  "init=epsg:4326"
>END # PROJECTION
>STATUS ON
>METADATA
>   "wms_timeextent" "2017-04-01/2017-06-10"
>   "wms_timeitem" "datetime" #datetime is a column in postgis table of
>type timestamp
>   "wms_timedefault" "2017-06-06"
>   "wms_enable_request" "*"
>END
>TEMPLATE "fooOnlyForWMSGetFeatureInfo"
>TYPE POINT
>CLASS
>NAME "a"
>STYLE
>SIZE 4
>COLOR "#FF00FF"
>SYMBOL "circle_fill"
>END # style
>END #class
>END # final layer
>
>  LAYER
>NAME "the_geom_denisty"
>TYPE RASTER
>CONNECTIONTYPE KERNELDENSITY
>CONNECTION "the_geom"
>STATUS ON
>PROCESSING "RANGE_COLORSPACE=HSL"
>PROCESSING "KERNELDENSITY_RADIUS=20"
>PROCESSING "KERNELDENSITY_COMPUTE_BORDERS=ON"
>PROCESSING "KERNELDENSITY_NORMALIZATION=2.0"
>OFFSITE 0 0 0
>
>METADATA
>   "wms_title" "the_geom_denisty WMS-T"
>   "wms_timeextent" "2017-04-01/2017-06-10"
>   "wms_timeitem" "datetime" #datetime is a column in postgis table of
>type timestamp
>   "wms_timedefault" "2017-06-06"
>   "wms_enable_request" "*"
>END
>
>CLASS
>  STYLE
>COLORRANGE  "#f46d43FF"  "#d73027FF"
>DATARANGE 0 255
>  END
>END
>  END
>
>###
>tag: HEATMAP, WMS-T
>
>Regards, Domenico.
>-- next part --
>An HTML attachment was scrubbed...
>URL: users/attachments/20170606/ac764e0b/attachment-0001.html>
>
>--
>
>Subject: Digest Footer
>
>___
>mapserver-users mailing list
>mapserver-users@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>--
>
>End of mapserver-users Digest, Vol 113, Issue 7
>***
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] geotiff 48bit with mapserver 7 wms

[Berger, Cora]

Dear Jukka,
you can find the original input-image of the wcs, an output image without any 
processing and an output image with processing scale=auto here: 
https://www.bscw.nrw.de/pub/bscw.cgi/7035084

Cora 


>-Ursprüngliche Nachricht-
>Von: Rahkonen Jukka (MML) [mailto:jukka.rahko...@maanmittauslaitos.fi]
>Gesendet: Mittwoch, 19. April 2017 22:14
>An: Berger, Cora; 'mapserver-users@lists.osgeo.org'
>Betreff: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>
>Hi Cora,
>
>Could you prepare a small sample image and put it somewhere for downloading?
>Or did you already do it in some earlier mail?
>
>-Jukka Rahkonen-
>
>
>Lähettäjä: mapserver-users <mapserver-users-boun...@lists.osgeo.org> käyttäjän
>puolestaBerger, Cora <cora.ber...@bezreg-koeln.nrw.de>
>Lähetetty: 19. huhtikuuta 2017 17:45
>Vastaanottaja: 'mapserver-users@lists.osgeo.org'
>Aihe: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>
>Hi David,
>Thanks for your help. I tried PROCESSING "SCALE=AUTO". This method results in
>a red/white image. All the labels in the map are drawn red (originally black). 
>The
>whole topographic information in the background is just white (originally many
>different colors). I tried it with a combination of different 
>outputformat-declarations
>and processings. Unfortunately I didn't get a correct result.
>
>Cheers Cora
>
>
>>Message: 2
>>Date: Tue, 18 Apr 2017 14:07:04 +
>>From: David <da...@impstyle.com>
>>To: "'mapserver-users@lists.osgeo.org'"
>>   <mapserver-users@lists.osgeo.org>
>>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>>Message-ID: <em2654a657-d1b7-4616-b1ae-3b1d6f8122f3@laptop-dfriedrich>
>>Content-Type: text/plain; format=flowed; charset=utf-8
>>
>>Hi Cora,
>>
>>do you use PROCESSING "SCALE=AUTO" with you LAYER definition?
>>
>>SCALE[_n]=AUTO or min,max
>>This directive instructs the GDAL reader to pre-scale the incoming
>>raster data. It is primarily used to scale 16bit or floating point data
>>to the range 0-255, but can also be used to constrast stretch 8bit data.
>>
>>http://mapserver.org/input/raster.html#special-processing-directives
>>
>>Cheers David
>>
>>
>>-- Original Message --
>>From: "Berger, Cora" <cora.ber...@bezreg-koeln.nrw.de>
>>To: "'mapserver-users@lists.osgeo.org'"
>><mapserver-users@lists.osgeo.org>
>>Sent: 4/18/2017 10:47:42 AM
>>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>>
>>>Dear David, Steve, Ben, etc.
>>>I am working with MapServer-WCS. I still have problems defining the
>>>correct output formats. Input to most of our WCS are 8bit Geotiffs. The
>>>MapServer WCS-output is either tiff, png or jpeg with 24bit or
>>>Png;mode=8bit with 8 bit (if no output format is defined). The
>>>png;mode=8bit-format changes the imagecolours, so it isn't really
>>>useful. I can't get a colored 8bit Geotiff as output (a 8bit-definition
>>>always results in greyscale images). I tried different output
>>>format-definitions, none of them worked. I can define a palette for the
>>>png-format, but unfortunately not for any other format.
>>>For our WCS it is important that the output-data looks the same like
>>>the input-data. It seems that at the moment MapServer can't just pass
>>>the input-data through... This might be a GDAL issue...
>>>
>>>So if you find a way to define your wished output-format, please share
>>>it, maybe it helps me, too. Maybe anybody else has an idea?
>>>
>>>Cora
>>>
>>>
>
>___
>mapserver-users mailing list
>mapserver-users@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] geotiff 48bit with mapserver 7 wms

[Berger, Cora]

Hi David,
Thanks for your help. I tried PROCESSING "SCALE=AUTO". This method results in a 
red/white image. All the labels in the map are drawn red (originally black). 
The whole topographic information in the background is just white (originally 
many different colors). I tried it with a combination of different 
outputformat-declarations and processings. Unfortunately I didn't get a correct 
result. 

Cheers Cora


>Message: 2
>Date: Tue, 18 Apr 2017 14:07:04 +
>From: David <da...@impstyle.com>
>To: "'mapserver-users@lists.osgeo.org'"
>   <mapserver-users@lists.osgeo.org>
>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>Message-ID: <em2654a657-d1b7-4616-b1ae-3b1d6f8122f3@laptop-dfriedrich>
>Content-Type: text/plain; format=flowed; charset=utf-8
>
>Hi Cora,
>
>do you use PROCESSING "SCALE=AUTO" with you LAYER definition?
>
>SCALE[_n]=AUTO or min,max
>This directive instructs the GDAL reader to pre-scale the incoming
>raster data. It is primarily used to scale 16bit or floating point data
>to the range 0-255, but can also be used to constrast stretch 8bit data.
>
>http://mapserver.org/input/raster.html#special-processing-directives
>
>Cheers David
>
>
>-- Original Message --
>From: "Berger, Cora" <cora.ber...@bezreg-koeln.nrw.de>
>To: "'mapserver-users@lists.osgeo.org'"
><mapserver-users@lists.osgeo.org>
>Sent: 4/18/2017 10:47:42 AM
>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>
>>Dear David, Steve, Ben, etc.
>>I am working with MapServer-WCS. I still have problems defining the
>>correct output formats. Input to most of our WCS are 8bit Geotiffs. The
>>MapServer WCS-output is either tiff, png or jpeg with 24bit or
>>Png;mode=8bit with 8 bit (if no output format is defined). The
>>png;mode=8bit-format changes the imagecolours, so it isn't really
>>useful. I can't get a colored 8bit Geotiff as output (a 8bit-definition
>>always results in greyscale images). I tried different output
>>format-definitions, none of them worked. I can define a palette for the
>>png-format, but unfortunately not for any other format.
>>For our WCS it is important that the output-data looks the same like
>>the input-data. It seems that at the moment MapServer can't just pass
>>the input-data through... This might be a GDAL issue...
>>
>>So if you find a way to define your wished output-format, please share
>>it, maybe it helps me, too. Maybe anybody else has an idea?
>>
>>Cora
>>
>>

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] geotiff 48bit with mapserver 7 wms

[Berger, Cora]

Dear David, Steve, Ben, etc.
I am working with MapServer-WCS. I still have problems defining the correct 
output formats. Input to most of our WCS are 8bit Geotiffs. The MapServer 
WCS-output is either tiff, png or jpeg with 24bit or Png;mode=8bit with 8 bit 
(if no output format is defined). The png;mode=8bit-format changes the 
imagecolours, so it isn't really useful. I can't get a colored 8bit Geotiff as 
output (a 8bit-definition always results in greyscale images). I tried 
different output format-definitions, none of them worked. I can define a 
palette for the png-format, but unfortunately not for any other format. 
For our WCS it is important that the output-data looks the same like the 
input-data. It seems that at the moment MapServer can't just pass the 
input-data through... This might be a GDAL issue...

So if you find a way to define your wished output-format, please share it, 
maybe it helps me, too. Maybe anybody else has an idea? 

Cora


>Message: 1
>Date: Mon, 17 Apr 2017 22:14:28 +
>From: David 
>To: mapserver-users@lists.osgeo.org
>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>Message-ID: 
>Content-Type: text/plain; format=flowed; charset=utf-8
>
>Thank you very much Steve. You helped me to understand the problem!
>
>David F.
>
>-- Original Message --
>From: "Stephen Woodbridge" 
>To: mapserver-users@lists.osgeo.org
>Sent: 4/14/2017 9:54:20 PM
>Subject: Re: [mapserver-users] geotiff 48bit with mapserver 7 wms
>
>>Yeah, technically a geotiff can be any format, but mapserver only
>>supports a limit set for band widths.
>>
>>A new version of Mapcache was just released and it has GDAL support in
>>it  and serves WMS, but I'm not sure if it will do what you want.
>>
>>Sorry, I'm out of ideas on this.
>>
>>-Steve W
>>
>>On 4/14/2017 6:56 PM, David F. wrote:
>>>I did not reply after my latest test, sorry.
>>>I tried all tiff IMAGEMODE for my data set. None gave me 16 bit at the
>>>gis client.
>>>As far as I understand gtiff is 8 bit.
>>>The only IMAGEMODE for integer is signed INT16 , which is
>>>unfortunately the only supported integer data type. For RGB data
>>>unsigned integer is the only integer data type that makes sense. Just
>>>if i change the IMAGEMODE to FLOAT32 mapserver will serve more than 8
>>>bit per band.
>>>I think i will give gdal and float32 bit a try nevertheless it will
>>>double the image size.
>>>Maybe someone else has an idea.
>>>
>>>
>>>
>>>
>>>
>>>On April 14, 2017 1:43:09 PM Stephen Woodbridge
>>> wrote:
>>>
http://mapserver.org/mapfile/outputformat.html

Why not serve them a GTiff format for qgis?

You can define multiple output formats in the mapfile, and let the
browser use the 8bit png and have qgis request images in gtiff
format.

-Steve

On 4/13/2017 11:03 AM, David wrote:
>Hi Steve,
>
>thank you very much for your help. The Mapserver is serving the
>tiles
>with the correct RGB values now. The problem is, that it is serving
>8
>bit per band and not 16 bit.
>I need the 16bit because i want to use the wms as a base layer for
>some
>further processing with qgis or another gis client. So no problem
>regarding browsers for me.
>
>I will take a look and change the data type to float32 for the tiff
>files. At least this is an supported OUTPUTFORMAT for mapserver.
>Any suggestions on this matter are highly appreciated.
>
>Cheers,
>David
>
>-- Original Message --
>From: mapserver-users-requ...@lists.osgeo.org
>To: mapserver-users@lists.osgeo.org
>Sent: 4/12/2017 4:00:02 PM
>Subject: mapserver-users Digest, Vol 111, Issue 5
>
>>Send mapserver-users mailing list submissions to
>>  mapserver-users@lists.osgeo.org
>>
>>To subscribe or unsubscribe via the World Wide Web, visit
>>  https://lists.osgeo.org/mailman/listinfo/mapserver-users
>>or, via email, send a message with subject or body 'help' to
>>  mapserver-users-requ...@lists.osgeo.org
>>
>>You can reach the person managing the list at
>>  mapserver-users-ow...@lists.osgeo.org
>>
>>When replying, please edit your Subject line so it is more specific
>>than "Re: Contents of mapserver-users digest..."
>>
>>
>>Today's Topics:
>>
>>1. geotiff 48bit with mapserver 7 wms (David)
>>2. Re: geotiff 48bit with mapserver 7 wms (Stephen Woodbridge)
>>
>>
>>--
>>
>>Message: 1
>>Date: Wed, 12 Apr 2017 00:22:12 +
>>From: David 
>>To: mapserver-users@lists.osgeo.org
>>Subject: [mapserver-users] geotiff 48bit with mapserver 7 wms
>>Message-ID:
>>

Re: [mapserver-users] mapserver-users Digest, Vol 104, Issue 3

[Berger, Cora]

Hello Jeff,
thanks for your help. It seems that QGIS requests the WCS in its full extent. 
The size of the data I'm using is quite big. That's why I'm using a Tileindex. 
When the whole Extent gets requested it comes to a timeout. 
QGIS send these 3 Requests to the Server. 

http://vbrk21nt15.bezreg-koeln.nrw.de/wms/wcs_nw_dgm?SERVICE=WCS=1.0.0=GetCoverage=GTiff=nw_dgm=278000,556,536000,5828000=EPSG:25832_CRS=EPSG:25832=10=10

http://vbrk21nt15.bezreg-koeln.nrw.de/wms/wcs_nw_dgm?SERVICE=WCS=1.0.0=GetCoverage=GTiff=nw_dgm=406613,5693799,407387,5694201=EPSG:25832_CRS=EPSG:25832=6=3

http://vbrk21nt15.bezreg-koeln.nrw.de/wms/wcs_nw_dgm?SERVICE=WCS=1.0.0=GetCoverage=GTiff=nw_dgm=327278,5724552,331535,5729242=EPSG:25832_CRS=EPSG:25832=33=35

The first BBOX is the extent defined in the mapfile. I tried different WCs and 
the first GetCoverage request always requests the whole extent with width and 
height = 10.  
So I guess my only chance is to reduce my data volume...

Yours
Cora


>-Ursprüngliche Nachricht-
>Von: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] Im
>Auftrag von mapserver-users-requ...@lists.osgeo.org
>Gesendet: Samstag, 3. September 2016 21:00
>An: mapserver-users@lists.osgeo.org
>Betreff: mapserver-users Digest, Vol 104, Issue 3
>
>Send mapserver-users mailing list submissions to
>   mapserver-users@lists.osgeo.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>   http://lists.osgeo.org/mailman/listinfo/mapserver-users
>or, via email, send a message with subject or body 'help' to
>   mapserver-users-requ...@lists.osgeo.org
>
>You can reach the person managing the list at
>   mapserver-users-ow...@lists.osgeo.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of mapserver-users digest..."
>
>
>Today's Topics:
>
>   1. Re: WCS with elevation data (Jeff McKenna)
>
>
>--
>
>Message: 1
>Date: Sat, 3 Sep 2016 15:28:05 -0300
>From: Jeff McKenna 
>To: mapserver-users@lists.osgeo.org
>Subject: Re: [mapserver-users] WCS with elevation data
>Message-ID:
>   
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>Hi Cora,
>
>I believe QGIS defaults to using VERSION=1.0.0 for WCS.
>
>A nice way to see the exact OGC request sent by QGIS, is to use Fiddler:
>
>  - download and install Fiddler (Google will help you find its current
>download)
>  - open it and leave it running
>  - in QGIS goto /Settings/Options/Network
>  - click on "Use proxy for web access"
>  - for Proxy Type select "HttpProxy"
>  - for Host enter: 127.0.0.1
>  - for Port enter: 
>  - presss "ok" button
>  - now Add a WCS layer in QGIS again, but watch the Fiddler window
>  - click on the GetCoverage request in Fiddler
>  - to see the full requested url in Fiddler, check the 'Inspector' tab,
>and then select 'Raw'
>
>This is a handy trick especially when debugging MapServer services.
>(beware that QGIS caches the service though, see previous warnings by me
>on this list for that).
>
>Have a nice weekend,
>
>-jeff
>
>
>
>--
>Jeff McKenna
>MapServer Consulting and Training Services
>http://www.gatewaygeomatics.com/
>
>
>
>
>--
>
>Subject: Digest Footer
>
>___
>mapserver-users mailing list
>mapserver-users@lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>--
>
>End of mapserver-users Digest, Vol 104, Issue 3
>***
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS with elevation data

[Berger, Cora]

Hello list,
I created a WCS with MapServer 7 (on windows), which displays elevation data. 
I have some problems which I can't solve and hope you can support me.

1.) Since I'm using a Tileindex I need to fill the Layers metadata-tags 
"wcs_size" and wcs_resolution". Unfortunately, the documentation of MapServer 
doesn't give a hint what values to use for this tags. I read somewhere that the 
values come from GDAL when you create the Tileindex with GDAL, but I didn't 
create the index with GDAL.

2.) The Input data are 1km tiles with 2000 x 2000 x 8 BPP, 32-bit, 96dpi. If I 
request the WCS I get a 24-bit image back. I tried to define different output 
formats, but couldn't find a solution yet.

3.) I tried to display the WCS in QGIS, which works, but it works really slow 
and I get an image with huge pixels back. If I request the height values and 
compare it to the original data, they are correct, but instead of float-values 
I get integer-values back. E. g. 42,33355m becomes 42m. Is there a way to 
influence this?

4.) If I request the WCS via browser with version=1.0.0 I get a fast response. 
If I request it with version 2.0 I always get a Timeout. Is there a problem 
with the different versions? Maybe that explains why QGIS is so slow.

You find my mapfile below:

MAP 
  EXTENT 278000 556 536000 5828000
  IMAGECOLOR 255 255 255
  NAME "WCS_NW_DGM"
  FONTSET"C:/ms4w/apps/GDI/fonts/fonts.list" # True-Type Schriften
  MAXSIZE 5000
  RESOLUTION 90.714285714285714285714285714286
  STATUS on
  UNITS meters


  PROJECTION
"init=epsg:25832"
  END

  WEB
imagepath "/tmp/"
imageurl "/tmp/"

METADATA
  "wcs_enable_request"   "*"
  "wcs_label" "WCS DGM"
  "wcs_encoding" "UTF-8"
  "wcs_title""WCS NW DGM"
  "wcs_onlineresource"   
"http://vbrk21nt15.bezreg-koeln.nrw.de/wms/wcs_nw_dgm;
  "wcs_description" "Höhenberechnungsdienst auf Basis des 
DGM"
  "wcs_keywordlist" "NRW-Atlas,NW,NRW,Bezirksregierung 
Köln,Abteilung 7,Geobasis 
NRW,Geobasisdaten,Landesvermessung,AdV,Arbeitsgemeinschaft der 
Vermessungsverwaltungen der Länder"  

END
  END

#-LAYER-

LAYER
  NAME "nw_dgm"
  TILEINDEX "//bezreg-koeln.nrw.de/BRK/Abt7/72_URA/NAS/URA/DGM1/utm32/DGM1"
  TILEITEM "LOCATION" 
  STATUS ON
  TYPE RASTER
  MINSCALE 1
  MAXSCALE 50001

  PROJECTION
"init=epsg:25832"
  END

  METADATA
"ows_srs" "EPSG:25832"
"wcs_extent""278000 556 536000 5828000"
"wcs_size" "600 600"
"wcs_resolution" "1 1"
"wcs_label" "DGM Hoehen"
"wcs_native_format" "32-bit GeoTIF"
"wcs_rangeset_name" "Range 1"
"wcs_rangeset_label" "DGM Höhen"
END
END 
END #map

Thanks in advance for any help!


Cora 
   


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Slow Response or Timeout for Mapserver

[Berger, Cora]

Hello Jeff,
thanks for the advice.
I checked the access logs and found out that our MaClient - Application (all 
the requests work fine here) makes POST-Request.
E.g. 

10.213.35.10 - - [30/Jun/2016:11:56:11 +0200] "GET 
/cgi-bin/test5?REQUEST=GetCapabilities=WMS HTTP/1.1" 200 10997 "-" 
"Java/1.6.0_30"
10.213.35.10 - - [30/Jun/2016:11:58:01 +0200] "POST /cgi-bin/test5 HTTP/1.1" 
200 321529 "-" "Java/1.6.0_30"

QGIS and our Open Layer applications use GET-Requests for the map-Request. 
Sometimes those requests don't seem to reach the server, because they are not 
logged if the request runs on a timeout or sth. 
We get a Mapimage if Firebug is on. A working request from the access-log looks 
like this:

10.213.31.120 - - [30/Jun/2016:07:11:40 +0200] "GET 
/cgi-bin/test5?REQUEST=GetCapabilities=WMS HTTP/1.0" 200 10997 "-" "-"
10.213.31.120 - - [30/Jun/2016:07:12:33 +0200] "GET 
/cgi-bin/test5?LAYERS==image%2Fpng=TRUE==WMS=1.1.1=GetMap=EPSG%3A25832=-181189.87723015,5458184.3609017,992882.87723015,5939737.6390983=1920=787
 HTTP/1.0" 200 354 
"http://vbrk21nt15.bezreg-koeln.nrw.de/tim-online2-chg/timobile.html; 
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0"

We have Mapserver 7.0 and Mapserver 6.3 running on Windows-machines and never 
has any comparable problems..



Cora Berger
   
- -
Bezirksregierung Köln
Dezernat 74 -  Geodatenzentrum / Geodateninfrastruktur
50606 Köln 
Internet: www.bezreg-koeln.nrw.de

Dienstgebäude: Muffendorfer Str. 19-21, 53177 Bonn
Telefon:   +49 (0) 221 - 147 - 4847
Telefax:   +49 (0) 228 - 180 - 33360 und (digital) 0221 - 147 - 4874
mailto: cora.ber...@bezreg-koeln.nrw.de
Internet: www.geobasis.nrw.de 
eShop:  www.geoportal.nrw.de

Folgen Sie uns auf Twitter: https://twitter.com/BezRegKoeln


Message: 2
Date: Wed, 29 Jun 2016 09:58:08 -0300
From: Jeff McKenna 
To: mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] Slow Response or Timeout for Mapserver
6.4 on Linux
Message-ID:
<4fe27792-5b14-5ac6-2d80-bab522fc4...@gatewaygeomatics.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello,

I would check your Apache access logs for the full requests, and compare 
them for the different clients (OpenLayers, QGIS, etc.), you might even 
paste 2 of these full GetMap urls here for the mailing list to compare 
the parameters - maybe one client is using something different causing 
your issue (?)

I had been facing a lot of truncated GetCapabilities requests in the 
MapServer 6 series, but have not seen any issues with MapServer 7. 
(there were lots of tickets for that old issue, but here is one example: 
https://github.com/mapserver/mapserver/issues/4505)

-jeff


-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Slow Response or Timeout for Mapserver 6.4 on Linux

[Berger, Cora]

Hello all,
I was working with Mapserver on Windows before. Now we moved to Linux. We use 
Mapserver 6.4.1. 
The response time to GetCapabilities and GetMap - requests for the same WMS 
vary a lot, depending on if you send the requests via browser or an Open Layers 
application or some other viewers or GIS. Often the requests even run on a 
timeout. The server is not busy at all. 
Does anybody know why? 
I saw your message from 2014 Jukka Rahkonen concerning " Slow output to PNG 
format with Mapserver 6.4" but you didn't seem to get a response.
Any clues?

Thanks a lot!


Cora Berger
   
- -
Bezirksregierung Köln
Dezernat 74 -  Geodatenzentrum / Geodateninfrastruktur
50606 Köln 
Internet: www.bezreg-koeln.nrw.de

Dienstgebäude: Muffendorfer Str. 19-21, 53177 Bonn
Telefon:   +49 (0) 221 - 147 - 4847
Telefax:   +49 (0) 228 - 180 - 33360 und (digital) 0221 - 147 - 4874
mailto: cora.ber...@bezreg-koeln.nrw.de
Internet: www.geobasis.nrw.de 
eShop:  www.geoportal.nrw.de

Folgen Sie uns auf Twitter: https://twitter.com/BezRegKoeln



___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Cascading Legend with selected Style

[Berger, Cora]

Hello everybody,
I'm using a WMS as a layer with Mapserver 7. The source WMS is available in 3 
different styles. I want my WMS to display the style called "SW", so I add  
   "wms_style"  "SW"  to my layers METADATA, which works fine. 
If I try to add a legend to this layer I get problems. 

I tried this
  
"wms_style"  "SW"
  "wms_style__legendurl_href" "example-url"
  "wms_style__legendurl_width" "531"
  "wms_style__legendurl_height" "769"
  "wms_style__legendurl_format" "image/png" 
  "wms_feature_info_mime_type" "text/html"

And this

  "wms_style"  "SW"
  "wms_style_SW_legendurl_href" "example-url"
  "wms_style_SW_legendurl_width" "531"
  "wms_style_SW_legendurl_height" "769"
  "wms_style_SW_legendurl_format" "image/png" 
  "wms_feature_info_mime_type" "text/html"

Nothing works. The legend gets displayed, if I leave the "wms_style"-tag empty:

"wms_style"  ""
  "wms_style__legendurl_href" "example-url"
  "wms_style__legendurl_width" "531"
  "wms_style__legendurl_height" "769"
  "wms_style__legendurl_format" "image/png" 
  "wms_feature_info_mime_type" "text/html"

But now the mapimage gets displayed with the default-style, which is in color 
and not in black and white (SW), as I want it to be. 

The error-message for the 2 examples above is: msWMSLoadGetMapParams(): WMS 
server error. Style (SW) not defined on layer.


Any ideas?

Thanks!


Cora Berger
   
- -
Bezirksregierung Köln
Dezernat 74 -  Geodatenzentrum / Geodateninfrastruktur
50606 Köln 
Internet: www.bezreg-koeln.nrw.de

Dienstgebäude: Muffendorfer Str. 19-21, 53177 Bonn
Telefon:   +49 (0) 221 - 147 - 4847
Telefax:   +49 (0) 228 - 180 - 33360 und (digital) 0221 - 147 - 4874
mailto: cora.ber...@bezreg-koeln.nrw.de
Internet: www.geobasis.nrw.de 
eShop:  www.geoportal.nrw.de

Folgen Sie uns auf Twitter: https://twitter.com/BezRegKoeln


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] RE Cascaded WMS GetFeatureInfo

[Berger, Cora]

Dear Steve,
yes, I have read this. My layers do cascade. The only thing that doesn't work 
is the GetFeatureInfo Request.
The original WMS supports GetFeatureInfo. But if I connect to this WMS and use 
it as a layer for my new WMS GetFeatureInfo stops working.
Cora



Von: steve.tout...@inspq.qc.ca [mailto:steve.tout...@inspq.qc.ca]
Gesendet: Mittwoch, 28. Oktober 2015 13:25
An: Berger, Cora
Cc: 'mapserver-users@lists.osgeo.org'; mapserver-users
Betreff: RE [mapserver-users] Cascaded WMS GetFeatureInfo

Cora have you read this?
http://mapserver.org/ogc/wms_server.html#cascading-wms-request
It might help to know why a layer is not cascaded

What happen if you don't modify the style?
steve



"Berger, Cora" 
<cora.ber...@bezreg-koeln.nrw.de<mailto:cora.ber...@bezreg-koeln.nrw.de>>@lists.osgeo.org
Envoyé par : "mapserver-users" 
<mapserver-users-boun...@lists.osgeo.org<mailto:mapserver-users-boun...@lists.osgeo.org>>

2015-10-27 04:01

A

"'mapserver-users@lists.osgeo.org'" 
<mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>>

cc

Objet

[mapserver-users] Cascaded WMS GetFeatureInfo









Hello everybody,
I am building a cascaded WMS. My layers all have connectiontype WMS and all of 
them use one layer of the same WMS as source. The only thing I change is the 
style of the original WMS.
My problem is that the GetFeatureInfo does not cascade. I am using Mapserver 
7.0. I read that the GetFeatureInfo request supports cascading. All requests 
are enabled in the metadata. Do I have to add a special tag in the metatada or 
layer section to "pass through" the GetFeatureInfo from the original WMS?

Thanks for your help.

Best regards

Cora Berger


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto: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

[mapserver-users] Cascaded WMS GetFeatureInfo

[Berger, Cora]

Hello everybody,
I am building a cascaded WMS. My layers all have connectiontype WMS and all of 
them use one layer of the same WMS as source. The only thing I change is the 
style of the original WMS. 
My problem is that the GetFeatureInfo does not cascade. I am using Mapserver 
7.0. I read that the GetFeatureInfo request supports cascading. All requests 
are enabled in the metadata. Do I have to add a special tag in the metatada or 
layer section to "pass through" the GetFeatureInfo from the original WMS?

Thanks for your help.

Best regards

Cora Berger
   

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users