WCS client: small corrections

[Peter Baumann]

• there should be a way to select the protocol (GET, POST, SOAP, REST); can be packaged into a section "protocol binding extension"
• going to ​http://ows.rasdaman.org/rasdaman/ows and doing a GetCapabilities I can pick any functionality except GetCoverage. Obviously doing a DescibeCov first is required by the client. This should not be the case.

• HTML title says "petascope web client", should be: "rasdaman OGC Web service client"

Please fix asap as in Testbed 12 it will be used by the OGC experts.

[Alex Toader]

At the moment the client sends queries as KVP and works with the returned XML. SOAP is not supported natively by the browser, and adding support will require around 40 hours of work.

The controls on the GetCoverage tab require the user to select a coverage. If I just enable the tab, it will be blank until the user selects a coverage in the GetCapabilities tab or on the DescribeCoverage tab. Do you want to add a text box from which the user can select a coverage on the GetCoverage tab? The interaction will be as follows:

1. The user navigates to the OGC Web client.
2. The user selects the GetCoverage tab which is blank.
3. The user types in a coverage name into the text box and presses a button to retrieve the coverage information.
4. The GetCoverage tab is populated with information from the coverage and the user can do slicing, trimming etc.
5. The user presses Download Coverage to get the coverage.

Does that sound better? Please advise.

[Peter Baumann]

thanks for detailing. Based on this,

• allow GetCoverage with id selection as described above, it will simplify the client interaction's state automaton significantly.
• postpone SOAP support by the client.

[Dimitar Misev]

Vlad you could forward this to Nate perhaps.

[Bang Pham Huu]

I wanted to learn AngularJS so assign to me.

[Bang Pham Huu]

now web client can access the GetCoverage directly instead of DescribeCoverage then GetCoverage, close ticket as patch was accepted.