Open Geospatial Consortium
Submission Date: 2015-02-10
Approval Date: 2015-05-29
Publication Date: 2016-01-29
External identifier of this OGC® document: http://www.opengis.net/doc/BP/dgiwg-wms1.3-profile/2.0
Internal reference number of this OGC® document:

OGC 09-102r3
Version: 2.0

Category: OGC® Best Practice
Editors: Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey

DGIWG – Web Map Service 1.3 Profile – Revision
Copyright notice
Copyright © 2016 Open Geospatial Consortium
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/.
Warning
This document defines an OGC Best Practices on a particular technology or approach related to an
OGC standard. This document is not an OGC Standard and may not be referred to as an OGC
Standard. It is subject to change without notice. However, this document is an official position of the
OGC membership on this particular technology topic.

Document type:
Document subtype:
Document stage:
Document language:

OGC Best Practice
ProfileApproved
EnglishLicense Agreement
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth below, toany person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without
restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute,
and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided
that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnishedagrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyrightnotice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTS THAT
MAY BE IN FORCE ANYWHERE IN THE WORLD.
THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THISNOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE INTELLECTUAL PROPERTY WILL MEET YOURREQUIREMENTS OR THAT THE OPERATION OF THE INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR
FREE. ANY USE OF THE INTELLECTUAL PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO
EVENT SHALL THE COPYRIGHT HOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THEINTELLECTUAL PROPERTY BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE,DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY,ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION OR PERFORMANCE OF
THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies inany form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in thefollowing sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual
Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of theIntellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third
party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, yourlicensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together
with all copies in any form, whether held by you or by any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property
shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written
authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any
third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or
specifications. This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of theUnited Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of thisAgreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as
so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to
be a waiver of any rights or remedies available to it.

DGIWG – 112
DGIWG – Web Map Service 1.3 Profile – Revision
Document type:
Document subtype:
Document date:
Edition number:Supersedes:
Responsible Party:
Audience:
Abstract:

Copyright:

Standard
Implementation Profile
16 November 2015
2.1.0
This document supersedes DGIWG – 112 Ed. 2.0.0, Web
Feature Service (WFS) Profile, dated 04 February 2015.
DGIWG
DGIWG participants and liaisonsThis document defines specific DGIWG requirements,
recommendations and guidelines for implementations of the
ISO and OGC Web Map Service standards; ISO 19128:2005
Web Map Server Interface and the OpenGIS Web Map Server
Implementation Specification 1.3.0.
(C) Copyright DGIWG, some rights reserved - (CC) (By:) Attribution

You are free:- to copy, distribute, display, and perform/execute the work
- to make derivative works- to make commercial use of the work
Under the following conditions:- (By:) Attribution. You must give the original author (DGIWG)
credit.
- For any reuse or distribution, you must make clear to others
the license terms of this work.
Any of these conditions can be waived if you get permission fromthe copyright holder DGIWG.
Your fair use and other rights are in no way affected by theabove.
This is a human-readable summary of the Legal Code (the fulllicenseisavailable
from
Creative
Commons<http://creativecommons.org/licenses/by/2.0/ >).

STD-DP-14-013r3

16 November 2015

Table of Contents
1.

INTRODUCTION ..................................................................................................................................... 1

2.

SCOPE ........................................................................................................................................................ 2

3.

CONFORMANCE ...................................................................................................................................... 2

4.

NORMATIVE AND INFORMATIVE REFERENCES .......................................................................... 2

4.1.

NORMATIVE REFERENCES .............................................................................................................. 2

4.2.

INFORMATIVE REFERENCES .......................................................................................................... 3

5.

TERMS, DEFINITIONS, AND ABBREVIATIONS .............................................................................. 3

5.1.

DEFINITIONS ....................................................................................................................................... 3

5.2.

ABBREVIATIONS ................................................................................................................................ 36.

DGIWG WMS PROFILE (NORMATIVE) ............................................................................................ 6

6.1.

INTRODUCTION .................................................................................................................................. 6

6.2.

NORMATIVE REQUIREMENTS ........................................................................................................ 6

6.3.

NON-NORMATIVE RECOMMENDATIONS FOR IMPLEMENTATION .................................... 8

6.4.

SERVICE TYPE ..................................................................................................................................... 9

6.5.

BASIC SERVICE ELEMENTS.............................................................................................................. 9

6.5.1.

VERSION NUMBER.......................................................................................................................... 9

6.5.2.

BINDING ............................................................................................................................................ 9

6.5.3.

OUTPUT FORMATS ........................................................................................................................ 9

6.5.4.

COORDINATE SYSTEMS .............................................................................................................. 10

6.5.5.

REQUEST PARAMETER RULES ................................................................................................. 11

6.6.

OPERATIONS ..................................................................................................................................... 126.6.1.

GETCAPABILITIES OPERATION REQUEST ........................................................................... 126.6.2.

GETCAPABILITIES OPERATION RESPONSE ......................................................................... 126.6.3.

GETMAP OPERATION REQUEST .............................................................................................. 17

6.6.4.

GETMAP RESPONSE ..................................................................................................................... 19i

STD-DP-14-013r3

16 November 2015

6.6.5.

GETFEATUREINFO OPERATION REQUEST ........................................................................... 19

6.6.6.

GETFEATUREINFO RESPONSE.................................................................................................. 21

7.

QUALITY OF SERVICE ......................................................................................................................... 22

7.1.

PERFORMANCE ................................................................................................................................. 22

7.2.

CAPACITY ........................................................................................................................................... 22

7.3.

AVAILABILITY ................................................................................................................................... 22

ANNEX A – ABSTRACT TEST SUITE ........................................................................................................ 23
A.1 DGIWG SERVICE TYPE ......................................................................................................................... 23
A.1.1 DGIWG SERVICE TYPE ........................................................................................................................................ 23
A.1.2 DGIWG WMS BINDING ...................................................................................................................................... 23
A.1.3 DGIWG WMS OUTPUT FORMAT ....................................................................................................................... 23
A.1.4 DGIWG WMS CRS .............................................................................................................................................. 24
A.1.5 DGIWG WMS REQUEST PARAMETERS - EXCEPTIONS ................................................................................. 24
A.2 DGIWG WMS OPERATIONS ................................................................................................................ 24
A.2.1 DGIWG WMS GETCAPABILITIES REQUEST .................................................................................................... 24
A.2.2 DGIWG WMS GETCAPABILITES RESPONSE ................................................................................................... 24
A.2.3 DGIWG WMS GETMAP REQUEST .................................................................................................................... 25
A.2.4 DGIWG GETFEATUREINFO OPERATION REQUEST - FEATURE_COUNT .............................................. 26
A.2.5 DGIWG GETFEATUREINFO OPERATION REQUEST - EXCEPTIONS ......................................................... 26
A.2.6 DGIWG WMS GETFEATUREINFO RESPONSE................................................................................................. 26
ANNEX B – USE CASES ................................................................................................................................ 27
ANNEX C – EXAMPLES ................................................................................................................................ 29
ANNEX D – CLIENT REQUIREMENTS AND RECOMMENDATIONS ................................................. 35
ANNEX E – UTM GRID AND MGRS GRID SYSTEM HANDLING IN WMS CLIENTS AND
PORTALS ........................................................................................................................................................ 37ii

STD-DP-14-013r3

16 November 2015

List of Tables

Table 1: DGIWG WMS Profile Normative Server Requirements ............................................. 8
Table 2: DGIWG WMS Profile Non-normative Recommendations for Server Implementation8
Table 3: The parameters of a GetCapabilities request URL as per Normative Reference [1]............................................................................................................................................... 12
Table 4: Layer attributes ........................................................................................................ 16
Table 5: GetMap request parameters .................................................................................... 17
Table 6: GetFeatureInfo Request parameters ....................................................................... 20
Table 7: Normative client requirements ................................................................................. 36
Table 8: DGIWG WMS Profile Non-normative Recommendations for Client Implementation............................................................................................................................................... 36iii

STD-DP-14-013r3

16 November 2015

Executive Summary

This document defines specific DGIWG requirements, recommendations and guidelines for
implementations of the ISO / OGC Web Map Service standard which is based on ISO
19128:2005 Web Map Server Interface / OpenGIS Web Map Server Implementation
Specification 1.3.0.
ISO 19128: 2005 defines a Web Map Service as:"A Web Map Service (WMS) produces maps of spatially referenced data dynamically fromgeographic information. This International Standard defines a “map” to be a portrayal ofgeographic information as a digital image file suitable for display on a computer screen. A
map is not the data itself. WMS-produced maps are generally rendered in a pictorial format
such as PNG, GIF or JPEG, or occasionally as vector-based graphical elements in Scalable
Vector Graphics (SVG) or Web Computer Graphics Metafile (WebCGM) formats."
Previous versions of the WMS standard have not been considered in this profile.
The WMS Interface offers 3 Operations:
GetCapabilities (mandatory): Allows for obtaining Service Metadata
GetMap (mandatory): Returns a map
GetFeatureInfo (optional): Provides additional information about features in the
pictures of maps that were returned by previous GetMap requests
The WMS Implementation Specification defines two conformance classes, “Basic WMS” and“Queryable WMS”. The Basic WMS supports the mandatory GetCapabilities and GetMap
operations (requests and responses) whereas the Queryable WMS supports all Basic WMS
operations and the GetFeatureInfo operation. The DGIWG WMS profile mandates theimplementation of the Queryable WMS.
Software implementations that claim to be conformant with the DGIWG WMS profile shallsupport all mandatory operations, parameters and elements of the base standard, as wellas the specifically defined requirements in this document.
The DGIWG WMS profile references the different operations and parameters of the basestandard
andsubsequently
defines
specific
DGIWG
requirements
andrecommendations for software implementations to foster interoperability and use in the
military domain.

iv

STD-DP-14-013r3

i.

16 November 2015

Submitting organizations

For the Defence Geospatial Information Working Group (DGIWG):

NationParent organization

Germany

Bundeswehr Geoinformation Centre (BGIC)FranceInstitut Géographique National (IGN)

United States

National Geospatial-Intelligence Agency (NGA)

United Kingdom

Defence Science and Technology Laboratory (DSTL)

ii. Revision history
This document is a revision of OGC Best Practice 09-102 DGIWG WMS 1.3 Profile and systems
requirements for interoperability for use within a military environment (0.9.0). This document is alsoa revision of NGA.STND.0038_1.0.1_ WMS National System for Geospatial-Intelligence (NSG) OGC
Web Map Service 1.3 Interoperability Standard, version 1.0.1, 22 May 2013.

iii. Future work
A revision of WMS 1.3 is currently undertaken at the OGC. The revision will produce a version
1.4. WMS standard. This DGIWG WMS profile will be updated accordingly. Currently the WMS
2.0 Standards Working Group is working off several Change Requests including support for
JavaScript Object Notation (JSON) encoded GetFeatureInfo responses. This profile will be
updated to the new base standard version as requirements dictate.

v

STD-DP-14-013r3

16 November 2015

1. Introduction

This document defines specific DGIWG requirements, recommendations and guidelines for
implementations of the ISO / OGC Web Map Service standard which is based on ISO
19128:2005 Web Map Server Interface / OpenGIS Web Map Server Implementation
Specification 1.3.0.
A Web Map Service (WMS) produces maps of spatially referenced data dynamically fromgeographic information.
The OGC WMS Interface offers 3 Operations:
W GetCapabilities (mandatory): Allows for obtaining Service Metadata
W GetMap (mandatory): Returns a map
W GetFeatureInfo (optional): Provides additional information about features in the pictures ofmaps that were returned by previous GetMap requests
The WMS Implementation Specification defines two conformance classes, “Basic WMS” and“Queryable WMS”.
The Basic WMS supports the mandatory GetCapabilities and GetMap operations (requests andresponses) whereas the Queryable WMS supports all Basic WMS operations and the
GetFeatureInfo operation.
Software implementations that claim to be conformant with the DGIWG WMS profile shallsupport the Queryable WMS, as well as the specifically defined requirements in thisdocument.
The DGIWG WMS profile is written in such a way that it references the different operations andparameters of the base standard and then defines specific requirements for software
implementation.

1

STD-DP-14-013r3

16 November 2015

2. Scope

This document defines specific DGIWG requirements, recommendations and guidelines for
implementations of the ISO / OGC Web Map Service standard which is based on ISO
19128:2005 Web Map Server Interface / OpenGIS Web Map Server Implementation
Specification 1.3.0.

3. ConformanceThis document establishes one conformance class: DGIWG WMS. Annex A lists theconformance abstract tests which shall be exercised on any software artefact claiming to
implement a DGIWG WMS profile.
DGIWG WMS Profile conformance class defines requirements for WMS servers allowing
distribution of geographic data in a military environment.
Conformanceclass nameOperation or behavior

WMS Basic

The server shall implement the
Basic WMS conformance class

WMS
Queryable

The server shall implement the
Basic WMS conformance class

OGC WMS
Conformance
Test

A.1 Basic WMS

DGIWG WMS
Conformance
Test

A.2 QueryableWMS

DGIWG Requirement 1
DGIWG WMS

DGIWG requirements

Annex ADGIWG WMS Profile (normative)
Requirement 2 to Requirement 32

4. Normative and informative References
4.1. Normative references
ID

Title

Reference

Version[1]

OGC Web Map Service Implementation
Specification 1.3.0, 2006 (same as ISO 19128)

OGC 06-042

1.3.0

[2]

Best Practices for using OGC WMS with TimeDependent or Elevation-Dependent Data

12-111r1

1.0[3]

DGIWG Metadata Foundation

DGIWG – 114[4]

DGIWG Feature Data Dictionary, Baseline

2013-1.00

2

1.10 (72014)2013-1.00

STD-DP-14-013r3

16 November 2015

4.2. Informative References
Title

Reference

VersionDGIWG WMS 1.3 Profile and Systems Requirements forInteroperability for Use within a Military Environment,
STD-08-054-ED1.3, 2008.

OGC 09-102

0.9National System for Geospatial-Intelligence (NSG) OGC
Web Map Service 1.3 Interoperability Standard, 22 May
2013

NGA.STND.0038_1.
0.1_NSG_WMS_1 30_Interoperability_St
andard1.0.1

GBR Web Map Service Draft Implementation Profile for
WMS 1.3.0, 2012

1.0

DEU Web Map Service Draft Implementation Profile for
WMS 1.3.0

1.0

UK MOD CGTS Phase 2 Research Project - Core Profile
and Best Practice Guide for Use of OpenGIS Web Map
Service Version 1.3.0 in support of Military Operations,2011.

600\10012459\SPC\
63\1

OGC NSG Plugweek Engineering Report, 2010

OGC 09-140r2

OGC TESTBED 10 CCI Profile Interoperability
Engineering Report

OGC 14-021r2

OpenGIS Wrapping OGC HTTP-GET and -POST
Services with SOAP - Discussion Paper; dated: 2008-0124

OGC 07-158

1.0

3.0

NOTE: Implementers of the DGIWG WMS 1.3 Profile should verify all Reference documentsforlatesteditionagainsttheholdings
found
under
http://www.dgiwg.org/dgiwg/htm/documents/documents.htm, Open Geospatial Consortium(OGC) documents are located at: http://www.opengeospatial.org/standards andhttps://nsgreg.nga.mil/index.jsp

5. Terms, definitions, and abbreviations
5.1. Definitions

For the purposes of this document, terms and definitions found in WMS 1.3, ISO
19128:2005 / [OGC 06-042] apply.

5.2. Abbreviations
BBox

Bounding Box

CRS

Coordinate Reference System

CS

Coordinate System

CSW

Catalogue Service for the Web

DGIWG

Defence Geospatial Information Working GroupDFDD

DGIWG Feature Data Dictionary3

STD-DP-14-013r3

16 November 2015

DMF

DGIWG Metadata Framework

EPSG

European Petroleum Survey Group

FES

Filter Encoding Specification

FGDC

Federal Geographic Data Committee

GI

Georeferenced Information

GIF

Graphics Interchange Format

GeoInfGeospatial Information

GeoIntGeospatial Intelligence

GML

Geography Markup Language

GZIP

GNU Zip File format

HTTP

Hypertext Transfer Protocol

IETF

Internet Engineering Task Force

ISO

International Organization for Standardization

ISO/DISISO Draft International Standard

JPEG

Joint Photographics Expert GroupJSON

JavaScript Object Notation

KVP

Keyword Value Pairs

LAN

Local Area Network

MIME

Multipurpose Internet Mail Extension

NATO

North Atlantic Treaty Organization

NGIF

NATO Geospatial Information Framework

NSG

National System for Geospatial-Intelligence

OGC

Open Geospatial Consortium

OWS

OGC Web Service

PNG

Portable Network Graphics

SDI

Spatial Data Infrastructure

SOAP

Simple Object Access Protocol

SQL

Structured Query Language

SVG

Scalable Vector Graphics

UML

Unified Modelling Language

UPS

Universal polar stereographic coordinate system

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

URN

Uniform Resource Name

UTM

Universal Transverse Mercator

VSP

Vendor Specific Parameter

4

STD-DP-14-013r3

16 November 2015

WFS

Web Feature Service

WMS

Web Map Service

WMTS

Web Map Tile Service

WAN

Wide Area Network

WFS

Web Feature Service

WSDL

Web Services Description Language

XML

Extensible Markup Language

XPath

XML Path Language

XQueryXML Query5

STD-DP-14-013r3

16 November 2015

6. DGIWG WMS Profile (normative)
6.1. Introduction

A WMS that complies with the DGIWG WMS profile willa) satisfy all requirements stipulated in the OGC WMS 1.3.0 Specification;b) satisfy all requirements stipulated in this document.
This profile provides advice on the implementation of the WMS so that tests can beprovided to ensure objective compliance to the profile. The profile provides a “Normative
Clause” to describe how each component shall be implemented. The Normative Clausedefines requirements where mandatory compliance is required for attainment ofconformance. However, the profile also includes optional Recommendations which may
require a subjective test.
The following syntax is used to indicate the compliance requirement within the profile:
W Mandatory (M) – The requirement shall be implemented
W Conditional (C) – Mandatory when “If” statement applies
W Optional (O) – Should be implemented
Note: All Requirements and Recommendations presented within this document are theresult of information gathered during the DGIWG Nations questionnaire/survey process.
Implementers should be aware that certain requirements are unique to a national profilesuch as the metadata requirements for the US shall include conformance with the NSG
Metadata Framework while the DGIWG requires conformance with the DGIWG
Metadata Framework. These two metadata profiles have been synchronized to thefullest extent possible.

6.2. Normative Requirements

The Normative requirements requested by this profile are summarized in Table 1
No.
1
2
3
4
5

6

Requirement

A DGIWG WMS server shall be compliant to the Queryable WMS
conformance class.
A DGIWG WMS server shall support HTTP GET.
A DGIWG WMS server shall support text/xml and text/html as
output formats for the GetCapabilities and the GetFeatureInfo
Operations.
A DGIWG WMS server shall provide metadata content in a
response to a "GetCapabilities" or “GetFeatureInfo” request in
English language.
A DGIWG WMS server shall support the following raster formats
for the GetMap operation:
W image/png (Portable Network Graphics)
W image/gif (Graphics Interchange Format)
W image/jpeg (Joint Photographics Expert Group)
A DGIWG WMS server shall support the following coordinate
reference systems:
W CRS:84 WGS84 geographic longitude, then latitude, expressedin decimal degrees
W EPSG:4326 WGS84 geographic latitude, then longitude,
expressed in decimal degrees

6Compliance
M
M
M
M
M

M

STD-DP-14-013r3

16 November 201524

W EPSG:3395 World Mercator projection
Among the following Coordinate Reference Systems, the service
shall support all those which validity zone overlaps data publishedby the service:W UTM projections over WGS84 (north zones)… EPSG:32601 to
EPSG:32660
W UTM projections over
WGS84
(southzones)…
EPSG:32701 to EPSG:32760
W UPS projection over WGS84 (north zone)…… EPSG:32661
W UPS projection over WGS84 (south zone)…… EPSG:32761
A DGIWG WMS server shall provide service exceptions in English
language.
A DGIWG WMS server shall support all GetCapabilities request
parameters.
A DGIWG WMS server shall provide all mandatory and optional
service metadata elements.
A DGIWG WMS server shall identify the highest classification levelof the content accessible through the WMS service by populating
the wms:AccessConstraints element.
A DGIWG WMS server shall include the following information in
the abstract element of the service metadata: "This service
implements the DGIWG WMS 1.3 profile version 1.0."
A DGIWG WMS server shall provide a minimum keyword list
based on the DFDD groups.
A DGIWG WMS server shall provide information on the supported
styles.
A DGIWG WMS server shall always provide at least one styleelement and that style shall be advertised even if it's only thedefault style.
The MaxWidth and MaxHeight shall be greater or equal to 800
pixels.
Each vector data layer's style shall have an associated legend,available as an image in one of the following formats: PNG, GIF or
JPEG.
This legend shall be accessible online at the URL specified by
LegendURL.
A DGIWG WMS server shall provide scale denominators for all
layers it provides.
The <MinScaleDenominator> value shall always be less than orequal to the <MaxScaleDenominator> value.
If the GetCapabilities document identifies support for
FeatureListURL then the list of features that are in the particularlayer shall be resolvable through the provided URL.
If the GetCapabilities document identifies support for DataURL
then the underlying data of the particular layer shall be resolvablethrough the provided URL.
A DGIWG WMS server shall provide the XML Attributes according
to Table 4.
A DGIWG WMS server shall support all GetMap request
parameters.
A DGIWG WMS Service shall support transparency

25

A DGIWG WMS server shall support the INIMAGE EXCEPTIONS.

M

26

A DGIWG WMS server shall support the BLANK EXCEPTIONS.

M

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

7

M
M
M
M
M
M
M
M
M
M
M
M
M
C
C
M
M
M

STD-DP-14-013r3
27

28

29
30
31
32

16 November 2015

If a DGIWG WMS server provides multi-dimensional data then it
shall:
W 0PKKJMO OC@ Q@MOD><G "G@Q<ODJI <I? O@HKJM<G 1DH@ M@LP@NO
parameters.
W%<I?G@?<O<PODGDU@?DIOC@N@K<M<H@O@MNDI<>>JM?<I>@RDOCOC@
"OGC Best Practices for using OGC WMS with Time-Dependent
or Elevation-Dependent Data [2]"A DGIWG WMS server that announces available sample
dimensions in its service metadata shall resolve the corresponding
parameters provided in the GetMap operation for requesting these
dimensional values.
A DGIWG WMS server shall support the FEATURE_COUNT
parameter to enable the increase of the number of features per
layer for which the server returns information.
A DGIWG WMS server shall support the EXCEPTIONS parameter
support of text/xml and text/html.
A DGIWG WMS server shall provide a response according to the
INFO_Format.
A DGIWG WMS server shall return the units of measure fordimensional values returned in a GetFeatureInfo response.

C

M

M
M
M
M

Table 1: DGIWG WMS Profile Normative Server Requirements

6.3. Non-Normative
Implementation

Recommendationsfor

The non-normative requirements requested by this profile are summarized in Table 2
No.

1

2

Recommendation

If a service requires vector based graphical elements output, a
DGIWG WMS server should provide image/svg+xml (Scalable
Vector Graphics) for the GetMap operation.
It is recommended to also provide legends for raster layers
representing numeric data like for instance elevation ortemperature data

3

A DGIWG WMS service should be configured to serve requests
that range from at least 4x to at least 0.25x the native scale(s) or
resolution(s) of the underlying datasets".

45

In an SDI like architecture, a DGIWG WMS server should provide
a link to the metadata resource via a resolvable URL for example
to a CSW server.
Vector layers returned by a WMS server should be queryable6

For a 470 Kilobytes image, the response time for sending theinitial response to a Get Map Request to a view service shall be
maximum 5 seconds in normal situation.

7
8

The number of simultaneous service requests that a DGIWG
WMS server should be able to support is at least 20 per second.
A DGIWG WMS server should be available 99.9% of the time.

Compliance

O

O

O

O

O
O

O
O

Table 2: DGIWG WMS Profile Non-normative Recommendations for Server
Implementation

8

STD-DP-14-013r3

16 November 2015

6.4. Service TypeThe OGC WMS Implementation Specification defines two conformance classes, “Basic
WMS” and “Queryable WMS”. A Basic WMS supports the GetCapabilities and GetMap
operations (requests and responses); a Queryable WMS includes all Basic WMS
operations and an additional GetFeatureInfo operation.
Requirement 1: A DGIWG WMS server shall be compliant to the Queryable WMS
conformance class.
According to this requirement a DGIWG WMS server shall support the GetCapabilities,
GetMap and GetFeatureInfo operations. This requirement ensures compatibility with thebase standard.

6.5. Basic service elements

The Basic service elements specify aspects of Web Map Server behavior that are
independent of particular operations or are common to several operations.

6.5.1. Version number

The VERSION parameter is mandatory in GetMap and GetFeatureInfo requests. The
version number is 1.3.0.

6.5.2. Binding

The OGC WMS 1.3.0 standard requires support for HTTP Get. Support for HTTP Post is
optional. A SOAP binding is not defined in the standard.
Requirement 2: A DGIWG WMS server shall support HTTP GET.

6.5.3. Output Formats

The response to a Web Map Service request is always a computer file. The file may
contain text, or the file may represent a map image depending on the operation. For theparticular operations a DGIWG WMS server shall support the following output formats.

6.5.3.1.
Output formats for GetCapabilities and GetFeatureInfo
requests
The response to a GetCapabilities or GetFeatureInfo request is always a text file.
Requirement 3: A DGIWG WMS server shall support text/xml and text/html as output
formats for the GetCapabilities and the GetFeatureInfo Operations.
Requirement 4: A DGIWG WMS server shall provide metadata content in a response toa "GetCapabilities" or “GetFeatureInfo” request in English language.
NOTE: Services can also be provided using alternative languages to English: This profile
does not specify the details for implementation of multilingual services.

6.5.3.2.

Output formats for GetMap requests

The response to a GetMap request is either a raster or vector file.
Requirement 5: A DGIWG WMS server shall support the following raster formats for
the GetMap operation:
W image/png (Portable Network Graphics)
9STD-DP-14-013r3

16 November 2015

W image/gif (Graphics Interchange Format)
W image/jpeg (Joint Photographics Expert Group)
Recommendation 1: If a service requires vector based graphical elements output, a
DGIWG WMS server should provide image/svg+xml (Scalable Vector Graphics) for the
GetMap operation.
NOTE: Users should be aware that only the output formats GIF and PNG support
transparency.

6.5.4. Coordinate Systems

The Web Map Service standard uses two principal classes of Coordinate Systems: a
Map CS applicable to the map portrayal generated by the WMS, and a Layer CRS for a
Bounding Box applied to the source data. During a portrayal operation, a WMS converts
or transforms geographic information from a Layer CRS into a Map CS. In addition, aLayer may have an associated vertical, temporal or other coordinate system.

6.5.4.1.

Map CSA Map CS is a coordinate reference system for a map produced by a WMS. A WMS map
is a rectangular grid of pixels displayed on a computer screen (or a digital file that could
be so displayed). The Map CS has a horizontal axis denoted i, and a vertical axis
denoted j. i and j shall have only nonnegative integer values. The origin (i,j) =(0,0) is the
pixel in the upper left corner of the map; i increases to the right and j increases
downward.

6.5.4.2.

Layer CRS

A Layer CRS is a horizontal coordinate reference system for the geographic informationthat serves as the source for a map. A WMS must support at least one CRS, and maps
from multiple servers may be overlaid only if all the selected servers support at least one
CRS in common.
Requirement 6: A DGIWG WMS server shall support the following coordinate
reference systems:
W CRS:84 WGS84 geographic longitude, then latitude, expressed in decimaldegreesW EPSG:4326 WGS84 geographic latitude, then longitude, expressed in decimaldegreesW EPSG:3395 World Mercator projection
Among the following Coordinate Reference Systems, the service shall support all
those which validity zone overlaps data published by the service:W
W
WW

UTM projections over WGS84 (north zones)… EPSG:32601 to EPSG:32660
UTM projections over WGS84 (south zones)… EPSG:32701 to EPSG:32760
UPS projection over WGS84 (north zone)… EPSG:32661
UPS projection over WGS84 (south zone)… EPSG:32761

Implementation guidance:
NOTE: Normative Reference 1, Section 7.2.4.6.6 states that: "Every named Layer shall have exactly
one <EX_GeographicBoundingBox> element that is either stated explicitly or inherited from a parent
Layer”. This is unclear in the base standard. Chapter 7.2.4.6.8 BoundingBox in the base standard
states that: The <EX_GeographicBoundingBox> element (7.2.4.6.6) is conceptually similar to a
BoundingBox in which the attribute CRS="CRS:84" is implicit. However,10STD-DP-14-013r3

16 November 2015

<EX_GeographicBoundingBox> shall not be used as a substitute for <BoundingBox CRS="CRS:84">.
If the server wishes to provide bounding box information in the CRS:84 CRS, then a separate
BoundingBox element explicitly naming CRS:84 shall be included in the service metadata.
This means that Ex_GeographicBoundingBox within a DGIWG server shall always be in
CRS="CRS:84".

Some geographic information may be available at other dimensions like for instanceelevation or time (3D / 4D). For example, in the case of elevation, atmospheric information
like ozone concentrations, may be available at different altitudes. Similarly, geographic
information may be available at multiple times, like hourly tidal information.
NOTE: Appropriate vertical and temporal coordinate systems have to be defined in thecontext of the particular application.
The verticalCRSid “CRS:88” refers to the vertical CRS defined in B.6 (elevation in meters in
the North American Vertical Datum 1988). The unitSymbol “m” would be used.. See
Normative Reference 1, Annex C “Handling multi-dimensional data” for more information.

6.5.5. Request Parameter Rules

Parameter names shall not be case sensitive, but parameter values shall be. Parameters ina request may be specified in any order.

6.5.5.1.

Common Request Parameters

There are three common request parameters:
W Version: The VERSION parameter specifies the protocol version number.
W Request: The REQUEST parameter indicates which service operation is being
invoked.
W Format: The FORMAT parameter specifies the output format of the response to an
operation.

6.5.5.2.

Exceptions

The EXCEPTIONS request parameter states the format in which to report errors.
Requirement 7: A DGIWG WMS server shall provide service exceptions in English
language.

6.5.5.3.

Extended capabilities and operations

The Web Map Service allows for optional extended capabilities and operations. Extended
capabilities or operations shall be defined when necessary by providing instances of theabstract <_ExtendedCapabilities> or <_ExtendedOperations> elements in the service
metadata schema.

11

STD-DP-14-013r3

16 November 2015

6.6. Operations

The WMS Interface offers 3 Operations.
W GetCapabilities (mandatory): Allows for obtaining Service Metadata
W GetMap (mandatory): Returns a map
W GetFeatureInfo (optional): Provides additional information about features in the
pictures of maps that were returned by previous GetMap requests

6.6.1. GetCapabilities Operation Request

The purpose of the mandatory GetCapabilities operation is to obtain service metadata, which
is a machine readable (and human-readable) description of the server’s information content
and acceptable request parameter values. Table 3 lists the GetCapabilities request
parameters.
Request Parameter

OGC
Description
Mandatory/Optional

VERSION=version

O

Request version

SERVICE=WMS

M

Service type (WMS)

REQUEST=GetCapabilities

M

Request name (GetCapabilities)

FORMAT=MIME_type

O

Output format of service metadata (text/xml)

UPDATESEQUENCE=stringO

Sequence number or string for cache control

Table 3: The parameters of a GetCapabilities request URL as per Normative Reference[1]
Requirement 8: A DGIWG WMS server shall support all GetCapabilities request
parameters.

6.6.2. GetCapabilities Operation Response

When invoked on a WMS, the response to a GetCapabilities request shall be an XML
document containing service metadata formatted according to the XML Schema in annex
E.1 of the OGC WMS 1.3 standard Normative Reference [1].

6.6.2.1.

Names and titles

A number of elements have both a <Name> and a <Title>. The Name is a text string used
for machine-to-machine communication while the Title is for the benefit of humans.

6.6.2.2.

General service metadata

The first part of the service metadata is a <Service> element providing general metadata forthe server as a whole. It shall include a Name, Title, and Online Resource URL. Optional
service metadata includes Abstract, Keyword List, Contact Information, Fees, Access
Constraints, and limits the number of layers in a request or the output size of maps.
Requirement 9: A DGIWG WMS server shall provide all mandatory and optional
service metadata elements.
The optional <LayerLimit> element in the service metadata is a positive integer indicating the
maximum number of layers a client is permitted to include in a single GetMap request. If thiselement is absent, the server imposes no limit.
12

STD-DP-14-013r3

16 November 2015

The elements <Fees> and <AccessConstraints> may be omitted in an OGC WMS if they do
not apply to the server. If either of those elements is present, the reserved word "none"(case-insensitive) shall be used if there are no fees or access constraints, as follows:<Fees>none</Fees>, <AccessConstraints>none</AccessConstraints>.
In a DGIWG WMS server the AccessConstraints element shall always be used. In an NATOenvironment, the common NATO classification scheme has to be applied (see Normative
Reference [3] DMF chapter 5.6.1.4 Classification Level Codelist).
Requirement 10: A DGIWG WMS server shall identify the highest classification level ofthe content accessible through the WMS service by populating thewms:AccessConstraints element.

6.6.2.3.

Capability metadata

The <Capability> element of the service metadata names the actual operations that aresupported by the server, the output formats offered for those operations, and the URL prefix
for each operation. The XML schema includes placeholders for Distributed Computing
Platforms other than HTTP, but currently only the HTTP platform is defined.
W Layers and styles: Each available map is advertised by a <Layer> element in theservice metadata. A server shall include at least one <Layer> element for each map
layer offered.
W Layer properties: The <Layer> element can enclose child elements providing
metadata about the Layer. The values of some of these elements can be inherited bysubsidiary layers. The following metadata elements are available:o Title: A <Title> is mandatory for all layers; it is a human-readable string forpresentation in a menu. The Title is not inherited by child Layers.
o Name: If, and only if, a layer has a <Name>, then it is a map layer that can berequested by using that Name in the LAYERS parameter of a GetMap request. If
the layer has a Title but no Name, then that layer is only a category title for all
the layers nested within. A containing category itself may include a Name bywhich a map portraying all of the nested layers can be requested at once. For
example, a parent layer "Roads" may have children “Interstates” and “State
Highways” and allow the user to request either child individually or both together.
o The elements <Abstract> and <KeywordList> are optional in the basestandard. Abstract is a narrative description of the map layer. KeywordList
contains zero or more <Keyword> elements to aid in catalogue searches.

13

STD-DP-14-013r3

16 November 2015

Requirement 11: A DGIWG WMS server shall include the following information in the
abstract element of the service metadata: "This service implements the DGIWG WMS
1.3 profile version 1.0."
Requirement 12: A DGIWG WMS server shall provide a minimum keyword list basedon the DFDD groups:
Aeronautical
Biota
Characteristics
Demarcation
Hydrography and Oceanography
Industries and Services
Metadata and References
Military
Names and Designations
Physiography
Socio-economic Geography
Transportation
Weather and Climate
NOTE: Additional keywords may be added to the list as appropriate to support data
discovery.
oZero or more Styles may be advertised for a Layer or collection of layers using<Style> elements, each of which shall have <Name> and <Title> elements.
§
The style's Name is used in the Map request STYLES parameter.
§
The Title is a human-readable string. If only a single style is available, thatstyle is known as the “default” style and need not be advertised by theserver.

Requirement 13: A DGIWG WMS server shall provide information on the supported
styles.
Requirement 14: A DGIWG WMS server shall always provide at least one style element
and that style shall be advertised even if it's only the default style.
Requirement 15: The MaxWidth and MaxHeight shall be greater or equal to 800 pixels.
o<LegendURL> contains the location of an image of a map legend appropriate to
the enclosing style.

Requirement 16: Each vector data layer's style shall have an associated legend,available as an image in one of the following formats: PNG, GIF or JPEG.
Recommendation 2: It is recommended to also provide legends for raster layers
representing numeric data like for instance elevation or temperature data
Requirement 17: This legend shall be accessible online at the URL specified by
LegendURL.
o

Scale denominators: The <MinScaleDenominator> and<MaxScaleDenominator> elements define the range of scales for which it isappropriate to generate a map of a Layer.

14

STD-DP-14-013r3

16 November 2015

Requirement 18: A DGIWG WMS server shall provide scale denominators for all layers
it provides.
Requirement 19: The <MinScaleDenominator> value shall always be less than or equal
to the <MaxScaleDenominator> value.
Recommendation 3: A DGIWG WMS service should be configured to serve requests
that range from at least 4x to at least 0.25x the native scale(s) or resolution(s) of theunderlying datasets".
NOTE: Users should be aware that changing the resolution at a range of 4 times to 0.25
times effects the accuracy of the displayed data significantly and will influence the usabilityof the data for certain use cases (e.g. measurements in the map).
ooSample dimensions: Some geographic information may be available at otherdimensions (for example, satellite images in different wavelength bands). The
dimensions other than the four space-time dimensions are referred to as “sample
dimensions. A DGIWG WMS server may allow for requesting a particular layer
along one or more dimensional axes other than time or elevation.
MetadataURL: A server should use one or more <MetadataURL> elements tooffer detailed, standardized metadata about the data corresponding to aparticular layer. The “type” attribute indicates the standard to which the metadata
complies. Two “type” attribute values are defined in ISO 19128:2005, "ISO19115:2003" and “FGDC:1998”. The enclosed <Format> element indicates thefile format MIME type of the metadata record.

Recommendation 4: In an SDI like architecture, a DGIWG WMS server should provide
a link to the metadata resource via a resolvable URL for example to a CSW server.
oFeatureListURL: A server may use a <FeatureListURL> element to point to alist of the features represented in a Layer. The enclosed Format element
indicates the file format MIME type of the feature list.

Requirement 20: If the GetCapabilities document identifies support for
FeatureListURL then the list of features that are in the particular layer shall be
resolvable through the provided URL.
o

DataURL: A server may use DataURL to offer a link to the underlying data
represented by a particular layer. The enclosed Format element indicates the fileformat MIME type of the data file.

Requirement 21: If the GetCapabilities document identifies support for DataURL thenthe underlying data of the particular layer shall be resolvable through the provided
URL.
W Layer attributes: A <Layer> may have zero or more of the following XML attributes:
queryable, cascaded, opaque, noSubsets, fixedWidth, and fixedHeight. All of these
attributes are optional and default to 0. The meaning of each attribute is summarized inTable 415

STD-DP-14-013r3
AttributequeryablecascadedOpaque16 November 2015
OGC
allowed values

DGIWG
allowedvalues0, false,
0, false,
1, true
1, true0, positive integer 0,
positive
integer0, false,
0, false,
1, true
1, truenoSubsets

0, false,
1, true0, false,

fixedWidth0,
positive integer0,

fixedHeight 0,
positive integer

0,

Meaning (0 is default value)0, false: layer is not queryable.
1, true: layer is queryable.
0: layer has not been retransmitted by a
Cascading Map Server.
n: layer has been retransmitted n times.
0, false: map data represents vector
features that probably do not completely
fill space.
1, true: map data are mostly or completely
opaque.
0, false: WMS can map a subset of thefull bounding box.
1, true: WMS can only map the entire
bounding box.
0: WMS can produce map of arbitrary
width.
nonzero: value is fixed map width thatcannot be changed by the WMS.
0: WMS can produce map of arbitraryheight.
nonzero: value is fixed map height thatcannot be changed by the WMS.

Table 4: Layer attributes
Requirement 22: A DGIWG WMS server shall provide the Layer Attributes according
to Table 4.
Recommendation 5: A DGIWG WMS server offering vector layers should be queryable
The Layer metadata may also include three optional attributes that indicate a map serverthat is less functional than a normal WMS, because it is not able to extract a subset of alarger dataset or because it only serves maps of a fixed size and cannot resize them.
When set to a true value, noSubsets indicates that the server is not able to make a map of
a geographic area other than the layer's bounding box.
When present and nonzero, fixedWidth and fixedHeight indicate that the server is not able
to produce a map of the layer at a width and height different from the fixed sizes indicated.
According to Table 4 a DGIWG WMS server provides only subsettable (nosubsets=0) andresizable (fixedWidth=0 and fixedHeight=0) layers. As the 0 values are the default values,
they do not have to be included explicitly for all layers.

16

STD-DP-14-013r3

16 November 2015

6.6.3. GetMap Operation Request

The GetMap operation returns a map. Upon receiving a GetMap request, a WMS shall either
satisfy the request or issue a service exception. Table 5 lists the parameters of a GetMap
request.
Request Parameter

OGC
Mandatory/Optional

DGIWG
Mandatory/
Optional/
Conditional

Description

VERSION=1.3.0

M

M

Request version.

REQUEST=GetMap

M

M

Request name.

LAYERS=layer_list

M

M

Comma-separated list of one or more
map layers.

STYLES=style_list

M

M

Comma-separated list of one
rendering style per requested layer.

CRS=namespace:identifier

M

M

Coordinate reference system.

BBOX=minx,miny,maxx,maxy

M

M

Bounding box corners (lower left,
upper right) in CRS units.

WIDTH=output_width

M

M

Width in pixels of map picture.

HEIGHT=output_height

M

M

Height in pixels of map picture.

FORMAT=output_format

M

M

Output format of map.

TRANSPARENT=TRUE|FALSE

O

C

Background transparency of map(default=FALSE).

BGCOLOR=color_value

O

O

Hexadecimal red-green-blue color
value for the background color(default=0xFFFFFF).

EXCEPTIONS=exception_format

O

M

The format in which exceptions areto be reported by the WMS(default=XML).

TIME=timeO

C

Time value of layer desired.

ELEVATION=elevationOC

Elevation of layer desired.

Other sample dimension(s)O

C

Value of other dimensions as
appropriate.

Table 5: GetMap request parameters

17

STD-DP-14-013r3

16 November 2015

Requirement 23: A DGIWG WMS server shall support all GetMap request parameters.
W Styles: The mandatory STYLES parameter lists the style in which each layer is to berendered.
W Width, Height: The mandatory WIDTH and HEIGHT parameters specify the size in
integer pixels of the map to be produced.
W TRANSPARENT: The optional TRANSPARENT parameter specifies whether the map
background is to be made transparent or not. TRANSPARENT can take on two values,"TRUE" or "FALSE". The default value is FALSE if this parameter is absent from therequest.
Requirement 24: A DGIWG WMS Service shall support transparency
W EXCEPTIONS: The optional EXCEPTIONS parameter defines the format of an error
message. XML is mandatory and the default format for exceptions.
o

INIMAGE: If the EXCEPTIONS parameter is set to INIMAGE, the WMS shall,
upon detecting an error, return an object of the MIME type specified in the
FORMAT parameter whose content includes text describing the nature of theerror. In the case of a picture format, the error message shall be drawn on the
returned picture. In the case of a graphic element format, the text of the error
message shall be rendered in the manner that text is normally represented inthat format.

Requirement 25: A DGIWG WMS server shall support the INIMAGE EXCEPTIONS.
oBLANK: If the EXCEPTIONS parameter is set to BLANK, the WMS shall, upondetecting an error, return an object of the type specified in FORMAT whose
content is uniformly “off”. In the case of a picture format, that response shall be
an image containing only pixels of one color (the background color). In the caseof a picture format supporting transparency, if TRANSPARENT=TRUE is
specified the pixels shall all be transparent. In the case of a graphic element
output format, no visible graphic elements shall be included in the response
output.

Requirement 26: A DGIWG WMS server shall support the BLANK EXCEPTIONS.
W

Time, Elevation, Other sample dimensions: An example would be the request for asingle ozone map at specified time and height:

Examplehttp://ageobwserver.org/...?VERSION=1.3.0&REQUEST=GetMap&CRS=CRS:84&BBOX=-180,-90,180,90&WIDTH=600&HEIGHT=300&LAYERS=ozone&TIME=2000-0803&ELEVATION=1000&FORMAT=image/gif

18

STD-DP-14-013r3

16 November 2015

Requirement 27: If a DGIWG WMS server provides multi-dimensional data then it
shall:W Support the vertical Elevation and temporal Time request parameters.
W Handle data utilized in these parameters in accordance with the "OGC Best
Practices for using OGC WMS with Time-Dependent or Elevation-Dependent
Data [2]"NOTE: Conformant WMS servers should express the values of the time dimension either
as one time interval with non-zero resolution when the temporal dependency of the data is
time instants or as a comma separated list of timestamps.
The WMS 1.3 specification allows the possibility to define multiple times as several triplets:
start/end/interval. The triplets define sets of time instants that may overlap. It is difficult for ahuman reader to determine the allowed times of the time dimension. Hence, the time
dimension should not be specified as a list of triplets, except if the time instants are regularly
spaced with a unique interval of time. If not the time instance should be specified as acomma separated list.
Requirement 28: A DGIWG WMS server that announces available sample dimensions
in its service metadata shall resolve the corresponding parameters provided in the
GetMap operation for requesting these dimensional values.
ExampleA WMS Layer is described as having an extent along a dimension named “wavelength”
as follows:<Dimension name="wavelength" units="Angstrom"
unitSymbol="Ao">3000,4000,5000,6000<Dimension>.A GetMap request for a portrayal ofthe data at 4000 Angstroms would include the parameter “DIM_WAVELENGTH=4000”."

6.6.4. GetMap Response

The response to a valid GetMap request shall be a map of the spatially referenced
information layer requested, in the desired style, and having the specified coordinate
reference system, bounding box, size, format and transparency.

6.6.5. GetFeatureInfo Operation Request

GetFeatureInfo is an optional operation. It is only supported for those Layers for which theattribute queryable="1" (true) has been defined or inherited. A client shall not issue a
GetFeatureInfo request for other layers. A WMS shall respond with a properly formatted
service exception (XML) response (code = OperationNotSupported) if it receives a
GetFeatureInfo request but does not support it.
The GetFeatureInfo operation is designed to provide clients of a WMS with more information
about features in the pictures of maps that were returned by previous Map requests. The
canonical use case for GetFeatureInfo is that a user sees the response of a Map request
and chooses a point (I,J) on that map for which to obtain more information. The basic
operation provides the ability for a client to specify which pixel is being asked about, whichlayer(s) should be investigated, and what format the information should be returned in.
Because the WMS protocol is stateless, the GetFeatureInfo request indicates to the WMS
what map the user is viewing by including most of the original GetMap request parameters(all but VERSION and REQUEST). From the spatial context information (BBOX, CRS,

19

STD-DP-14-013r3

16 November 2015

WIDTH, HEIGHT) in that GetMap request, along with the I,J position the user chose, theWMS can (possibly) return additional information about that position.
The parameters of a GetFeatureInfo request are listed in Table 6.
Request Parameter

OGC
DGIWG
Description
Mandatory Mandatory/ Optional / Optional

VERSION=1.3.0

M

M

Request version.

REQUEST=GetFeatureInfo

M

M

Request name.

map request partM

M

Partial copy of the Map request
parameters that generated the map forwhich information is desired.

QUERY_LAYERS=layer_list

M

M

Comma-separated list of one or morelayers to be queried.

INFO_FORMAT=output_format

M

M

Return format of feature information(MIME type).

FEATURE_COUNT=number

O

M

Number of features about which toreturn information (default=1).

I=pixel_columnMM

i coordinate in pixels of feature in Map
CS.

J=pixel_row

MM

j coordinate in pixels of feature in Map
CS.

EXCEPTIONS=exception_format

O

M

The format in which exceptions are to
be reported by the WMS (default=
XML). Support of text/xml andtext/html is mandatory.

Table 6: GetFeatureInfo Request parameters

6.6.5.1.

VersionThe VERSION parameter is mandatory. The value “1.3.0” shall be used for GetFeatureInfo
requests that comply with ISO 19128:2005.

6.6.5.2.

RequestThe REQUEST parameter is mandatory. For GetFeatureInfo, the value “GetFeatureInfo”
shall be used.

6.6.5.3.

Map request part

The mandatory “map request part” represents a sequence of parameters from the GetMap
request that generated the original map. Two of the GetMap parameters are omitted
because GetFeatureInfo provides its own values: VERSION and REQUEST. The remainderof the GetMap request shall be embedded contiguously in the GetFeatureInfo request.

6.6.5.4.

Query_Layers

The mandatory QUERY_LAYERS parameter states the map layer(s) from which feature
information is desired to be retrieved. Its value is a comma-separated list of one or more
map layers. This parameter shall contain at least one layer name, but may contain fewer
layers than the original GetMap request. If any layer in the QUERY_LAYERS parameter is
not defined in the service metadata of the WMS, the server shall issue a service exception(code = LayerNotDefined).

20

STD-DP-14-013r3

6.6.5.5.

16 November 2015

INFO_FORMAT

The mandatory INFO_FORMAT parameter indicates what format to use when returning thefeature information.

6.6.5.6.

Feature_COUNTThe optional FEATURE_COUNT parameter states the maximum number of features per
layer for which feature information shall be returned. Its value is a positive integer. The
default value is 1 if this parameter is omitted or is other than a positive integer.
Requirement 29: A DGIWG WMS server shall support the FEATURE_COUNT
parameter to enable the increase of the number of features per layer for which theserver returns information.
NOTE: Using a high value for the Feature_COUNT parameter may affect server
performance. A server might restrict the number of features for which information isretrievable. This limitation has to be advertised in the capabilities document.

6.6.5.7.

I, J

The mandatory I and J request parameters are integers that indicate a point of interest on
the map that was produced by the embedded GetMap request (the “map request part”
described in 7.4.3.3). The point (I,J) is a point in the (i,j) space defined by the Map CS (see6.7.2). Therefore:
W the value of I shall be between 0 and the maximum value of the i axis;
W the value of J shall be between 0 and the maximum value of the j axis;
W the point I=0, J=0 indicates the pixel at the upper left corner of the map;
W I increases to the right and J increases downward.
The point (I,J) represents the centre of the indicated pixel.
If the value of I or of J is invalid, the server shall issue a service exception (code =InvalidPoint).

6.6.5.8.

EXCEPTIONSThe EXCEPTIONS parameter is optional. If this parameter is absent from the request, thedefault value is "XML". No other values are defined by ISO 19128:2005 for the WMS
GetFeatureInfo request. Use of text/html is for the benefit of human readable content.
Requirement 30: A DGIWG WMS server shall support the EXCEPTIONS parameter
support of text/xml and text/html.

6.6.6. GetFeatureInfo response

The server shall return a response according to the requested INFO_FORMAT if the request
is valid, or issue a service exception otherwise. The nature of the response is at thediscretion of the service provider, but it shall pertain to the feature(s) nearest to (I,J).
Requirement 31: A DGIWG WMS server shall provide a response according to the
INFO_Format.
Requirement 32: A DGIWG WMS server shall return the units of measure fordimensional values returned in a GetFeatureInfo response.

21

STD-DP-14-013r3

16 November 2015

7. Quality of Service

Quality of service comprises requirements on all the aspects of a connection. A DGIWG
WMS server should meet the following guidelines for performance, availability and capacity.

7.1. Performance
Recommendation 6: For a 470 Kilobytes image, the response time for sending theinitial response to a Get Map Request to a view service shall be maximum 5 seconds
in normal situation.
NOTE: Normal situation represents periods out of peak load. It is set at 90% of the time.

7.2. Capacity
Recommendation 7: The number of simultaneous service requests that a DGIWG
WMS server should be able to support is at least 20 per second.

7.3. Availability
Recommendation 8: A DGIWG WMS server should be available 99.9% of the time.
NOTE: This relates to 10 minutes downtime per week, 0.73 hours per month and 8.73 hours
per year.

22

STD-DP-14-013r3

16 November 2015

Annex A – Abstract Test Suite(normative)

A.1

DGIWG Service Type

A.1.1

DGIWG Service Typea) Test Purpose: Verify that a DGIWG WMS server satisfies all requirements for a OGC
Queryable WMS conformance class (DGIWG Requirement 1)b) Test Method: Submit a GetFeatureInfo requests to the server and verify that it isproviding a proper response.
c) References: Clauses 6.4d) Test Type: Capability

A.1.2

DGIWG WMS Bindinga) Test Purpose: Verify that a DGIWG WMS server supports HTTP Get requests(DGIWG Requirement 2).
b) Test Methods:
1. Submit HTTP Get GetCapabilities request and verify that the server isproviding a proper response.
2. Submit HTTP Get GetMap request and verify that the server is providing aproper response.
c) References: Clauses 6.5.2d) Test Type: Capability

A.1.3

DGIWG WMS Output formata) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements forsupported outputs (DGIWG Requirement 3, 4 and 5).
b) Test Method: Submit requests and verify that the server implements support for:1. Submit a GetCapabilities request (FORMAT = text/xml) and verify that the
response is text/xml
2. Submit a GetCapabilities request (FORMAT = text/html) and verify that the
response is text/html
3. Submit a GetFeatureInfo request (FORMAT = text/xml) and verify that the
response is text/xml
4. Submit a GetFeatureInfo request (FORMAT = text/html) and verify that the
response is text/html
5. A response to a "GetCapabilities" request in English language
6. Submit a GetMap request (FORMAT = image/png) and verify that the
response is image/png
7. Submit a GetMap request (FORMAT = image/gif) and verify that the response
is image/gif
8. Submit a GetMap request (FORMAT = image/jpeg) and verify that the
response is image/jpeg23

STD-DP-14-013r3

16 November 2015c) References: Clauses 6.5.3d) Test Type: Capability

A.1.4

DGIWG WMS CRSa) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements forhandling CRS’s (DGIWG Requirement 2).
b) Test Method:
1. Submit requests and verify that all supported CRS are advertised for all
available data in the XML response (Capabilities document) to a valid
GetCapabilities request.
2. Submit GetMap requests and verify that maps are provided in the mandatory
CRSs and the appropriate projections for each validity zone.
c) References: Clauses 6.5.4d) Test Type: Capability

A.1.5

DGIWG WMS Request Parameters - Exceptionsa) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements for the
exceptions request parameter rule (DGIWG Requirement 7).
b) Test Method: Generate a sample of invalid requests from a client. Verify that theserver provides an appropriate response in English.
c) References: Clauses 6.5.5.2d) Test Type: Capability

A.2

DGIWG WMS Operations

A.2.1

DGIWG WMS GetCapabilities requesta) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements for a
GetCapabilities operation request (DGIWG Requirement 8).
b) Test Method: Generate sufficient GetCapabilities requests from the client to verify
that each parameter is supported.
c) References: Clauses 6.6.1d) Test Type: Capability

A.2.2

DGIWG WMS GetCapabilites Responsea) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements for a
GetCapabilities operation request (DGIWG Requirements 9 - 22).
b) Test Method:
1. Submit a GetCapabilities request and verify that the response has all required
service metadata elements.
24

STD-DP-14-013r3

16 November 2015

2. Submit a GetCapabilities request and verify that the response uses
<AccessContraints> to identify classification levels for the service.
3. Submit a GetCapabilities request and verify that the response in the Abstractelement contains the following information: "This service implements the
DGIWG WMS 1.3 profile version 1.0."
4. Submit a GetCapabilities request and verify that the response provides a
keywordlist that is based on the DFDD groups.
5. Submit a GetCapabilities request and verify that the response provides
information on the supported styles.
6. Submit a GetCapabilities request and verify that the response provides adefined style for the default style.
7. Submit a GetCapabilities request and verify that the values for MaxWidth andMaxHeight, when used, are greater than or equal to 800 pixels.
8. Submit a GetCapabilities request and verify that the response provides anassociated legend in at least one of the following formats: PNG, GIF, JPEG.
9. Submit a GetCapabilities request and verify that the provided LegendURL isaccessible online.
10. Submit a GetCapabilities request and verify that the response provides scale
denominators for all layers.
11. Submit a GetCapabilities request and verify that the provided<MinScaleDenominator> value is less than or equal to the<MaxScaleDenominator>.
12. Submit a GetCapabilities request and verify that for all provided
FeatureListURLs the list of features is resolvable through the provided URL.
13. Submit a GetCapabilities request and verify that for all provided DatURLs thedata is resolvable through the provided URL.
14. Submit a GetCapabilities request and verify that all XML attributes areprovided according to Table 4.
c) References: Clauses 6.6.2d) Test Type: Capability

A.2.3

DGIWG WMS GetMap Requesta) Test Purpose: Verify that a basic WMS client satisfies all requirements for a GetMap
request (DGIWG Requirements 23 - 28).
b) Test Method:
1. Submit a GetMap request and verify support for all GetMap request
parameters according to Table 5.
2. Submit a GetMap request and verify support for transparency.
3. Submit a GetMap request and verify support for INIMAGE_EXCEPTIONS.
4. Submit a GetMap request and verify support for BLANK_EXCEPTIONS.
5. Submit a GetMap request and verify that for WMS that serve multidimensional data support for ELEVATION and TIME parameters is provided.
6. Submit a GetMap request and verify that for WMS that serve multidimensional data the data utilized is provided according to OGC MetOc “Best
Practices for using OGC WMS with Time-Dependent or Elevation-DependentData”.
7. Submit a GetMap request and verify that for WMS servers that advertise
sample dimensions resolve corresponding parameters correctly.
8. Submit a GetMap request with a non-existent layer and verify that the client
handles the resulting LayerNotDefined exception appropriately, e.g. by
adjusting the layer structure.
25

STD-DP-14-013r3

16 November 2015c) References: Clauses 6.6.3d) Test Type: Capability

A.2.4 DGIWG GetFeatureInfo Operation Request FEATURE_COUNTa) Test Purpose: Verify that a DGIWG WMS server satisfy all the requirements for the
FEATURE_COUNT parameter (DGIWG Requirement 29).
b) Test Method: Submit a GetFeatureInfo request from the client and verify that the
FEATURE_COUNT parameter can be used to increase the number of features per
layer for which the server returns information.
c) References: Clauses 6.6.5.1d) Test Type: Capability

A.2.5

DGIWG GetFeatureInfo Operation Request - EXCEPTIONSa) Test Purpose: Verify that a DGIWG WMS server satisfies all the requirements for the
EXCEPTIONS parameter (DGIWG Requirement 30).
b) Test Method: Submit a GetFeatureInfo request from the client and verify that the
EXCEPTIONS parameter is used and supports both text/xml and text/html formats.
c) References: Clauses 6.6.5.3d) Test Type: Capability

A.2.6

DGIWG WMS GetFeatureInfo Responsea) Test Purpose: Verify that a DGIWG WMS interface satisfies all requirements for theoperation GetFeatureInfo (DGIWG Requirement 31).
b) Test Method: Submit a GetFeatureInfo request from the client and verify that an
appropriate response is returned according to the requested INFO_Format.
c) References: Clauses 6.6.6d) Test Type: Capability

26

STD-DP-14-013r3

16 November 2015

Annex B – Use cases(informative)

Type
DiscoverTitle
Discovergeoreferenced
information (GI)for task

Discover

Load GI into
applications

Discover

Unload GI fromapplication

CreatePopulate
Metadata

The Advanced User populates
pre-defined metadata fields.

CreateLink
textual/audio/vis
ual data to
GeoINT
Create Custom
Symbology (S)The Advanced User links textual/ audio / visual data to GI.

Identify Query GI
at apixel/feature/obj
ect on thedisplay
Selectfeatures/objects
based on spatial
extent

The Basic User queries
information about GI for a
pixel/feature/object on thedisplay.

Analysis

Select GI basedon temporal data

The Basic User selects GI
based on temporal data.

Analysis

Select Raster or
Grid Cells

The Advanced User selects
raster or grid cells based on cellor cell values

Display

View 2D and/or
3D GI

The Basic User views 2D and/or
3D GI (including GeoINF (basemapping), GeoINT and othergeo-referenced
information)
rendered in an appropriatemanner vector and/or raster in asingle coherent view.

CreateAnalysisAnalysis

Use Case Description
The ability to locate GI available
for exploitation within an
application. The Basic User cannavigate lists of GI datasets todecide which are appropriate to
his task.
The Basic User has identified GI
and/or services of interest whichhave a geospatial context andwishes to use them within theapplication.
The Basic User wishes tounload data or services fromapplication

The Advanced User
creates/edits custom symbology
and saves it.

The Basic User selects
features/objects based on a
spatial extent in a graphicaldisplay.

27

Relevance
The ability to retrieve a list oflayers served by WMS throughthe use of a GetCapabilities
request.
The ability to use WMS to load
GI into applications or clients
which support the OGC WMS
specification.
The ability to remove
connections to WMS services orhide visibility of layers using
clients which support the OGC
WMS specification
The ability to add descriptive
information about a data service
and layer in the <Abstract>
The ability to incorporate URL
links to other documents andresources within WMS
attributes.
The ability to define how layers
should be symbolised within a
WMS map service, including
thematic ranges.
The ability to perform a
GetFeatureInfo request to
retrieve information about afeature at a specific location.
The ability to display map
features following thesubmission of a request
containing a bounding box map
extent.
The ability to submit a GetMap
request incorporating a timeparameter to retrieve data for a
specific point in time
The ability to query raster data
values in WMS layers anddisplay them thematically basedon their value
The ability to view 2D data
presented as a map image

STD-DP-14-013r3
Type
Display

Display

Display

Title
View the quality,
accuracy orconfidence levelof the GI
Set the scale
threshold at
which data shallbe displayed (foruser createddata)
Display Legend

Display

Projections andDatums Views

Display

Projections andDatumsChanges (S)Display

View Temporalsequences ofenvironmental
eventsLayer Display
andManagement

Display

Display

View GI Labels

Display

View GI
Attributes

Share or
ExportShare or
ExportShare User
Created GI(Advanced User)
Publish to Web
Service

Share or
ExportUnpublish from a
Web Service

16 November 2015
Use Case Description
The Basic User views thequality, accuracy or confidence
level of the GI.

Relevance
The ability to view additional
information about the accuracyof a layer as part of its metadata

The Advanced User sets thescale threshold at which user
created data shall be displayed.

The ability to define zoom scale
thresholds for the appearance oflayersThe Basic User views a display
legend and the corresponding
real-world objects.
The Basic User views GI
displayed using a pre-defined
operational datum and views
GeoINF in the approved
projection for the area and thedata provided.
The Advanced User changes
the projection of the display or
the datum to another approved
projection/datum.
The Basic User views temporalsequences of environmental
events.

The ability to view a legend
containing representations ofeach layer’s symbology
The ability to display data in
defined projections

The Basic User performs layer
display and management
functions
The Basic User views the GI
labels and turns off the label
display.
The Basic User view theattributes or metadata of the GI.
The Advanced User shares user
created GI to LAN or WAN orother users cross domain.
The Advanced User can publish
to a Web Service to support thesharing of GI to other users andapplications.
The Advanced User canunpublish GI from a web service
which has been previously been
published.

28

The ability to modify projections
used to display data
The ability to submit a GetMap
request incorporating a timeparameter to retrieve data for a
specific point in time
The ability to define layerordering within a map service
and define which layers torequest for display.
The ability to present labels as
layers within the WMS
The ability to query a feature
within a WMS layer to retrieve
associated information or view
related metadata
The ability to share access todata through WMS services.
The ability to publish data via
WMS services.
The ability to remove data frombeing published via the WMS.

STD-DP-14-013r3

Annex C – Examples

16 November 2015

(informative)

Example of a Profile Compliant GetCapabilities Response (Does not include Best
Practice Below)
This response is compliant with the profile and can be objectively tested.
The parts of the GetCapabilities, highlighted in yellow and contained within remarks <!-"Remarks" -->, if omitted would still provide a compliant GetCapabilities Response.
This GetCapabilites Response returns a Category Layer “MGCP” and 3 Named Layers:“MGCP_Transportation”“MGCP_Boundaries”“MGCP_Administration”<?xml version="1.0" encoding="UTF-8"?><WMS_Capabilities
version="1.3.0"
xmlns="http://www.opengis.net/wms"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xlink="http://www.w3.org/1999/xlink"
xsi:schemaLocation="http://www.opengis.net/wms
http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd"><Service><Name>WMS</Name><Title>DGIWG test implementation of DGIWG WMS profile</Title><Abstract>This is provided to test the development of a profile for WMS, This service
implements the DGIWG WMS 1.3 profile version 1.0. </Abstract><KeywordList><Keyword vocabulary="https://www.dgiwg.org/FAD/">Transportation</Keyword><Keyword vocabulary="https://www.dgiwg.org/FAD/">Military</Keyword><Keyword
vocabulary="https://www.dgiwg.org/FAD/">SocioEconomicGeography</Keyword><Keyword vocabulary="ISO 19115:2003”">transportation</Keyword><Keyword vocabulary="ISO 19115:2003”">society</Keyword><Keyword vocabulary="ISO 19115:2003”">intelligenceMilitary</Keyword><Keyword>DGIWG</Keyword></KeywordList><OnlineResource xlink:type="simple" xlink:href="https://www.dgiwg.org"/><!--No requirement on LayerLimit value. If omitted would still produce a compliant
GetCapabilities --><LayerLimit>25</LayerLimit><!--MaxWidth and MaxHeight if omitted would still produce a compliant GetCapabilities -><MaxWidth>800</MaxWidth><MaxHeight>800</MaxHeight></Service><Capability><Request><GetCapabilities><Format>text/xml</Format><Format>text/html</Format><DCPType><HTTP>

29

STD-DP-14-013r3

16 November 2015
<Get>

<OnlineResource xlink:type="simple"
xlink:href="https://myServer.com/WMS"/></Get></HTTP></DCPType></GetCapabilities><GetMap><Format>image/jpeg</Format><Format>image/png</Format><Format>image/gif</Format><DCPType><HTTP><Get><OnlineResource xlink:type="simple"
xlink:href="https://myServer.com/WMS"/></Get></HTTP></DCPType></GetMap><GetFeatureInfo><Format>text/xml</Format><Format>text/html</Format><DCPType><HTTP><Get><OnlineResource xlink:type="simple"
xlink:href="https://myServer.com/WMS"/></Get></HTTP></DCPType></GetFeatureInfo></Request><Exception><Format>INIMAGE</Format><Format>XML</Format><Format>BLANK</Format></Exception></Abstract><!-- this is a hierarchical layer --><Layer><Name>MGCP</Name><Title>MGCP layer</Title><Abstract>This layer has been generated from MGCP data at 1/50K scale.

<KeywordList><Keyword vocabulary="https://www.dgiwg.org/FAD/">Railways</Keyword><Keyword
vocabulary="https://www.dgiwg.org/FAD/">RoadsTracks</Keyword><Keyword
vocabulary="https://www.dgiwg.org/FAD/">AirTransportation</Keyword><Keyword vocabulary="https://www.dgiwg.org/FAD/">Restricted Areas
and/or Boundaries</Keyword><Keyword vocabulary="https://www.dgiwg.org/FAD/">Politics and/or
Administration</Keyword></KeywordList><CRS>CRS:84</CRS><CRS>EPSG:4326</CRS><CRS>EPSG:3395</CRS><EX_GeographicBoundingBox>

30

STD-DP-14-013r3

16 November 2015

<westBoundLongitude>-10.1535960995563</westBoundLongitude><eastBoundLongitude>4.28847853801868</eastBoundLongitude><southBoundLatitude>49.1760995690644</southBoundLatitude><northBoundLatitude>62.1716681019098</northBoundLatitude></EX_GeographicBoundingBox><BoundingBox CRS="CRS:84" minx="-10.1535960995563"
miny="49.1760995690644" maxx="4.28847853801868" maxy="62.1716681019098"/><BoundingBox CRS="EPSG:4326" minx="49.1760995690644" miny="10.1535960995563" maxx="62.1716681019098" maxy="4.28847853801868"/><BoundingBox CRS="EPSG:3395" minx="-1130293.14752318"
miny="6255875.09329192" maxx="477391.247130122" maxy="8840315.18828581"/>

data.</Abstract><!-- This is layer 1 with transportation features --><Layer queryable="1" noSubsets="0" fixedWidth="0" fixedHeight="0" opaque="0"><!-- Layer queryable=”0” would also be valid --><Name>MGCP_Transportation</Name><Title>MGCP transportation layer</Title><Abstract>This layer contains transportation features from MGCP

<KeywordList><Keyword
vocabulary="https://www.dgiwg.org/FAD/">Railways</Keyword><Keyword
vocabulary="https://www.dgiwg.org/FAD/">RoadsTracks</Keyword><Keyword
vocabulary="https://www.dgiwg.org/FAD/">AirTransportation</Keyword></KeywordList><CRS>CRS:84</CRS><CRS>EPSG:4326</CRS><CRS>EPSG:3395</CRS><CRS>EPSG:32628</CRS><!-- Following CRS are UTM zones --><CRS>EPSG:32629</CRS><CRS>EPSG:32630</CRS><CRS>EPSG:32631</CRS><EX_GeographicBoundingBox><westBoundLongitude>-9.49713815455354</westBoundLongitude><eastBoundLongitude>3.6320205928561</eastBoundLongitude><southBoundLatitude>49.7668072354576</southBoundLatitude><northBoundLatitude>61.4645902255622</northBoundLatitude></EX_GeographicBoundingBox><BoundingBox CRS="CRS:84" minx="-9.49713815455354"
miny="49.7668072354576" maxx="3.6320205928561" maxy="61.4645902255622"/><BoundingBox CRS="EPSG:4326" minx="49.7668072354576" miny="9.49713815455354" maxx="61.4645902255622" maxy="3.6320205928561"/><BoundingBox CRS="EPSG:3395" minx="-1057216.58335827"
miny="6373349.64406279" maxx="404314.682947424" maxy="8695713.5043031"/><BoundingBox CRS="EPSG:32628" minx="793024.68315553"
miny="5527248.51711237" maxx="1837454.99286334" maxy="6956813.88497105"/><BoundingBox CRS="EPSG:32629" minx="464199.601699745"
miny="5512703.78924251" maxx="1408401.65601044" maxy="6879829.43013705"/><BoundingBox CRS="EPSG:32630" minx="32287.7441544105"
miny="5512703.78916081" maxx="977414.853119147" maxy="6832515.66692919"/><BoundingBox CRS="EPSG:32631" minx="-398729.782539505"
miny="5512703.78912287" maxx="545513.62628886" maxy="6878440.59046608"/><MetadataURL type="urn:dgiwg:metadata:dmf:1.0:profile:all"><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/cswservice/csw?service=CSW&amp;version=2.0.2&amp;Request=G
etRecordById&amp;id=123456"/>

31

STD-DP-14-013r3

16 November 2015</MetadataURL><DataURL><Format></Format><OnlineResource></OnlineResource></DataURL><FeatureListURL><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/MGCPFeatureList.xml"/></FeatureListURL><Style><Name>default</Name><Title>default MGCP style</Title><LegendURL width="200" height="600"><Format>image/png</Format><OnlineResource
xlink:href="http://myServer.com/MGCPLegend.png" xlink:type="simple"/></LegendURL></Style><MinScaleDenominator>12500</MinScaleDenominator><MaxScaleDenominator>200000</MaxScaleDenominator></Layer><!-- This is layer 2 with boundaries features --><Layer queryable="1" noSubsets="0" fixedWidth="0" fixedHeight="0" opaque="0"><!-- Layer queryable=”0” would also be valid --><Name>MGCP_Boundaries</Name><Title>MGCP boundaries layer</Title><Abstract>This layer contains boundaries and administration features from
MGCP data.</Abstract><KeywordList><Keyword vocabulary="https://www.dgiwg.org/FAD/">Restricted
Areas and/or Boundaries</Keyword></KeywordList><CRS>CRS:84</CRS><CRS>EPSG:4326</CRS><CRS>EPSG:3395</CRS><!-- Following CRS are UTM zones --><CRS>EPSG:32628</CRS><CRS>EPSG:32629</CRS><CRS>EPSG:32630</CRS><CRS>EPSG:32631</CRS><EX_GeographicBoundingBox><westBoundLongitude>-9.49713815455354</westBoundLongitude><eastBoundLongitude>3.6320205928561</eastBoundLongitude><southBoundLatitude>49.7668072354576</southBoundLatitude><northBoundLatitude>61.4645902255622</northBoundLatitude></EX_GeographicBoundingBox><BoundingBox CRS="CRS:84" minx="-9.49713815455354"
miny="49.7668072354576" maxx="3.6320205928561" maxy="61.4645902255622"/><BoundingBox CRS="EPSG:4326" minx="49.7668072354576" miny="9.49713815455354" maxx="61.4645902255622" maxy="3.6320205928561"/><BoundingBox CRS="EPSG:3395" minx="-1057216.58335827"
miny="6373349.64406279" maxx="404314.682947424" maxy="8695713.5043031"/><BoundingBox CRS="EPSG:32628" minx="793024.68315553"
miny="5527248.51711237" maxx="1837454.99286334" maxy="6956813.88497105"/><BoundingBox CRS="EPSG:32629" minx="464199.601699745"
miny="5512703.78924251" maxx="1408401.65601044" maxy="6879829.43013705"/><BoundingBox CRS="EPSG:32630" minx="32287.7441544105"
miny="5512703.78916081" maxx="977414.853119147" maxy="6832515.66692919"/>32

STD-DP-14-013r3

16 November 2015

<BoundingBox CRS="EPSG:32631" minx="-398729.782539505"
miny="5512703.78912287" maxx="545513.62628886" maxy="6878440.59046608"/><MetadataURL type="urn:dgiwg:metadata:dmf:1.0:profile:all"><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/cswservice/csw?service=CSW&amp;version=2.0.2&amp;Request=G
etRecordById&amp;id=123456"/></MetadataURL><DataURL><Format></Format><OnlineResource></OnlineResource></DataURL><FeatureListURL><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/MGCPFeatureList.xml"/></FeatureListURL><Style><Name>default</Name><Title>default MGCP style</Title><LegendURL width="200" height="600"><Format>image/png</Format><OnlineResource
xlink:href="http://myServer.com/MGCPLegend.png" xlink:type="simple"/></LegendURL></Style><MinScaleDenominator>125000</MinScaleDenominator><MaxScaleDenominator>200000</MaxScaleDenominator></Layer>data.</Abstract><!-- This is layer 3 with administration features --><Layer queryable="1" noSubsets="0" fixedWidth="0" fixedHeight="0" opaque="0"><!-- Layer queryable=”0” would also be valid --><Name>MGCP_Administration</Name><Title>MGCP administration layer</Title><Abstract>This layer contains administration features from MGCP

<KeywordList><Keyword vocabulary="https://www.dgiwg.org/FAD/">Politics and/or
Administration</Keyword></KeywordList><CRS>CRS:84</CRS><CRS>EPSG:4326</CRS><CRS>EPSG:3395</CRS><!-- Following CRS are UTM zones --><CRS>EPSG:32628</CRS><CRS>EPSG:32629</CRS><CRS>EPSG:32630</CRS><CRS>EPSG:32631</CRS><EX_GeographicBoundingBox><westBoundLongitude>-9.49713815455354</westBoundLongitude><eastBoundLongitude>3.6320205928561</eastBoundLongitude><southBoundLatitude>49.7668072354576</southBoundLatitude><northBoundLatitude>61.4645902255622</northBoundLatitude></EX_GeographicBoundingBox><BoundingBox CRS="CRS:84" minx="-9.49713815455354"
miny="49.7668072354576" maxx="3.6320205928561" maxy="61.4645902255622"/><BoundingBox CRS="EPSG:4326" minx="49.7668072354576" miny="9.49713815455354" maxx="61.4645902255622" maxy="3.6320205928561"/>33

STD-DP-14-013r3

16 November 2015

<BoundingBox CRS="EPSG:3395" minx="-1057216.58335827"
miny="6373349.64406279" maxx="404314.682947424" maxy="8695713.5043031"/><BoundingBox CRS="EPSG:32628" minx="793024.68315553"
miny="5527248.51711237" maxx="1837454.99286334" maxy="6956813.88497105"/><BoundingBox CRS="EPSG:32629" minx="464199.601699745"
miny="5512703.78924251" maxx="1408401.65601044" maxy="6879829.43013705"/><BoundingBox CRS="EPSG:32630" minx="32287.7441544105"
miny="5512703.78916081" maxx="977414.853119147" maxy="6832515.66692919"/><BoundingBox CRS="EPSG:32631" minx="-398729.782539505"
miny="5512703.78912287" maxx="545513.62628886" maxy="6878440.59046608"/><MetadataURL type="urn:dgiwg:metadata:dmf:1.0:profile:all"><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/cswservice/csw?service=CSW&amp;version=2.0.2&amp;Request=G
etRecordById&amp;id=123456"/></MetadataURL><DataURL><Format></Format><OnlineResource></OnlineResource></DataURL><FeatureListURL><Format>text/xml</Format><OnlineResource xlink:type="simple"
xlink:href="http://myServer.com/MGCPFeatureList.xml"/></FeatureListURL><Style><Name>default</Name><Title>default MGCP style</Title><LegendURL width="200" height="600"><Format>image/png</Format><OnlineResource
xlink:href="http://myServer.com/MGCPLegend.png" xlink:type="simple"/></LegendURL></Style><MinScaleDenominator>125000</MinScaleDenominator><MaxScaleDenominator>200000</MaxScaleDenominator></Layer></Layer></Capability></WMS_Capabilities>

34

STD-DP-14-013r3

16 November 2015

Annex D – Client Requirements and Recommendations

The Normative client requirements requested by this profile are summarized in Table 7
No.

Requirement

Compliance

1

A DGIWG WMS client shall support access to a Queryable WMS bysupporting the GetFeatureInfo request to enable the querying of alllayers.
A DGIWG WMS client shall support HTTP GET.

M

3

A DGIWG WMS client shall support text/xml and text/html output
formats of the GetCapabilities and the GetFeatureInfo Operations.

M

4

M

17

A DGIWG WMS client shall provide metadata content in a response
to a "GetCapabilities" or “GetFeatureInfo” request in English
language.
A DGIWG WMS client shall support the following raster formats for
the GetMap operation:
W image/png (Portable Network Graphics)
W image/gif (Graphics Interchange Format)
W image/jpeg (Joint Photographics Expert Group)
A DGIWG WMS client shall support the following coordinate
reference systems:
W CRS:84 WGS84 geographic longitude, then latitude, expressed indecimal degrees
W EPSG:4326 WGS84 geographic latitude, then longitude,
expressed in decimal degrees
W EPSG:3395 World Mercator projection
W UTM projections over WGS84 (north zones)… EPSG:32601 to
EPSG:32660
W UTM projections over
WGS84
(southzones)…
EPSG:32701 to EPSG:32760
W UPS projection over WGS84 (north zone)…… EPSG:32661
W UPS projection over WGS84 (south zone)…… EPSG:32761
A DGIWG WMS client shall support service exceptions in English
language.
A DGIWG WMS client shall support all GetCapabilities request
parameters.
A DGIWG WMS client shall support all mandatory and optional
service metadata elements.
A DGIWG WMS client shall be able to utilize classification levels of
the content accessible through the WMS service by the
wms:AccessConstraints element.
A DGIWG WMS client shall use style information to display the given
information.
A DGIWG WMS server requirement only; normative requirements(mandatory) for a WMS 1.3 server implementation are found in Table
1. DGIWG WMS Profile Normative Requirements
A DGIWG WMS client shall support MaxWidth and MaxHeightelements.
A DGIWG WMS client shall support associated legends for vector
data layers available as an image in one of the following formats:
PNG, GIF or JPEG.
A DGIWG WMS client shall support LegendURL.

18

A DGIWG WMS client shall support scale denominators for all layers.

M

19

A DGIWG WMS server requirement only; normative requirements(mandatory) for a WMS 1.3 server implementation are found in Table
1. DGIWG WMS Profile Normative Requirements

N.A.

2

5

6

7
8
9
10
13
14
15
16

35

M

M

M

M
M
M
M
M
N.A.
M
M
M

STD-DP-14-013r3

16 November 201520

A DGIWG WMS client shall support FeatureListURL to list anddisplay the features provided through the given URL.

C

21

N.A.

23

A DGIWG WMS server requirement only; normative requirements(mandatory) for a WMS 1.3 server implementation are found in Table
1. DGIWG WMS Profile Normative Requirements
A DGIWG WMS server requirement only; normative requirements(mandatory) for a WMS 1.3 server implementation are found in Table
1. DGIWG WMS Profile Normative Requirements
A DGIWG WMS client shall support all GetMap request parameters.

24

A DGIWG WMS client shall support transparency.

M

25

A DGIWG WMS client shall support the INIMAGE EXCEPTIONS.

M

26

A DGIWG WMS client shall support the BLANK EXCEPTIONS.

M

27

A DGIWG WMS client shall support multi-dimensional data bysupporting the vertical Elevation and temporal Time request
parameters in accordance with the "OGC Best Practices for using
OGC WMS with Time-Dependent or Elevation-Dependent Data [2]"M

28

A DGIWG WMS client shall resolve sample dimensions by adding
additional parameters to the GetMap request.

M

29

A DGIWG WMS client shall support the FEATURE_COUNT
parameter.

M

30

A DGIWG WMS client shall support the EXCEPTIONS parameter
support of text/xml and text/html. Use of text/html is for the benefit ofhuman readable content.
A DGIWG WMS client shall support the INFO_Format parameter.

M

A DGIWG WMS client shall display the units of measure fordimensional values returned in a GetFeatureInfo response.
A DGIWG WMS client shall provide a user interface to hide and show
individual layers in the service.

M

22

31
32
33

N.A.
M

M

M

Table 7: Normative client requirements
The non-normative client recommendations requested by this profile are summarized inTable 8
No.

1

2

3

4

Recommendation

Compliance

If a service requires vector based graphical elements output, A
DGIWG WMS client should provide image/svg+xml (Scalable
Vector Graphics) for the GetMap operation.

O

A DGIWG WMS client should be able to display legends also for
raster layers representing numeric data like for instance elevationor temperature data.

O

A DGIWG WMS client should provide a link to the metadata
resource via a resolvable URL for example to a CSW server.
A DGIWG WMS client should be able to connect to, display andoverlay multiple services at the same time.

O
O

Table 8: DGIWG WMS Profile Non-normative Recommendations for Client
Implementation

36

STD-DP-14-013r3

16 November 2015

Annex E – UTM Grid and MGRS Grid System Handling in
WMS Clients and Portals(informative)

The Universal Transverse Mercator (UTM) Grid and Military Grid Reference System (MGRS)
Grid values are commonly used by military operational staff to exchange positions. Theyboth are based on an underlying set of Universal Transverse Mercator projections based onhorizontal cylinders which are distributed around the earth (there is a different projection foreach six degrees of longitude). UTM projection values tend to be large numbers (a pair of x
and y numbers) so to make these easier to deal with by humans, two grid systems (UTM
Grid and MGRS Grid) are used. Both allocate grid cells across the world, using the ‘Zone’
between 1 and 60 to define the UTM Projection and a letter to define the vertical dimension.

UTM Zones and Cell letters
So the intersection of the equator and Greenwich Meridian intersect (lat long 0,0) exists inseveral overlapping cells including 31N. Within a cell, UTM Grid simply allocates values
based on x and y increments in the projection, so: Lat Long 0, 0 would be UTM Grid 31N
0166021 0000000. MGRS however further subdivides the square into more lettered squares,
and so would be 31N AA 66021 00000 (see below).

MGRS Cell names

37

STD-DP-14-013r3

16 November 2015

Issues associated with UTM Grid and MGRS Grid Values in WMS Services
Firstly, there is the issue of using UTM Grid and MGRS Grid Coordinates. It is unlikely thatclient applications will want to request WMS display areas using either of these grid values,
as client applications are unlikely to internally use these Grids. Most client applications
convert the grid values to numeric Universal Transverse Mercator values using a table(associating the cell with an X/Y coordinate in UTM projection) and then work in UTM
coordinates.
Additionally there is an issue with treating a UTM Grid or MGRS Grid as a coordinate
reference system as there is no defined separation between ordinates (the Cell names of AA
etc. embody both X and Y) and therefore it is impossible to define individual ordinates or anaxis order which is mandatory for a CRS. Most common is for dialogs or entry methods that
support the grids to be included, and a conversion applied (which is as stated a simple table
look up). This is also true for querying where clicking on the map generates a grid value.
While it is quite possible to implement this in JavaScript another approach is to have a web
service (maybe WPS or a simple Restful service) which takes a Lat/Long or UTM value andgenerates a UTM grid or MGRS grid value and vice versa.
Displaying UTM Grid and MGRS Grid
A typical approach here is to have a Web Map Service which simply displays the relevant
UTM Grid or MGRS Grid at the correct resolution (see the examples above). This can thenbe simply added as a layer to the client over the background WMSs. Configuration of level ofdetail, colour style etc. is also potentially a requirement but this is a fairly simple service toproduce and is really unrelated to the coordinate system issues. However it would bepossible for it to provide a ‘GetFeatureInfo’ service which returned the coordinate values in
one or more grid systems that it is presenting.
It is not uncommon for most military focused client software packages (example below)
which in many cases exploit WMS to provide all of the above capabilities (including a UTM
Grid and MGRS Grid Helper, and Visualisation of the grids).

MapLink Pro MGRS/UTM Entry/Conversion and WMS Grid display (Lat Long/MGRS)

38