Re: [mapserver-users] WCS GetCoverage request one by one pixel

2020-04-06 Thread Rahkonen Jukka (MML) 
Hi,

Could you have a try with the default resampling "nearest"? And then also with 
subset having lower limit equal to upper. Now it fails, I tried already.

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS=GetCoverage=2.0.1=ahn3_05m_dsm=image/tiff=x(196396.75,196396.75)=y(450031.75,450031.75)

GetCoverage trim with equal low and high has at least worked in the past, see 
http://osgeo-org.1560.x6.nabble.com/Why-WCS-2-0-1-slice-is-not-supported-td5343277.html

It should be OK by the WCS standard because all intersected pixels should be 
included and in this case the intersection is a single pixel. But see also 
https://osgeo-org.atlassian.net/browse/GEOS-9553 and learn that Geoserver 
supports slicing but not trimming to one pixel.

-Jukka Rahkonen-

Lähettäjä: mapserver-users  Puolesta 
Bakker, Anton
Lähetetty: maanantai 6. huhtikuuta 2020 16.00
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WCS GetCoverage request one by one pixel

Hi all,

I am running into a problem when sending HTTP requests to a MapServer backed 
WCS service.  I am trying to request a GeoTIFF of exactly 1 by 1 pixel, however 
this request fails by responding with a huge pixel (here is the 
describeCoverage request of the coverage requested):

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS=GetCoverage=2.0.1=ahn3_05m_dsm=image/tiff=x(196396.75,196397.25)=y(450031.75,450032.25)

When I modify the request to cover an area of 2X2 pixels, the response turns 
out fine:

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS=GetCoverage=2.0.1=ahn3_05m_dsm=image/tiff=x(196396.75,196397.75)=y(450031.75,450032.75)

See the screenshots hosted on imgur; (https://imgur.com/a/8IBGs3G (first 
screenshot is the erronous response of the request with the 1X1 extent, second 
screenshot is the result of the 2X2 request).

The MapServer version we are running is 7.4.3. Here is an excerpt of the 
mapfile that is used to configure the WCS service:

LAYER
NAME ahn3_05m_dsm
METADATA
  "wcs_srs"  "EPSG:28992"
  "wcs_label"   "ahn3_05m_dsm"
  "wcs_rangeset_name"   "ahn3_05m_dsm"
  "wcs_rangeset_label"  "ahn3_05m_dsm"
  "wcs_extent"  "1 25 356250 618750"
  "wcs_resolution"  "0.5 0.5"
  "wcs_formats" "GEOTIFF_FLOAT32 GEOTIFF_BYTE GEOTIFF_INT16 
GEOTIFF_RGB"
  "wcs_imagemode"   "FLOAT32"
  "wcs_bandcount"   "1"
END
TYPE RASTER
DUMP TRUE
STATUS ON
DATA /srv/data/ahn3_05m_dsm/ahn3_05m_dsm.vrt
PROCESSING "RESAMPLE=BILINEAR"
PROJECTION
  "init=epsg:28992"
END
END

I quickly skimmed the issue tracker on Github but could not find any issue 
causing this problem. Any thoughts on the cause of the problem are highly 
appreciated.

Kind regards,

Anton Bakker, Software Engineer
Kadaster / Geo- en Vastgoedinformatie en Advies / PDOK
tel. 06 - 29 737 351
anton.bak...@kadaster.nl
www.kadaster.nl



Disclaimer:
De inhoud van dit bericht is uitsluitend bestemd voor geadresseerde.
Gebruik van de inhoud van dit bericht door anderen zonder toestemming van het 
Kadaster
is onrechtmatig. Mocht dit bericht ten onrechte bij u terecht komen, dan 
verzoeken wij u
dit direct te melden aan de verzender en het bericht te vernietigen.
Aan de inhoud van dit bericht kunnen geen rechten worden ontleend.

Disclaimer:
The content of this message is meant to be received by the addressee only.
Use of the content of this message by anyone other than the addressee without 
the consent
of the Kadaster is unlawful. If you have received this message, but are not the 
addressee,
please contact the sender immediately and destroy the message.
No rights can be derived from the content of this message.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS GetCoverage request one by one pixel

2020-04-06 Thread Bakker, Anton 
Hi all,

I am running into a problem when sending HTTP requests to a MapServer backed 
WCS service.  I am trying to request a GeoTIFF of exactly 1 by 1 pixel, however 
this request fails by responding with a huge pixel (here is the 
describeCoverage request of the coverage requested):

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS=GetCoverage=2.0.1=ahn3_05m_dsm=image/tiff=x(196396.75,196397.25)=y(450031.75,450032.25)

When I modify the request to cover an area of 2X2 pixels, the response turns 
out fine:

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS=GetCoverage=2.0.1=ahn3_05m_dsm=image/tiff=x(196396.75,196397.75)=y(450031.75,450032.75)

See the screenshots hosted on imgur; (https://imgur.com/a/8IBGs3G (first 
screenshot is the erronous response of the request with the 1X1 extent, second 
screenshot is the result of the 2X2 request).

The MapServer version we are running is 7.4.3. Here is an excerpt of the 
mapfile that is used to configure the WCS service:

LAYER
NAME ahn3_05m_dsm
METADATA
  "wcs_srs"  "EPSG:28992"
  "wcs_label"   "ahn3_05m_dsm"
  "wcs_rangeset_name"   "ahn3_05m_dsm"
  "wcs_rangeset_label"  "ahn3_05m_dsm"
  "wcs_extent"  "1 25 356250 618750"
  "wcs_resolution"  "0.5 0.5"
  "wcs_formats" "GEOTIFF_FLOAT32 GEOTIFF_BYTE GEOTIFF_INT16 
GEOTIFF_RGB"
  "wcs_imagemode"   "FLOAT32"
  "wcs_bandcount"   "1"
END
TYPE RASTER
DUMP TRUE
STATUS ON
DATA /srv/data/ahn3_05m_dsm/ahn3_05m_dsm.vrt
PROCESSING "RESAMPLE=BILINEAR"
PROJECTION
  "init=epsg:28992"
END
END

I quickly skimmed the issue tracker on Github but could not find any issue 
causing this problem. Any thoughts on the cause of the problem are highly 
appreciated.

Kind regards,

Anton Bakker, Software Engineer
Kadaster / Geo- en Vastgoedinformatie en Advies / PDOK
tel. 06 - 29 737 351
anton.bak...@kadaster.nl
www.kadaster.nl



Disclaimer:
De inhoud van dit bericht is uitsluitend bestemd voor geadresseerde.
Gebruik van de inhoud van dit bericht door anderen zonder toestemming van het 
Kadaster 
is onrechtmatig. Mocht dit bericht ten onrechte bij u terecht komen, dan 
verzoeken wij u 
dit direct te melden aan de verzender en het bericht te vernietigen. 
Aan de inhoud van dit bericht kunnen geen rechten worden ontleend.

Disclaimer:
The content of this message is meant to be received by the addressee only.
Use of the content of this message by anyone other than the addressee without 
the consent 
of the Kadaster is unlawful. If you have received this message, but are not the 
addressee, 
please contact the sender immediately and destroy the message.
No rights can be derived from the content of this message
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Proxy WMS Request via Mapcache

2020-04-06 Thread Uwe Kickstein 
Hi,

i managed to configure a Layer from an external WMS just by configure a 
forwarding rule. So it won't get cached but the downside is that the 
Capabilties document does not containing this layer.
So is there a way to avoid this downside? 


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