Hi Birgit,
It seems that there are 3 issues.
- Envelope has wrong axis order for EPSG:3857, northing is first in <gml:lowerCorner>6113175.5 1167595.0</gml:lowerCorner> and easting after that, but is should be another way round.
- Axis labels are X and Y and they should mean the first and second axis in the envelope. However, if you use slice point X= 6150000 and you get "SlicePoint outside coverage envelope" error it most probably means that GeoServer is checking against the second, easting, axis, which has label Y in the envelope.
- When you give the slice point as Y and Geoserver is testing it against Northing, which is the right thing to do, it is assuming that 6150000 means degrees latitude instead of 6150000 meters N in EPSG:3857.
You can perhaps get over the third error by explaining that your slice point is in EPSG:3857. Unfortunately the POST bindings document OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension does not give an example about how to do that. The KVP binding document OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension does have examples about how to define spatial subset in certain projection:
&subset=lon,http://www.opengis.net/def/crs/EPSG/0/4326(-71,47)
But finally from a third document OGC® Web Coverage Service Interface Standard - CRS Extension you can find how to tell which projection is used in subsetting:
<wcs:Extension>
<wcscrs:subsettingCrs>
http://www.opengis.net/def/crs/EPSG/0/4326
</wcscrs:subsettingCrs>
<wcscrs:outputCrs>
http://www.opengis.net/def/crs/EPSG/0/4326
</wcscrs:outputCrs>
</wcs:Extension>
But because EPSG:3857 is the nativeCRS of your coverage your original request should work without defining subsettingCrs once you have overridden wrong axis labels and envelope. I think that your requests are correct but Geoserver has one or more bugs.
-Jukka Rahkonen-
-----Alkuperäinen viesti-----
Lähettäjä: Birgit Wunschheim | GAF AG [mailto:birgit.wunschheim@…1115…]
Lähetetty: 18. elokuuta 2015 12:45
Vastaanottaja: Rahkonen Jukka (MML); geoserver-users@lists.sourceforge.net
Aihe: AW: [Geoserver-users] BoundingBox axis troubles with WCS 2.0.1
Hi Jukka,
The DescribeCoverage request returned:
...
-<gml:EnvelopeWithTimePeriod srsDimension="2" uomLabels="m m s"
axisLabels="X Y time" srsName="http://www.opengis.net/def/crs/EPSG/0/3857">
<gml:lowerCorner>6113175.5 1167595.0</gml:lowerCorner>
<gml:upperCorner>6218105.0 1264624.625</gml:upperCorner>
<gml:beginPosition>2015-08-10T00:00:00.000Z</gml:beginPosition>
<gml:endPosition>2015-08-12T23:00:00.000Z</gml:endPosition>
...
<gml:sequenceRule axisOrder="+2 +1">Linear</gml:sequenceRule>
<gml:startPoint>0 0</gml:startPoint>
...
The GetCoverage Request is as follows:
// POST
http://localhost:8080/geoserver/wcs?SERVICE=WCS&Version=2.0.1&REQUEST=GetCoverage
<?xml version="1.0" encoding="UTF-8"?>
<wcs:GetCoverage xmlns:wcs="http://www.opengis.net/wcs/2.0"
xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/wcs/2.0 http://schemas.opengis.net/wcs/2.0/wcsAll.xsd"
service="WCS" version="2.0.1">
<wcs:CoverageId>oyb__a3_all_fm</wcs:CoverageId>
<wcs:DimensionSlice>
<wcs:Dimension>X</wcs:Dimension>
<wcs:SlicePoint>6150000</wcs:SlicePoint>
</wcs:DimensionSlice>
<wcs:DimensionSlice>
<wcs:Dimension>Y</wcs:Dimension>
<wcs:SlicePoint>1190000</wcs:SlicePoint>
</wcs:DimensionSlice>
<wcs:format>application/gml+xml</wcs:format>
</wcs:GetCoverage>
The response exception is
"SlicePoint outside coverage envelope"
If I switch the axis, the response says:
"Failed to read the coverage oyb__a3_all_fm
org.geotools.referencing.operation.projection.ProjectionException: Latitude 6149640°00.0&apos;N is too close to a pole.
Latitude 6149640°00.0&apos;N is too close to a pole.
"
It seems to me that the WebMercator Projection could be an issue here. Is this a known behaviour?
The WMS-T - which is based on the same image mosaic data - is working fine.
Best,
Birgit
-----Ursprüngliche Nachricht-----
----------------------------------------------------------------------------
Birgit Wunschheim
GAF AG | Arnulfstr. 199 | 80634 Munich | Germany
Phone: +49 89 121528 877 | Fax: +49 89 121528 79
mailto:birgit.wunschheim@…1115… | http://www.gaf.de
CEO: Dr. Peter Volk, Chairman of the supervisory board: Marcello Maranesi
Place of business: Munich, Magistrate's court Munich HRB 140 509
WARNING: This message contains confidential and/or proprietary information which may be subject to privilege or immunity and which is intended for the use of its addressee only. Should you receive this message in error, you are kindly requested to inform the sender and to definitively remove it from any paper or electronic format. Any other use of this e-mail is strictly forbidden. Thank you in advance for your cooperation.
Von: Rahkonen Jukka (MML) [mailto:jukka.rahkonen@…6847…]
Gesendet: Donnerstag, 13. August 2015 15:56
An: Birgit Wunschheim | GAF AG <birgit.wunschheim@...1115...>; geoserver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] BoundingBox axis troubles with WCS 2.0.1
Hi,
Could you show us the whole GetCoverage request? A "valid slice" is not accurate enough for trying to repeat your issue.
-Jukka Rahkonen-
GEOSurfer wrote:
Hi,
I have exactly the same Problem with Geoserver V2.5.3. The WCS 2.0.1 DescibeCoverage request retrieves:
...
-<gml:EnvelopeWithTimePeriod srsDimension="2" uomLabels="m m s"
axisLabels="X Y time" srsName="http://www.opengis.net/def/crs/EPSG/0/3857">
<gml:lowerCorner>6113175.5 1167595.0</gml:lowerCorner>
<gml:upperCorner>6218105.0 1264624.625</gml:upperCorner> <gml:beginPosition>2015-08-10T00:00:00.000Z</gml:beginPosition>
<gml:endPosition>2015-08-12T23:00:00.000Z</gml:endPosition>
...
<gml:sequenceRule axisOrder="+2 +1">Linear</gml:sequenceRule>
<gml:startPoint>0 0</gml:startPoint>
...
Requesting a valid slice results in an exception "Empty intersection after subsetting".
If I change the axis, I get a "Failed to read the coverage
org.geotools.referencing.operation.projection.ProjectionException:
Latitude 6149640°00.0&apos;N is too close to a pole. "
Hope someone can help.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/BoundingBox-axis-troubles-with-WCS-2-0-1-tp5218757p5219329.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users