Web Map Service 1.1.1 Compliance Test - Executive Summary

1. Scope

This document describes the test suite for the Web Map Service 1.1.1 specification (01-068r3).

2. Test Requirements

The WMS test suite defines two test profiles, Basic and Queryable.

  • Basic - A Basic WMS implementation must meet the following requirements in addition to meeting the minimum requirements of the WMS spec.

    • It must support image/png or image/gif for GetMap requests.

    • It must contain the CITE dataset in layers that are subsetable and resizable and support EPSG:4326.

    • The EPSG:4326 support must be precise up to the ten-thousandth of a degree.

    • The default style for the cite:Lakes layer must fill in the polygon with non-white pixels.

  • Queryable - A Queryable WMS implementation must meet the following requirements in addition to meeting the requirements for the Basic profile.

    • GetFeatureInfo requests must be supported

    • The CITE dataset layers that contain polygons must be queryable.

WMS implementations which don't implement the requirements for either profile may still be tested, but many of the available tests may not apply. For example, most of the GetMap and GetFeatureInfo tests depend on the CITE dataset and will not be executed if the dataset is not properly loaded. One of the profiles must be supported for an implementation to receive a certification mark.

3. Test Data

The majority of the CITE standard dataset for WMS is based on the Conformance Test Guidelines for OpenGIS Simple Features Specification for SQL. This set of features makes up a map of a fictional location called Blue Lake. The features have been converted to WGS84 coordinates and have been reoriented so the area is centered at 0 degrees latitude, 0 degrees longitude. Figure 1 shows an overview map of the area with the prominent features labeled. Figure 2 shows the location of each of the data points.

Figure 1. Overview of Blue Lake vicinity features

Overview of Blue Lake vicinity features

Figure 2. Blue Lake vicinity data points

Blue Lake vicinity data points

Additional features have also been defined to test data at a larger scale. These consist of a diamond and two overlapping squares, as shown in figure 3. It does not matter which square appears on top.

Figure 3. Basic Polygon Features

Basic Polygon Features

The features are organized into layers as shown in table 1. The layers may be named in any fashion, but must be titled exactly as shown in the table below.

Table 1. CITE Dataset Layers

Layer TitleFeatures Contained
cite:BasicPolygonsContains all the featrues shown in figure 3
cite:BridgesContains Cam Bridge
cite:BuildingsContains the two buildings along Main Street
cite:DividedRoutesContains both lanes of Route 75
cite:ForestsContains the State Forest polygon
cite:LakesContains Blue Lake
cite:MapNeatlineContains the border surrounding the Blue Lake vicinity
cite:NamedPlacesContains Ashton and Goose Island
cite:PondsContains both pools of Stock Pond
cite:RoadSegmentsContains all the sections of Route 5, Main Street, and the dirt road
cite:StreamsContains Cam Stream and the unnamed stream south of Blue Lake

A sample capabilities document which implements these layers is available at http://cite.opengeospatial.org/OGCTestData/wms/1.1.1/data/WmsCapabilities.xml. The dataset is available in GML, MapInfo Interchange Format, and ESRI Shapefile format and can be downloaded from http://cite.opengeospatial.org/OGCTestData/wms/1.1.1/data/WmsTestData.zip.

4. Assumptions

In some cases, the WMS 1.1.1 specification is a bit ambiguous. Where additional interpretation is needed, the tests described in this document assume the following:

  • The root Layer in the capabilities document must contain at least one SRS element.

  • Scientific notation is allowed in the LatLonBoundingBox element.

  • If the INFO_FORMAT parameter is not explicitly stated on a GetFeatureInfo request, the response must still be one of the formats advertised in the GetFeatureInfo Request section of the capabilities document.

  • For resizable layers, servers must be able to generate maps as large as 1024x768 and as small as 8x5.

A. WMS 1.1.1 Conformance Test Report

1. Summary

This section summarizes the testing results. It lists URL of the WMS tested, the Profile tested (Basic, Queryable, or None), and the overall result and score. The result will be PASSED if all of the tests passed, FAILED if any of the tests failed, or Incomplete if none of the tests failed, but some of them have not been executed. The score will be (# of tests passed) / (total # of tests), or Incomplete if any of the tests have not been executed.

Capabilities URLhttp://hostname/wms?service=WMS&version=1.1.1&request=GetCapabilities

2. Automatically Selected Tests

This section details results for tests which are automatically selected by the test engine based on the capabilities advertised by the server and the profile chosen by the user. If none of the tests in the Test Group applies to the server tested, the Result and Score will be "Not Tested".

Test GroupResultScore
Profile Requirements  
Basic Service Elements  
GetCapabilities Request  
GetMap Request  
GetFeatureInfo Request  
Handling Multi-Dimensional Data  

3. Optional Tests

This section details results for the optional tests which the user may have selected to execute when the test session was set up. For each group of tests the user did not select to run, the Result and Score will be "Not Tested".

Test GroupResultScore
Recommendation Support  
GML FeatureInfo  
Fees and Access Constraints  
STRICT BoundingBox Constraint  
LOOSE BoundingBox Constraint  

4. Formats

This section lists various formats which are commonly used in WMS implementations, whether the test server reports that it supports the format, and whether it actually does or not.

Format TypeFormatReportedActual