Web Coverage Service 1.0.0 Compliance Tests - Executive Summary


Table of Contents

1. Scope
2. Test overview
a. Manual Test Scopes
b. Automated Test Scopes

The tests performed against an implementation are selected based on the capabilities document for the WCS implementation. By omitting a request, operation or capability from the capabilities document the tests for that functionality will not be executed against the implementation. The test suite makes a few basic assumptions about the WCS:

  • That there are at least two coverages provided by the tested server.
  • The first coverage offering should include all the tested features while the second coverage could be any thing.
  • The first coverage offering must take one of the 5 formats described in the WCS1.0.0 standard document as the first supported format.
  • The first coverage offering should have parameters defined in the axisDescription.
  • If the xml encoding is tested, the first coverage offering should have interpolation method defined.
  • If the server support time position, the first coverage offering should define time feature.

There is no standard MIME header definitions for the 5 required formats. Thus the actual MIME header depends on the server. The assertion test will check the results based on the first available format for the first coverage. A MIME header value should be entered during session configuration.

The WCS spec allows servers to use an UpdateSequence value for maintaining cache consistency. If the server advertises an UpdateSequence value then values that are lexically higher and lower than the current updateSequence value should be entered during session configuration.

Those values are required to test GetCoverage with parameter RESX and RESY. The values depends on the crs provided by the first offering. Values for RESX and RESY should be entered during session configuration.