Re: [MapServer-users] WCS no data issuse

[Aleš Grlj]

Hi,

1. For me, specifying

wcs_nilvalues" "-"


in the mapfile layer metadata worked and WCS returns non-zero and
transparent no data. - is no data value of my rasters read from the
database but it should work on other storages too.

2. MapServer will not aggregate mosaics for you as far as I know. It will
respect the order in which rasters are called and present no data pixels
even if they overlay valid data pixels from previous raster. And the same
goes for vrts.

If your rasters are stored in the database you could probably specify a
simple query to do a maximum value aggregation on rasters before MapServer
renders them as mosaic. That is if your no data value is lower than valid
values and if this is applicable for your datasets of course. To my
knowledge connection to raster database table is treated as regular
path/url so you have to mind the length of the query. At least I had huge
problems with this.

Cheers

Aleš


V čet., 17. avg. 2023, 21:01 je oseba <
mapserver-users-requ...@lists.osgeo.org> napisala:

> 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. How to handle NoData in WCS Request? Continuation of [Speed
>   of WMS vs Speed of WCS; How to speed up WCS service?]
>   (Marcin Niemyjski)
>
>
> --
>
> Message: 1
> Date: Thu, 17 Aug 2023 08:41:09 +
> From: Marcin Niemyjski 
> To: Marcin Niemyjski via MapServer-users
> 
> Subject: [MapServer-users] How to handle NoData in WCS Request?
> Continuation of [Speed of WMS vs Speed of WCS; How to speed up WCS
> service?]
> Message-ID:
> <
> as1pr03mb814665d8bb6c998c3032a8...@as1pr03mb8149.eurprd03.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
>
> Regarding the topic discussed in
> https://marc.info/?l=mapserver-users&m=169049275409489&w=2, I have
> implemented Jukka's suggestions. I created two new attributes, "start" and
> "stop." Here's the improved mapfile:
>
> https://pastecode.io/s/myjemd1r
> As you can see, there are 4 layers served from two tile indexes. The first
> layer consists of preprocessed OCGs with burned NoData, while the remaining
> three are served through VRT targeting different spatial resolutions
> depending on the requested zoom level, with the alpha channel set as a
> cloud mask. Here's an example of such a VRT (the others are similar):
> https://pastecode.io/s/af2tiwsj
>
>
> What is the problem?
>
>   1.  When I try to create a cloudless mosaic using this request for data
> stored in COGs for a single day and there is data available for the
> requested area, the raster is returned. However, instead of transparent
> NoData, a value of 0 is burned in the place of transparent NoData, and I
> need NoData transparency (it's a must-have).
>
>
> http://localhost/cgi-bin/mapserv?map=/var/www/mapbender/piramida_cloudless2.map&service=WCS&version=1.0.0&request=GetCoverage&coverage=test3&BBOX=3180020.455126192886,5542878.218003957532,3184499.682433307637,5548362.511879335158&CRS=EPSG:3857&WIDTH=771&HEIGHT=944&FORMAT=GTiff&start=2023-07-01&stop=2023-07-01
>
>   2.  When I try to create a cloudless mosaic using this request for data
> stored in COGs for multiple days(!), a black tile filled with values of 0
> is returned. This happens because there were no S2 revisions over that area
> for those days, except for 2023-07-01, but data from that day were covered
> with NoData from other days - this is an undesired effect :(
>
>
> http://localhost/cgi-bin/mapserv?map=/var/www/mapbender/piramida_cloudless2.map&service=WCS&version=1.0.0&request=GetCoverage&coverage=test3&BBOX=3180020.455126192886,5542878.218003957532,3184499.682433307637,5548362.511879335158&CRS=EPSG:3857&WIDTH=771&HEIGHT=944&FORMAT=GTiff&start=2023-07-01&stop=2023-07-0
> <
> http://localhost/cgi-bin/mapserv?map=/var/www/mapbender/piramida_cloudless2.map&service=WCS&version=1.0.0&request=GetCoverage&coverage=test3&BBOX=3180020.455126192886,5542878.218003957532,3184499.682433307637,5548362.511879335158&CRS=EPSG:3857&WIDTH=771&HEIGHT=944&FORMAT=GTiff&start=2023-07-01&stop=2023-07-01
> >5
>
>   3.  When I try to request data stored in VRT for a single day using this
> request, data is returned, but the alpha channel is not taken into account,
> so once again, transparency information is omitted.
>
>
> http://localhost/cgi-bin/mapserv?map=/var/www/mapbender/piramida_cloudless2.map&service=WCS&version=

Re: [MapServer-users] WCS 2.0.1 GetCoverage request results in corrupted geotiff

[Bakker, Anton via MapServer-users]

Hi Jukka,

Thanks for your suggestion, in the end I managed to resolve the issue.

The corrupted geotiff was not produced by MapServer, but by a Bash script I 
wrote 🤦‍♂️ which I used to convert the multipart response from the WCS 2.0.1 
GetCoverage request. It worked in the docker-compose setup presumably due to a 
different version of Bash compared with the docker setup in which the script 
was run on my local machine...

In any case we will not be needing the Bash script anymore to split the 
multipart response. Since I managed to solve the 
issue<https://github.com/MapServer/MapServer/issues/6551> that our MapServer 
setup is returning multipart responses for WCS 2.0.1 GetCoverage requests.

Cheers,
Anton


From: Rahkonen Jukka 
Sent: 27 August 2022 00:58
To: Bakker, Anton ; mapserver-users@lists.osgeo.org 

Subject: Re: WCS 2.0.1 GetCoverage request results in corrupted geotiff

Deze e-mail is afkomstig van buiten de organisatie

Hi,



Your question is exceptionally detailed but because the issue happens only with 
a certain Docker image maybe you should contact the authors of the image 
https://github.com/PDOK/mapserver-docker/. But you seem to be one of the 
contributors yourself 
https://github.com/PDOK/mapserver-docker/graphs/contributors. Generally 
speaking, if one Docker works while another one does not I think I would start 
by studying how they differ.



-Jukka Rahkonen-





Lähettäjä: MapServer-users  Puolesta 
Bakker, Anton via MapServer-users
Lähetetty: perjantai 26. elokuuta 2022 19.20
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [MapServer-users] WCS 2.0.1 GetCoverage request results in corrupted 
geotiff



Hi all,



I am running into a curious issue in which WCS 2.0.1 getcoverage requests 
produces a corrupted geotiff (which is bad) and WCS 1.0.0 getcoverage requests 
produce valid geotiffs (which is good). This behaviour occurs with our 
https://hub.docker.com/r/pdok/mapserver<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fpdok%2Fmapserver&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280290882891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Q0s0yCgZuksu7M6TBPSUQ8uu8jKgKVw%2F0b17z4DXKKU%3D&reserved=0>
 Docker image. I could not reproduce the behaviour with 
https://hub.docker.com/r/camptocamp/mapserver/<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fcamptocamp%2Fmapserver%2F&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fWyRMTs5BbWDGVGFqS%2FnDUFTx2gZrP3qVW6%2BS2V9rSA%3D&reserved=0>
 Docker image.

On top of that; I can only reproduce this issue when running with docker. When 
running the same example with docker-compose it works fine.



I detailed the full issue description and steps to reproduce in this 
gist<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>.
  If anyone has any suggestions or ideas what might be causing it I would be 
grateful for a response.

Kind regards,



[https://github.githubassets.com/images/modules/gists/gist-og-image.png]<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>

MapServer WCS 2.0.1 GetCoverage request results in corrupt 
geotiff<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>

MapServer WCS 2.0.1 GetCoverage request results in corrupt geotiff - README.md

gist.githu

Re: [MapServer-users] WCS 2.0.1 GetCoverage request results in corrupted geotiff

[Rahkonen Jukka]

Hi,

Your question is exceptionally detailed but because the issue happens only with 
a certain Docker image maybe you should contact the authors of the image 
https://github.com/PDOK/mapserver-docker/. But you seem to be one of the 
contributors yourself 
https://github.com/PDOK/mapserver-docker/graphs/contributors. Generally 
speaking, if one Docker works while another one does not I think I would start 
by studying how they differ.

-Jukka Rahkonen-


Lähettäjä: MapServer-users  Puolesta 
Bakker, Anton via MapServer-users
Lähetetty: perjantai 26. elokuuta 2022 19.20
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [MapServer-users] WCS 2.0.1 GetCoverage request results in corrupted 
geotiff

Hi all,

I am running into a curious issue in which WCS 2.0.1 getcoverage requests 
produces a corrupted geotiff (which is bad) and WCS 1.0.0 getcoverage requests 
produce valid geotiffs (which is good). This behaviour occurs with our 
https://hub.docker.com/r/pdok/mapserver<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fpdok%2Fmapserver&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280290882891%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Q0s0yCgZuksu7M6TBPSUQ8uu8jKgKVw%2F0b17z4DXKKU%3D&reserved=0>
 Docker image. I could not reproduce the behaviour with 
https://hub.docker.com/r/camptocamp/mapserver/<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Fr%2Fcamptocamp%2Fmapserver%2F&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fWyRMTs5BbWDGVGFqS%2FnDUFTx2gZrP3qVW6%2BS2V9rSA%3D&reserved=0>
 Docker image.

On top of that; I can only reproduce this issue when running with docker. When 
running the same example with docker-compose it works fine.

I detailed the full issue description and steps to reproduce in this 
gist<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>.
  If anyone has any suggestions or ideas what might be causing it I would be 
grateful for a response.

Kind regards,

[https://github.githubassets.com/images/modules/gists/gist-og-image.png]<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>
MapServer WCS 2.0.1 GetCoverage request results in corrupt 
geotiff<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.github.com%2Farbakker%2F889b10d839573c4cebb983ff19b17e94&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C8c5cd02a7bd44282578908da877fd14d%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C637971280291039128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U8TUOBs16nkC0D3ni7nkb53L5U3h0q2K4SoKu2rG7EM%3D&reserved=0>
MapServer WCS 2.0.1 GetCoverage request results in corrupt geotiff - README.md
gist.github.com


​Anton Bakker


Disclaimer:
De inhoud van deze e-mail is vertrouwelijk en uitsluitend bestemd voor de 
geadresseerde(n).
Gebruik, openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van 
deze informatie aan derden is niet toegestaan.
Op al onze producten en diensten zijn onze algemene leveringsvoorwaarden van 
toepassing
[https://www.kadaster.nl/algemene-leveringsvoorwaarden].

Disclaimer:
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, you are notified that disclosing, 
copying, distributing or taking any action in reliance on the contents of this 
information is strictly prohibited.
Our general terms and conditions of delivery apply to all our products and 
services
[https://www.kadaster.com/general-terms-and-conditions].
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[MapServer-users] WCS 2.0.1 GetCoverage request results in corrupted geotiff

[Bakker, Anton via MapServer-users]

Hi all,

I am running into a curious issue in which WCS 2.0.1 getcoverage requests 
produces a corrupted geotiff (which is bad) and WCS 1.0.0 getcoverage requests 
produce valid geotiffs (which is good). This behaviour occurs with our 
https://hub.docker.com/r/pdok/mapserver Docker image. I could not reproduce the 
behaviour with https://hub.docker.com/r/camptocamp/mapserver/ Docker image.

On top of that; I can only reproduce this issue when running with docker. When 
running the same example with docker-compose it works fine.

I detailed the full issue description and steps to reproduce in this 
gist.  If 
anyone has any suggestions or ideas what might be causing it I would be 
grateful for a response.

Kind regards,

[https://github.githubassets.com/images/modules/gists/gist-og-image.png]
MapServer WCS 2.0.1 GetCoverage request results in corrupt 
geotiff
MapServer WCS 2.0.1 GetCoverage request results in corrupt geotiff - README.md
gist.github.com



​Anton Bakker


Disclaimer:
De inhoud van deze e-mail is vertrouwelijk en uitsluitend bestemd voor de 
geadresseerde(n).
Gebruik, openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van 
deze informatie aan derden is niet toegestaan.
Op al onze producten en diensten zijn onze algemene leveringsvoorwaarden van 
toepassing
[https://www.kadaster.nl/algemene-leveringsvoorwaarden].

Disclaimer:
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, you are notified that disclosing, 
copying, distributing or taking any action in reliance on the contents of this 
information is strictly prohibited.
Our general terms and conditions of delivery apply to all our products and 
services
[https://www.kadaster.com/general-terms-and-conditions].
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS layer units question...

[Carl Godkin]

 Hi Jukka,

Thanks for pasting in your METADATA.  I copied yours to my map file and,
sure enough, I finally see the uom displayed!

After some experiments, I discovered that "wcs_band_names" is required if
you want to affect the metadata.  It actually says this in the
documentation but I overlooked it.

Once I added that, then I see my desired uom displayed by GetCoverage.
Hooray!

Thanks again for all of the help,

carl



On Thu, Jan 13, 2022 at 1:05 AM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> I can only tell that with these metadata settings in my mapfile
>
> METADATA
>
>   "wcs_label""orto_vv"  ### required
>
>   "wcs_resolution" "0.5 0.5"
>
>   "wcs_imagemode" "BYTE"
>
>   "wcs_bandcount" "3"
>
>   "wcs_band_names" "Band1 Band2 Band3"
>
>   "wcs_timeposition"
> "2000-11-11T11:11:11Z,2001-11-11T11:11:11Z"
>
>   "Band1_band_description""NIR range 700-900 nm"
>
>   "Band2_band_description""Red range 600-700 nm"
>
>   "Band3_band_description""Green range 500-600"
>
>   "Band1_band_uom" "foo"
>
>   "Band2_band_uom" "bar"
>
>   "Band3_band_uom" "foobar"
>
>   "wcs_rangeset_axis" "E,N"
>
>
>
>   "wcs_extent"  "212000.000 6762000.000 218000.000
> 6768000.000"
>
>   "wcs_rangeset_name"   "Range 1"  ### required to support
> DescribeCoverage request
>
>   "wcs_rangeset_label"  "My Label" ### required to support
> DescribeCoverage request
>
> END
>
> I can see for example this in DescribeCoverage
> 
>
> 
>
> Green range 500-600
>
> 
>
> 
>
>
>
> I have the same version 7.7.0-dev (MS4W 4.0.5).
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* torstai 13. tammikuuta 2022 2.45
> *Vastaanottaja:* Mapserver-Users (mapserver-users@lists.osgeo.org) <
> mapserver-users@lists.osgeo.org>
> *Aihe:* Re: [mapserver-users] WCS layer units question...
>
>
>
> Hi Jukka,
>
>
>
> Thanks for the documentation pointer.  I have attached a .map file in
> which I have all three of the possibilities
>
>
>
>   # Trying all three.  My single band is called "band"
>   "wcs_band_uom"  "m"
>   "ows_band_uom"  "m"
>   "band_band_uom"  "m"
>
>
>
> but I still only see
>
>
>
> 
>
>
>
> from DescribeCoverage.  I am very curious to know what I've overlooked!
>
>
>
> By the way, I'm running MapServer from the "camptocamp" docker image.  It
> appears to by MapServer 7.7-dev.
>
>
>
> Thanks so much,
>
> carl
>
>
>
> On Wed, Jan 12, 2022 at 9:47 AM Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
> Hi,
>
>
>
> Sorry, I thought that our service is open. This should work
> https://demo.mapserver.org/cgi-bin/wcs?SERVICE=wcs&VERSION=2.0.0&REQUEST=DescribeCoverage&COVERAGEID=modis
>
>
>
> The default value of uom is documented in
> https://www.mapserver.org/ogc/wcs_server.html
>
> “If no specific or default value is given, the output is dependent on the
> metadata key. The UOM, for example will be set to ‘W.m-2.Sr-1’”
>
>
>
> WCS metadata keywords, including “{band_name}_band_uom” work for us. I am
> sure that you will make it to work as well but if you won’t, show us your
> mapfile.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* keskiviikko 12. tammikuuta 2022 17.13
> *Vastaanottaja:* Mapserver-Users (mapserver-users@lists.osgeo.org) <
> mapserver-users@lists.osgeo.org>
> *Aihe:* Re: [mapserver-users] WCS layer units question...
>
>
>
> Thanks for the reply, Jukka.
>
>
>
> I found "wcs_band_uom" in the docs but I can't seem to make the value I
> put into my map file appear in the DescribeCoverage output.  (The link you
> sent doesn't work for me.)
>
>
>
> I do see this though:
>
>
>
> 
>
> 
>
> 
>
> 

Re: [mapserver-users] WCS layer units question...

[Rahkonen Jukka (MML)]

Hi,

I can only tell that with these metadata settings in my mapfile

METADATA
  "wcs_label""orto_vv"  ### required
  "wcs_resolution" "0.5 0.5"
  "wcs_imagemode" "BYTE"
  "wcs_bandcount" "3"
  "wcs_band_names" "Band1 Band2 Band3"
  "wcs_timeposition" "2000-11-11T11:11:11Z,2001-11-11T11:11:11Z"
  "Band1_band_description""NIR range 700-900 nm"
  "Band2_band_description""Red range 600-700 nm"
  "Band3_band_description""Green range 500-600"
  "Band1_band_uom" "foo"
  "Band2_band_uom" "bar"
  "Band3_band_uom" "foobar"
  "wcs_rangeset_axis" "E,N"

  "wcs_extent"  "212000.000 6762000.000 218000.000 
6768000.000"
  "wcs_rangeset_name"   "Range 1"  ### required to support 
DescribeCoverage request
  "wcs_rangeset_label"  "My Label" ### required to support 
DescribeCoverage request
END

I can see for example this in DescribeCoverage


Green range 500-600



I have the same version 7.7.0-dev (MS4W 4.0.5).

-Jukka Rahkonen-




Lähettäjä: MapServer-users 
mailto:mapserver-users-boun...@lists.osgeo.org>>
 Puolesta Carl Godkin
Lähetetty: torstai 13. tammikuuta 2022 2.45
Vastaanottaja: Mapserver-Users 
(mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>) 
mailto:mapserver-users@lists.osgeo.org>>
Aihe: Re: [mapserver-users] WCS layer units question...

Hi Jukka,

Thanks for the documentation pointer.  I have attached a .map file in which I 
have all three of the possibilities

  # Trying all three.  My single band is called "band"
  "wcs_band_uom"  "m"
  "ows_band_uom"  "m"
  "band_band_uom"  "m"

but I still only see



from DescribeCoverage.  I am very curious to know what I've overlooked!

By the way, I'm running MapServer from the "camptocamp" docker image.  It 
appears to by MapServer 7.7-dev.

Thanks so much,
carl

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

Re: [mapserver-users] WCS layer units question...

[Carl Godkin]

Hi Jukka,

Thanks for the documentation pointer.  I have attached a .map file in which
I have all three of the possibilities

  # Trying all three.  My single band is called "band"
  "wcs_band_uom"  "m"
  "ows_band_uom"  "m"
  "band_band_uom"  "m"

but I still only see



from DescribeCoverage.  I am very curious to know what I've overlooked!

By the way, I'm running MapServer from the "camptocamp" docker image.  It
appears to by MapServer 7.7-dev.

Thanks so much,
carl

On Wed, Jan 12, 2022 at 9:47 AM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> Sorry, I thought that our service is open. This should work
> https://demo.mapserver.org/cgi-bin/wcs?SERVICE=wcs&VERSION=2.0.0&REQUEST=DescribeCoverage&COVERAGEID=modis
>
>
>
> The default value of uom is documented in
> https://www.mapserver.org/ogc/wcs_server.html
>
> “If no specific or default value is given, the output is dependent on the
> metadata key. The UOM, for example will be set to ‘W.m-2.Sr-1’”
>
>
>
> WCS metadata keywords, including “{band_name}_band_uom” work for us. I am
> sure that you will make it to work as well but if you won’t, show us your
> mapfile.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* keskiviikko 12. tammikuuta 2022 17.13
> *Vastaanottaja:* Mapserver-Users (mapserver-users@lists.osgeo.org) <
> mapserver-users@lists.osgeo.org>
> *Aihe:* Re: [mapserver-users] WCS layer units question...
>
>
>
> Thanks for the reply, Jukka.
>
>
>
> I found "wcs_band_uom" in the docs but I can't seem to make the value I
> put into my map file appear in the DescribeCoverage output.  (The link you
> sent doesn't work for me.)
>
>
>
> I do see this though:
>
>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> -3.4028e+38 3.4028e+38
>
> 12
>
> 
>
> 
>
> 
>
> 
>
>
>
> The "swe:uom code" would seem to be what I want to affect.  For some
> reason I see the value "watts per square meter per steradian" which appears
> nowhere in my map file so I wonder if it's some sort of default baked into
> the code or something.  (I had seen that before but hadn't bothered to try
> to figure out what it was until just now.  That's weird.)
>
>
>
> Thanks for your help,
>
>
>
> carl
>
>
>
>
>
>
>
> On Tue, Jan 11, 2022 at 11:57 PM Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
> Hi,
>
>
>
> WCS users are supposed to read the metadata with DescribeCoverage, for
> example
> https://avoin-visukuva.nls.fi/ortokuvat-ja-korkeusmallit/wcs/v1?service=WCS&version=2.0.1&request=DescribeCoverage&coverageID=ortokuva_vari
>
> The units can be configured in the mapfile with “wcs_band_uom”. I do not
> know if it is possible to configure the outputformat to write uom also into
> the TIFF. That is something that GDAL should do.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* keskiviikko 12. tammikuuta 2022 3.58
> *Vastaanottaja:* Mapserver-Users (mapserver-users@lists.osgeo.org) <
> mapserver-users@lists.osgeo.org>
> *Aihe:* [mapserver-users] WCS layer units question...
>
>
>
> Hi,
>
>
>
> I have a local WCS & WMS server.
>
>
>
> I am trying to figure out if I can somehow define the Z units of a terrain
> layer I'm serving.
>
>
>
> The single band from the individual GeoTIFF files providing the terrain
> data looks like this (from gdalinfo):
>
>
>
> Band 1 Block=512x512 Type=Float32, ColorInterp=Gray
>   Description = Layer_1
>   NoData Value=-99
>   Unit Type: m <= units are meters
>   Metadata:
> LAYER_TYPE=athematic
> RepresentationType=ATHEMATIC
>
>
>
> but when I download a GeoTIFF using a WCS GetCoverage request on this
> layer, the GeoTIFF's single band just looks like this:
>
>
>
> Band 1 Block=571x3 Type=Float32, ColorInterp=Gray
>
>
>
> without "Unit Type."
>
>
>
> I also tried using
>
>UNITS Meters
>
> in my LAYER definition in my map file (copying an example I found among
> the case studies on the web site) but it didn't seem to have any effect.
>
>
>
> Is there some way to define and retrieve the Z units for a WCS server?
>
>
>
> Thanks very much

Re: [mapserver-users] WCS layer units question...

[Rahkonen Jukka (MML)]

Hi,

Sorry, I thought that our service is open. This should work 
https://demo.mapserver.org/cgi-bin/wcs?SERVICE=wcs&VERSION=2.0.0&REQUEST=DescribeCoverage&COVERAGEID=modis

The default value of uom is documented in 
https://www.mapserver.org/ogc/wcs_server.html
“If no specific or default value is given, the output is dependent on the 
metadata key. The UOM, for example will be set to ‘W.m-2.Sr-1’”

WCS metadata keywords, including “{band_name}_band_uom” work for us. I am sure 
that you will make it to work as well but if you won’t, show us your mapfile.

-Jukka Rahkonen-


Lähettäjä: MapServer-users  Puolesta 
Carl Godkin
Lähetetty: keskiviikko 12. tammikuuta 2022 17.13
Vastaanottaja: Mapserver-Users (mapserver-users@lists.osgeo.org) 

Aihe: Re: [mapserver-users] WCS layer units question...

Thanks for the reply, Jukka.

I found "wcs_band_uom" in the docs but I can't seem to make the value I put 
into my map file appear in the DescribeCoverage output.  (The link you sent 
doesn't work for me.)

I do see this though:







-3.4028e+38 3.4028e+38
12





The "swe:uom code" would seem to be what I want to affect.  For some reason I 
see the value "watts per square meter per steradian" which appears nowhere in 
my map file so I wonder if it's some sort of default baked into the code or 
something.  (I had seen that before but hadn't bothered to try to figure out 
what it was until just now.  That's weird.)

Thanks for your help,

carl



On Tue, Jan 11, 2022 at 11:57 PM Rahkonen Jukka (MML) 
mailto:jukka.rahko...@maanmittauslaitos.fi>>
 wrote:
Hi,

WCS users are supposed to read the metadata with DescribeCoverage, for example 
https://avoin-visukuva.nls.fi/ortokuvat-ja-korkeusmallit/wcs/v1?service=WCS&version=2.0.1&request=DescribeCoverage&coverageID=ortokuva_vari
The units can be configured in the mapfile with “wcs_band_uom”. I do not know 
if it is possible to configure the outputformat to write uom also into the 
TIFF. That is something that GDAL should do.

-Jukka Rahkonen-



Lähettäjä: MapServer-users 
mailto:mapserver-users-boun...@lists.osgeo.org>>
 Puolesta Carl Godkin
Lähetetty: keskiviikko 12. tammikuuta 2022 3.58
Vastaanottaja: Mapserver-Users 
(mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>) 
mailto:mapserver-users@lists.osgeo.org>>
Aihe: [mapserver-users] WCS layer units question...

Hi,

I have a local WCS & WMS server.

I am trying to figure out if I can somehow define the Z units of a terrain 
layer I'm serving.

The single band from the individual GeoTIFF files providing the terrain data 
looks like this (from gdalinfo):

Band 1 Block=512x512 Type=Float32, ColorInterp=Gray
  Description = Layer_1
  NoData Value=-99
  Unit Type: m <= units are meters
  Metadata:
LAYER_TYPE=athematic
RepresentationType=ATHEMATIC

but when I download a GeoTIFF using a WCS GetCoverage request on this layer, 
the GeoTIFF's single band just looks like this:

Band 1 Block=571x3 Type=Float32, ColorInterp=Gray

without "Unit Type."

I also tried using
   UNITS Meters
in my LAYER definition in my map file (copying an example I found among the 
case studies on the web site) but it didn't seem to have any effect.

Is there some way to define and retrieve the Z units for a WCS server?

Thanks very much.

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

Re: [mapserver-users] WCS layer units question...

[Carl Godkin]

Thanks for the reply, Jukka.

I found "wcs_band_uom" in the docs but I can't seem to make the value I put
into my map file appear in the DescribeCoverage output.  (The link you sent
doesn't work for me.)

I do see this though:







-3.4028e+38 3.4028e+38
12





The "swe:uom code" would seem to be what I want to affect.  For some reason
I see the value "watts per square meter per steradian" which appears
nowhere in my map file so I wonder if it's some sort of default baked into
the code or something.  (I had seen that before but hadn't bothered to try
to figure out what it was until just now.  That's weird.)

Thanks for your help,

carl



On Tue, Jan 11, 2022 at 11:57 PM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> WCS users are supposed to read the metadata with DescribeCoverage, for
> example
> https://avoin-visukuva.nls.fi/ortokuvat-ja-korkeusmallit/wcs/v1?service=WCS&version=2.0.1&request=DescribeCoverage&coverageID=ortokuva_vari
>
> The units can be configured in the mapfile with “wcs_band_uom”. I do not
> know if it is possible to configure the outputformat to write uom also into
> the TIFF. That is something that GDAL should do.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* keskiviikko 12. tammikuuta 2022 3.58
> *Vastaanottaja:* Mapserver-Users (mapserver-users@lists.osgeo.org) <
> mapserver-users@lists.osgeo.org>
> *Aihe:* [mapserver-users] WCS layer units question...
>
>
>
> Hi,
>
>
>
> I have a local WCS & WMS server.
>
>
>
> I am trying to figure out if I can somehow define the Z units of a terrain
> layer I'm serving.
>
>
>
> The single band from the individual GeoTIFF files providing the terrain
> data looks like this (from gdalinfo):
>
>
>
> Band 1 Block=512x512 Type=Float32, ColorInterp=Gray
>   Description = Layer_1
>   NoData Value=-99
>   Unit Type: m <= units are meters
>   Metadata:
> LAYER_TYPE=athematic
> RepresentationType=ATHEMATIC
>
>
>
> but when I download a GeoTIFF using a WCS GetCoverage request on this
> layer, the GeoTIFF's single band just looks like this:
>
>
>
> Band 1 Block=571x3 Type=Float32, ColorInterp=Gray
>
>
>
> without "Unit Type."
>
>
>
> I also tried using
>
>UNITS Meters
>
> in my LAYER definition in my map file (copying an example I found among
> the case studies on the web site) but it didn't seem to have any effect.
>
>
>
> Is there some way to define and retrieve the Z units for a WCS server?
>
>
>
> Thanks very much.
>
>
>
> carl
>
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS layer units question...

[Rahkonen Jukka (MML)]

Hi,

WCS users are supposed to read the metadata with DescribeCoverage, for example 
https://avoin-visukuva.nls.fi/ortokuvat-ja-korkeusmallit/wcs/v1?service=WCS&version=2.0.1&request=DescribeCoverage&coverageID=ortokuva_vari
The units can be configured in the mapfile with “wcs_band_uom”. I do not know 
if it is possible to configure the outputformat to write uom also into the 
TIFF. That is something that GDAL should do.

-Jukka Rahkonen-



Lähettäjä: MapServer-users  Puolesta 
Carl Godkin
Lähetetty: keskiviikko 12. tammikuuta 2022 3.58
Vastaanottaja: Mapserver-Users (mapserver-users@lists.osgeo.org) 

Aihe: [mapserver-users] WCS layer units question...

Hi,

I have a local WCS & WMS server.

I am trying to figure out if I can somehow define the Z units of a terrain 
layer I'm serving.

The single band from the individual GeoTIFF files providing the terrain data 
looks like this (from gdalinfo):

Band 1 Block=512x512 Type=Float32, ColorInterp=Gray
  Description = Layer_1
  NoData Value=-99
  Unit Type: m <= units are meters
  Metadata:
LAYER_TYPE=athematic
RepresentationType=ATHEMATIC

but when I download a GeoTIFF using a WCS GetCoverage request on this layer, 
the GeoTIFF's single band just looks like this:

Band 1 Block=571x3 Type=Float32, ColorInterp=Gray

without "Unit Type."

I also tried using
   UNITS Meters
in my LAYER definition in my map file (copying an example I found among the 
case studies on the web site) but it didn't seem to have any effect.

Is there some way to define and retrieve the Z units for a WCS server?

Thanks very much.

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

[mapserver-users] WCS layer units question...

[Carl Godkin]

Hi,

I have a local WCS & WMS server.

I am trying to figure out if I can somehow define the Z units of a terrain
layer I'm serving.

The single band from the individual GeoTIFF files providing the terrain
data looks like this (from gdalinfo):

Band 1 Block=512x512 Type=Float32, ColorInterp=Gray
  Description = Layer_1
  NoData Value=-99
  Unit Type: m <= units are meters
  Metadata:
LAYER_TYPE=athematic
RepresentationType=ATHEMATIC

but when I download a GeoTIFF using a WCS GetCoverage request on this
layer, the GeoTIFF's single band just looks like this:

Band 1 Block=571x3 Type=Float32, ColorInterp=Gray

without "Unit Type."

I also tried using
   UNITS Meters
in my LAYER definition in my map file (copying an example I found among the
case studies on the web site) but it didn't seem to have any effect.

Is there some way to define and retrieve the Z units for a WCS server?

Thanks very much.

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

Re: [mapserver-users] WCS Tile index question

[Carl Godkin]

Thanks again; I had messed up the gdaltindex paths so (as the debug log
told me), mapserver couldn't find the .hgt files.

I just fixed that and I'm thrilled to report I've got a WCS serving terrain
now.

Thanks so much!!
carl

On Wed, Oct 20, 2021 at 3:55 PM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> I was just about to suggest to use DEBUG. GDAL does not use 
> “wcs_native_format”,
> it is used for setting what will be written into DescribeCoverage.
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* Carl Godkin 
> *Lähetetty:* torstai 21. lokakuuta 2021 1.50
> *Vastaanottaja:* Rahkonen Jukka (MML)  >
> *Aihe:* Re: [mapserver-users] WCS Tile index question
>
>
>
> Sorry, right after I sent that last reply to the list, I thought of
> turning up the DEBUG value in the mapfile to 5 and now I see it's not
> finding my .hgt files for some reason.
>
>
>
> I will dig into this; maybe mapserver + GDAL don't actually needs
> wcs_native_format.
>
>
>
> More later to the list if I sort this out.  I really appreciate the help
> you and Jeff and others on the list have given me!
>
>
>
> carl
>
>
>
> On Tue, Oct 19, 2021 at 5:37 PM Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
> Hi,
>
>
>
> Here is more accurate documentation but only in the text
> https://www.mapserver.org/ogc/wcs_server.html
>
>
>
> “The convention is that once (wcs|ows)_extent and one of (wcs|ows)_size
> and (wcs|ows)_resolution is set in the layer metadata, all the coverage
> specific metadata will be retrieved from there. Otherwise the source image
> is queried via GDAL, if possible.”
>
>
>
> It seems that only wcs_extent is documented in the list of metadata
> elements but this is what they do:
>
>- wcs_extent defines the bounding box or your coverage -> that will go
>into DescribeCoverage
>- wcs_size is the size of the coverage as pixels -> pixel size can be
>computed by extent and size
>- wcs_resolution tells the pixel size explicitly -> size of the
>coverage in pixels can be computed
>
>
>
> We have in the LAYER-METADATA:
>
> "wcs_resolution" "0.5 0.5"
>
> "wcs_extent"  "19970 6597278 749676 7785300"
>
>
>
> That should be enough and Describe Coverage will have correct limits,
> origin, and offset vectors in RectifiedGrid.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* MapServer-users  
> *Puolesta
> *Carl Godkin
> *Lähetetty:* keskiviikko 20. lokakuuta 2021 1.17
> *Vastaanottaja:* mapserver-users@lists.osgeo.org
> *Aihe:* [mapserver-users] WCS Tile index question
>
>
>
> Hi again,
>
>
>
> I am working with Mapserver trying to set up a WCS layer based on a large
> collection of SRTM .hgt files.
>
>
>
> Since I have many input files instead of a single file, I want to use a
> tile index.  I know how to make and use a tile index for WMS, but there's a
> twist for WCS that I don't understand.
>
>
>
> According to this section of the docs:
>
>
>  
> https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers
>
> <https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers>
>
>
>
> I need to set “wcs_extent”, “wcs_size”, and “wcs_resolution” but I don't
> see where they are defined or documented.
>
>
>
> Can you point me to documentation?  The WCS Use Cases page gives some
> hints so I think I understand wcs_extent (though it's "ows_extent" in some
> examples there so I guess these are interchangeable?)
>
>
>
> How are the others defined?
>
>
>
> Thank you for your help,
>
> carl
>
>
>
>
>
>
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS Tile index question

[Rahkonen Jukka (MML)]

Hi,

I was just about to suggest to use DEBUG. GDAL does not use 
“wcs_native_format”, it is used for setting what will be written into 
DescribeCoverage.

-Jukka Rahkonen-

Lähettäjä: Carl Godkin 
Lähetetty: torstai 21. lokakuuta 2021 1.50
Vastaanottaja: Rahkonen Jukka (MML) 
Aihe: Re: [mapserver-users] WCS Tile index question

Sorry, right after I sent that last reply to the list, I thought of turning up 
the DEBUG value in the mapfile to 5 and now I see it's not finding my .hgt 
files for some reason.

I will dig into this; maybe mapserver + GDAL don't actually needs 
wcs_native_format.

More later to the list if I sort this out.  I really appreciate the help you 
and Jeff and others on the list have given me!

carl

On Tue, Oct 19, 2021 at 5:37 PM Rahkonen Jukka (MML) 
mailto:jukka.rahko...@maanmittauslaitos.fi>>
 wrote:
Hi,

Here is more accurate documentation but only in the text 
https://www.mapserver.org/ogc/wcs_server.html

“The convention is that once (wcs|ows)_extent and one of (wcs|ows)_size and 
(wcs|ows)_resolution is set in the layer metadata, all the coverage specific 
metadata will be retrieved from there. Otherwise the source image is queried 
via GDAL, if possible.”

It seems that only wcs_extent is documented in the list of metadata elements 
but this is what they do:

  *   wcs_extent defines the bounding box or your coverage -> that will go into 
DescribeCoverage
  *   wcs_size is the size of the coverage as pixels -> pixel size can be 
computed by extent and size
  *   wcs_resolution tells the pixel size explicitly -> size of the coverage in 
pixels can be computed

We have in the LAYER-METADATA:
"wcs_resolution" "0.5 0.5"
"wcs_extent"  "19970 6597278 749676 7785300"

That should be enough and Describe Coverage will have correct limits, origin, 
and offset vectors in RectifiedGrid.

-Jukka Rahkonen-


Lähettäjä: MapServer-users 
mailto:mapserver-users-boun...@lists.osgeo.org>>
 Puolesta Carl Godkin
Lähetetty: keskiviikko 20. lokakuuta 2021 1.17
Vastaanottaja: 
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
Aihe: [mapserver-users] WCS Tile index question

Hi again,

I am working with Mapserver trying to set up a WCS layer based on a large 
collection of SRTM .hgt files.

Since I have many input files instead of a single file, I want to use a tile 
index.  I know how to make and use a tile index for WMS, but there's a twist 
for WCS that I don't understand.

According to this section of the docs:
 
https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers
<https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers>

I need to set “wcs_extent”, “wcs_size”, and “wcs_resolution” but I don't see 
where they are defined or documented.

Can you point me to documentation?  The WCS Use Cases page gives some hints so 
I think I understand wcs_extent (though it's "ows_extent" in some examples 
there so I guess these are interchangeable?)

How are the others defined?

Thank you for your help,
carl


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

Re: [mapserver-users] WCS Tile index question

[Carl Godkin]

Hi again Jukka,

Thanks for the speedy response.  I now think that I have the resolution and
extent correct with these.  (I was getting various errors trying other
things but this
set seems okay for GetCoverage, GetCapabilities and DescribeCoverage):

"ows_extent" "-125 24 -66 50"
"wcs_resolution" "0.000833 0.000833"

I actually retrieve a correctly located GeoTIFF (yay!!) out with this query
for instance:

http://localhost:8080/wcs?service=WCS&version=2.0.1&; request=GetCoverage&
coverageid=SRTM_3_arc-second_grid& format=geotiff_16&
subset=Lat(43.256274,43.721318)& subset=Long(-112.357549,-111.719135)

but it's all zeros.

My data files are all native SRTM ".hgt" files. (And yes, I did "gdalinfo
-stats" on one tile for the above query and there are good values.)

I could gdal_translate them all to GeoTIFF, but since GDAL supports HGT
files I hoped I could use them as is.

I have tried everything I can think of for the "wcs_native_format" metadata:

  "wcs_native_format" "application/srtmhgt"

and application/hgt, image/hgt, srtmhgt, etc. I don't see errors in
mapserver log though no matter what I try. Is this my problem?

What do you suggest?

Thanks again,
carl









On Wed, Oct 20, 2021 at 3:23 PM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

>
>
> Lähettäjä: MapServer-users 
> Puolesta Carl Godkin
>
>
>
> >> On Tue, Oct 19, 2021 at 5:37 PM Rahkonen Jukka (MML)  jukka.rahko...@maanmittauslaitos.fi> wrote:
> >> Hi,
>
> >> Here is more accurate documentation but only in the text
> >> https://www.mapserver.org/ogc/wcs_server.html
>
> >> “The convention is that once (wcs|ows)_extent and one of
> >> (wcs|ows)_size and (wcs|ows)_resolution is set in the layer metadata,
> all the coverage specific metadata will be retrieved from there. Otherwise
> the source image is queried via GDAL, if possible.”
>
> >> It seems that only wcs_extent is documented in the list of metadata
> elements but this is what they do:
> >> • wcs_extent defines the bounding box or your coverage -> that will
> >> go into DescribeCoverage • wcs_size is the size of the coverage as
> >> pixels -> pixel size can be computed by extent and size •
> >> wcs_resolution tells the pixel size explicitly -> size of the
> >> coverage in pixels can be computed
>
> > Thanks a lot, Jukka.  That all makes some sense as far as it goes, but
> > I'm still not clear on a few details. I have this range of data: 24N to
> 50N and 125W to 66W which is 26 degrees by 59 degrees.
>
> >  Since the SRTM data has 3 arc-second spacing, that's 1200 pixels per
> > degree plus one for the extra edge so I have tried a number of things
> without success.
>
> What fails? Don't you get anything into DescribeCoverage or is all that
> you get wrong?
>
> > 1. Is wcs_size the size FULL range of the tiles that I have?  And what
> is the order?
>
> You do not need to bother about the size if you set the resolution, but
> yes, it is the full range of the coverage. See this
> https://beta-karttakuva.maanmittauslaitos.fi/wcs/service/ows?service=WCS&REQUEST=DescribeCoverage&VERSION=2.0.1&COVERAGEID=ortokuva__ortokuva
>
> The size is converted into the pixel space of the coverage
> gml:GridEnvelope>
> 0 0
> 1348356 2316499
> 
> I would say that the order is left-to-right - down-to-up but I fear that
> by the GML standard it can be something else. You can read about rectified
> grid from the OpenGIS Geography Markup Language (GML) Encoding Standard
> 3.2.1. I have never understood it but there are some images which may
> clarify this: "rectified grid: grid for which there is an affine
> transformation between the grid coordinates and the coordinates of an
> external coordinate reference system"
>
> > 2. Again, what is the order for wcs_resolution?  Are the units degrees
> since the coordinate system of the original data is EPSG:4326?
> With Mapserver the order is easting/longitude - northing/latitude
>
> > I've tried all of these, one at a time, and get various errors.  (1 /
> > 1200 = 0.0008...)
> What errors?
>
> >#"wcs_resolution" "0.0008 0.0008"
> Looks right
> >#"wcs_size" "70801 31201"
> Looks right if you prefer to give size instead of resolution
> >"wcs_size" "31201 70801"
> This is wrong.
>
> > In case it's helpful, here's my LAYER definition (with probably extra
> things I've tried based on my searching and trial & error):
>
> LAYER
>   NAME SRTM_3_arc-second_grid
>   METADATA
> "wcs_label"   "SRTM - 3 arc-second grid"  ### required
> "wcs_rangeset_name"   "Range 1"  ### required to support
> DescribeCoverage request
> "wcs_rangeset_label"  "Lower 48" ### required to support
> DescribeCoverage request
> "ows_extent" "-125 24 -66 50"
> #"wcs_resolution" "0.0008 0.0008"# 1/1200 for 3"
> spacing?
> #"wcs_size" "70801 31201"# Not sure of order
> "wcs_size" "31201 70801"
> "wcs_bandc

Re: [mapserver-users] WCS Tile index question

[Rahkonen Jukka (MML)]

Lähettäjä: MapServer-users  Puolesta 
Carl Godkin



>> On Tue, Oct 19, 2021 at 5:37 PM Rahkonen Jukka (MML) 
>>  wrote:
>> Hi,
 
>> Here is more accurate documentation but only in the text 
>> https://www.mapserver.org/ogc/wcs_server.html
 
>> “The convention is that once (wcs|ows)_extent and one of 
>> (wcs|ows)_size and (wcs|ows)_resolution is set in the layer metadata, all 
>> the coverage specific metadata will be retrieved from there. Otherwise the 
>> source image is queried via GDAL, if possible.”
 
>> It seems that only wcs_extent is documented in the list of metadata elements 
>> but this is what they do:
>> • wcs_extent defines the bounding box or your coverage -> that will 
>> go into DescribeCoverage • wcs_size is the size of the coverage as 
>> pixels -> pixel size can be computed by extent and size • 
>> wcs_resolution tells the pixel size explicitly -> size of the 
>> coverage in pixels can be computed

> Thanks a lot, Jukka.  That all makes some sense as far as it goes, but 
> I'm still not clear on a few details. I have this range of data: 24N to 50N 
> and 125W to 66W which is 26 degrees by 59 degrees.

>  Since the SRTM data has 3 arc-second spacing, that's 1200 pixels per 
> degree plus one for the extra edge so I have tried a number of things without 
> success.

What fails? Don't you get anything into DescribeCoverage or is all that you get 
wrong?

> 1. Is wcs_size the size FULL range of the tiles that I have?  And what is the 
> order?

You do not need to bother about the size if you set the resolution, but yes, it 
is the full range of the coverage. See this 
https://beta-karttakuva.maanmittauslaitos.fi/wcs/service/ows?service=WCS&REQUEST=DescribeCoverage&VERSION=2.0.1&COVERAGEID=ortokuva__ortokuva

The size is converted into the pixel space of the coverage gml:GridEnvelope>
0 0
1348356 2316499
 2. Again, what is the order for wcs_resolution?  Are the units degrees since 
> the coordinate system of the original data is EPSG:4326?
With Mapserver the order is easting/longitude - northing/latitude

> I've tried all of these, one at a time, and get various errors.  (1 /
> 1200 = 0.0008...)
What errors?

>        #"wcs_resolution" "0.0008 0.0008"
Looks right
>        #"wcs_size" "70801 31201"
Looks right if you prefer to give size instead of resolution
>        "wcs_size" "31201 70801"
This is wrong.

> In case it's helpful, here's my LAYER definition (with probably extra things 
> I've tried based on my searching and trial & error):

    LAYER
      NAME SRTM_3_arc-second_grid
      METADATA
        "wcs_label"           "SRTM - 3 arc-second grid"  ### required
        "wcs_rangeset_name"   "Range 1"  ### required to support 
DescribeCoverage request
        "wcs_rangeset_label"  "Lower 48" ### required to support 
DescribeCoverage request
        "ows_extent" "-125 24 -66 50"
        #"wcs_resolution" "0.0008 0.0008"# 1/1200 for 3" spacing?
        #"wcs_size" "70801 31201"# Not sure of order
        "wcs_size" "31201 70801"
        "wcs_bandcount" "1"
        "wcs_native_format" "SRTMHGT"# What should this be?  I can't find 
examples...

It is supposed to be the native format of the layer data, format that 
theoretically requires no processing, just selecting the right pixels. In 
practice the format that you users get by default with GetCoverage. It goes 
into DescribeCoverage about this way:
image/tiff 
and it is documented in the WCS 2.0.1 Core standard:
"4.7 Native Format
encoding format where, in a GetCoverage request, the range set values can be 
obtained unaltered"

        "wcs_srs" "EPSG:4326"
      END

      TYPE RASTER ### required
      STATUS ON
      TILEINDEX "../srtm_3_hgt/srtm_3_hgt-index.shp" # Path is relative to 
SHAPEPATH
      TILEITEM "Location"
      PROJECTION
        "init=epsg:4326"
      END
    END

> I feel like I must be close.  Thanks a lot for any further pointers,

-Jukka-

> carl

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

Re: [mapserver-users] WCS Tile index question

[Carl Godkin]

On Tue, Oct 19, 2021 at 5:37 PM Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> Here is more accurate documentation but only in the text
> https://www.mapserver.org/ogc/wcs_server.html
>
>
>
> “The convention is that once (wcs|ows)_extent and one of (wcs|ows)_size
> and (wcs|ows)_resolution is set in the layer metadata, all the coverage
> specific metadata will be retrieved from there. Otherwise the source image
> is queried via GDAL, if possible.”
>
>
>
> It seems that only wcs_extent is documented in the list of metadata
> elements but this is what they do:
>
>- wcs_extent defines the bounding box or your coverage -> that will go
>into DescribeCoverage
>- wcs_size is the size of the coverage as pixels -> pixel size can be
>computed by extent and size
>- wcs_resolution tells the pixel size explicitly -> size of the
>coverage in pixels can be computed
>
> Thanks a lot, Jukka.  That all makes some sense as far as it goes, but I'm
still not clear on a few details.  I have this range of data: 24N to 50N
and 125W to 66W which is 26 degrees by 59 degrees.

Since the SRTM data has 3 arc-second spacing, that's 1200 pixels per degree
plus one for the extra edge so I have tried a number of things without
success.

1. Is wcs_size the size FULL range of the tiles that I have?  And what is
the order?
2. Again, what is the order for wcs_resolution?  Are the units degrees
since the coordinate system of the original data is EPSG:4326?

I've tried all of these, one at a time, and get various errors.  (1 / 1200
= 0.0008...)

#"wcs_resolution" "0.0008 0.0008"
#"wcs_size" "70801 31201"
"wcs_size" "31201 70801"

In case it's helpful, here's my LAYER definition (with probably extra
things I've tried based on my searching and trial & error):

LAYER
  NAME SRTM_3_arc-second_grid
  METADATA
"wcs_label"   "SRTM - 3 arc-second grid"  ### required
"wcs_rangeset_name"   "Range 1"  ### required to support
DescribeCoverage request
"wcs_rangeset_label"  "Lower 48" ### required to support
DescribeCoverage request
"ows_extent" "-125 24 -66 50"
#"wcs_resolution" "0.0008 0.0008" # 1/1200 for 3" spacing?
#"wcs_size" "70801 31201" # Not sure of order
"wcs_size" "31201 70801"
"wcs_bandcount" "1"
"wcs_native_format" "SRTMHGT" # What should this be? I can't find
examples...
"wcs_srs" "EPSG:4326"
  END

  TYPE RASTER ### required
  STATUS ON
  TILEINDEX "../srtm_3_hgt/srtm_3_hgt-index.shp" # Path is relative to
SHAPEPATH
  TILEITEM "Location"
  PROJECTION
"init=epsg:4326"
  END
END
I feel like I must be close. Thanks a lot for any further pointers,

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

Re: [mapserver-users] WCS Tile index question

[Rahkonen Jukka (MML)]

Hi,

Here is more accurate documentation but only in the text 
https://www.mapserver.org/ogc/wcs_server.html

“The convention is that once (wcs|ows)_extent and one of (wcs|ows)_size and 
(wcs|ows)_resolution is set in the layer metadata, all the coverage specific 
metadata will be retrieved from there. Otherwise the source image is queried 
via GDAL, if possible.”

It seems that only wcs_extent is documented in the list of metadata elements 
but this is what they do:

  *   wcs_extent defines the bounding box or your coverage -> that will go into 
DescribeCoverage
  *   wcs_size is the size of the coverage as pixels -> pixel size can be 
computed by extent and size
  *   wcs_resolution tells the pixel size explicitly -> size of the coverage in 
pixels can be computed

We have in the LAYER-METADATA:
"wcs_resolution" "0.5 0.5"
"wcs_extent"  "19970 6597278 749676 7785300"

That should be enough and Describe Coverage will have correct limits, origin, 
and offset vectors in RectifiedGrid.

-Jukka Rahkonen-


Lähettäjä: MapServer-users  Puolesta 
Carl Godkin
Lähetetty: keskiviikko 20. lokakuuta 2021 1.17
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WCS Tile index question

Hi again,

I am working with Mapserver trying to set up a WCS layer based on a large 
collection of SRTM .hgt files.

Since I have many input files instead of a single file, I want to use a tile 
index.  I know how to make and use a tile index for WMS, but there's a twist 
for WCS that I don't understand.

According to this section of the docs:
 
https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers
<https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers>

I need to set “wcs_extent”, “wcs_size”, and “wcs_resolution” but I don't see 
where they are defined or documented.

Can you point me to documentation?  The WCS Use Cases page gives some hints so 
I think I understand wcs_extent (though it's "ows_extent" in some examples 
there so I guess these are interchangeable?)

How are the others defined?

Thank you for your help,
carl


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

[mapserver-users] WCS Tile index question

[Carl Godkin]

Hi again,

I am working with Mapserver trying to set up a WCS layer based on a large
collection of SRTM .hgt files.

Since I have many input files instead of a single file, I want to use a
tile index.  I know how to make and use a tile index for WMS, but there's a
twist for WCS that I don't understand.

According to this section of the docs:
 
https://mapserver.org/optimization/tileindex.html?highlight=wcs_resolution#note-for-wcs-layers


I need to set “wcs_extent”, “wcs_size”, and “wcs_resolution” but I don't
see where they are defined or documented.

Can you point me to documentation?  The WCS Use Cases page gives some hints
so I think I understand wcs_extent (though it's "ows_extent" in some
examples there so I guess these are interchangeable?)

How are the others defined?

Thank you for your help,
carl
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS: Write error at scanline xxxx

[Rahkonen Jukka (MML)]

Hi,

When I try to get any bigger output from WCS (in this case 12000x12000 pixels 
RGB) with a request like

http://localhost:8060/cgi-bin/mapserv.exe?map=c:/ms4w_data/wcs_vv_jr.map&service=WCS&version=2.0.0&request=GetCoverage&CoverageID=orto_vv&format=image/tiff&geotiff:tiling=true&geotiff:tileheight=256&geotiff:tilewidth=256
I get errors like this

http://www.opengis.net/ows/2.0 
http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd>


msWCSWriteFile20(): General error message. msSaveImage() failed 
msSaveImageGDAL(): General error message. Failed to create output GTiff file. 
TIFFAppendToStrip:Write error at scanline 1024




I managed to get bigger images = more pixels by asking for compressed output 
with &geotiff:compression=jpeg
I wonder what is the limiting resource and if there is something I could 
improve with some configuration. Because the output is a tiled GeoTIFF but the 
error is about writing a strip I guess that Mapserver is writing first an 
interim TIFF.

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

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

[Rahkonen Jukka (MML)]

Hi,

I verified the error and I am pretty sure that subsetting with min=max has been 
working for me couple of years ago with some Mapserver version.

This sends a GeoTIFF:
http://localhost:8060/cgi-bin/mapserv.exe?map=c:\ms4w_data\raster_test.map&service=WCS&version=2.0.1&request=GetCoverage&CoverageID=natural_earth&SUBSET=long(27,28)&SUBSET=lat(62,63)

This sends an error:
http://localhost:8060/cgi-bin/mapserv.exe?map=c:\ms4w_data\raster_test.map&service=WCS&version=2.0.1&request=GetCoverage&CoverageID=natural_earth&SUBSET=long(27,27)&SUBSET=lat(62,62)
msImageCreate(): Image handling error. Attempt to allocate raw image failed, 
out of memory.

I believe that 1x1 pixel image is expected because WCS 2.0.1 standard defines 
that the request is OK.

"Then, for the trim bounds trimLow and trimHigh the following
shall hold: L <= trimLow <= trimHigh <= H"

Here is my MS4W mapfile for the Natural Earth raster 
https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/50m/raster/NE1_50M_SR_W.zip<https://www.naturalearthdata.com/http/www.naturalearthdata.com/download/50m/raster/NE1_50M_SR_W.zip>

MAP
  NAME ""
  STATUS ON
MAXSIZE 5000
CONFIG "MS_ERRORFILE" "c:\ms4w_data\test_error.txt"
#DEBUG 3
EXTENT -180 -90 180 90
  SIZE 600 600
  #SHAPEPATH "c:\ms4w\tmp\ms_tmp"
  IMAGECOLOR 255 255 255
  UNITS METERS
  WEB
#IMAGEPATH "c:\ms4w\tmp\ms_tmp"
#IMAGEURL "c:\ms4w\tmp\ms_tmp"
  METADATA
  "ows_enable_request" "*"
  "wms_srs""EPSG:4326"
  "ows_onlineresource"
"http://localhost:8060/cgi-bin/mapserv.exe?map=c:\ms4w_data\test.map";
  "wms_title""wms-test"
  "wcs_label"   "wcs-test" ### required
  "wcs_description" "wcs-test"
  "wcs_enable_request"   "*"
 END
  END
PROJECTION
"init=epsg:4326"
  END
  OUTPUTFORMAT
  NAME 'AGG_Q'
  MIMETYPE "image/png"  DRIVER "AGG/PNG"
  EXTENSION "png"
  IMAGEMODE RGB
  FORMATOPTION "QUANTIZE_FORCE=ON"
  FORMATOPTION "QUANTIZE_DITHER=OFF"
  FORMATOPTION "QUANTIZE_COLORS=256"
  END
OUTPUTFORMAT
  NAME GEOTIFF
  DRIVER "GDAL/GTiff"
  MIMETYPE "image/tiff"
  IMAGEMODE BYTE
  EXTENSION "tif"
END

LAYER
NAME "natural_earth"
TYPE RASTER
STATUS ON
DATA "c:\ms4w_data\ne_raster\NE1_50M_SR_W.tif"
PROJECTION
"init=epsg:4326"
END
METADATA
  "wms_title" "ne_raster"
  "wcs_title" "ne_raster"
END

END #layer
END #map


Lähettäjä: mapserver-users  Puolesta 
Even Rouault
Lähetetty: lauantai 9. toukokuuta 2020 21.41
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: Re: [mapserver-users] WCS GetCoverage request one by one pixel


Anton,



> 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.



I believe this is a bug in MapServer due to a difference between pixel-center 
vs pixel-corner convention between WCS conventions and MapServer conventions, 
which must lead to an empty bounding box when the request is 1x1, and thus 
causing invalid resolution to be computed at some point (division by zero). 
This could presumably be fixed



Even



--

Spatialys - Geospatial professional services

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

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

[Even Rouault]

Anton,

> 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.

I believe this is a bug in MapServer due to a difference between pixel-center 
vs 
pixel-corner convention between WCS conventions and MapServer conventions, 
which must lead to an empty bounding box when the request is 1x1, and thus 
causing invalid resolution to be computed at some point (division by zero). 
This 
could presumably be fixed

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

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

[Bakker, Anton]

Hi Jukka,

I finally managed to check up on your suggestion. I set the RESAMPLE mode to 
NEAREST in the mapfile on a MapServer instance running locally on my machine. 
This results in the same response as setting the resampling method in the url 
(see my previous email) :

http://localhost:32788/ahn3/wcs?service=WCS&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=y(450031.75,450031.75)


http://www.opengis.net/ows/2.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="2.0.1" 
xml:lang="en-US" xsi:schemaLocation="http://www.opengis.net/ows/2.0 
https://geodata.nationaalgeoregister.nl/ows/2.0/owsExceptionReport.xsd">
  
msImageCreate(): Image handling error. Attempt to 
allocate raw image failed, out of memory.
  


Also all resampling methods result in the same response (tested by supplying 
through the query parameter in the url). When  I look in the logs I see that 
MapServer determines the dimensions of the request to be 0x0 pixels, causing 
the creation of the image to fail:

2020-05-06 17:38:11: (mod_fastcgi.c.421) FastCGI-stderr: Subset for X-axis 
found: x
2020-05-06 17:38:11: (mod_fastcgi.c.421) FastCGI-stderr: Subset for Y-axis 
found: y
2020-05-06 17:38:11: (mod_fastcgi.c.421) FastCGI-stderr: msWCSGetCoverage20(): 
Set parameters from originaldata. Width: 0, height: 0, cellsize: -nan, extent: 
-nan,-nan,-nan,-nan
2020-05-06 17:38:11: (mod_fastcgi.c.421) FastCGI-stderr: msImageCreate(): Image 
handling error. Attempt to allocate raw image failed, out of memory.

​I also quickly checked whether requesting a 1x1 subset works, but this fails 
by returning geotiff image of 1x1 pixel with a pixel size of "-135000,162500":
http://localhost:32788/ahn3/wcs?service=WCS&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.25)&subset=y(450031.75,450032.25)

However requesting an image of 2x2 pixels still works as expected:
http://localhost:32788/ahn3/wcs?service=WCS&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.75)&subset=y(450031.75,450032.75)

Kind regards,
Anton


From: Rahkonen Jukka (MML) 
mailto:jukka.rahko...@maanmittauslaitos.fi>>
Sent: Tuesday, April 7, 2020 5:49 PM
To: Bakker, Anton mailto:anton.bak...@kadaster.nl>>; 
mapserver-users@lists.osgeo.org 
mailto:mapserver-users@lists.osgeo.org>>
Subject: Re: WCS GetCoverage request one by one pixel


Hi Anton,



What I meant was to have a try by commenting out this line from your mapfile

PROCESSING "RESAMPLE=BILINEAR"



Actually it would be interesting to know what really happens if the 
interpolation/resampling method is configured in the mapfile and GetCoverage 
comes also with Interpolation parameter.



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

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

[Bakker, Anton]

Hi Jukka,

Thanks for your response; do you mean to set the default resampling method in 
the mapfile? Setting the resampling method in the WCS request does not work 
(for both GET and POST requests):

POST:

http://www.opengis.net/wcs/2.0
http://schemas.opengis.net/wcs/2.0/wcsAll.xsd";
  xmlns="http://www.opengis.net/wcs/2.0";
  xmlns:wcs="http://www.opengis.net/wcs/2.0";
  xmlns:wcscrs="http://www.opengis.net/wcs/crs/1.0";
  xmlns:scal="http://www.opengis.net/wcs/scaling/1.0";
  xmlns:int="http://www.opengis.net/wcs/interpolation/1.0";
  service="WCS"
  version="2.0.1">
ahn3_05m_dsm

x
196396.75
196396.75


y
450031.75
450031.75

image/tiff


NEAREST




GET:

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=y(450031.75,450031.75)&INTERPOLATION=NEAREST

Both POST and GET request fail with the same error: "msImageCreate(): Image 
handling error. Attempt to allocate raw image failed, out of memory."

Cheers,
Anton


From: Rahkonen Jukka (MML) 
mailto:jukka.rahko...@maanmittauslaitos.fi>>
Sent: Monday, April 6, 2020 5:26 PM
To: Bakker, Anton mailto:anton.bak...@kadaster.nl>>; 
mapserver-users@lists.osgeo.org 
mailto:mapserver-users@lists.osgeo.org>>
Subject: Re: WCS GetCoverage request one by one pixel


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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=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-


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

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

[Rahkonen Jukka (MML)]

Hi Anton,

What I meant was to have a try by commenting out this line from your mapfile
PROCESSING "RESAMPLE=BILINEAR"

Actually it would be interesting to know what really happens if the 
interpolation/resampling method is configured in the mapfile and GetCoverage 
comes also with Interpolation parameter.

-Jukka-

Lähettäjä: Bakker, Anton 
Lähetetty: tiistai 7. huhtikuuta 2020 18.40
Vastaanottaja: Rahkonen Jukka (MML) ; 
mapserver-users@lists.osgeo.org
Aihe: RE: WCS GetCoverage request one by one pixel

Hi Jukka,

Thanks for your response; do you mean to set the default resampling method in 
the mapfile? Setting the resampling method in the WCS request does not work 
(for both GET and POST requests):

POST:

http://www.opengis.net/wcs/2.0
http://schemas.opengis.net/wcs/2.0/wcsAll.xsd";
  xmlns="http://www.opengis.net/wcs/2.0";
  xmlns:wcs="http://www.opengis.net/wcs/2.0";
  xmlns:wcscrs="http://www.opengis.net/wcs/crs/1.0";
  xmlns:scal="http://www.opengis.net/wcs/scaling/1.0";
  xmlns:int="http://www.opengis.net/wcs/interpolation/1.0";
  service="WCS"
  version="2.0.1">
ahn3_05m_dsm

x
196396.75
196396.75


y
450031.75
450031.75

image/tiff


NEAREST




GET:

https://geodata.nationaalgeoregister.nl/ahn3/wcs?service=WCS&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=y(450031.75,450031.75)&INTERPOLATION=NEAREST

Both POST and GET request fail with the same error: "msImageCreate(): Image 
handling error. Attempt to allocate raw image failed, out of memory."

Cheers,
Anton


From: Rahkonen Jukka (MML) 
mailto:jukka.rahko...@maanmittauslaitos.fi>>
Sent: Monday, April 6, 2020 5:26 PM
To: Bakker, Anton mailto:anton.bak...@kadaster.nl>>; 
mapserver-users@lists.osgeo.org 
mailto:mapserver-users@lists.osgeo.org>>
Subject: Re: WCS GetCoverage request one by one pixel


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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=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-


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

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

[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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196396.75)&subset=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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.25)&subset=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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.75)&subset=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<mailto:anton.bak...@kadaster.nl>
www.kadaster.nl<http://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

[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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.25)&subset=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&Request=GetCoverage&version=2.0.1&CoverageId=ahn3_05m_dsm&format=image/tiff&subset=x(196396.75,196397.75)&subset=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

Re: [mapserver-users] WCS 2.0.1 not returning same image as WCS 1.0.0

[Moisan, Yves (NRCAN/RNCAN)]

bbox=376509,4898728,377163,4899504 resx=0.4 resy=0.4 # WCS 1.0.0

become

SUBSET=x(376509,377163) SUBSET=y(4898728,4899504) RESOLUTION=x(0.4) 
RESOLUTION=y(0.4) # WCS 2.0.1

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

Re: [mapserver-users] WCS 2.0.1 not returning same image as WCS 1.0.0

[Rahkonen Jukka (MML)]

Hi,

I recommend to read the WCS 2.0 core standard which does not support bbox, resx 
or resy anymore. Mapserver documentation shows also how to use SUBSET 
https://www.mapserver.org/ogc/wcs_server.html. If you need to change the pixel 
size then the document to read is the WCS Scaling extension standard 
https://portal.opengeospatial.org/files/12-039.


-Jukka Rahkonen-

Lähettäjä: mapserver-users  Puolesta 
Moisan, Yves (NRCAN/RNCAN)
Lähetetty: keskiviikko 5. kesäkuuta 2019 21.05
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WCS 2.0.1 not returning same image as WCS 1.0.0

Hi All,

On Ubuntu 18.04 with :

MapServer version 7.0.7 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ 
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS 
SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER 
SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER 
SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS INPUT=JPEG 
INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

When I issue a GetCoverage in WCS 1.0.1 I get a 1635 X 1940 pixels GTiff image :

http://myserver?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=myCoverage&bbox=376509,4898728,377163,4899504&crs=EPSG:26918&resx=0.4&resy=0.4&FORMAT=image/tiff

The same request, only in 2.0.1 and with COVERAGEID instead of COVERAGE, I get :

msWCSGetCoverage20(): WCS server error. Raster size out of range, width and 
height of resulting coverage must be no more than MAXSIZE=4096.

How can that be ?  I'm specifying resx resy to the values pixels have in the 
image behind the service (and when I overlay the image I get back from the WCS 
1.0.0 call it matches the original image pixel for pixel) so there can't be 
interpolation going on here.  I'm surprised.

Thanx for pointers,

Yves


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

[mapserver-users] WCS 2.0.1 not returning same image as WCS 1.0.0

[Moisan, Yves (NRCAN/RNCAN)]

Hi All,

On Ubuntu 18.04 with :

MapServer version 7.0.7 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ 
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS 
SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER 
SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER 
SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS INPUT=JPEG 
INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

When I issue a GetCoverage in WCS 1.0.1 I get a 1635 X 1940 pixels GTiff image :

http://myserver?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=myCoverage&bbox=376509,4898728,377163,4899504&crs=EPSG:26918&resx=0.4&resy=0.4&FORMAT=image/tiff

The same request, only in 2.0.1 and with COVERAGEID instead of COVERAGE, I get :

msWCSGetCoverage20(): WCS server error. Raster size out of range, width and 
height of resulting coverage must be no more than MAXSIZE=4096.

How can that be ?  I'm specifying resx resy to the values pixels have in the 
image behind the service (and when I overlay the image I get back from the WCS 
1.0.0 call it matches the original image pixel for pixel) so there can't be 
interpolation going on here.  I'm surprised.

Thanx for pointers,

Yves


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

[mapserver-users] WCS 2.0.1 not returning same image as WCS 1.0.0

[Moisan, Yves (NRCAN/RNCAN)]

Hi All,

On Ubuntu 18.04 with :

MapServer version 7.0.7 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ 
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS 
SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER 
SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER 
SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS INPUT=JPEG 
INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

When I issue a GetCoverage in WCS 1.0.1 I get a 1635 X 1940 pixels GTiff image :

http://myserver?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=myCoverage&bbox=376509,4898728,377163,4899504&crs=EPSG:26918&resx=0.4&resy=0.4&FORMAT=image/tiff

The same request, only in 2.0.1 and with COVERAGEID instead of COVERAGE, I get :

msWCSGetCoverage20(): WCS server error. Raster size out of range, width and 
height of resulting coverage must be no more than MAXSIZE=4096.

How can that be ?  I'm specifying resx resy to the values pixels have in the 
image behind the service (and when I overlay the image I get back from the WCS 
1.0.0 call it matches the original image pixel for pixel) so there can't be 
interpolation going on here.  I'm surprised.

Thanx for pointers,

Yves

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

Re: [mapserver-users] WCS 2.0.1 sends multipart response for ascii grid format

[Rahkonen Jukka (MML)]

Hi,

I thought I could resolve the problem by setting
CONFIG "GDAL_PAM_ENABLED" "NO"

Unfortunately nothing changed.

-Jukka Rahkonen-


Lähettäjä: Rahkonen Jukka (MML)
Lähetetty: keskiviikko 8. toukokuuta 2019 18.53
Vastaanottaja: Mapserver-Users (mapserver-users@lists.osgeo.org) 

Aihe: WCS 2.0.1 sends multipart response for ascii grid format

Hi,

I have Mapserver 7.2.1 and outputformat defined as

OUTPUTFORMAT
NAME AAIGRID
DRIVER "GDAL/AAIGRID"
MIMETYPE "application/x-ascii-grid"
IMAGEMODE FLOAT32
EXTENSION "grd"
FORMATOPTION "SIGNIFICANT_DIGITS=5"
END

The WCS 2.0.1 GetCoverage request is sending the response as multipart.  The 
first part is the ASCII grid and it is followed by these two parts

--wcs
Content-Type: application/octet-stream
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.grd.aux.xml
Content-Disposition: INLINE; filename=out.grd.aux.xml


  
2
72.00
72.00
  


--wcs
Content-Type: application/octet-stream
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.prj
Content-Disposition: INLINE; filename=out.prj

PROJCS["ETRS89_TM35FIN_E_N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",27],PARAMETER["scale_factor",0.9996],PARAMETER["false_easting",50],PARAMETER["false_northing",0],UNIT["Meter",1]]

Is there a way to get rid of the last parts of the response?

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

[mapserver-users] WCS 2.0.1 sends multipart response for ascii grid format

[Rahkonen Jukka (MML)]

Hi,

I have Mapserver 7.2.1 and outputformat defined as

OUTPUTFORMAT
NAME AAIGRID
DRIVER "GDAL/AAIGRID"
MIMETYPE "application/x-ascii-grid"
IMAGEMODE FLOAT32
EXTENSION "grd"
FORMATOPTION "SIGNIFICANT_DIGITS=5"
END

The WCS 2.0.1 GetCoverage request is sending the response as multipart.  The 
first part is the ASCII grid and it is followed by these two parts

--wcs
Content-Type: application/octet-stream
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.grd.aux.xml
Content-Disposition: INLINE; filename=out.grd.aux.xml


  
2
72.00
72.00
  


--wcs
Content-Type: application/octet-stream
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.prj
Content-Disposition: INLINE; filename=out.prj

PROJCS["ETRS89_TM35FIN_E_N",GEOGCS["GCS_ETRS_1989",DATUM["D_ETRS_1989",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",27],PARAMETER["scale_factor",0.9996],PARAMETER["false_easting",50],PARAMETER["false_northing",0],UNIT["Meter",1]]

Is there a way to get rid of the last parts of the response?

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

[mapserver-users] WCS 2.0.1 does not honour the list of crsSupported

[Rahkonen Jukka (MML)]

Hi,

I have defined the CRS list for the WCS service with the "ows_srs" metadata and 
that reflects correctly to CRS list in GetCapabilities 
"". However, it seems that Mapserver accepts 
any CRS as SubsettingCRS and OutputCRS. According to the standard the service 
should give expections  "SubsettingCrs-NotSupported" or 
"OutputCrs-NotSupported" .  Also if I use some non-existing CRS the error is 
not the one defined in the standard, but: msProcessProjection(): Projection 
library error. proj error "no options found in 'init' file" for 
"init=epsg:045".  Value "epsg:3034" does work as OutputCRS even it probably 
shouldn't because in GetCapabilities it is shown as
http://www.opengis.net/def/crs/EPSG/0/3045

I wonder if I have understood something wrong with the WCS configuration of if 
I have just discovered a couple of bugs.

I guess that there is no way to disable the older WCS 1.x versions by using 
just mapfile but I would be glad to be wrong.

-Jukka Rahkonen-


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

Re: [mapserver-users] WCS 2.0 request without interpolation

[Even Rouault]

On mardi 13 novembre 2018 13:34:56 CET Rousseau Lambert2, Louis-Philippe (EC) 
wrote:
> Hi guys,
> 
> Do you know if it's possible to do a WCS 2.0 request without interpolation,
> like simply clip the original file on it's native grid?
> 
> I know that there is the INTERPOLATION parameter for WCS, but the only
> possible values are "NEAREST", "BILINEAR" and "AVERAGE". And I don't see a
> way using wcs keywords in the mapfile to add or modify the interpolation
> options...
> 
> I get that for this to even be possible the BBOX of the request would have
> to be made in the the dataset native CRS.

Indeed. And you need to align your BBOX with the grid coordinates returned by 
DescribeCoverage, and use NEAREST for double security.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS 2.0 request without interpolation

[Rahkonen Jukka (MML)]

Hi,

There are lots of good reading in the WCS section of OGC standards 
http://www.opengeospatial.org/standards/wcs. Subsetting that is used for 
BBOX-alike queries is explained in the core. There are also WCS 2.0 KVP 
examples in https://www.mapserver.org/ogc/wcs_server.html

Clip in native CRS and without interpolation (effectively the same as nearest 
because every pixel match) is the main use case for WCS 2.0 core service. You 
can test with this and get a subset of a DEM coverage

https://beta-karttakuva.maanmittauslaitos.fi/wcs/service/ows?service=WCS&version=2.0.1&request=GetCoverage&CoverageID=korkeusmalli_2m&SUBSET=E(496000,50)&SUBSET=N(7181000,7185000)&format=image/tiff
Save the response on disk and compare what gdalinfo shows about the image with 
how the coverage is defined in DescribeCoverage


-Jukka Rahkonen-

Lähettäjä: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] 
Puolesta Rousseau Lambert2, Louis-Philippe (EC)
Lähetetty: 13. marraskuuta 2018 15:35
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WCS 2.0 request without interpolation


Hi guys,
Do you know if it's possible to do a WCS 2.0 request without interpolation, 
like simply clip the original file on it's native grid?

I know that there is the INTERPOLATION parameter for WCS, but the only possible 
values are "NEAREST", "BILINEAR" and "AVERAGE". And I don't see a way using wcs 
keywords in the mapfile to add or modify the interpolation options...

I get that for this to even be possible the BBOX of the request would have to 
be made in the the dataset native CRS.

Thanks

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

[mapserver-users] WCS 2.0 request without interpolation

[Rousseau Lambert2, Louis-Philippe (EC)]

Hi guys,

Do you know if it's possible to do a WCS 2.0 request without interpolation, 
like simply clip the original file on it's native grid?

I know that there is the INTERPOLATION parameter for WCS, but the only possible 
values are "NEAREST", "BILINEAR" and "AVERAGE". And I don't see a way using wcs 
keywords in the mapfile to add or modify the interpolation options...

I get that for this to even be possible the BBOX of the request would have to 
be made in the the dataset native CRS.

Thanks

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

[mapserver-users] WCS exclude style from coverage

[Roberto Marzocchi]

Dear all,  I want to create a OWS server to publish raster data. I define CLASS 
and STYLE for WMS service and it works correctly.  It is possible to exclude 
CLASS and STYLE from WCS? Otherwise when I download the coverage I have the RGB 
bands and not the original data.  Thanks in advanced for your help.  R Eng. 
Roberto Marzocchi, PhD
GIS Project Coordinator
Gter srl (Unige spin-off)
Piazza De Marini 3/61 - 16123 Genova
P.IVA/CF 01998770992
ph: 010-8694830 - mob: 349-8786575
E-mail: roberto.marzoc...@gter.it
skype: roberto.marzocchi84
www.gter.it

--
Gter social
www.twitter.com/Gteronline - www.facebook.com/Gteronline - 
https://plus.google.com/+GterIt/posts 
www.linkedin.com/company/gter-srl-innovazione-in-geomatica-gnss-e-gis

-
Please consider the environment before printing this email!___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS default band ?

[Stephan Meißl]

Hi, I don't think that this is possible, neither in MapServer nor in
WCS. I'd recommend to pre-process the files to only contain the needed
bands. cu Stephan


On 06/14/2018 05:12 PM, Rousseau Lambert2, Louis-Philippe (EC) wrote:
> Hi !
> 
> 
> I'm configuring a WCS web services with files that have many bands, like
> 150.
> 
> 
> The layer is only available in WCS and I would like to be able to
> specify a default band to use. I tried the WMS way with the PROCESSING
> "BANDS=1" but if I ask for the layer with a WCS 2.0.1 request, all
> always get all the bands...
> 
> 
> Here is the request I use:
> 
> localhost:8080/mapserv?map=/some/path/wcs.map&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=layer_name&FORMAT=image/tiff&SUBSET=x(-160,-45)&SUBSET=y(25,85)
> 
> 
> the result (from a 3 band layer) is always a 3 bands layer unless I
> specify a band to use in my WCS request. I would like it to only give a
> default band when I don't specify the RANGESUBSET...
> 
> 
> Any idea on how to do, or I am doing something wrong ?
> 
> 
> Thanks guys!
> 
> 
> LP
> 
> 
> Example mapfile:
> 
> 
> MAP
>  NAME "test"
>  PROJECTION
>   "init=epsg:4326"
>  END
>  OUTPUTFORMAT
>   NAME GEOTIFF_16
>   DRIVER "GDAL/GTiff"
>   MIMETYPE "image/tiff"
>   IMAGEMODE FLOAT32
>   EXTENSION "tif"
>  END
>  EXTENT -180 -90 180 90
>  SIZE 500 300
>  WEB
>   METADATA
>     "ows_enable_request" "*"
>     "ows_title" "My Web Services"
>     "wcs_label" "test for cccs"
>   END
>  END
> 
> LAYER
>  NAME "layer_name"
>  STATUS ON
>  TYPE RASTER
>  DUMP TRUE
>  TEMPLATE "ttt.html"
> PROJECTION
>  "init=epsg:4326"
>  "lon_wrap=180"
> END
>  DATA '/data/geomet/afsslor/cccs/cmip5/test.tif'
>  PROCESSING "BANDS=1"
>  METADATA
>   "ows_title" "test"
>   "ows_include_items" "all"
>   "wms_enable_request" "!*"
>   "wcs_enable_request" "*"
>   "wcs_label" "test for cccs"
>   "wcs_size" "360 180"
>   "wcs_extent" "-180 -90 180 90"
>   "wcs_imagemode" "FLOAT32"
>   "wcs_bandcount" "3"
>   "wcs_band_names" "BandA BandB BandC"
>   #default values
>   "wcs_band_interpretation"   "This is default interpretation"
>   "wcs_band_uom"  "DefaultUOM"
>   "wcs_band_definition"   "DefaultDefinition"
>   "wcs_band_description"  "This is default description"
>   "wcs_interval"  "195 310"
>   "wcs_significant_figures"   "3"
>  END
>     END
> END
> 
> 
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 




signature.asc
Description: OpenPGP digital signature
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS default band ?

[Rousseau Lambert2, Louis-Philippe (EC)]

Hi !


I'm configuring a WCS web services with files that have many bands, like 150.


The layer is only available in WCS and I would like to be able to specify a 
default band to use. I tried the WMS way with the PROCESSING "BANDS=1" but if I 
ask for the layer with a WCS 2.0.1 request, all always get all the bands...


Here is the request I use:

localhost:8080/mapserv?map=/some/path/wcs.map&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=layer_name&FORMAT=image/tiff&SUBSET=x(-160,-45)&SUBSET=y(25,85)


the result (from a 3 band layer) is always a 3 bands layer unless I specify a 
band to use in my WCS request. I would like it to only give a default band when 
I don't specify the RANGESUBSET...


Any idea on how to do, or I am doing something wrong ?


Thanks guys!


LP


Example mapfile:

MAP
 NAME "test"
 PROJECTION
  "init=epsg:4326"
 END
 OUTPUTFORMAT
  NAME GEOTIFF_16
  DRIVER "GDAL/GTiff"
  MIMETYPE "image/tiff"
  IMAGEMODE FLOAT32
  EXTENSION "tif"
 END
 EXTENT -180 -90 180 90
 SIZE 500 300
 WEB
  METADATA
"ows_enable_request" "*"
"ows_title" "My Web Services"
"wcs_label" "test for cccs"
  END
 END

LAYER
 NAME "layer_name"
 STATUS ON
 TYPE RASTER
 DUMP TRUE
 TEMPLATE "ttt.html"
PROJECTION
 "init=epsg:4326"
 "lon_wrap=180"
END
 DATA '/data/geomet/afsslor/cccs/cmip5/test.tif'
 PROCESSING "BANDS=1"
 METADATA
  "ows_title" "test"
  "ows_include_items" "all"
  "wms_enable_request" "!*"
  "wcs_enable_request" "*"
  "wcs_label" "test for cccs"
  "wcs_size" "360 180"
  "wcs_extent" "-180 -90 180 90"
  "wcs_imagemode" "FLOAT32"
  "wcs_bandcount" "3"
  "wcs_band_names" "BandA BandB BandC"
  #default values
  "wcs_band_interpretation"   "This is default interpretation"
  "wcs_band_uom"  "DefaultUOM"
  "wcs_band_definition"   "DefaultDefinition"
  "wcs_band_description"  "This is default description"
  "wcs_interval"  "195 310"
  "wcs_significant_figures"   "3"
 END
END
END

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

Re: [mapserver-users] WCS 2.0.1 and output with RangeSubset

[Rahkonen Jukka (MML)]

Hi,

Issue filed https://github.com/mapserver/mapserver/issues/5415

-Jukka Rahkonen-

Stephan Meißl wrote:
Re: [mapserver-users] WCS 2.0.1 and output with RangeSubset

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Jukka,

there should be only one band in the response when you ask for one band.
I think this qualifies for a bug report. Thanks.

cu
Stephan


On 03/09/2017 03:36 PM, Rahkonen Jukka (MML) wrote:
> Hi,
> 
>  
> 
> I have been experimenting with WCS 2.0.1 and orthoimages. When I selec
t
> only one band by including &RangeSubset=BandA into the GetCoverage 
> request I get a greyscale geotiff as output as I expect. However, the 
> output is actually a 3-band tiff with BandA copied to all three bands.

> Is this how it is planned to be or something worth a bug report / 
> feature request?
> 
>  
> 
> -Jukka Rahkonen-
> 
> 
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYwoUbAAoJEKNQXeNWi+qtXLcQAMoRX8I5E+1xg+NLuE6yOgjF
SGE7b0KWr3xh7Emt2Mnp4VRqjG6E9cd1kIm3ua6eiY2MxXAmbCQkfuC0j+oERnyK
cD3O9YuxFSZABGZ0suZiQfsMrk5fNNMy4u5k2jMZQDVIELwTwH6Cg8kUkAwzFvB2
VCTUh/3vS8++90L2JZ1Suby9/P5JCVMK2HOygZpRlhF6WEuteXQWmiVbkqju5unF
4Bwzax/mEYTVkQOW3Z97chIkfqUyi9d9bWv4rNJ4mdGPPmuN4Zov25TxkQz9re4P
H+pm2GfJCeU38svxpfmnV7cZJKXYF16shW8TkhHLAktaWnOIOYObSDNnLzfAzkgv
H6P1sgvxe0IxokfFjoZwL5xGleIEuxyOD+H3+hXsgoAoAV4dhJEkvEwzotsA+SCV
QKw9ugRmdLAzkcK5P2wvm860Q2w60Ti27nM74WNbu85yEFS28jn3GONMqF+BHYfB
3EerTSDPf/gemUSExSmQ97lkfLZpMr16gMVltowgt8Sgrw5BxHf03KWz7ftxo0yh
wuHXUVXXznqIhDjSgxghg4vBBHArnxzrdII7P9qz+F/Wf79jWh7XlRZMv35dl1dt
jvC40BTuixVeMheGRRoZGBvwj1CGMeUT256LjMSmQ6a5ODS2Zp90DamQK1qW66g6
ahxYAu2WKi2HZT9zg5MU
=9fWV
-END PGP SIGNATURE-
___
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] WCS 2.0.1 and output with RangeSubset

[Stephan Meißl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Jukka,

there should be only one band in the response when you ask for one band.
I think this qualifies for a bug report. Thanks.

cu
Stephan


On 03/09/2017 03:36 PM, Rahkonen Jukka (MML) wrote:
> Hi,
> 
>  
> 
> I have been experimenting with WCS 2.0.1 and orthoimages. When I selec
t
> only one band by including &RangeSubset=BandA into the GetCoverage
> request I get a greyscale geotiff as output as I expect. However, the
> output is actually a 3-band tiff with BandA copied to all three bands.

> Is this how it is planned to be or something worth a bug report /
> feature request?
> 
>  
> 
> -Jukka Rahkonen-
> 
> 
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYwoUbAAoJEKNQXeNWi+qtXLcQAMoRX8I5E+1xg+NLuE6yOgjF
SGE7b0KWr3xh7Emt2Mnp4VRqjG6E9cd1kIm3ua6eiY2MxXAmbCQkfuC0j+oERnyK
cD3O9YuxFSZABGZ0suZiQfsMrk5fNNMy4u5k2jMZQDVIELwTwH6Cg8kUkAwzFvB2
VCTUh/3vS8++90L2JZ1Suby9/P5JCVMK2HOygZpRlhF6WEuteXQWmiVbkqju5unF
4Bwzax/mEYTVkQOW3Z97chIkfqUyi9d9bWv4rNJ4mdGPPmuN4Zov25TxkQz9re4P
H+pm2GfJCeU38svxpfmnV7cZJKXYF16shW8TkhHLAktaWnOIOYObSDNnLzfAzkgv
H6P1sgvxe0IxokfFjoZwL5xGleIEuxyOD+H3+hXsgoAoAV4dhJEkvEwzotsA+SCV
QKw9ugRmdLAzkcK5P2wvm860Q2w60Ti27nM74WNbu85yEFS28jn3GONMqF+BHYfB
3EerTSDPf/gemUSExSmQ97lkfLZpMr16gMVltowgt8Sgrw5BxHf03KWz7ftxo0yh
wuHXUVXXznqIhDjSgxghg4vBBHArnxzrdII7P9qz+F/Wf79jWh7XlRZMv35dl1dt
jvC40BTuixVeMheGRRoZGBvwj1CGMeUT256LjMSmQ6a5ODS2Zp90DamQK1qW66g6
ahxYAu2WKi2HZT9zg5MU
=9fWV
-END PGP SIGNATURE-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS 2.0.1 and output with RangeSubset

[Rahkonen Jukka (MML)]

Hi,

I have been experimenting with WCS 2.0.1 and orthoimages. When I select only 
one band by including &RangeSubset=BandA into the GetCoverage request I get a 
greyscale geotiff as output as I expect. However, the output is actually a 
3-band tiff with BandA copied to all three bands.  Is this how it is planned to 
be or something worth a bug report / feature request?

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

[mapserver-users] WCS layer parameters from data

[Michael Smith]

Is there a way to set the WCS layer level parameters, such as rangeset_name,
from a data column?

Mike


Michael Smith
US Army Corps
Remote Sensing GIS/Center
michael.sm...@usace.army.mil



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

Re: [mapserver-users] WCS with elevation data

[Jeff McKenna]

On 2016-09-03 3:28 PM, Jeff McKenna wrote:

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





When you search the mailing list archives for your own answer and are 
happy to find it :)


-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

Re: [mapserver-users] WCS with elevation data

[Jeff McKenna]

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/


___
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] wcs 1.0.0 bbox problem

[Rahkonen Jukka (Tike)]

Hi,

I wonder where BBOX (-2.5,-2.5,2.5,2.5) comes. If Mapserver is generating it 
automatically then it feels like a bug.

Your request does not contain BBOX at all and it is OK because it has TIME, and 
WCS 1.0.0 standard says  "One of BBOX or TIME is required".  CRS is required 
but because there is no BBOX it should not have any effect on the result. 
Standard says here
"GetCoverage requests must use this parameter to specify the coordinate 
reference system in which the request domain constraints are expressed (BBOX). 
The values of this re-quest parameter must be one of those defined in a 
requestResponseCRSs or requestCRSs element under the requested coverage." Thus 
you are allowed to use any CRS that your service supports and the result should 
be correct and identical. And your CRS list seems to be this:
"wcs_srs" "EPSG:4326 EPSG:900913 EPSG:3857 EPSG:32615 EPSG:32616 EPSG:32617"

Do you get the same error also if you make the request with for example 
&CRC=900913?
I guess that your system is sometimes generating requests with EPSG:4326 BBOX 
and therefore you just that as a compulsory dummy CRS parameter with your bare 
TIME requests and therefore using the native EPSG:32626 is not a good 
workaround.

-Jukka Rahkonen-


Lähettäjä: mapserver-users-boun...@lists.osgeo.org 
[mailto:mapserver-users-boun...@lists.osgeo.org] Puolesta Peter Freimuth
Lähetetty: 29. tammikuuta 2014 9:17
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] wcs 1.0.0 bbox problem


Hi,
executing the following request
https://devcloud.blackbridge.com/wcs/PlenumsoftDemo?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=testdata_raw&FORMAT=GEOTIFF_INT16&RESX=5&RESY=5&RESPONSE_CRS=EPSG:32616&CRS=EPSG:4326&TIME=2012-04-05

results in


xmlns="http://www.opengis.net/ogc"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.opengis.net/ogc 
http://schemas.opengeospatial.net/wcs/1.0.0/OGC-exception.xsd";>
msWCSGetCoverage(): WCS server error. Requested BBOX (-2.5,-2.5,2.5,2.5) is 
outside requested coverage BBOX (210500,2230500,261500,2281500)
msProjectRect(): Projection library error. All points failed to reproject.
msProjectPoint(): Projection library error. proj says: latitude or longitude 
exceeded limits

The corresponding layer d3efinition is:

MAP
...
LAYER
# this is the tileindex that aggregates the single image products together and 
makes them accessible by date and extend
NAME "data_raw_idx"
STATUS ON

DEBUG 5
TYPE POLYGON
DATA 
"/mnt/mapserver/mapserver_wms/Raster/Plenumosft_RE_Sample_forWCS/plenumsoft_demo_data"
PROJECTION
"init=epsg:32616"
END
VALIDATION
# 'productid' '^([0-9])$'
END
#FILTER ( '[productid]'='%productid%')
METADATA
#'productid_validation_pattern' '^([0-9])$'
#'default_productid' '1234567'
#disable explicitly everything that shall not be supported for this Layer
"wms_enable_request" "!GetCapabilities !GetMap !GetLegendgraphic"
"wcs_enable_request" "!GetCapabilities !GetCoverage !DescribeCoverage"
"wfs_enable_request" "!GetCapabilities !GetFeature !DescribeFeatureType"
END
END
LAYER
# this layer serves the 16bit raw data
NAME "testdata_raw"
STATUS ON

DUMP TRUE
DEBUG 5
TYPE RASTER ### required
PROJECTION
"init=epsg:32616"
END
OFFSITE 0 0 0
UNITS meters
TILEINDEX "data_raw_idx"
TILEITEM "location"
#MASK "mask2"
METADATA
"wcs_title" "5 band 16bit RE Testdata with time support"
"wcs_extent" "210500.0 2230500.0 261500.0 2281500.0" # shall be set dynamically 
by the wrapper script on mapObj base
"wcs_srs" "EPSG:4326 EPSG:900913 EPSG:3857 EPSG:32615 EPSG:32616 EPSG:32617"
"wcs_label" "5 band 16bit RE Testdata" ### required
"wcs_rangeset_axes" "bands"
"wcs_rangeset_name" "Bands" ### required to support DescribeCoverage request
"wcs_rangeset_label" "RE Radiometric Bands" ### required to support 
DescribeCoverage request
"wcs_rangeset_nullvalue" "0"

#"wcs_size" "15000 15000" #if we have a global ows_extent set in web-metadata 
and a wcs_resolution this gets calculated by mapserver
"wcs_resolution" "5.0 5.0"
"wcs_bandcount" "5"
"wcs_band_names" "Blue Green Red Rededge Nir"
"wcs_imagemode" "INT16"
"wcs_formats" "GEOTIFF_INT16 AAIGRID"
"wcs_native_format" "image/tiff"
"wcs_nativeformat" "GTiff"
"wcs_enable_request" "*"
"wcs_timeposition" "2011-01-04,2011-04-20,2012-04-05" 

[mapserver-users] wcs 1.0.0 bbox problem

[Peter Freimuth]

Hi,
executing the following request
https://devcloud.blackbridge.com/wcs/PlenumsoftDemo?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=testdata_raw&FORMAT=GEOTIFF_INT16&RESX=5&RESY=5&RESPONSE_CRS=EPSG:32616&CRS=EPSG:4326&TIME=2012-04-05

results in


xmlns="http://www.opengis.net/ogc"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.opengis.net/ogc 
http://schemas.opengeospatial.net/wcs/1.0.0/OGC-exception.xsd";>
msWCSGetCoverage(): WCS server error. Requested BBOX (-2.5,-2.5,2.5,2.5) is 
outside requested coverage BBOX (210500,2230500,261500,2281500)
msProjectRect(): Projection library error. All points failed to reproject.
msProjectPoint(): Projection library error. proj says: latitude or longitude 
exceeded limits

The corresponding layer d3efinition is:

MAP
...
LAYER
# this is the tileindex that aggregates the single image products together and 
makes them accessible by date and extend
NAME "data_raw_idx"
STATUS ON

DEBUG 5
TYPE POLYGON
DATA 
"/mnt/mapserver/mapserver_wms/Raster/Plenumosft_RE_Sample_forWCS/plenumsoft_demo_data"
PROJECTION
"init=epsg:32616"
END
VALIDATION
# 'productid' '^([0-9])$'
END
#FILTER ( '[productid]'='%productid%')
METADATA
#'productid_validation_pattern' '^([0-9])$'
#'default_productid' '1234567'
#disable explicitly everything that shall not be supported for this Layer
"wms_enable_request" "!GetCapabilities !GetMap !GetLegendgraphic"
"wcs_enable_request" "!GetCapabilities !GetCoverage !DescribeCoverage"
"wfs_enable_request" "!GetCapabilities !GetFeature !DescribeFeatureType"
END
END
LAYER
# this layer serves the 16bit raw data
NAME "testdata_raw"
STATUS ON

DUMP TRUE
DEBUG 5
TYPE RASTER ### required
PROJECTION
"init=epsg:32616"
END
OFFSITE 0 0 0 
UNITS meters
TILEINDEX "data_raw_idx"
TILEITEM "location"
#MASK "mask2"
METADATA
"wcs_title" "5 band 16bit RE Testdata with time support"
"wcs_extent" "210500.0 2230500.0 261500.0 2281500.0" # shall be set dynamically 
by the wrapper script on mapObj base
"wcs_srs" "EPSG:4326 EPSG:900913 EPSG:3857 EPSG:32615 EPSG:32616 EPSG:32617"
"wcs_label" "5 band 16bit RE Testdata" ### required
"wcs_rangeset_axes" "bands"
"wcs_rangeset_name" "Bands" ### required to support DescribeCoverage request
"wcs_rangeset_label" "RE Radiometric Bands" ### required to support 
DescribeCoverage request
"wcs_rangeset_nullvalue" "0"

#"wcs_size" "15000 15000" #if we have a global ows_extent set in web-metadata 
and a wcs_resolution this gets calculated by mapserver
"wcs_resolution" "5.0 5.0"
"wcs_bandcount" "5"
"wcs_band_names" "Blue Green Red Rededge Nir"
"wcs_imagemode" "INT16"
"wcs_formats" "GEOTIFF_INT16 AAIGRID"
"wcs_native_format" "image/tiff"
"wcs_nativeformat" "GTiff"
"wcs_enable_request" "*"
"wcs_timeposition" "2011-01-04,2011-04-20,2012-04-05" #this might get set by 
the mapscript wrapper accodingly to the dates avaialable for the service and is 
mandatory to allow temporal subsettings
"wcs_timeextent" "2011-01-04/2012-04-05" # shall be set dynamically by the 
wrapper script on mapObj base
"wcs_timeitem" "acquidate"
#disable explicitly everything that shall not be supported for this Layer
"wms_enable_request" "!GetCapabilities !GetMap !GetLegendgraphic"
"wfs_enable_request" "!GetCapabilities !GetFeature !DescribeFeatureType"
END
CLASS
NAME "5 Band (16bit) RE Imagedata"
KEYIMAGE "drgs_keyimage.png"
END
END
...
END

If i use CRS=EPSG:32616 which is the epsg code of the layer itself, everything 
works fine. I would expect that mapserver would reproject the wcs_extent or 
layer_extent or map_extent to the given CRS and use that BBOX by default.

related to:
https://github.com/mapserver/mapserver/issues/4853

-- 
Peter Freimuth 

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

Re: [mapserver-users] wcs 1..0.0 getcapabilities problem in mapserver 6.4dev and 6.2.x

[Peter Freimuth]

Hi Even,
thanks for the tip. Actually this solved the problem. I did not found an 
example which makes clear for what this metadata element is used and how 
this url should look like but at least the warning from the capabilities 
doc is gone.

Best regards,
Peter
On 29/08/2013 1:38 PM, Even Rouault wrote:

Le jeudi 29 août 2013 18:56:48, Peter Freimuth a écrit :

Hi,
i ran into s small problem with setting up a WCS service on umn
mapserver 6.2 and newer.
When requesting the capabilities for VERSION=1.0.0 i get the following
Warning printed to the Capabilities Doc:

Any idea what is missing. The fact that the missing mandatory metadata
accesses a "null" string point to a bug in the code otherwise it should
tell which parameter is missing.

Yes, the call to msOWSPrintURLType() in msWCSGetCapabilities_Service in
mapwcs.c pass tag_name == NULL, hence the (null) in the warning. Looking at
the conditions that trigger the warning, I believe the reason for the warning
is that you need to define the "ows_metadatalink_href" metadata item.


Thanks for any hint on this topic.
Kind regards,
Peter


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

Re: [mapserver-users] wcs 1..0.0 getcapabilities problem in mapserver 6.4dev and 6.2.x

[Even Rouault]

Le jeudi 29 août 2013 18:56:48, Peter Freimuth a écrit :
> Hi,
> i ran into s small problem with setting up a WCS service on umn
> mapserver 6.2 and newer.
> When requesting the capabilities for VERSION=1.0.0 i get the following
> Warning printed to the Capabilities Doc:
> 

> Any idea what is missing. The fact that the missing mandatory metadata
> accesses a "null" string point to a bug in the code otherwise it should
> tell which parameter is missing.

Yes, the call to msOWSPrintURLType() in msWCSGetCapabilities_Service in 
mapwcs.c pass tag_name == NULL, hence the (null) in the warning. Looking at 
the conditions that trigger the warning, I believe the reason for the warning 
is that you need to define the "ows_metadatalink_href" metadata item.

> 
> Thanks for any hint on this topic.
> Kind regards,
> Peter

-- 
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] wcs 1..0.0 getcapabilities problem in mapserver 6.4dev and 6.2.x

[Peter Freimuth]

Hi,
i ran into s small problem with setting up a WCS service on umn 
mapserver 6.2 and newer.
When requesting the capabilities for VERSION=1.0.0 i get the following 
Warning printed to the Capabilities Doc:



http://www.opengis.net/wcs";
   xmlns:xlink="http://www.w3.org/1999/xlink";
   xmlns:gml="http://www.opengis.net/gml";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://www.opengis.net/wcs 
http://schemas.opengeospatial.net/wcs/1.0.0/wcsCapabilities.xsd";>


  This service serves RE L3A image products with different acquisition dates and 
supports filtering by using the OGC'time'  parameter and 
the'imageidentifier'  parameter to address single images.
  MapServer WCS
  RE 5Band LI_USA-MT OWS Servis
  
wcs
  wms
  wfs
  living image
  

...

In all other Version like 1.1.x or 2.0.0 everything is fine and i also have no 
problem with WMS or WFS capabilities.

this is the WEB section of the corresponding mapfile:
WEB
IMAGEPATH "//image_path"
METADATA
"ows_title"   "RE 5 Band Imagedata Service"
#"ows_onlineresource"  
"http://devcloud.blackbridge.com/ows/LI_USA-MT.cgi?"; ### recommended
"ows_onlineresource"  "http://***/LI_USA-MT.cgi?"; ### recommended
"ows_description" "This service serves images registered in the OWS 
streaming platform"
"ows_abstract" "This service serves images registered in the OWS 
streaming platform"
"ows_srs" "EPSG:4326 EPSG:900913 EPSG:3857 EPSG:32662"
#necessary to get the WCS virtual dataset metadata thing working
"ows_extent" "-116.364631680367 44.1932837062986 
-103.698350095065 49.1892799088128"
"ows_schemas_location" "http://schemas.opengeospatial.net";
"ows_fees""none"
"ows_accessconstraints""none"
"ows_keywordlist"  "wcs, wms, wfs, living image"
"ows_metadatalink_type""TC211"
"ows_metadatalink_format"  "text/plain"
"ows_addresstype"  "postal"
"ows_address"  "fgdfgdgs."
"ows_city" "fdgfgdf"
"ows_stateorprovince"  "dgdfg"
"ows_postcode" "dgdfg"
"ows_country"  "dgdg"
"ows_contactelectronicmailaddress" "***"
"ows_contactperson" "***"
"ows_contactorganization"   "***"
"ows_contactposition"   "ows manager"
"ows_role"  "ows manager"
"ows_contactvoicetelephone" "453453453"
"ows_contactfacsimiletelephone" "345345345"
"ows_contactinstructions" "send us an email"
"ows_service_onlineresource" "http://*/cgi-bin/LI_USA-MT.cgi?";
"ows_hoursofservice" "8-17 MCT"
"ows_http_max_age"   "100"
#"ows_updatesequence" ""

"wcs_enable_request" "GetCapabilities GetCoverage DescribeCoverage"
"wcs_description""This service serves RE L3A image products 
with different acquisition dates and supports filtering by using the OGC 'time' parameter and the 
'imageidentifier' parameter to address single images."
"wcs_abstract""This service serves RE L3A image products 
with different acquisition dates and supports filtering by using the OGC 'time' parameter and the 
'imageidentifier' parameter to address single images."
"wcs_extent" "-116.364631680367 44.1932837062986 
-103.698350095065 49.1892799088128"
"wcs_label""RE 5Band LI_USA-MT OWS Servis" ### required

"wms_enable_request" "GetCapabilities GetMap GetLegendGraphic"
"wms_extent" "-116.364631680367 44.1932837062986 
-103.698350095065 49.1892799088128"
"wms_feature_info_mime_type" "application/json"
"wms_bbox_extended"   "true"

"wfs_enable_request" "GetCapabilities GetFeature 
DescribeFeatureType"
"wfs_extent"  "-116.364631680367 44.1932837062986 
-103.698350095065 49.1892799088128"
"wfs_description"   "This WFS service serves as a catalog service to 
find out which image products are available in the the service for further usage." ## 
Recommended
"wfs_abstract"   "This WFS service serves as a catalog service to 
find out which image products are available in the the service for further usage." ## 
Recommended
"wfs_srs"   "EPSG:4326 EPSG:4269 EPSG:3978 EPSG:3857 EPSG:900913 
EPSG:32662" #output for WFS data for WFS 1.0.0
"wfs_maxfeatures"  "1"
"wfs_namespace_uri" "http://www.rapideye.de/ows/wfs/re";
"wfs_namespace_prefix" "re"
END
VALIDATION
'productid' '[a-zA-Z0-9\-\_\,]+'

[mapserver-users] WCS timeseries data via mapserver

[pcreso]

Does anyone have an example of using mapserver to deliver 1D timeseries data as 
a WCS service?

Is mapserver able to do this?

Is there a generic client that can display such WCS content?

Thanks,

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

Re: [mapserver-users] WCS server, getcoverage request fail

[Rahkonen Jukka]

Hi,

It is set with MAXSIZE at MAP level, for example
MAXSIZE 1

Our server can deliver something like 8000x8000 pixel sized uncompressed 
3-channel geotiffs well but not much bigger.  I have not considered that as a 
big problem (it is already 192 MB for the client to download) and not studied 
if I could adjust the server it to send bigger files.

-Jukka-

Luca Delucchi wrote:
 
> 2012/10/26 Rahkonen Jukka :
> > Hi,
> >
> 
> Hi
> 
> > First thing is that BBOX seems odd but perhaps it is a typo
> > BBOX=2168000,7716750,77,%205447750&
> >
> 
> ops sorry I didn't see it.
> Now it return me an error because the width and height are to big
> 
> [Fri Oct 26 10:42:57 2012].537605 msWCSGetCoverage(): WCS server error.
> Raster size out of range, width and height of resulting coverage must be no
> more than MAXSIZE=2048.
> 
> How can I find the maximum bounding box the the right resolution and the
> MAXSIZE?
> otherwise can I force the MAXSIZE?
> 
> > -Jukka Rahkonen-
> >
> 
> Thanks
> 
> 
> --
> ciao
> Luca
> 
> http://gis.cri.fmach.it/delucchi/
> www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS server, getcoverage request fail

[Luca Delucchi]

2012/10/26 Rahkonen Jukka :
> Hi,
>

Hi

> First thing is that BBOX seems odd but perhaps it is a typo
> BBOX=2168000,7716750,77,%205447750&
>

ops sorry I didn't see it.
Now it return me an error because the width and height are to big

[Fri Oct 26 10:42:57 2012].537605 msWCSGetCoverage(): WCS server
error. Raster size out of range, width and height of resulting
coverage must be no more than MAXSIZE=2048.

How can I find the maximum bounding box the the right resolution and
the MAXSIZE?
otherwise can I force the MAXSIZE?

> -Jukka Rahkonen-
>

Thanks


-- 
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS server, getcoverage request fail

[Rahkonen Jukka]

Hi,

First thing is that BBOX seems odd but perhaps it is a typo
BBOX=2168000,7716750,77,%205447750&

-Jukka Rahkonen-

Luca Delucchi wrote:
> 
> Hi everybody,
> I'm testing WCS server with MapServer 6.0 compiled from svn in a Debian
> system.
> GetCapabilities and DescribeCoverage works fine; GetCoverage instead as
> some problems when I try to use RESX and RESY, I obtain this "Premature
> end of script headers: mapserv" i error.log of Apache.
> My request is like this
> 
> http://localhost/cgi-
> bin/mapserv?map=/var/www/wcs_test/wcs_test.map&SERVICE=WCS&VER
> SION=1.0.0&REQUEST=GetCoverage&COVERAGE=MODIS_LST_2002_08&CR
> S=EPSG:3035&BBOX=2168000,7716750,77,%205447750&RESX=250&RESY
> =250&FORMAT=GTiff
> 
> Someone can help me?
> 
> --
> ciao
> Luca
> 
> http://gis.cri.fmach.it/delucchi/
> www.lucadelu.org
> ___
> 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

[mapserver-users] WCS server, getcoverage request fail

[Luca Delucchi]

Hi everybody,
I'm testing WCS server with MapServer 6.0 compiled from svn in a Debian system.
GetCapabilities and DescribeCoverage works fine; GetCoverage instead
as some problems when I try to use RESX and RESY, I obtain this
"Premature end of script headers: mapserv" i error.log of Apache.
My request is like this

http://localhost/cgi-bin/mapserv?map=/var/www/wcs_test/wcs_test.map&SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=MODIS_LST_2002_08&CRS=EPSG:3035&BBOX=2168000,7716750,77,%205447750&RESX=250&RESY=250&FORMAT=GTiff

Someone can help me?

-- 
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS Geotiff output issue

[thomas bonfort]

Hi Guillaume,
The environment shouldn't be an issue here, you can test on whichever
is easiest for you. Using branch-6-2 is the way to go, but I can't
guarantee there won't be any other bugs getting in your way.

thanks,
thomas

On Mon, Aug 20, 2012 at 6:44 PM, Guillaume Loiselle
 wrote:
> Hi Thomas,
>
> I do not work at the same place anymore and won't be able to test on the
> same environment at all. I was on Windows XP; the closest I have now is
> Vista x64. Would a test on this system still be worth anything to you? I
> never compiled MapServer either. Can it be done on a 64-bits Windows? Should
> I use the current dev 6.2 branch (with your fix, of course) or are other
> bugs gonna get in my way?
>
> This should be an interesting adventure.
>
> Yours sincerely,
> Guillaume
>
>
>
>
> 2012/8/20 thomas bonfort 
>>
>> Guillaume,
>> I have added a fix that I believe would resolve your issue, at
>> https://github.com/mapserver/mapserver/pull/4079 . Attached is the
>> generated output with the patch applied.
>>
>> Can you please confirm on the issue tracker that this fixes your
>> issues, and I will then make sure this gets applied in 6.2 and
>> backported to 6.0.4
>>
>> regards,
>> thomas
>>
>> On Mon, Nov 7, 2011 at 10:06 PM, Guillaume Loiselle
>>  wrote:
>> > Hi,
>> >
>> > Both mapfile and datasource are available in the first email I sent.
>> >
>> >
>> > http://lists.osgeo.org/pipermail/mapserver-users/2011-November/070670.html
>> >
>> > Filenames appear to be a little bit messed up but the data itself is
>> > fine. I
>> > don't know why it went so wrong.
>> >
>> > Mapfile :
>> >
>> > http://lists.osgeo.org/pipermail/mapserver-users/attachments/2004/78e5fa24/2011102811-0001.obj
>> >
>> > Data (HDF5 format) :
>> >
>> > http://lists.osgeo.org/pipermail/mapserver-users/attachments/2004/78e5fa24/data-0001.obj
>> >
>> > I intend to stick with 1.0.0 indeed. At least until it works... I will
>> > look
>> > up 1.1.0's details in due time.
>> >
>> >
>> >
>> >
>> >
>> > 2011/11/7 Rahkonen Jukka 
>> >>
>> >> Pity that is was not just version mismatch.  Could it be possible to
>> >> see
>> >> your mapfile and info about the datasource?
>> >> Stay with version 1.0.0 while testing. With version 1.1.0 you must give
>> >> EPSG:4326 coordinates in Northing-Easting order which can make things
>> >> more
>> >> complicated.
>> >>
>> >> -Jukka Rahkonen-
>> >> 
>> >> Guillaume Loiselle wrote:
>> >>
>> >> Hi,
>> >>
>> >> I'm afraid it isn't. I didn't notice the request version I sent was a
>> >> "mixed" one but I tried Coverage on 1.0.0 and Identifier on 1.1.0 as
>> >> well
>> >> and the result was basically the same.
>> >> Here is the 1.1.0 version of the error :
>> >>
>> >>
>> >> 
>> >> > >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> >> xmlns:ows="http://www.opengis.net/ows/1.1"; version="1.1.0"
>> >> xml:lang="en-US"
>> >> xsi:schemaLocation="http://www.opengis.net/ows/1.1
>> >> http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd";>
>> >>  
>> >>
>> >> msWCSGetCoverage(): WCS server error. Requested BBOX
>> >> (-178.804111261525,2802.84894277903,179.578125552223,2907.18853507175)
>> >> is
>> >> outside requested coverage BBOX (-70,45,-55,52)
>> >>  
>> >> 
>> >>
>> >>
>> >> I of course spent a lot of time on the WCS server documentation page. I
>> >> saw no reference to such a problem, though. My request,
>> >>
>> >> http://localhost/cgi-bin/mapserv.exe?
>> >> map=D:/Guillaume/ProjetCourantsGlaces/WCSproblem/2011102811.map&
>> >> SERVICE=WCS&
>> >> VERSION=1.0.0&
>> >> REQUEST=GetCoverage&
>> >> COVERAGE=thelayer&
>> >> CRS=EPSG:4326&
>> >> BBOX=-67.5,48.922499263758255,-64.6875,50.736455137010665&
>> >> WIDTH=256&
>> >> HEIGHT=256&
>> >> FORMAT=GTiff
>> >>
>> >> is formatted the same way the example is :
>> >>
>> >> http://my.host.com/cgi-bin/mapserv?
>> >> map=mywcs.map&
>> >> SERVICE=wcs&
>> >> VERSION=1.0.0&
>> >> REQUEST=GetCoverage&
>> >> coverage=bathymetry&
>> >> CRS=EPSG:42304&
>> >> BBOX=-220,-712631,3072800,384&
>> >> WIDTH=3199&
>> >> HEIGHT=2833&
>> >> FORMAT=GTiff
>> >>
>> >>
>> >> My mapfile contains every required attribute.
>> >>
>> >> Thank you.
>> >> Guillaume Loiselle
>> >>
>> >>
>> >> 2011/11/7 Rahkonen Jukka
>> >> mailto:jukka.rahko...@mmmtike.fi>>
>> >> Hi,
>> >>
>> >> See examples in http://www.mapserver.org/ogc/wcs_server.html and try to
>> >> avoid mixing versions 1.0.0 and 1.1.0. Let's hope using "coverage"
>> >> instead
>> >> of "identifier" will be enough.
>> >>
>> >> -Jukka Rahkonen-
>> >> 
>> >> Lähettäjä:
>> >>
>> >> mapserver-users-boun...@lists.osgeo.org
>> >>
>> >> [mapserver-users-boun...@lists.osgeo.org]
>> >> käyttäjän Guillaume Loiselle
>> >> [loiselle.guilla...@gmail.com]
>> >> puolesta
>> >> Lähetetty: 7. marraskuuta 2011 21:21
>> >> Vastaanottaja:

[mapserver-users] WCS 1.1 TimeSequence

[Radim Blazek]

Hi,
it seems that WCS 1.1 (mapserver 6.0.3) completely ignores
TemporalDomain. Some code (copy-pasted from 1.0) is commented in
msWCSDescribeCoverage_CoverageDescription11() and GetCoverage
TimeSequence param is not supported at all. If a coverage is defined
with timeposition in mapfile, the result of GetCoverage is empty
raster (all values 0). Anybody was able to get WCS 1.1 with
timeposition working?

Unfortunately 3 of 4 coverages on
http://demo.mapserver.org/cgi-bin/wcs are using timeposition and those
coverages do not work with WCS 1.1.

I am working on WCS client in QGIS, it supports WCS 1.0 and 1.1 and
prefers 1.1. One of the most obvious first tests - demo.mapserver.org
fails. Would not it be better to set demo.mapserver.org to default in
1.0 if one of features configured in mapfile is not fully supported by
1.1?

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

Re: [mapserver-users] WCS server not

[Stephan Meißl]

On Tue, 2012-02-21 at 13:11 +0100, Jorge Lopez wrote:
> Hello; 
> 
> I am newbie to Mapserver, so maybe this is a naive question but I am
> doing my best to find a solution to serve raster data by using
> Mapserver.
> 
> I have MapServer 5.6.5, I have prepared my map server with WFS and WMS
> and I would like to serve GEOTIFF images with WCS 1.0.0 protocol.
> 
> I prepared a map file, with two layers to be served and I made a
> capabilities of the server:
> 
> http://domainserver/cgi-bin/mapserv?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCapabilities
> 
> The problem is that all metadata is full but there is no content for
> coverages ("identifiers" in v.1.1.0), that is, the content between
> ContentMetada labels is empty, 
> 
> 
> 
> 
> So I don't know what is happen, I made a probe like using shp2img to
> generate a image png from mapfile and it is done
> 
> My Mapfile (only one layer) looks like in the following way: 
> 
> 
> MAP
> 
>   NAME " Map Server"
>   SIZE  100 100   # NECESARIO PARA LA UTILIDAD shp2img 
>   UNITS DD
>   EXTENT -90 -90 90 90
>   DEBUG 5
>   CONFIG "CPL_DEBUG" "ON"
>   CONFIG "MS_ERRORFILE" "/tmp/mapserver.log" #a este fichero van
> mensajes de error!! (equivalent to set SetEnv MS_ERRORFILE
> "/tmp/mapserver.log" in /etc/apache2/apache2.conf)
>   PROJECTION
>"init=epsg:4326"
>END # end projection
> # Background color for the map canvas -- change as desired
>   IMAGECOLOR 192 192 192
>   IMAGEQUALITY 95
>   IMAGETYPE jpeg
> 
>   # Usamos el driver GDAL para crear el formato Ráster en modo IMAGEN
> RGB 
>   OUTPUTFORMAT
>NAME GEOTIFF_RGB
>DRIVER "GDAL/GTiff"
>MIMETYPE "image/tiff"
>IMAGEMODE RGB
>EXTENSION 'tif'
>   END   #end outputformat
>  
>   # Legend
>   LEGEND
>   IMAGECOLOR 255 255 255
>   STATUS ON
>   KEYSIZE 18 12
>LABEL
>   TYPE BITMAP
>   SIZE MEDIUM
>   COLOR 0 0 89
> END #end label
>   END #end legend
> 
>   
>   # Web interface definition. Only the template parameter is required
> to display a map. See MapServer documentation
>   WEB
>   
> # Set IMAGEPATH to the path where MapServer should write its
> output.
> IMAGEPATH '/tmp/'
> # Set IMAGEURL to the url that points to IMAGEPATH as defined in
> your web server configuration
> IMAGEURL '/tmp/'
> 
> # WCS server settings
> METADATA
>   'wms_title'' Map Server'
>   'wms_enable_request'   '*'
>   'ows_onlineresource'   'http://domainserver/cgi-bin/mapserv?'
>   #'ows_srs' 'CRS:84 EPSG:4326
> urn:x-ogc:def:crs:EPSG:4326 urn:x-ogc:def:crs:EPSG:3035 EPSG:3035
> EPSG:4258'
>   'ows title''Intamap WCS'
>   'ows_srs'  'CRS:84 EPSG:4326
> urn:x-ogc:def:crs:EPSG:4326'
>   'ows_abstract' 'Comentarios Blah Blah Blah'
>   #'ows_srs' 'EPSG:3035 urn:x-ogc:def:crs:EPSG:3035'
>   'wfs_title'' WFS Server'
>   'wfs_onlineresource'   'http://domainserver/cgi-bin/wfs?'
>   'wfs_srs'  'EPSG:4326' ## Recommended
>   'wfs_abstract' 'Web Feature Service for the  central
> geonode.' ## Recommended
>   'wfs_enable_request'   '*'
>   'wms_abstract' 'Web Map Service for the  central
> geonode'
> ## WCS  
>   'wcs_label'  ' WCS Server' ### required for WCS
>   'wcs_title'  'XXX  Web Coverage Service Server'
>   'wcs_description''Web Coverage Service for the 
> central geonode to serve coverages'
>   'wcs_onlineresource' 'http://domainserver/cgi-bin/wcs?'
>   'wcs_service_onlineresource' 'http://domainserver/cgi-bin/wcs?'
>   'wcs_fees'   'none'
>   'wcs_srs''EPSG:4326' ## Recommended
> # 'wcs_abstract'   'Web Coverage Service for the XX
> central geonode.' ## Recommended
>   'wcs_accessconstraints'  'none'
>   'wcs_keywordlist''WCS, TEXT, Coverage'
>   'wcs_metadatalink_format'  "text/plain" #tipo MIME para formato
> de ficheros 
>   'wcs_metadatalink_href'"http://domainserver/catalog";  # URL
> al metadata
>   'wcs_metadatalink_type'"TC211"   # standard que cumple el
> metadata
>   "wcs_address"  "124 Gilmour Street"
>   "wcs_city" "Ottawa"
>   "wcs_stateorprovince"  "ON"
>   "wcs_postcode" "90210"
>   "wcs_country"  "Canada"
>   "wcs_contactelectronicmailaddress" "blah@blah"
>   "wcs_contactperson""me"
>   "wcs_contactorganization"  "unemployed"
>   "wcs_contactposition"  "manager"
>   "wcs_contactvoicetelephone""613-555-1234"
>   "wcs_contactfacimiletelephone" "613-555-1235"
> #  "wcs_service_onlineresource"
> "http://domainserver/cgi-bin/wcs?";
>   'wcs_enable_request'   '*'
> END #end metadata
> 
> #Scale range at which web interface will operate
> # Template and heade

Re: [mapserver-users] WCS server not

[Stephan Meißl]

On Tue, 2012-02-21 at 13:11 +0100, Jorge Lopez wrote:
> Hello; 
> 
> I am newbie to Mapserver, so maybe this is a naive question but I am
> doing my best to find a solution to serve raster data by using
> Mapserver.
> 
> I have MapServer 5.6.5, I have prepared my map server with WFS and WMS
> and I would like to serve GEOTIFF images with WCS 1.0.0 protocol.
> 
> I prepared a map file, with two layers to be served and I made a
> capabilities of the server:
> 
> http://domainserver/cgi-bin/mapserv?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCapabilities
> 
> The problem is that all metadata is full but there is no content for
> coverages ("identifiers" in v.1.1.0), that is, the content between
> ContentMetada labels is empty, 
> 
> 
> 
> 
> So I don't know what is happen, I made a probe like using shp2img to
> generate a image png from mapfile and it is done
> 
> My Mapfile (only one layer) looks like in the following way: 
> 
> 
> MAP
> 
>   NAME " Map Server"
>   SIZE  100 100   # NECESARIO PARA LA UTILIDAD shp2img 
>   UNITS DD
>   EXTENT -90 -90 90 90
>   DEBUG 5
>   CONFIG "CPL_DEBUG" "ON"
>   CONFIG "MS_ERRORFILE" "/tmp/mapserver.log" #a este fichero van
> mensajes de error!! (equivalent to set SetEnv MS_ERRORFILE
> "/tmp/mapserver.log" in /etc/apache2/apache2.conf)
>   PROJECTION
>"init=epsg:4326"
>END # end projection
> # Background color for the map canvas -- change as desired
>   IMAGECOLOR 192 192 192
>   IMAGEQUALITY 95
>   IMAGETYPE jpeg
> 
>   # Usamos el driver GDAL para crear el formato Ráster en modo IMAGEN
> RGB 
>   OUTPUTFORMAT
>NAME GEOTIFF_RGB
>DRIVER "GDAL/GTiff"
>MIMETYPE "image/tiff"
>IMAGEMODE RGB
>EXTENSION 'tif'
>   END   #end outputformat
>  
>   # Legend
>   LEGEND
>   IMAGECOLOR 255 255 255
>   STATUS ON
>   KEYSIZE 18 12
>LABEL
>   TYPE BITMAP
>   SIZE MEDIUM
>   COLOR 0 0 89
> END #end label
>   END #end legend
> 
>   
>   # Web interface definition. Only the template parameter is required
> to display a map. See MapServer documentation
>   WEB
>   
> # Set IMAGEPATH to the path where MapServer should write its
> output.
> IMAGEPATH '/tmp/'
> # Set IMAGEURL to the url that points to IMAGEPATH as defined in
> your web server configuration
> IMAGEURL '/tmp/'
> 
> # WCS server settings
> METADATA
>   'wms_title'' Map Server'
>   'wms_enable_request'   '*'
>   'ows_onlineresource'   'http://domainserver/cgi-bin/mapserv?'
>   #'ows_srs' 'CRS:84 EPSG:4326
> urn:x-ogc:def:crs:EPSG:4326 urn:x-ogc:def:crs:EPSG:3035 EPSG:3035
> EPSG:4258'
>   'ows title''Intamap WCS'
>   'ows_srs'  'CRS:84 EPSG:4326
> urn:x-ogc:def:crs:EPSG:4326'
>   'ows_abstract' 'Comentarios Blah Blah Blah'
>   #'ows_srs' 'EPSG:3035 urn:x-ogc:def:crs:EPSG:3035'
>   'wfs_title'' WFS Server'
>   'wfs_onlineresource'   'http://domainserver/cgi-bin/wfs?'
>   'wfs_srs'  'EPSG:4326' ## Recommended
>   'wfs_abstract' 'Web Feature Service for the  central
> geonode.' ## Recommended
>   'wfs_enable_request'   '*'
>   'wms_abstract' 'Web Map Service for the  central
> geonode'
> ## WCS  
>   'wcs_label'  ' WCS Server' ### required for WCS
>   'wcs_title'  'XXX  Web Coverage Service Server'
>   'wcs_description''Web Coverage Service for the 
> central geonode to serve coverages'
>   'wcs_onlineresource' 'http://domainserver/cgi-bin/wcs?'
>   'wcs_service_onlineresource' 'http://domainserver/cgi-bin/wcs?'
>   'wcs_fees'   'none'
>   'wcs_srs''EPSG:4326' ## Recommended
> # 'wcs_abstract'   'Web Coverage Service for the XX
> central geonode.' ## Recommended
>   'wcs_accessconstraints'  'none'
>   'wcs_keywordlist''WCS, TEXT, Coverage'
>   'wcs_metadatalink_format'  "text/plain" #tipo MIME para formato
> de ficheros 
>   'wcs_metadatalink_href'"http://domainserver/catalog";  # URL
> al metadata
>   'wcs_metadatalink_type'"TC211"   # standard que cumple el
> metadata
>   "wcs_address"  "124 Gilmour Street"
>   "wcs_city" "Ottawa"
>   "wcs_stateorprovince"  "ON"
>   "wcs_postcode" "90210"
>   "wcs_country"  "Canada"
>   "wcs_contactelectronicmailaddress" "blah@blah"
>   "wcs_contactperson""me"
>   "wcs_contactorganization"  "unemployed"
>   "wcs_contactposition"  "manager"
>   "wcs_contactvoicetelephone""613-555-1234"
>   "wcs_contactfacimiletelephone" "613-555-1235"
> #  "wcs_service_onlineresource"
> "http://domainserver/cgi-bin/wcs?";
>   'wcs_enable_request'   '*'
> END #end metadata
> 
> #Scale range at which web interface will operate
> # Template and heade

[mapserver-users] WCS server not

[Jorge Lopez]

Hello;

I am newbie to Mapserver, so maybe this is a naive question but I am doing
my best to find a solution to serve raster data by using Mapserver.

I have MapServer 5.6.5, I have prepared my map server with WFS and WMS  and
I would like to serve GEOTIFF images with WCS 1.0.0 protocol.

I prepared a map file, with two layers to be served and I made a
capabilities of the server:

http://domainserver/cgi-bin/mapserv?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCapabilities

The problem is that all metadata is full but there is no content for
coverages ("identifiers" in v.1.1.0), that is, the content between
ContentMetada labels is empty,




So I don't know what is happen, I made a probe like using shp2img to
generate a image png from mapfile and it is done

My Mapfile (only one layer) looks like in the following way:


MAP

  NAME " Map Server"
  SIZE  100 100   # NECESARIO PARA LA UTILIDAD shp2img
  UNITS DD
  EXTENT -90 -90 90 90
  DEBUG 5
  CONFIG "CPL_DEBUG" "ON"
  CONFIG "MS_ERRORFILE" "/tmp/mapserver.log" #a este fichero van mensajes
de error!! (equivalent to set SetEnv MS_ERRORFILE "/tmp/mapserver.log" in
/etc/apache2/apache2.conf)
  PROJECTION
   "init=epsg:4326"
   END # end projection
# Background color for the map canvas -- change as desired
  IMAGECOLOR 192 192 192
  IMAGEQUALITY 95
  IMAGETYPE jpeg

  # Usamos el driver GDAL para crear el formato Ráster en modo IMAGEN RGB
  OUTPUTFORMAT
   NAME GEOTIFF_RGB
   DRIVER "GDAL/GTiff"
   MIMETYPE "image/tiff"
   IMAGEMODE RGB
   EXTENSION 'tif'
  END   #end outputformat

  # Legend
  LEGEND
  IMAGECOLOR 255 255 255
  STATUS ON
  KEYSIZE 18 12
   LABEL
  TYPE BITMAP
  SIZE MEDIUM
  COLOR 0 0 89
END #end label
  END #end legend


  # Web interface definition. Only the template parameter is required to
display a map. See MapServer documentation
  WEB

# Set IMAGEPATH to the path where MapServer should write its output.
IMAGEPATH '/tmp/'
# Set IMAGEURL to the url that points to IMAGEPATH as defined in your
web server configuration
IMAGEURL '/tmp/'

# WCS server settings
METADATA
  'wms_title'' Map Server'
  'wms_enable_request'   '*'
  'ows_onlineresource'   'http://domainserver/cgi-bin/mapserv?'
  #'ows_srs' 'CRS:84 EPSG:4326 urn:x-ogc:def:crs:EPSG:4326
urn:x-ogc:def:crs:EPSG:3035 EPSG:3035 EPSG:4258'
  'ows title''Intamap WCS'
  'ows_srs'  'CRS:84 EPSG:4326 urn:x-ogc:def:crs:EPSG:4326'
  'ows_abstract' 'Comentarios Blah Blah Blah'
  #'ows_srs' 'EPSG:3035 urn:x-ogc:def:crs:EPSG:3035'
  'wfs_title'' WFS Server'
  'wfs_onlineresource'   'http://domainserver/cgi-bin/wfs?'
  'wfs_srs'  'EPSG:4326' ## Recommended
  'wfs_abstract' 'Web Feature Service for the  central
geonode.' ## Recommended
  'wfs_enable_request'   '*'
  'wms_abstract' 'Web Map Service for the  central geonode'
## WCS  
  'wcs_label'  ' WCS Server' ### required for WCS
  'wcs_title'  'XXX  Web Coverage Service Server'
  'wcs_description''Web Coverage Service for the  central
geonode to serve coverages'
  'wcs_onlineresource' 'http://domainserver/cgi-bin/wcs?'
  'wcs_service_onlineresource' 'http://domainserver/cgi-bin/wcs?'
  'wcs_fees'   'none'
  'wcs_srs''EPSG:4326' ## Recommended
# 'wcs_abstract'   'Web Coverage Service for the XX central
geonode.' ## Recommended
  'wcs_accessconstraints'  'none'
  'wcs_keywordlist''WCS, TEXT, Coverage'
  'wcs_metadatalink_format'  "text/plain" #tipo MIME para formato de
ficheros
  'wcs_metadatalink_href'"http://domainserver/catalog";  # URL al
metadata
  'wcs_metadatalink_type'"TC211"   # standard que cumple el metadata
  "wcs_address"  "124 Gilmour Street"
  "wcs_city" "Ottawa"
  "wcs_stateorprovince"  "ON"
  "wcs_postcode" "90210"
  "wcs_country"  "Canada"
  "wcs_contactelectronicmailaddress" "blah@blah"
  "wcs_contactperson""me"
  "wcs_contactorganization"  "unemployed"
  "wcs_contactposition"  "manager"
  "wcs_contactvoicetelephone""613-555-1234"
  "wcs_contactfacimiletelephone" "613-555-1235"
#  "wcs_service_onlineresource"   "http://domainserver/cgi-bin/wcs?";
  'wcs_enable_request'   '*'
END #end metadata

#Scale range at which web interface will operate
# Template and header/footer settings
# Only the template parameter is required to display a map. See
MapServer documentation
  END #end web

  LAYER
NAME 'GLOBCORINE_Color'
TYPE RASTER
STATUS ON
METADATA
   'wms_title''GLOBCORINE_2009'
#  'ows_metadataurl_format'   'text/html'
#  'ows_metadataurl_href' '

[mapserver-users] WCS GetCoverage

[David Hildebrand]

I am trying to implement a WCS server and am running into difficulty
with GetCoverage and the following request.

 

REQUEST=GetCoverage&COVERAGE=awifs&CRS=EPSG:4269&BBOX=-116,51,-114,53&RE
SX=100&RESY=100&FORMAT=GTiff&RESPONSE_CRS=EPSG:4269

 

The following ServiceException is raised.

 

msImageCreateGD(): Image handling error. Cannot create GD image of size
0x0

 

I can do a WCS GetCapabilities and DescribeCoverage without error.
Also, when I issue the following WMS request it works fine.

 

REQUEST=GetMap&LAYERS=awifs&SRS=EPSG:4269&BBOX=-116,51,-114,53&WIDTH=800
&HEIGHT=600&FORMAT=image/png&STYLES=

 

The GetCoverage and GetMap requests have the same parameters and yet WCS
thinks the image size is 0x0.  The MapServer configuration for the layer
file is given below

 

LAYER

  NAME "awifs"

  PROCESSING "BANDS=2,1,3"

  PROCESSING "SCALE_2=19,159"

  PROCESSING "SCALE_1=10,130"

  PROCESSING "SCALE_3=9,124"

  METADATA

"wcs_label" "awifs"

"wcs_rangeset_name" "RGB"

"wcs_rangeset_label" "rgb"

"wms_title" "awifs"

"wms_opaque" "1"

"ows_resolution" "56 56"

"wms_srs" "EPSG:43001"

  END

  STATUS off 

  TYPE raster

  DATA "e:/awifs/July.tif"

  PROJECTION

"init=epsg:43001"

  END

  TEMPLATE "empty.html"

  DUMP TRUE

END

 

Thanks for the help.

 

 

===
David V. Hildebrand
Agriculture Financial Services Corporation
(403) 782-8239   



 

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

[mapserver-users] WCS GetCoverage error

[Juan Rapoport]

Hello list,

I have a raster datasource in epsg:900913.
I make a GetCoverage request using WCS standard 1.1.0, using this
parameters:

-SERVICE=WCS&VERSION=1.1.0&REQUEST=GetCoverage&IDENTIFIER=ImagenSatelitalbajares&FORMAT=image/tiff&BOUNDINGBOX=-36,-60,-34,-56,urn:ogc:def:crs:EPSG::4326

the resulting image is one pixel only.

Changing the BOUNDINGBOX to miny, minx, maxy, maxx
(BOUNDINGBOX=-60,-36,-56,-34,urn:ogc:def:crs:EPSG::4326), makes this error:

WCS server error. Requested BBOX
(-4007501.66855785,-7558415.65608178,-4007501.66855785,21542212.205083) is
outside requested coverage BBOX
(-8688253.27640932,-7822332.37194489,-5635586.68352614,-1988107.35315028)

Seems that the upper tight coordinate is not taken into account.
Is Mapserver misunderstanding the boundingbox parameters?
Using Mapserver 5.6.

Thanks in advance.
-- 
Juan Rapoport
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS GetCoverage responses in multi-part mime format

[Stephan Meißl]

Bryan,

from my experience firefox does pretty good with multipart files.
Usually the first part is of type "text/xml" which is shown in the
browser directly and the second part is opened in an external image
viewer. Unfortunately I don't know a way how to turn multipart of with
WCS 1.1.

However, I do know that in WCS 2.0 you explicitly have to request
multipart files ("mediatype=multipart/mixed") which means by default
plain image files are returned. Please note that WCS 2.0 is a fairly new
standard which adopts the new modular specification model of OGC and
some of the extensions are not yet published which might cause some
problems for the time being.

Best regards,
Stephan


On Wed, 2011-08-17 at 17:04 +0200, Bryan Hempen wrote: 
> Hi there!
> 
> I am currently setting up a WCS server using MapServer 5.6.5. I am 
> serving hyperspectral images and my goal is to visualize a subset of 
> bands within a BBOX in a webclient. This should work fine if WCS 1.1.0 
> GetCoverage requests would not return results in a multi-part mime 
> format as stated on 
> http://mapserver.org/ogc/wcs_server.html#getcoverage. Browsers can't 
> seem to deal with this type of format.
> 
> I can't use WCS 1.0.0 requests because they do not allow for subsetting 
> of bands.
> Since I use MapServer version 5.6.5, WCS 2.0 is not supported, but if a 
> WCS 2.0 (as supported by MapServer 6.x) also returns GetCoverage 
> requests in a multi-part mime format it would be useless for me anyway.
> 
> Is there any way to turn off the response of WCS GetCoverage requests in 
> a multi-part mime format in MapServer?
> 
> If I upgrade to WCS 2.0, will I still have the same problem?
> 
> Or does anyone know how to make a browser visualize the image-part of 
> the reponse? I can't find anything useful on the web.
> 
> Thanks for your help,
> Bryan
> 
> 
> This message and any attachments are intended for the use of the addressee or 
> addressees only. The unauthorised disclosure, 
> 
> use, dissemination or copying (either in whole or in part) of its content is 
> not permitted. If you received this message in 
> 
> error, please notify the sender and delete it from your system. Emails can be 
> altered and their integrity cannot be guaranteed by   
> 
> the sender. 
> 
> Please consider the environment before printing this email.
> =
> 
> ___
> 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

[mapserver-users] WCS GetCoverage responses in multi-part mime format

[Bryan Hempen]

Hi there!

I am currently setting up a WCS server using MapServer 5.6.5. I am 
serving hyperspectral images and my goal is to visualize a subset of 
bands within a BBOX in a webclient. This should work fine if WCS 1.1.0 
GetCoverage requests would not return results in a multi-part mime 
format as stated on 
http://mapserver.org/ogc/wcs_server.html#getcoverage. Browsers can't 
seem to deal with this type of format.


I can't use WCS 1.0.0 requests because they do not allow for subsetting 
of bands.
Since I use MapServer version 5.6.5, WCS 2.0 is not supported, but if a 
WCS 2.0 (as supported by MapServer 6.x) also returns GetCoverage 
requests in a multi-part mime format it would be useless for me anyway.


Is there any way to turn off the response of WCS GetCoverage requests in 
a multi-part mime format in MapServer?


If I upgrade to WCS 2.0, will I still have the same problem?

Or does anyone know how to make a browser visualize the image-part of 
the reponse? I can't find anything useful on the web.


Thanks for your help,
Bryan


This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, 

use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in 

error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by   

the sender. 


Please consider the environment before printing this email.
=

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

Re: [mapserver-users] WCS pops up to open image

[Virginia Maffei]

I changed the format to PNG and it worked!

Virginia


On Tue, Jun 14, 2011 at 10:44 AM, Stephan Meißl  wrote:

> Virginia,
>
> as far as I know only Safari supports displaying TIFF images natively.
> There are add-ons available for Firofox, though.
>
> cu
> Stephan
>
>
> On Sun, 2011-06-12 at 17:14 -0300, Virginia Maffei wrote:
> > Hi, i'm trying to publish a tiff loaded in postgis raster and when i
> > make a GetCoverage it just pops up a window to download the image
> > (mapserv.exe.tiff)
> > Why is it happening? If i download the image its looking correctly
> > what i'm expecting but i want to see it in the browser.
> >
> >
> > Thanks!
> >
> >
> > Virginia
> >
> >
> > ___
> > 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

Re: [mapserver-users] WCS pops up to open image

[Stephan Meißl]

Virginia,

as far as I know only Safari supports displaying TIFF images natively.
There are add-ons available for Firofox, though.

cu
Stephan


On Sun, 2011-06-12 at 17:14 -0300, Virginia Maffei wrote:
> Hi, i'm trying to publish a tiff loaded in postgis raster and when i
> make a GetCoverage it just pops up a window to download the image
> (mapserv.exe.tiff)  
> Why is it happening? If i download the image its looking correctly
> what i'm expecting but i want to see it in the browser.
> 
> 
> Thanks!
> 
> 
> Virginia
> 
> 
> ___
> 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

[mapserver-users] WCS pops up to open image

[Virginia Maffei]

Hi, i'm trying to publish a tiff loaded in postgis raster and when i make a
GetCoverage it just pops up a window to download the image
(mapserv.exe.tiff)
Why is it happening? If i download the image its looking correctly what i'm
expecting but i want to see it in the browser.

Thanks!

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

Re: [mapserver-users] WCS reprojection issue

[Rahkonen Jukka]

Hi,

You can start with these two projection settings:

Map level projection: The default output projection of your service. For making 
everything to work as expected the EXTENT must be edited also so that it gives 
the output in the units of the output projection. For example EXTENT -83.938  
34.746  -81.340  36.361 makes a pretty small window as meters. 

Layer level projection: The projection of the source data.

After editing the projection values continue systematically. Read the 
GetCapabilities and DescribeCoverage outputs carefully and look if they make 
sense. Have a try with a browser and GetCoverage for seeing that you can get 
something out. When you continue to ArcGIS have a look at the Apache access.log 
and see how do the requests sent by ArcMAP look like. If there are still 
problems, sending the GetCoverages created by ArcMAP will make is much easier 
for us to find out what is going wrong.

-Jukka Rahkonen-


-Alkuperäinen viesti-
Lähettäjä: Mark Phillips [mailto:m...@geomtech.com]
Lähetetty: pe 3.6.2011 18:14
Vastaanottaja: Rahkonen Jukka
Kopio: mapserver-users@lists.osgeo.org
Aihe: Re: [mapserver-users] WCS reprojection issue
 
> Thanks for your suggestion; I will try this.

> My end goal, however, is to set up a MapServer WCS that can be consumed by
> ArcMap.   This project is for a client that uses ArcMap, and it's not an
> option for me to tell them to use something else.  So, although writing WCS
> queries by hand for testing might be instructive, as far as I know there is
> no way for me to customize the queries that ArcMap generates --- the service
> itself needs to be set up so that it will just work in ArcMap.

> Any ideas on how to do that?  Are there any known compatibility issues with
> ArcMap?  Should I force ArcMap to use a specific WCS version?  (I've been
> telling it to use version 1.0.0 so far.)

--Mark

> On Fri, Jun 3, 2011 at 10:26 AM, Rahkonen Jukka
wrote:

>> Hi,
>
>> Response_crs exists for letting user to select the output CRS. Have you
>> tried it yet?
>> There are better possibilities for a success and especially for
>> understanding what is really happening if you write WCS requests by hand and
>> semd them with a browser instead of using a GIS client.  Request examples at
>> http://mapserver.org/ogc/wcs_server.html are good to start with.
>
> -Jukka Rahkonen-
>
>
> -Alkuperäinen viesti-
> Lähettäjä: mapserver-users-boun...@lists.osgeo.org puolesta: Mark Phillips
> Lähetetty: to 2.6.2011 22:16
> Vastaanottaja: mapserver-users@lists.osgeo.org
> Aihe: [mapserver-users] WCS reprojection issue
>
> Hi,
>
> I'm struggling with an issue related to projections in a MapServer WCS
> service.  I've got a raster data file that is in EPSG:2163, and I'd like to
> serve it via WCS in EPSG:4326.  The only way I have managed to get this to
> work is to reproject the data manually in advance and then reference the
> ESPG:4326 copy of the data in my mapfile.  When I do that, with the mapfile
> below, the service seems to work beautifully. What I really want, though,
> is
> to be able to leave my data in its original projection and have MapServer
> reproject on the fly.
>
> When I change the mapfile to use the original ESPG:2163 copy of the data,
> and update the relevant projections in the mapfile from 4326 to 2163,
> though, the service breaks, in the sense that the data shows up in (very
> much) the wrong place.  I first tried just changing the
> projections commented in the mapfile below with ###LAYER_PROJECTION and
> ###LAYER_WCS_SRS from 4326 to 2163 (after changing the DATA line in the
> layer to point to the EPSG:2163 copy of the data, of course), but that
> didn't work.  I then experimented with changing the ###SERVICE_WCS_SRS line
> and/or the ###MAP_PROJECTION as well, but no luck.
>
> What is especially confusing is that I *can* get this to work for a WMS
> service.  In the case of WMS, MapServer seems quite happy to serve
> EPSG:2163
> data in ESPG:4326, as long as the ###LAYER_PROJECTION and ###LAYER_WCS_SRS
> lines say EPSG:2163 (with "wcs" replaced by "wms", of course).
>
> I'm sure that part of my problem is that I don't completely understand the
> purpose served by each of the various projections specified in the mapfile.
>  Can someone offer some insight into what the correct approach is to
> getting
> MapServer to reproject on the fly in a WCS?
>
> In case it matters: I'm using MapServer 6.0, and am testing the WCS with
> ArcMap 9.3.
>
> Thanks!
>
> --Mark
>
> Here is my working mapfile for ESPG:4326:
>
>MAP
>  NAME   lucky
>  STATUS ON
>  SIZE   600 400
>  EXTENT -83.938  34.746  -81.340  

Re: [mapserver-users] WCS reprojection issue

[Mark Phillips]

Thanks for your suggestion; I will try this.

My end goal, however, is to set up a MapServer WCS that can be consumed by
ArcMap.   This project is for a client that uses ArcMap, and it's not an
option for me to tell them to use something else.  So, although writing WCS
queries by hand for testing might be instructive, as far as I know there is
no way for me to customize the queries that ArcMap generates --- the service
itself needs to be set up so that it will just work in ArcMap.

Any ideas on how to do that?  Are there any known compatibility issues with
ArcMap?  Should I force ArcMap to use a specific WCS version?  (I've been
telling it to use version 1.0.0 so far.)

--Mark

On Fri, Jun 3, 2011 at 10:26 AM, Rahkonen Jukka
wrote:

> Hi,
>
> Response_crs exists for letting user to select the output CRS. Have you
> tried it yet?
> There are better possibilities for a success and especially for
> understanding what is really happening if you write WCS requests by hand and
> semd them with a browser instead of using a GIS client.  Request examples at
> http://mapserver.org/ogc/wcs_server.html are good to start with.
>
> -Jukka Rahkonen-
>
>
> -Alkuperäinen viesti-
> Lähettäjä: mapserver-users-boun...@lists.osgeo.org puolesta: Mark Phillips
> Lähetetty: to 2.6.2011 22:16
> Vastaanottaja: mapserver-users@lists.osgeo.org
> Aihe: [mapserver-users] WCS reprojection issue
>
> Hi,
>
> I'm struggling with an issue related to projections in a MapServer WCS
> service.  I've got a raster data file that is in EPSG:2163, and I'd like to
> serve it via WCS in EPSG:4326.  The only way I have managed to get this to
> work is to reproject the data manually in advance and then reference the
> ESPG:4326 copy of the data in my mapfile.  When I do that, with the mapfile
> below, the service seems to work beautifully. What I really want, though,
> is
> to be able to leave my data in its original projection and have MapServer
> reproject on the fly.
>
> When I change the mapfile to use the original ESPG:2163 copy of the data,
> and update the relevant projections in the mapfile from 4326 to 2163,
> though, the service breaks, in the sense that the data shows up in (very
> much) the wrong place.  I first tried just changing the
> projections commented in the mapfile below with ###LAYER_PROJECTION and
> ###LAYER_WCS_SRS from 4326 to 2163 (after changing the DATA line in the
> layer to point to the EPSG:2163 copy of the data, of course), but that
> didn't work.  I then experimented with changing the ###SERVICE_WCS_SRS line
> and/or the ###MAP_PROJECTION as well, but no luck.
>
> What is especially confusing is that I *can* get this to work for a WMS
> service.  In the case of WMS, MapServer seems quite happy to serve
> EPSG:2163
> data in ESPG:4326, as long as the ###LAYER_PROJECTION and ###LAYER_WCS_SRS
> lines say EPSG:2163 (with "wcs" replaced by "wms", of course).
>
> I'm sure that part of my problem is that I don't completely understand the
> purpose served by each of the various projections specified in the mapfile.
>  Can someone offer some insight into what the correct approach is to
> getting
> MapServer to reproject on the fly in a WCS?
>
> In case it matters: I'm using MapServer 6.0, and am testing the WCS with
> ArcMap 9.3.
>
> Thanks!
>
> --Mark
>
> Here is my working mapfile for ESPG:4326:
>
>MAP
>  NAME   lucky
>  STATUS ON
>  SIZE   600 400
>  EXTENT -83.938  34.746  -81.340  36.361
>  IMAGECOLOR 255 255 255
>
>  WEB
>METADATA
>  "ows_enable_request" "*"
>  "wcs_label"  "My WCS Service"
>  "wcs_srs""EPSG:4326"   ###SERVICE_WCS_SRS
>END
>  END
>
>  PROJECTION
>   "init=epsg:4326"  ###MAP_PROJECTION
>  END
>
>  LAYER
> NAME mylayer
>TYPE RASTER
> DUMP TRUE
>STATUS   OFF
> DATA sampledata_wgs84/tif_wgs84.tif
>INCLUDE  "colormap.cmap"
>PROJECTION
>  "init=epsg:4326"   ###LAYER_PROJECTION
>END
>METADATA
>  "wcs_srs""EPSG:4326"  ###LAYER_WCS_SRS
>  "wcs_label"  "My Layer"
>  "wcs_rangeset_name"  "My Range"
>  "wcs_rangeset_label" "My Label"
>END
>  END
>END
>
>
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS reprojection issue

[Rahkonen Jukka]

Hi,

Response_crs exists for letting user to select the output CRS. Have you tried 
it yet?
There are better possibilities for a success and especially for understanding 
what is really happening if you write WCS requests by hand and semd them with a 
browser instead of using a GIS client.  Request examples at 
http://mapserver.org/ogc/wcs_server.html are good to start with. 

-Jukka Rahkonen-


-Alkuperäinen viesti-
Lähettäjä: mapserver-users-boun...@lists.osgeo.org puolesta: Mark Phillips
Lähetetty: to 2.6.2011 22:16
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WCS reprojection issue
 
Hi,

I'm struggling with an issue related to projections in a MapServer WCS
service.  I've got a raster data file that is in EPSG:2163, and I'd like to
serve it via WCS in EPSG:4326.  The only way I have managed to get this to
work is to reproject the data manually in advance and then reference the
ESPG:4326 copy of the data in my mapfile.  When I do that, with the mapfile
below, the service seems to work beautifully. What I really want, though, is
to be able to leave my data in its original projection and have MapServer
reproject on the fly.

When I change the mapfile to use the original ESPG:2163 copy of the data,
and update the relevant projections in the mapfile from 4326 to 2163,
though, the service breaks, in the sense that the data shows up in (very
much) the wrong place.  I first tried just changing the
projections commented in the mapfile below with ###LAYER_PROJECTION and
###LAYER_WCS_SRS from 4326 to 2163 (after changing the DATA line in the
layer to point to the EPSG:2163 copy of the data, of course), but that
didn't work.  I then experimented with changing the ###SERVICE_WCS_SRS line
and/or the ###MAP_PROJECTION as well, but no luck.

What is especially confusing is that I *can* get this to work for a WMS
service.  In the case of WMS, MapServer seems quite happy to serve EPSG:2163
data in ESPG:4326, as long as the ###LAYER_PROJECTION and ###LAYER_WCS_SRS
lines say EPSG:2163 (with "wcs" replaced by "wms", of course).

I'm sure that part of my problem is that I don't completely understand the
purpose served by each of the various projections specified in the mapfile.
 Can someone offer some insight into what the correct approach is to getting
MapServer to reproject on the fly in a WCS?

In case it matters: I'm using MapServer 6.0, and am testing the WCS with
ArcMap 9.3.

Thanks!

--Mark

Here is my working mapfile for ESPG:4326:

MAP
  NAME   lucky
  STATUS ON
  SIZE   600 400
  EXTENT -83.938  34.746  -81.340  36.361
  IMAGECOLOR 255 255 255

  WEB
METADATA
  "ows_enable_request" "*"
  "wcs_label"  "My WCS Service"
  "wcs_srs""EPSG:4326"   ###SERVICE_WCS_SRS
END
  END

  PROJECTION
   "init=epsg:4326"  ###MAP_PROJECTION
  END

  LAYER
NAME mylayer
TYPE RASTER
DUMP TRUE
STATUS   OFF
DATA sampledata_wgs84/tif_wgs84.tif
INCLUDE  "colormap.cmap"
PROJECTION
  "init=epsg:4326"   ###LAYER_PROJECTION
END
METADATA
  "wcs_srs""EPSG:4326"  ###LAYER_WCS_SRS
  "wcs_label"  "My Layer"
  "wcs_rangeset_name"  "My Range"
  "wcs_rangeset_label" "My Label"
END
  END
END

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

[mapserver-users] WCS reprojection issue

[Mark Phillips]

Hi,

I'm struggling with an issue related to projections in a MapServer WCS
service.  I've got a raster data file that is in EPSG:2163, and I'd like to
serve it via WCS in EPSG:4326.  The only way I have managed to get this to
work is to reproject the data manually in advance and then reference the
ESPG:4326 copy of the data in my mapfile.  When I do that, with the mapfile
below, the service seems to work beautifully. What I really want, though, is
to be able to leave my data in its original projection and have MapServer
reproject on the fly.

When I change the mapfile to use the original ESPG:2163 copy of the data,
and update the relevant projections in the mapfile from 4326 to 2163,
though, the service breaks, in the sense that the data shows up in (very
much) the wrong place.  I first tried just changing the
projections commented in the mapfile below with ###LAYER_PROJECTION and
###LAYER_WCS_SRS from 4326 to 2163 (after changing the DATA line in the
layer to point to the EPSG:2163 copy of the data, of course), but that
didn't work.  I then experimented with changing the ###SERVICE_WCS_SRS line
and/or the ###MAP_PROJECTION as well, but no luck.

What is especially confusing is that I *can* get this to work for a WMS
service.  In the case of WMS, MapServer seems quite happy to serve EPSG:2163
data in ESPG:4326, as long as the ###LAYER_PROJECTION and ###LAYER_WCS_SRS
lines say EPSG:2163 (with "wcs" replaced by "wms", of course).

I'm sure that part of my problem is that I don't completely understand the
purpose served by each of the various projections specified in the mapfile.
 Can someone offer some insight into what the correct approach is to getting
MapServer to reproject on the fly in a WCS?

In case it matters: I'm using MapServer 6.0, and am testing the WCS with
ArcMap 9.3.

Thanks!

--Mark

Here is my working mapfile for ESPG:4326:

MAP
  NAME   lucky
  STATUS ON
  SIZE   600 400
  EXTENT -83.938  34.746  -81.340  36.361
  IMAGECOLOR 255 255 255

  WEB
METADATA
  "ows_enable_request" "*"
  "wcs_label"  "My WCS Service"
  "wcs_srs""EPSG:4326"   ###SERVICE_WCS_SRS
END
  END

  PROJECTION
   "init=epsg:4326"  ###MAP_PROJECTION
  END

  LAYER
NAME mylayer
TYPE RASTER
DUMP TRUE
STATUS   OFF
DATA sampledata_wgs84/tif_wgs84.tif
INCLUDE  "colormap.cmap"
PROJECTION
  "init=epsg:4326"   ###LAYER_PROJECTION
END
METADATA
  "wcs_srs""EPSG:4326"  ###LAYER_WCS_SRS
  "wcs_label"  "My Layer"
  "wcs_rangeset_name"  "My Range"
  "wcs_rangeset_label" "My Label"
END
  END
END
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

RE: [mapserver-users] WCS

[David Hildebrand]

I'm not sure if anyone remembers this post from a while ago or not but I
discovered a solution.  I am running MapServer 5.3-dev and testing WCS
1.0.0.  I discovered that the RESPONSE_CRS parameter must be the same as
the CRS parameter (or, more simply, not be used at all).  If they are
different an error is generated with respect to the bounding box of the
request being outside the bounding box of the coverage.  It doesn't seem
to matter whether or not the coordinate system of the request is the
same as the coordinate system of the source.  The coordinate system of
the response will be the same as the coordinate system of the request.
The issue here is that the RESPONSE_CRS parameter does not seem to have
been implemented correctly and, considering that the parameter is
optional, perhaps it's not a big issue.  Just something the user needs
to be aware of.

 

 

===
David V. Hildebrand
Agriculture Financial Services Corporation
(403) 782-8239   

www.afsc.ca   <http://www.afsc.ca
<http://www.afsc.ca/> >
This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal and/or privileged
information. Please contact Agriculture Financial Services Corporation
immediately if you are not the intended recipient of this communication,
and do not copy, distribute, or take action relying on it. Any
communication received in error, or subsequent reply, should be deleted
or destroyed. Please consider the environment before printing this
email.



From: mapserver-users-boun...@lists.osgeo.org
[mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of David
Hildebrand
Sent: Tuesday, February 01, 2011 4:46 PM
To: mapserver-users@lists.osgeo.org
Subject: [mapserver-users] WCS

 

I am trying to develop a WCS layer (1.0.0) and I can successfully issue
the GetCapabilities and DescribeCoverage requests.  However, when I
issue a GetCoverage request I get a bounding box error due to bad
coordinates.  The layer is also set up as a WMS layer (1.1.1) and a
GetMap request works fine.  The metadata ows_srs and ows_resolution
parameters are being used in the map file and these work fine for WMS
requests.  Should I be using version 1.1.0?

 

Any ideas?

 

 

===

David V. Hildebrand

Agriculture Financial Services Corporation

(403) 782-8239   

 

www.afsc.ca <http://www.afsc.ca>

This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal and/or privileged
information. Please contact Agriculture Financial Services Corporation
immediately if you are not the intended recipient of this communication,
and do not copy, distribute, or take action relying on it. Any
communication received in error, or subsequent reply, should be deleted
or destroyed. Please consider the environment before printing this
email.

 

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

RE: [mapserver-users] WCS

[David Hildebrand]

Jukka:

 

If I issue the request in the same units as the coverage (as shown
below) the request works fine.

 

REQUEST=GetCoverage

COVERAGE=landsat_test

CRS=EPSG:2956

BBOX=41,5726000,411000,5727000

RESX=30

RESY=30

FORMAT=GTiff

RESPONSE_CRS=EPSG:2956

 

If I issue the request in another projection (as shown below) the
request has issues with reprojection.

 

REQUEST=GetCoverage

COVERAGE=landsat_test

CRS=EPSG:4269

BBOX=-113.179,51.761,-113.177,51.763

RESX=30

RESY=30

FORMAT=GTiff

RESPONSE_CRS=EPSG:3400

 

The service exception I get is 

 

msWCSGetCoverage(): WCS server error. Requested BBOX
(-98.179,66.761,-98.179,66.761) is outside requested coverage BBOX
(281685,5612685,538515,5840415)

 

As you can see, the requested BBOX the server picks up is nowhere near
the BBOX I provide in the URL.  The basic content of my map file is
shown below.  As you can see the layer is WMS as well as WCS and the WMS
call works fine.

 

MAP

  NAME "mapserv"

  OUTPUTFORMAT

NAME 'AGG_JPEG'

DRIVER AGG/JPEG

IMAGEMODE RGB

  END

  WEB

METADATA

  "ows_title" "OGC mapserv"

  "ows_contactorganization" "Agriculture Financial Services
Corporation"

  "ows_srs" "EPSG:3400 EPSG:2955 EPSG:2956 EPSG:3401 EPSG:3402
EPSG:3403 EPSG:4267 EPSG:4269 EPSG:4326"

  "ows_http_max_age" "3"

  "wcs_label" "WCS mapserv"

  "wcs_onlineresource"
"http://172.16.12.76/cgi-bin/mapserv.wcs.100.exe?";

  "wms_feature_info_mime_type" "text/html"

  "wms_title" "WMS mapserv"

  "wms_onlineresource"
"http://172.16.12.76/cgi-bin/mapserv.wms.111.exe?";END

IMAGEPATH "/ms4w/tmp/ms_tmp/"

IMAGEURL "/ms_tmp/"

  END

  SIZE 1200 1000   #arbitrary...

  PROJECTION

"init=epsg:3400"

  END

  EXTENT 133000 5365600 905200 6721100

  UNITS meters

  LAYER

NAME "Landsat_test"

METADATA

  "ows_srs" "EPSG:2956"  #UTM12...

  "ows_resolution" "30 30"

  "wcs_name" "Landsat_test"

  "wcs_label" "Landsat_test 30m"

  "wcs_bandcount" "3"

  "wcs_rangeset_name" "TheRangesetName"

  "wcs_rangeset_label" "TheRangesetLabel"

  "wms_title" "Landsat_test"

  "wms_opaque" "1"

END

STATUS off 

TYPE raster

DATA "//Plcoressatsb01/G$/Landsat/2010/processed/4124_708.tif"

PROJECTION

  "init=epsg:2956"

END

DUMP TRUE

  END

END

 

Any help would be appreciated.

 

 

===

David V. Hildebrand

Agriculture Financial Services Corporation

(403) 782-8239   

 

www.afsc.ca <http://www.afsc.ca>

This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal and/or privileged
information. Please contact Agriculture Financial Services Corporation
immediately if you are not the intended recipient of this communication,
and do not copy, distribute, or take action relying on it. Any
communication received in error, or subsequent reply, should be deleted
or destroyed. Please consider the environment before printing this
email.

 

-Original Message-
From: Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi] 
Sent: Tuesday, February 01, 2011 10:15 PM
To: David Hildebrand; mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WCS

 

Hi,

 

Your layer definitions and the GetCoverare request you were using would
help pretty much.

 

-Jukka Rahkonen-

 

David Hildebrand wrote:

 

> I am trying to develop a WCS layer (1.0.0) and I can successfully
issue

the GetCapabilities and DescribeCoverage requests.  However, when I

issue a GetCoverage request I get a bounding box error due to bad

coordinates.  The layer is also set up as a WMS layer (1.1.1) and a

GetMap request works fine.  The metadata ows_srs and ows_resolution

parameters are being used in the map file and these work fine for WMS

requests.  Should I be using version 1.1.0?

 

> Any ideas?

 

 

 

 

 

===

 

David V. Hildebrand

 

Agriculture Financial Services Corporation

 

(403) 782-8239   

 

 

 

www.afsc.ca <http://www.afsc.ca>

 

This communication is intended for the use of the recipient to which it

is addressed, and may contain confidential, personal and/or privileged

information. Please contact Agriculture Financial Services Corporation

immediately if you are not the intended recipient of this communication,

and do not copy, distribute, or take action relying on it. Any

communication received in error, or subsequent reply, should be deleted

or destroyed. Please consider the environment before printing this

email.

 

 

 

 

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

Re: [mapserver-users] WCS

[Carlos Ruiz]

David,

I got several WCS working. Remember that EXTENT must be specified as: 

MinX MinY MaxX MaxY

Like this:

EXTENT 667850.414115 2160714.942368 672400.414115 2165844.942368


Cheers
 
IC Carlos Ruiz




From: David Hildebrand 
To: mapserver-users@lists.osgeo.org
Sent: Tue, February 1, 2011 5:46:01 PM
Subject: [mapserver-users] WCS

 
I am trying to develop a WCS layer (1.0.0) and I can successfully issue the 
GetCapabilities and DescribeCoverage requests.  However, when I issue a 
GetCoverage request I get a bounding box error due to bad coordinates.  The 
layer is also set up as a WMS layer (1.1.1) and a GetMap request works fine. 
 The metadata ows_srs and ows_resolution parameters are being used in the map 
file and these work fine for WMS requests.  Should I be using version 1.1.0?
 
Any ideas?
 
 
===
David V. Hildebrand
Agriculture Financial Services Corporation
(403) 782-8239   
 
www.afsc.ca<http://www.afsc.ca>
This communication is intended for the use of the recipient to which it is 
addressed, and may contain confidential, personal and/or privileged 
information. 
Please contact Agriculture Financial Services Corporation immediately if you 
are 
not the intended recipient of this communication, and do not copy, distribute, 
or take action relying on it. Any communication received in error, or 
subsequent 
reply, should be deleted or destroyed. Please consider the environment before 
printing this email.


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

Re: [mapserver-users] WCS

[Jeff McKenna]

On 11-02-01 7:46 PM, David Hildebrand wrote:

I am trying to develop a WCS layer (1.0.0) and I can successfully issue
the GetCapabilities and DescribeCoverage requests. However, when I issue
a GetCoverage request I get a bounding box error due to bad coordinates.
The layer is also set up as a WMS layer (1.1.1) and a GetMap request
works fine. The metadata ows_srs and ows_resolution parameters are being
used in the map file and these work fine for WMS requests. Should I be
using version 1.1.0?


You can also see http://demo.mapserver.org/ for working MapServer WCS 
requests.


-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

Re: [mapserver-users] WCS

[Rahkonen Jukka]

Hi,

Your layer definitions and the GetCoverare request you were using would help 
pretty much.

-Jukka Rahkonen-

David Hildebrand wrote:
 
> I am trying to develop a WCS layer (1.0.0) and I can successfully issue
the GetCapabilities and DescribeCoverage requests.  However, when I
issue a GetCoverage request I get a bounding box error due to bad
coordinates.  The layer is also set up as a WMS layer (1.1.1) and a
GetMap request works fine.  The metadata ows_srs and ows_resolution
parameters are being used in the map file and these work fine for WMS
requests.  Should I be using version 1.1.0?

> Any ideas?

 

 

===

David V. Hildebrand

Agriculture Financial Services Corporation

(403) 782-8239   

 

www.afsc.ca 

This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal and/or privileged
information. Please contact Agriculture Financial Services Corporation
immediately if you are not the intended recipient of this communication,
and do not copy, distribute, or take action relying on it. Any
communication received in error, or subsequent reply, should be deleted
or destroyed. Please consider the environment before printing this
email.

 


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

[mapserver-users] WCS

[David Hildebrand]

I am trying to develop a WCS layer (1.0.0) and I can successfully issue
the GetCapabilities and DescribeCoverage requests.  However, when I
issue a GetCoverage request I get a bounding box error due to bad
coordinates.  The layer is also set up as a WMS layer (1.1.1) and a
GetMap request works fine.  The metadata ows_srs and ows_resolution
parameters are being used in the map file and these work fine for WMS
requests.  Should I be using version 1.1.0?

 

Any ideas?

 

 

===

David V. Hildebrand

Agriculture Financial Services Corporation

(403) 782-8239   

 

www.afsc.ca 

This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal and/or privileged
information. Please contact Agriculture Financial Services Corporation
immediately if you are not the intended recipient of this communication,
and do not copy, distribute, or take action relying on it. Any
communication received in error, or subsequent reply, should be deleted
or destroyed. Please consider the environment before printing this
email.

 

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

Re: [mapserver-users] WCS 1.1 multipart mime (correct usage)

[Frank Warmerdam]

turtlewax wrote:

I'm looking at the WCS 1.1.x specification for implementing an asynchronous
WCS service.

My assumption is that the WCS 1.1 XML manifest can be used to return a URI
to the asynchronous result. Is this correct?


Frank,

I don't know if this is permitted by the specification, but it is not
supported by the MapServer WCS Server implementation, or the GDAL WCS
driver client implementation.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent

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

[mapserver-users] WCS 1.1 multipart mime (correct usage)

[turtlewax]

I'm looking at the WCS 1.1.x specification for implementing an asynchronous
WCS service.

My assumption is that the WCS 1.1 XML manifest can be used to return a URI
to the asynchronous result. Is this correct?

Thanks in advance


 

-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/WCS-1-1-multipart-mime-correct-usage-tp5478246p5478246.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS GET_COVERAGE delivers corrupted geotiff

[Frank Warmerdam]

John Cartwright wrote:

 Thanks Frank,  I finally realized last night that I was getting a
multipart mime response and that was the problem.

I was using 1.1.1 because it was my understanding that there was a 1px
image shift between version 1.0 and 1.1 (see thread at
http://comments.gmane.org/gmane.comp.gis.mapserver.user/41599).  I
didn't see any ticket filed on this issue - are you aware of it?

Thanks again for your help!


John,

It is my understanding that there is a half-pixel offset difference
in the interpretation of the origin of a BBOX between WCS 1.1 and
1.0.  I believe MapServer accounts for that properly.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent

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

Re: [mapserver-users] WCS GET_COVERAGE delivers corrupted geotiff

[John Cartwright]

 Thanks Frank,  I finally realized last night that I was getting a
multipart mime response and that was the problem.

I was using 1.1.1 because it was my understanding that there was a 1px
image shift between version 1.0 and 1.1 (see thread at
http://comments.gmane.org/gmane.comp.gis.mapserver.user/41599).  I
didn't see any ticket filed on this issue - are you aware of it?

Thanks again for your help!

--john


On 07/21/2010 09:33 AM, Frank Warmerdam wrote:
> John Cartwright wrote:
>>  Hello All,
>>
>> I'm running Mapserver 5.6.3 and have a WCS service configured.  I'm
>> finding that a GetCoverage request like:
>>
>> http://mapserver.ngdc.noaa.gov/cgi-bin/public/etopo1/etopo1.tif?request=GetCoverage&service=WCS&version=1.1.1&COVERAGE=etopo1&crs=EPSG:4326&format=geotiff&resx=0.008333&resy=0.008333&bbox=-95,25,-75,40
>>
>>
>> delivers a corrupted geotiff that appears to have header information
>> prepended to the TIFF, e.g.
>>
>> --wcs
>> Content-Type: text/xml
>> Content-ID: wcs.xml
>>
>> 
>> >  xmlns="http://www.opengis.net/wcs/1.1";
> ...
>>
>> I've included the complete mapfile below.
>>
>> I'm assuming that I have something misconfigured in either Mapserver or
>> Apache - can someone please help me here?
>
> John,
>
> This is a WCS 1.1.x manifest and it is required by the
> WCS 1.1.x standard.  If you want a simple file back consider
> using the WCS 1.0 protocol.
>
> This is an aspect of WCS 1.1+ that I complained quite bitterly
> about.
>
> Best regards,
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WCS GET_COVERAGE delivers corrupted geotiff

[Frank Warmerdam]

John Cartwright wrote:

 Hello All,

I'm running Mapserver 5.6.3 and have a WCS service configured.  I'm
finding that a GetCoverage request like:

http://mapserver.ngdc.noaa.gov/cgi-bin/public/etopo1/etopo1.tif?request=GetCoverage&service=WCS&version=1.1.1&COVERAGE=etopo1&crs=EPSG:4326&format=geotiff&resx=0.008333&resy=0.008333&bbox=-95,25,-75,40

delivers a corrupted geotiff that appears to have header information
prepended to the TIFF, e.g.

--wcs
Content-Type: text/xml
Content-ID: wcs.xml


http://www.opengis.net/wcs/1.1";

...


I've included the complete mapfile below.

I'm assuming that I have something misconfigured in either Mapserver or
Apache - can someone please help me here?


John,

This is a WCS 1.1.x manifest and it is required by the
WCS 1.1.x standard.  If you want a simple file back consider
using the WCS 1.0 protocol.

This is an aspect of WCS 1.1+ that I complained quite bitterly
about.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent

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

[mapserver-users] WCS GET_COVERAGE delivers corrupted geotiff

[John Cartwright]

 Hello All,

I'm running Mapserver 5.6.3 and have a WCS service configured.  I'm
finding that a GetCoverage request like:

http://mapserver.ngdc.noaa.gov/cgi-bin/public/etopo1/etopo1.tif?request=GetCoverage&service=WCS&version=1.1.1&COVERAGE=etopo1&crs=EPSG:4326&format=geotiff&resx=0.008333&resy=0.008333&bbox=-95,25,-75,40

delivers a corrupted geotiff that appears to have header information
prepended to the TIFF, e.g.

--wcs
Content-Type: text/xml
Content-ID: wcs.xml


http://www.opengis.net/wcs/1.1";
 xmlns:ows="http://www.opengis.net/ows";
 xmlns:xlink="http://www.w3.org/1999/xlink";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://www.opengis.net/ows/1.1
../owsCoverages.xsd">
  

  

--wcs
Content-Type: image/tiff
Content-Description: coverage data
Content-Transfer-Encoding: binary
Content-ID: coverage/out.tif
Content-Disposition: INLINE

I've included the complete mapfile below.

I'm assuming that I have something misconfigured in either Mapserver or
Apache - can someone please help me here?

Thanks!

--john


MAP

NAME WCS_server
STATUS ON
SIZE 500 250
#SYMBOLSET ../etc/symbols.sym
EXTENT -180 -90 180 90
UNITS dd
SHAPEPATH "/nfs/gisdata/rasters"
IMAGECOLOR 255 255 255
FONTSET "/nfs/eogmapdata/fontset.txt"


#
# Start of web interface definition
#
WEB
  IMAGEPATH "/data/mapserver-vhost/html/tmp/"
  IMAGEURL "/tmp/"
  METADATA
"wcs_label""GMap WCS Demo Server" ### required
"wcs_description"  "Some text description of the service"
"wcs_onlineresource"  
"http://127.0.0.1/cgi-bin/mapserv.exe?"; ### recommended
"wcs_service_onlineresource"   "http://127.0.0.1/cgi-bin/mapserv.exe?";
  END
END

PROJECTION
  "init=epsg:4326"
END

OUTPUTFORMAT
  NAME GEOTIFF
  DRIVER "GDAL/GTiff"
  MIMETYPE "image/tiff"
  IMAGEMODE "BYTE"
  EXTENSION "tif"
  FORMATOPTION "COMPRESS=LZW"
END
OUTPUTFORMAT
  NAME GEOTIFF_FLOAT
  DRIVER "GDAL/GTiff"
  MIMETYPE "image/tiff"
  IMAGEMODE "FLOAT32"
  EXTENSION "tif"
  FORMATOPTION "COMPRESS=LZW"
END

LAYER
  NAME etopo1
  METADATA
"wcs_label"   "Elevation/Bathymetry"  ### required
"wcs_rangeset_name"   "Range 1"   ### required to
support DescribeCoverage request
"wcs_rangeset_label"  "My Label"  ### required to
support DescribeCoverage request
  END
  TYPE RASTER ### required
  STATUS ON
  DATA ETOPO1_Ice_g.tif
  PROJECTION
"init=epsg:4326"
  END
  DUMP TRUE ### required
END


END # Map File



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

[mapserver-users] WCS error. Requested BBOX (...) outside requested coverage

[turtlewax]

Thanks in advance for any guidance. I have my own server, but I'm using the
server referenced in the documentation to get a handle on expected behavior.

==
my request.
==
http://maps.dnr.state.mn.us/cgi-bin/mapserv50?
 MAP=/usr/local/www/docs_maps/mapserver_demos/wcs/demo.map&
 SERVICE=WCS&VERSION=1.0.0&
 REQUEST=GetCoverage&
 COVERAGE=modis&
 CRS=EPSG:26915&
 bbox=159707,4597895,1400207,5501395&
 Width=500&
 Height=500
==
Server Response
==

  
 msWCSGetCoverage(): WCS server error. Requested BBOX 
 (-97.7071758865421,41.0324719184183,-80.6778361148771,49.6650665681236) 
 is outside requested coverage BBOX (159707,4597895,1400207,5501395)
  

==

1. To keep things simple, I'm requesting coverage in the layers native CRS.
2. To keep things simple, I'm using the BBOX described in the
"DescribeCovearge"


   159707 4597895
   1400207 5501395


At this point I'm trying to perform a pretty basic "Hello World" WCS
operation. I've considered the possibility that there might be a problem
with this server, but I've set up my own local map file and I'm seeing
similar behavior. Hence, the most likely explanation is that I'm using bad
syntax in my request.

Thanks in advance for any advice...



-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/WCS-error-Requested-BBOX-outside-requested-coverage-tp5282810p5282810.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WCS resX, resY

[turtlewax]

I'm trying to get a handle on the relationship between the "wcs_resolution"
in the map file, and the resX, resY parameters in the request. Looking at
the description in the OGC spec:
=
RESX=x RESY=y : Request a coverage subset with a specific spatial resolution
along each axis of the reply CRS. The values are given in the units
appropriate to each axis of the CRS.
=

QUESTION 1:  If CRS = EPSG:4326, would the unit be ??? 
["degree",0.0174532925199433] ???

QUESTION 2: As a consumer of WCS, I'm looking for a way to ask for
"Full-Res", "1/2 res", etc.  But if I understand the "resX,resY" definition,
it seems like the consumer needs in-depth knowledge of the underlying
source, and needs to perform calculations to determine the desired resX/resY
values.  

This leads me to believe that my understanding of these parameters is
incorrect. Looking for clarification.

Thanks in advance.


-- 
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/WCS-resX-resY-tp5256227p5256227.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

RE: [mapserver-users] WCS/WMS/WFS version negotiation

[Kralidis,Tom [Ontario]]

 

> -Original Message-
> From: mapserver-users-boun...@lists.osgeo.org 
> [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of 
> john.c.cartwri...@noaa.gov
> Sent: Wednesday, 05 May 2010 22:49
> To: mapserver-users@lists.osgeo.org
> Subject: [mapserver-users] WCS/WMS/WFS version negotiation
> 
> Hello All,
> 
> is there a way to configure a mapfile to only support a given 
> version of WCS, WFS, WMS?  For example, can I configure 
> mapserver to only host WCS version 1.1 and refuse any request 
> specifying a different version?
> 

Not at this point.  You could write a MapScript WxS wrapper to further
process requests and deal with the  version parameter accordingly.

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

[mapserver-users] WCS/WMS/WFS version negotiation

[John . C . Cartwright]

Hello All,

is there a way to configure a mapfile to only support a given version of WCS, 
WFS, WMS?  For 
example, can I configure mapserver to only host WCS version 1.1 and refuse any 
request 
specifying a different version?

Thanks!

--john

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

Re: [mapserver-users] WCS 1.0 vs 1.1 image shifted

[Ben Tuttle]

Sorry for missing the previous discussion.
I do have a mapfile, data, and requests that result in offset grids
being returned.
I will re-read the spec once more before filing a ticket, but seems
strange (although not impossible) to me that the expected result would
be a grid that is shifted compared to the original data.
Would this still be the appropriate place to file the ticket?
http://trac.osgeo.org/mapserver/
Thanks for the help.

On Mon, May 3, 2010 at 8:19 AM, Lime, Steve D (DNR)
 wrote:
> Like I said in the referenced message, I thought all was well in this regard. 
> We'd need a good test case (data, mapfile, 1.0/1.1 requests) attached to a 
> ticket. If there's a difference in the pixel models between WCS 1.0 and 1.1 
> then a request that differs only in version might be expected to generate 
> slightly different output. I haven't looked at those specs in a good while 
> though.
>
> Steve
>
> 
> From: mapserver-users-boun...@lists.osgeo.org 
> [mapserver-users-boun...@lists.osgeo.org] On Behalf Of Roger André 
> [ran...@gmail.com]
> Sent: Sunday, May 02, 2010 11:45 AM
> To: Ben Tuttle
> Cc: mapserver-users@lists.osgeo.org
> Subject: Re: [mapserver-users] WCS 1.0 vs 1.1 image shifted
>
> Hi Ben,
>
> I think it's a bug, at least based on the conversation that took place last 
> year with Steve Lime regarding this - 
> http://www.mail-archive.com/mapserver-users@lists.osgeo.org/msg06123.html
>
> I'm not sure what the current state is of this though.
>
> Roger
> --
>
> On Fri, Apr 30, 2010 at 1:18 PM, Ben Tuttle 
> mailto:benjamin.tut...@gmail.com>> wrote:
> I am trying to understand the results I am getting from WCS requests
> to MapServer.
> If I make the same request changing only the WCS version the images I
> get back are shifted by 1 pixel in the x and y directions. A request
> for VERSION=1.1.0 gives me the image I expect while VERSION=1.0.0
> gives me back an image shifted by 1 pixel in the x and y directions to
> the North and West.
> The underlying data and mapfile are the same in both cases. So I am
> not sure if this is perhaps a MapServer bug or if perhaps I am reading
> the WCS spec incorrectly and this is actually the intended result (I
> hope it's not). Can anyone help me out?
>
> Request Examples:
> http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs100_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.0.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28
>
> http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs110_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.1.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28
>
>
> System Details:
> MapServer version 5.6.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP
> OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV
> SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
> SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
> SUPPORTS=THREADS SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS
> INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
>
> Red Hat Enterprise Linux Server release 5.5 (Tikanga)
>
> --
> Cheers, Ben Tuttle
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>



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

RE: [mapserver-users] WCS 1.0 vs 1.1 image shifted

[Lime, Steve D (DNR)]

Like I said in the referenced message, I thought all was well in this regard. 
We'd need a good test case (data, mapfile, 1.0/1.1 requests) attached to a 
ticket. If there's a difference in the pixel models between WCS 1.0 and 1.1 
then a request that differs only in version might be expected to generate 
slightly different output. I haven't looked at those specs in a good while 
though.

Steve
 

From: mapserver-users-boun...@lists.osgeo.org 
[mapserver-users-boun...@lists.osgeo.org] On Behalf Of Roger André 
[ran...@gmail.com]
Sent: Sunday, May 02, 2010 11:45 AM
To: Ben Tuttle
Cc: mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WCS 1.0 vs 1.1 image shifted

Hi Ben,

I think it's a bug, at least based on the conversation that took place last 
year with Steve Lime regarding this - 
http://www.mail-archive.com/mapserver-users@lists.osgeo.org/msg06123.html

I'm not sure what the current state is of this though.

Roger
--

On Fri, Apr 30, 2010 at 1:18 PM, Ben Tuttle 
mailto:benjamin.tut...@gmail.com>> wrote:
I am trying to understand the results I am getting from WCS requests
to MapServer.
If I make the same request changing only the WCS version the images I
get back are shifted by 1 pixel in the x and y directions. A request
for VERSION=1.1.0 gives me the image I expect while VERSION=1.0.0
gives me back an image shifted by 1 pixel in the x and y directions to
the North and West.
The underlying data and mapfile are the same in both cases. So I am
not sure if this is perhaps a MapServer bug or if perhaps I am reading
the WCS spec incorrectly and this is actually the intended result (I
hope it's not). Can anyone help me out?

Request Examples:
http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs100_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.0.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28

http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs110_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.1.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28


System Details:
MapServer version 5.6.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP
OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV
SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
SUPPORTS=THREADS SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS
INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

Red Hat Enterprise Linux Server release 5.5 (Tikanga)

--
Cheers, Ben Tuttle
___
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

Re: [mapserver-users] WCS 1.0 vs 1.1 image shifted

[Roger André]

Hi Ben,

I think it's a bug, at least based on the conversation that took place last
year with Steve Lime regarding this -
http://www.mail-archive.com/mapserver-users@lists.osgeo.org/msg06123.html

I'm not sure what the current state is of this though.

Roger
--

On Fri, Apr 30, 2010 at 1:18 PM, Ben Tuttle wrote:

> I am trying to understand the results I am getting from WCS requests
> to MapServer.
> If I make the same request changing only the WCS version the images I
> get back are shifted by 1 pixel in the x and y directions. A request
> for VERSION=1.1.0 gives me the image I expect while VERSION=1.0.0
> gives me back an image shifted by 1 pixel in the x and y directions to
> the North and West.
> The underlying data and mapfile are the same in both cases. So I am
> not sure if this is perhaps a MapServer bug or if perhaps I am reading
> the WCS spec incorrectly and this is actually the intended result (I
> hope it's not). Can anyone help me out?
>
> Request Examples:
>
> http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs100_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.0.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28
>
>
> http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs110_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.1.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28
>
>
> System Details:
> MapServer version 5.6.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP
> OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV
> SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
> SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
> SUPPORTS=THREADS SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS
> INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
>
> Red Hat Enterprise Linux Server release 5.5 (Tikanga)
>
> --
> Cheers, Ben Tuttle
> ___
> 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

[mapserver-users] WCS 1.0 vs 1.1 image shifted

[Ben Tuttle]

I am trying to understand the results I am getting from WCS requests
to MapServer.
If I make the same request changing only the WCS version the images I
get back are shifted by 1 pixel in the x and y directions. A request
for VERSION=1.1.0 gives me the image I expect while VERSION=1.0.0
gives me back an image shifted by 1 pixel in the x and y directions to
the North and West.
The underlying data and mapfile are the same in both cases. So I am
not sure if this is perhaps a MapServer bug or if perhaps I am reading
the WCS spec incorrectly and this is actually the intended result (I
hope it's not). Can anyone help me out?

Request Examples:
http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs100_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.0.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28

http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs110_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.1.0&format=geotiff&resx=0.008333&resy=0.008333&bbox=42,23,47,28


System Details:
MapServer version 5.6.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP
OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV
SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
SUPPORTS=THREADS SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS
INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

Red Hat Enterprise Linux Server release 5.5 (Tikanga)

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

Re: [mapserver-users] WCS GetCoverage question

[Frank Warmerdam]

bart...@osgis.nl wrote:

Hi Jukka,

it results in a fully black tiff file with all values 0.


Bart,

I think Jukka is going in the right direction with use of the IMAGEMODE,
but if your bathymetry data has negative values you might want to
substitute IMAGEMODE "INT16" for signed sixteen bit integer values
or even IMAGEMODE "FLOAT32" for floating point values.

Best regards,


Hi,

Here is my outputformat from some multichannel Landsat experiment.  I
remember that IMAGEMODE "BYTE" was needed for creating multichannel
GeoTIFFS.  Let's hope it makes something good with depth values as well.

-Jukka-

 OUTPUTFORMAT
NAME GEOTIFF
MIMETYPE "image/tiff"
DRIVER "GDAL/GTiff"
EXTENSION "tif"
IMAGEMODE "BYTE"
 END


--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent

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

Re: [mapserver-users] WCS GetCoverage question

[bartvde]

Hi Jukka,

it results in a fully black tiff file with all values 0.

I am using MS 5.2.0.

Best regards,
Bart

> Hi,
>
> Here is my outputformat from some multichannel Landsat experiment.  I
> remember that IMAGEMODE "BYTE" was needed for creating multichannel
> GeoTIFFS.  Let's hope it makes something good with depth values as well.
>
> -Jukka-
>
>  OUTPUTFORMAT
> NAME GEOTIFF
> MIMETYPE "image/tiff"
> DRIVER "GDAL/GTiff"
> EXTENSION "tif"
> IMAGEMODE "BYTE"
>  END
>
>
>
> bart...@osgis.nl wrote:
>
>
> Hi Jukka,
>
> this is the request:
>
> http://test.intranet.rijkswaterstaat.nl/services/geoservices/machu_topography?service=WCS&request=GetCoverage&coverage=GEBCO&version=1.0.0&format=GTiff&CRS=EPSG:4326&BBOX=-40.008,29.9916667,40.008,80.008&width=4801&height=3001
>
> I don't have an OUTPUTFORMAT explicitly defined.
>
> Best regards,
> Bart
>
>> Hi,
>>
>> How does your WCS request look like and how have you defined the GeoTIFF
>> output format?
>>
>> -Jukka Rahkonen-
>>
>>> bart...@osgis.nl wrote:
>>>
>>> Hi list,
>>>
>>> my bathymetry source raster (tiff file) has a field value_0
>>> which contains the depth in meters. I've got a classification
>>> on the raster on value_0.
>>>
>>> When doing a WCS GetCoverage request, I get out a Geotiff
>>> raster, but it contains value_0, value_1 and value_2 with the
>>> R G B values respectively.
>>>
>>> Is there a way to preserve the original attribute in the output tiff?
>>>
>>> TIA.
>>>
>>> Best regards,
>>> Bart
>>>
>>> ___
>>> 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

Re: [mapserver-users] WCS GetCoverage question

[Rahkonen Jukka]

Hi,
 
Here is my outputformat from some multichannel Landsat experiment.  I remember 
that IMAGEMODE "BYTE" was needed for creating multichannel GeoTIFFS.  Let's 
hope it makes something good with depth values as well.
 
-Jukka-
 
 OUTPUTFORMAT
NAME GEOTIFF
MIMETYPE "image/tiff"
DRIVER "GDAL/GTiff"
EXTENSION "tif"
IMAGEMODE "BYTE"
 END
 
 

bart...@osgis.nl wrote:


Hi Jukka,

this is the request:

http://test.intranet.rijkswaterstaat.nl/services/geoservices/machu_topography?service=WCS&request=GetCoverage&coverage=GEBCO&version=1.0.0&format=GTiff&CRS=EPSG:4326&BBOX=-40.008,29.9916667,40.008,80.008&width=4801&height=3001

I don't have an OUTPUTFORMAT explicitly defined.

Best regards,
Bart

> Hi,
>
> How does your WCS request look like and how have you defined the GeoTIFF
> output format?
>
> -Jukka Rahkonen-
>
>> bart...@osgis.nl wrote:
>>
>> Hi list,
>>
>> my bathymetry source raster (tiff file) has a field value_0
>> which contains the depth in meters. I've got a classification
>> on the raster on value_0.
>>
>> When doing a WCS GetCoverage request, I get out a Geotiff
>> raster, but it contains value_0, value_1 and value_2 with the
>> R G B values respectively.
>>
>> Is there a way to preserve the original attribute in the output tiff?
>>
>> TIA.
>>
>> Best regards,
>> Bart
>>
>> ___
>> 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

Re: [mapserver-users] WCS GetCoverage question

[bartvde]

Hi Jukka,

this is the request:

http://test.intranet.rijkswaterstaat.nl/services/geoservices/machu_topography?service=WCS&request=GetCoverage&coverage=GEBCO&version=1.0.0&format=GTiff&CRS=EPSG:4326&BBOX=-40.008,29.9916667,40.008,80.008&width=4801&height=3001

I don't have an OUTPUTFORMAT explicitly defined.

Best regards,
Bart

> Hi,
>
> How does your WCS request look like and how have you defined the GeoTIFF
> output format?
>
> -Jukka Rahkonen-
>
>> bart...@osgis.nl wrote:
>>
>> Hi list,
>>
>> my bathymetry source raster (tiff file) has a field value_0
>> which contains the depth in meters. I've got a classification
>> on the raster on value_0.
>>
>> When doing a WCS GetCoverage request, I get out a Geotiff
>> raster, but it contains value_0, value_1 and value_2 with the
>> R G B values respectively.
>>
>> Is there a way to preserve the original attribute in the output tiff?
>>
>> TIA.
>>
>> Best regards,
>> Bart
>>
>> ___
>> 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

Re: [mapserver-users] WCS GetCoverage question

[Rahkonen Jukka]

Hi,

How does your WCS request look like and how have you defined the GeoTIFF
output format?

-Jukka Rahkonen-

> bart...@osgis.nl wrote:
> 
> Hi list,
> 
> my bathymetry source raster (tiff file) has a field value_0 
> which contains the depth in meters. I've got a classification 
> on the raster on value_0.
> 
> When doing a WCS GetCoverage request, I get out a Geotiff 
> raster, but it contains value_0, value_1 and value_2 with the 
> R G B values respectively.
> 
> Is there a way to preserve the original attribute in the output tiff?
> 
> TIA.
> 
> Best regards,
> Bart
> 
> ___
> 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

[mapserver-users] WCS GetCoverage question

[bartvde]

Hi list,

my bathymetry source raster (tiff file) has a field value_0 which contains
the depth in meters. I've got a classification on the raster on value_0.

When doing a WCS GetCoverage request, I get out a Geotiff raster, but it
contains value_0, value_1 and value_2 with the R G B values respectively.

Is there a way to preserve the original attribute in the output tiff?

TIA.

Best regards,
Bart

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

Re: [mapserver-users] WCS Elevation and Edge Matching

[jasonbeverage]

Hi all,

I figured out what the issue was this morning.  I realized I needed to
expand the bounding box of each tile by half a pixel on all sides so that
the elevation values on the tile edges would line up with the CENTER of the
pixel rather than the edges.

Thanks and sorry for the noise!

Jason


jasonbeverage wrote:
> 
> Hi all,
> 
> I'm working on the osgEarth (http://www.osgearth.org) WCS plugin and I'm
> trying to connect to MapServer as a WCS to access SRTM data.
> 
> Things look great for the most part, but I'm having issues that tile edges
> don't line up exactly, the elevations are slightly off.  I am specifying
> bilinear resampling in the map file via PROCESSING "RESAMPLE=BILINEAR".
> 
> The edges of the bounding boxes I'm specifying should be lining up exactly
> with the neighboring tiles.
> 
> The SRTM I am using is a single tiled geotiff with overviews.
> 
> Are there any tricks to getting the edges of the tiles to match up
> exactly?
> 
> Thanks!
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/WCS-Elevation-and-Edge-Matching-tp2752933p2754493.html
Sent from the Mapserver - User mailing list archive at Nabble.com.

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

[mapserver-users] WCS Elevation and Edge Matching

[Jason Beverage]

Hi all,

I'm working on the osgEarth (http://www.osgearth.org) WCS plugin and I'm
trying to connect to MapServer as a WCS to access SRTM data.

Things look great for the most part, but I'm having issues that tile edges
don't line up exactly, the elevations are slightly off.  I am specifying
bilinear resampling in the map file via PROCESSING "RESAMPLE=BILINEAR".

The edges of the bounding boxes I'm specifying should be lining up exactly
with the neighboring tiles.

The SRTM I am using is a single tiled geotiff with overviews.

Are there any tricks to getting the edges of the tiles to match up exactly?

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