Opened 8 years ago
Last modified 8 years ago
#1508 closed defect
Petacope_AcceptVersions in WCS requests — at Initial Version
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.4 |
Component: | petascope | Version: | development |
Keywords: | WCS AcceptVersions, version | Cc: | Peter Baumann, Dimitar Misev, Vlad Merticariu |
Complexity: | Medium |
Description
From OGC document https://portal.opengeospatial.org/files/09-148r1, WCS request in XML should have a request like this
GetCapabilities Requirement 3 /req/post-xml/getCapabilities-request-structure: A GetCapabilities request using POST/XML shall consist of an XML document of type wcs:GetCapabilities. Example The following is a minimum GetCapabilities request encoded in XML: <?xml version="1.0" encoding="UTF-8"?> <GetCapabilities xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:wcs="http://www.opengis.net/wcs/2.0" xsi:schemaLocation= "http://schemas.opengis.net/wcs/2.0 ../wcsAll.xsd" service="WCS"> <ows:AcceptVersions> <ows:Version>2.0.0</ows:Version> </ows:AcceptVersions> </GetCapabilities>
It was fixed in WCS XML Parser to accept this format, but with KVP Request it uses the request like this
service=WCS&version=2.0.1&request=GetCapabilities
As Petascope only supports WCS version 2.0.1.
However, with some checks with WCS implementation provider
MapServer: http://mapserver.org/de/ogc/wcs_server.html#wcs-2-0
# GetCapabilities http://www.yourserver.com/wcs?SERVICE=WCS&ACCEPTVERSIONS=1.0.0,2.0.1 &REQUEST=GetCapabilities http://www.yourserver.com/wcs?SERVICE=WCS&REQUEST=GetCapabilities
and an INSPIRE guidance technical document
http://inspire.ec.europa.eu/file/1635/download?token=7m3PXp4a
http://myserver.ac.uk/some/folders/ows? service=WCS& request=GetCapabilities& AcceptVersions=2.0.1, 2.0.0&
it shows that version in KVP request should be change to AcceptVersions (even Petascope only supports WCS 2.0.1).