Notice: The Legacy CITE Engine (Open Group Engine) will be retired on 1 December 2009.
Web Coverage Service 1.0.0 Compliance Tests - Executive Summary
Table of Contents
- 1. Scope
- 2. Test overview
The purpose of this document is to provide a summary of the conformance test suite for the OGC Web Coverage Service 1.0.0 specification. This information is intended to assist WCS implementors running the tests against their products and WCS users in undestanding the conformance test report for WCS implementations and the capabilities they offer.
The conformance tests are performed using the OGC conformance test engine with a suite of test scripts and data for each specification. For each version of the specification a new test suite will be developed to add additional tests for new functionality. The WCS implementors use the test engine to run the test scripts against a test server and the test engine records the results of each test.
This document describes the test suite for the Web Coverage Service 1.0.0 specification.
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.
To verify that the server supports XML encoding, the checkbox labeled "Verify that the server supports XML encoding" should be checked during session configuration.
Verify that the server supports XML encoding.
To verify that the server supports axis description encoding, the checkbox labeled "Verify that the server supports range set axis" should be checked during session configuration.
Verify that the server supports range set axis.
The following test scopes will be tested automatically:
- HTTP GET is a mandatory test
- If HTTP POST appears in the capabilities document, HTTP POST will be tested.
- If updateSequence appears in the capabilities document, updateSequence is tested.
- If timePosition appears in the capabilities document, time is tested.
Posted May 23rd, 2007 by webmaster