Sorry, previouos message was not ready. I meant to ask if it is possible that Geoserver sends GridOrigin and GridOffset with faulty axis order and therefore GDAL is using the same values and gets into troubles.
wcs:GridOrigin-116.91699999999997 32.5833351</wcs:GridOrigin>
wcs:GridOffsets0.16666667 0.0 0.0 -0.16666667</wcs:GridOffsets>
-Jukka-
···
I wonder one thing. If you run this
http://193.175.162.189/geoserver/wcs?request=DescribeCoverage&identifiers=raster_example_20130208_113005_078&VERSION=1.1.0
You will see
wcs:SpatialDomain>
<ows:BoundingBox crs=“urn:ogc:def:crs:EPSG::4326” dimensions=“2”>
ows:LowerCorner-55.833333335 -117.00033333499998</ows:LowerCorner>
ows:UpperCorner32.666668435 -34.66699835499999</ows:UpperCorner>
</ows:BoundingBox>
wcs:GridCRSwcs:GridBaseCRSurn:ogc:def:crs:EPSG::4326</wcs:GridBaseCRS>
wcs:GridTypeurn:ogc:def:method:WCS:1.1:2dGridIn2dCrs</wcs:GridType>
wcs:GridOrigin-116.91699999999997 32.5833351</wcs:GridOrigin>
wcs:GridOffsets0.16666667 0.0 0.0 -0.16666667</wcs:GridOffsets>
wcs:GridCSurn:ogc:def:cs:OGC:0.0:Grid2dSquareCS
</wcs:GridCS></wcs:GridCRS>
</wcs:SpatialDomain>
So Geoserver is sending coordinates in lat-lon order for the GridOrigin. I can see that GDAL is automatically adding quite a lot metadata to the WCS.XML configuration file and this same GridOrigin gets saved also to there.
Lähettäjä: andrea.aime@anonymised.com [mailto:andrea.aime@anonymised.com] Puolesta Andrea Aime
Lähetetty: 8. helmikuuta 2013 15:07
Vastaanottaja: Rahkonen Jukka
Kopio: rob-news@anonymised.com; geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] Issue with noValue in WCS coverageOfferings
On Fri, Feb 8, 2013 at 1:08 PM, Rahkonen Jukka <jukka.rahkonen@anonymised.com> wrote:
Hi,
What really happens when you run gdalinfo is that it tries to capture a small image for further investigations.
The request isGET /geoserver/wcs?SERVICE=WCS&VERSION=1.1.0&REQUEST=GetCoverage&IDENTIFIER=raster_example_20130208_113005_078&FORMAT=image%2Ftiff%3Bsubtype%3D%22geotiff%22&BOUNDINGBOX=-116.917,32.41666843,-116.75033333,32.5833351,urn:ogc:def:crs:EPSG::4326&RangeSubset=contents HTTP/1.1
Host: 193.175.162.189
Accept: /
Accept-Encoding: gzip
Proxy-Connection: Keep-AliveGeoserver does not like the request and it sends an error message which is
<?xml version="1.0" encoding="UTF-8"?><ows:ExceptionReport version=“1.1.0”
xsi:schemaLocation=“http://www.opengis.net/ows/1.1 http://193.175.162.189:80/geoserver/schemas/ows/1.1.0/owsAll.xsd”
xmlns:ows=“http://www.opengis.net/ows/1.1” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<ows:Exception exceptionCode=“NoApplicableCode”>
ows:ExceptionTextjava.lang.IllegalArgumentException: The specified dimensional parameter is non-positive.
The specified dimensional parameter is non-positive.</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>Reason for the failure seems to be in BOUNDINGBOX=-116.917,32.41666843,-116.75033333,32.5833351,urn:ogc:def:crs:EPSG::4326
Reverse the lon-lat coordinates into lat-lon, and the request works.If Geoserver folks will tell that the GDAL WCS 1.1.0 request is wrong then you can try to get an answer to question b) by sending a question with this information into GDAL developer mailing list.
Yes, WCS 1.1 has swapped axis just like WFS 1.1.
See this table, it applies to WCS 1.1 as well:
http://docs.geoserver.org/latest/en/user/services/wfs/basics.html#axis-ordering
Given that as usual servers tend to implement axis swapping inconsistently (or not at all)
a probably wise move on the GDAL side would be to allow the user to manually
control which CRS to handle as swapped, and which not.
Cheers
Andrea
–
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://twitter.com/geosolutions_it