Hi,
It would be much easier for us if you can repeat the issue with some of the Geoserver demo layers. Without your data we are somewhat blind.
Do you get correct pixel size with WCS 1.0.0 and resx + resy? I have not played at all with WCS 1.1.0 yet and I not know when GridOffsets can be expressed with two numbers and when it should have four. Have you alreasy tried GroDOffsets=0.008333,0,0,-0.008333?
-Jukka Rahkonen-
Kytt MacManus wrote:
Hello and good day,
I have what I think is a simple question. I am trying to make a WCS
1.1.1 GetCoverage request to a Geoserver running version 2.5
http://sedac.ciesin.columbia.edu/geoserver/ows?SERVICE=WCS&VERSION=1.1.
1&REQUEST=GetCoverage&IDENTIFIER=species-v1-global-amphibian-family-
richness&FORMAT=image%2Ftiff&BOUNDINGBOX=42.0,16.0,45.5,18.5,urn:ogc:
def:crs:EPSG:4326&RangeSubset=contents&GridOffsets=0.008333,0.008333
For some reason the TIFF that is returned has an irregular cell size of:
0.005952381, 0.011666667
The expected cell size are the contents of GridOffsets=0.008333,0.008333
What am I doing wrong?
Many thanks,
Kytt
--
Kytt MacManus
Geographic Information Specialist
CIESIN
Earth Institute
Columbia University
Adjunct Lecturer
School of International and Public Affairs Columbia University
P.O. Box 1000
61 Route 9W
Palisades, NY 10964
845-365-8939 (V)
845-365-8922 (F)
www.ciesin.columbia.edu
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Good catch Jukka.
Kytt, your grid definition is citing this default grid type: 2dGridIn2dCrs
That means you’d have to use 4 values for your offsets. Also, keep your sign on the numbers. The grid knows how it’s defined. You can see this by describing the coverage. (The DescribeCoverage operation.) Typically you’ll have a step to the right and a step down as most grids seem to have an origin in the top left corner. So the next node would be down and to the right. If you want to use two values, you’d have to provide a GridType to the request and use 2dSimpleGrid. Then you can omit the 0,0 part of the GridOffsets. I’m not sure if that works in GeoServer or not, so YMMV.
Just take a look at the WCS 1.1.0 specification, page 47 for some hints.
Tim
···
On 04/09/2014 11:26 AM, Rahkonen Jukka (Tike) wrote:
Hi,
It would be much easier for us if you can repeat the issue with some of the Geoserver demo layers. Without your data we are somewhat blind.
Do you get correct pixel size with WCS 1.0.0 and resx + resy? I have not played at all with WCS 1.1.0 yet and I not know when GridOffsets can be expressed with two numbers and when it should have four. Have you alreasy tried GroDOffsets=0.008333,,0,0,-0.008333?
-Jukka Rahkonen-
Kytt MacManus wrote:
Hello and good day,
I have what I think is a simple question. I am trying to make a WCS
1.1.1 GetCoverage request to a Geoserver running version 2.5
[http://sedac.ciesin.columbia.edu/geoserver/ows?SERVICE=WCS&VERSION=1.1](http://sedac.ciesin.columbia.edu/geoserver/ows?SERVICE=WCS&VERSION=1.1).
1&REQUEST=GetCoverage&IDENTIFIER=species-v1-global-amphibian-family-
richness&FORMAT=image%2Ftiff&BOUNDINGBOX=42.0,16.0,45.5,18.5,urn:ogc:
def:crs:EPSG:4326&RangeSubset=contents&GridOffsets=0.008333,0.008333
For some reason the TIFF that is returned has an irregular cell size of:
0.005952381, 0.011666667
The expected cell size are the contents of GridOffsets=0.008333,0.008333
What am I doing wrong?
Many thanks,
Kytt
--
Kytt MacManus
Geographic Information Specialist
CIESIN
Earth Institute
Columbia University
Adjunct Lecturer
School of International and Public Affairs Columbia University
P.O. Box 1000
61 Route 9W
Palisades, NY 10964
845-365-8939 (V)
845-365-8922 (F)
[www.ciesin.columbia.edu](http://www.ciesin.columbia.edu)
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
[http://tv.slashdot.org/](http://tv.slashdot.org/)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
[http://tv.slashdot.org/](http://tv.slashdot.org/)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
–
Tim Astle
Development Manager
Web Technologies
CARIS
115 Waggoners Lane
Fredericton, New Brunswick
Canada E3B 2L4
Tel: +1.506.458.8533 Fax: +1.506.459.3849
www.caris.com
Connect with CARIS
Twitter | LinkedIn | Facebook | Google+ | YouTube
Download your free copy of CARIS Easy View today!
www.caris.com/easyview
This email and any files transmitted with it are confidential and intended only for the addressee(s). If you are not the intended recipient(s) please notify us by email reply. You should not use, disclose, distribute or copy this communication if received in error.
Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the company. No binding contract will result from this email until such time as a written document is signed on behalf of the company.