Web Map Service

The Maxar Web Map Service (WMS) is an interoperable, distributed Web Mapping system which defines a set of functions that clients may use to achieve WMS capabilities. Any client making requests that conform to the OGC WMS specification can interact with the WMS server.

A simple and typical example of the structure of a Web Mapping application is a web-based client-server architecture.

Typical Structure of a WMS Application

In a Web Mapping scenario, the client application requests information from the Web Map Server. The Map Server retrieves the appropriate layers of geo-feature data from the database for the specified spatial domain and generates a Map, which is a simple graphic image (i.e. GIF or PNG) that can be viewed directly in a graphical web browser or other pictorial software. The client and Web Map Server interact using Hypertext Transfer Protocol Secure (HTTPS).

WMS Client-Server Architecture

The following architecture depicts a sample integration of WMS client and server applications. Client Viewer is a series of HTML pages running inside a web browser that can interact with the WMS server via client application through HTTP calls. The WMS client manages the interactions with WMS interfaces through HTTPS requests and dynamically generates HTML that can run in a web browser.

The WMS server accepts requests from the WMS client and viewer client in the form of HTTP URL strings, and returns results encoded as XML, GIF, GML, and so on. The database stores geo-feature data that can be accessed and utilized by the WMS server to generate GML documents or draw Maps.

Sample WMS Client Server Application

WMS Service Details

The Maxar WMS supports OGC WMS specification version 1.1.1. The Maxar WMS supports KVP request encoding only; no Simple Object Access Protocol (SOAP) or other protocols are supported. The Maxar WMS provides raster imagery data at multiple resolutions in various formats for use in GIS applications that support the WMS standard.

The Maxar WMS supports the following operations:

  • GetCapabilities The GetCapabilities request is used to obtain information about the supported Map layers, including various imagery layers and metadata layers.
  • GetMap The GetMap request is used to retrieve Map images of the layers contained in the Online Catalogs.
  • GetFeatureInfo The GetFeatureInfo request is used to obtain metadata (information) about the Features displayed in Map images retrieved via GetMap requests.
  • GetLegendGraphic The GetLegendGraphic request is used to obtain information about the display styling of the Map layers, specifically the metadata layers.

The Maxar WMS does NOT support the following optional capabilities:

  • DescribeLayer operation
  • GetStyles operation
  • PutStyles operation

As stated above, the Maxar WMS supports Map layers of both imagery and imagery metadata. The data for these layers is supplied in the following way:

  • When metadata layers are requested at Map scales smaller than approximately 1:230,000, an imagery bounding box is returned.
  • When a Map scale larger than approximately 1:230,000 is requested, only an image date is returned.
  • When imagery layers are requested at Map scales smaller than approximately 1:200,000 no imagery is returned.
  • At Map scales larger than approximately 1:200,000, Map images are returned.

Integration Procedure

A WMS client application is a program that communicates with the WMS server using the three functions GetCapabilities, GetMap, and GetFeatureInfo, as noted earlier. More specifically, in a typical WMS client/server interaction, the following steps can be followed:

Step 1

The client must first request GetCapabilities from the WMS server in order to determine what the Map server can do and what Maps the Map server can provide.

https://evwhs.digitalglobe.com/mapservice/wmsaccess?connectId=<CONNECTID>&service=WMS&request=GetCapabilities&version=1.1.1

Note: Replace <CONNECTID> with the connectId provided by Maxar. Parameters are not required to be in the same order as shown above.

Step 2

The client can request GetMap with the Map server's capabilities information in order to get a Map image. The Maxar WMS supports Maps in these formats:

  • PNG
  • JPEG
  • GEOTIFF
  • JPEG-PNG

https://evwhs.digitalglobe.com/mapservice/wmsaccess?connectId=<CONNECTID>&SERVICE=WMS&REQUEST=GetMap&version=1.1.1&SRS=EPSG:4326&BBOX=-73.8854994266476,40.6341176876158,-73.8606463081034,40.6501752378911&WIDTH=1102&HEIGHT=712&LAYERS=DigitalGlobe:Imagery&format=image/jpeg

Note: Replace <CONNECTID> with the connectId provided by Maxar. Parameters are not required to be in the same order as shown above.

Step 3

The client can request GetFeatureInfo by specifying a point on the Map to receive more geographic Feature information. This is an optional operation supported for those layers that have the attribute queryable="1". The canonical use case for GetFeatureInfo is that a user sees the response of a Map request and chooses a point 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, which layer(s) should be investigated, and in what format the information should be returned. 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, SRS, WIDTH, HEIGHT) in that GetMap request, along with the X,Y position the user chose, the WMS can possibly return additional information about that position.

https://evwhs.digitalglobe.com/mapservice/wmsaccess?connectId=<CONNECTID>&SERVICE=WMS&REQUEST=GetFeatureInfo&version=1.1.1&SRS=EPSG:4326&BBOX=-73.8854994266476,40.6341176876158,-73.8606463081034,40.6501752378911&WIDTH=1102&HEIGHT=712&QUERY_LAYERS=DigitalGlobe:ImageryFootprint&X=200&Y=150&LAYERS=DigitalGlobe:ImageryFootprint

Note: Replace <CONNECTID> with the connectId provided by Maxar. Parameters are not required to be in the same order as shown above.

Service Exceptions

The WMS server throws an exception when a client request is invalid or the requested data is not available. The WMS server sends the exception as an XML document with content that varies in different scenarios and operation failures.

The EXCEPTIONS parameter in a request indicates the format in which the client wishes to be notified of Service Exceptions. The only value of the EXCEPTIONS parameter that is defined for the WMS Web Service is "application/vnd.ogc.se_xml", which means "Service Exception XML". The error messages appear as <ServiceException> elements within the <ServiceExceptionReport> in Service Exception XML.

The table below shows the WMS exception codes as defined by OGC and implemented by Maxar.

WMS Exception Codes and their Meanings

Exception Code

Meaning

InvalidFormat

The request contains a format not offered by the service instance

InvalidSRS

The request contains an SRS not offered by the service instance for one or more of the layers in the request.

LayerNotDefined

The request is for a layer not offered by the service instance.

StyleNotDefined

The request is for a layer in a style not offered by the service instance.

LayerNotQueriable

GetFeatureInfo request is applied to a layer which is not declared queryable.

CurrentUpdateSequence

Value of (optional) updateSequence parameter in GetCapabilities request is equal to current value of Capabilities XML update sequence number.

InvalidUpdateSequence

Value of (optional) updateSequence parameter in GetCapabilities request is greater

than current values of Capabilities XML update sequence number.

The following sample requests generate different service exceptions:

WMS Layers

WMS Layers

OGC Layer

Description

Imagery

Imagery for all data layers available to the account, with the default display for a location determined by stacking profile.

ImageryFootprint

Vector representation of the raster Coverage available in the Imagery Layer.

CrisisEvent

Imagery from the FirstLook Product, with the most recent image displayed by default.

CrisisEventFootprint

Vector representation of the raster Coverage available in the CrisisEvent Layer.

LegacyCountryCoverage

Imagery from the DGWS 1.0 system, formerly known as Layerstack 49. Stacking profiles do not apply.

LegacyCountryCoverageFootprint

Vector representation of the raster Coverage available in the LegacyCountryCoverageLayer.

LegacyGlobalBaseMap

Imagery from the DGWS 1.0 system, formerly known as Layerstack 58. Stacking profiles do not apply.

LegacyGlobalBasemapFootprint

Vector representation of the raster Coverage available in the LegacyGlobalBaseMap Layer.

LegacyOilAndGasCoverage

Imagery from the DGWS 1.0 system, formerly known as Layerstack 48. Stacking profiles do not apply

LegacyOilAndGasCoverageFootprint

Vector representation of the raster Coverage available in the LegacyOilAndGasCoverage Layer.

API Reference

The API reference provides a list of all possible request parameters for every WMS operation as well as detailed information about corresponding response. The client should provide the respective information in a Key-Value Pair (KVP) format for every WMS request, where the "name" field is the key, and the "value" field is the value; the data is supplied in the format "key=value"; for example, "service=WMS".

The parameter name COVERAGE_CQL_FILTER is used for GetMap requests and the parameter name CQL_FILTER is used for GetFeatureInfo requests.