Petascope gives error when valid OWS Common parameter is suppled as part of request

[jpass@…]

The WCS 2.0 Core (OGC 09-110r3) document indicates that valid GetCapabilities request parameters are those identified as such in OWS Common (OGC 06-121r9). One such parameter is 'sections'.

The server implementation note (for the section parameter in OWS Common (OGC 06-121r9)) states "When omitted or not supported by server, return complete service metadata document"

A request to the petascope service with a sections parameter like:

​http://earthserver.bgs.ac.uk/petascope?service=WCS&Request=GetCapabilities&version=2.0.0&sections=All

Does not follow the implementation rule and instead returns error:

<ows:ExceptionReport version="2.0.0" xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">
<ows:Exception locator="sections" exceptionCode="InvalidEncodingSyntax">
<ows:ExceptionText>
Document received does not conform with protocol syntax </ows:ExceptionText> </ows:Exception> </ows:ExceptionReport>

[Peter Baumann]

this traces back to an inconsistency introduced by OWS Common 2.0. It is on the table of OGC, but nobody addresses it currently. Seems we have to find a way forward by ourselves. As EOX is engaged in this issue, let's put our minds together.

[Dimitar Misev]

Not sure if this is still valid?

[James Passmore]

Well the issue still exists for Rasdaman 9.0.3

A request like:

​http://earthserver.bgs.ac.uk/rasdaman/ows?service=WCS&Request=GetCapabilities&version=2.0.1&sections=All&

Gives an error.

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<ows:ExceptionReport xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows/2.0" xsd:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" version="2.0.0">
<ows:Exception exceptionCode="InvalidEncodingSyntax" locator="sections">
<ows:ExceptionText>Document received does not conform with protocol syntax</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

As the sections parameter is not supported by the service we should instead get a standard GetCapabilities response and not an error.

[Bang Pham Huu]

Close as patch was accepted, thanks.