Skip to main content

SecureWatch Migration Guide

Overview​

SecureWatch customers, use this guide get started with your transition to the MGP Streaming APIs. This guide highlights the main differences between SecureWatch and MGP Pro Streaming APIs. Both SecureWatch and MGP streaming services conform to OGC standards.

SecureWatch has one API for streaming services. MGP Pro offers the following streaming APIs:

MGP APIContentUser Guide
Streaming - ImageryMaxar imagery featuresStreaming - Imagery user guide
Streaming - BasemapVivid basemaps and seamlinesStreaming - Basemap user guide
Vector AnalyticsChange Monitoring (CM) dataVector Analytics user guide

  • The URLs for MGP and SecureWatch are different. See example requests below.

  • MGP accepts an OAuth bearer token or an API key for authentication. SecureWatch uses Basic Auth with a Connect ID. There are no connect IDs in MGP. See Authentication.

  • In MGP the imagery layer name is Maxar:Imagery. In SecureWatch, the name is DigitalGlobe:Imagery.

  • In MGP, the available feature type for imagery is FinishedFeature.

  • MGP does not use feature profiles. Imagery results are returned beginning with the most recent.

  • Feature IDS formats are different. See Feature ID format.

Authentication​

MGP Pro requires an OAuth bearer token or a longer-lived API key for access. By default, API keys have a 180 day duration. This can be overridden when an API key is generated, but it cannot exceed 180 days.

Note: MGP does not use connect IDs

PlatformAuthentication method
SecureWatch APIsBasic authentication with username and password + connect ID
MGP APIsOAuth2 bearer token or API key

How to set up MGP Authentication​

All OGC services accept an API key or a bearer token for authentication.

Bearer tokens​

Oauth bearer tokens can also be used to authenticate API requests. Bearer tokens have a brief duration and must be refreshed frequently.

To authenticate with a bearer token, use the Authorization header:

Authorization: Bearer <Oauth2 token>

Learn about OAuth2 bearer tokens

API keys​

API keys can be passed using query parameters or in a custom header. No Authorization header is needed when using API keys.

To use the query parameter method, include this query parameter in your request:

maxar_api_key=<your API key>

The custom header takes the form of:

maxar-api-key: <your API key>

API keys expire 180 days from creation by default. A custom expiration date can be set but cannot exceed 180 days.

Learn about API keys

Base URLs​

SecureWatch base URL:

https://securewatch.maxar.com/

MGP base URL:

https://api.maxar.com/

MGP Authentication base URL:

https://account.maxar.com/  (for retrieving an Oauth2 Bearer token)

Feature ID format:​

The format of the unique identifier for the feature (feature ID) is different between SecureWatch and MGP.

  • SecureWatch: 098a113ee3f9743ec93a043f6ec5488e
  • MGP: 098a113e-e3f9-743e-c93a-043f6ec5488e (divided into 8-4-4-4-12 character groups)

WFS example​

WFS Get Feature with a bounding box​

This request returns metadata for Maxar Finished Features within the specified bounding box.

SecureWatch URL

https://securewatch.maxar.com/catalogservice/wfsaccess?SERVICE=WFS&REQUEST=GetFeature&maxFeatures=25&typeName=DigitalGlobe:FinishedFeature&VERSION=1.1.0&CONNECTID={{CONNECTID}}&BBOX=39.346038,-105.424805,40.131711,-104.545898

MGP URL

https://api.maxar.com/streaming/v1/ogc/wfs?service=WFS&request=GetFeature&typeNames=Maxar:FinishedFeature&version=2.0.0&count=25&bbox=39.346038,-105.424805,40.131711,-104.545898

WFS Get Feature with less than 5% cloud cover (cql filter example)​

This request uses a cql filter to find imagery features with less than 5% cloud cover.

SecureWatch URL

https://securewatch.maxar.com/catalogservice/wfsaccess?SERVICE=WFS&REQUEST=GetFeature%20&typeName=DigitalGlobe:FinishedFeature&VERSION=1.1.0&CONNECTID={{CONNECTID}}&srsName=EPSG:4326&CQL_Filter=cloudCover<.05

MGP URL

https://api.maxar.com/streaming/v1/ogc/wfs?service=WFS&request=&typeNames=Maxar:FinishedFeature&version=2.0.0&srsName=EPSG:4326&cql_filter=cloudCover<.05

In a WFS request, the bounding box and cql filter parameters are mutually exclusive and cannot be used together. To search for imagery features by both bounding box and a filter value, combine them into a multi-clause cql filter.

cql_filter=BBOX(featureGeometry,39.7530,-104.9962,39.7580,-104.9912) AND cloudCover<.05

Example MGP URL:

https://api.maxar.com/streaming/v1/ogc/wfs?service=WFS&request=GetFeature&typeNames=Maxar:FinishedFeature&version=2.0.0&srsName=EPSG:4326&cql_filter=BBOX(featureGeometry,39.7530,-104.9962,39.7580,-104.9912) AND cloudCover<.05

Learn more: OGC WFS User Guide

WMS example​

WMS request for a specific feature by ID​

SecureWatch request URL:

https://securewatch.maxar.com/mapservice/wmsaccess?CONNECTID={{CONNECTID}}&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=39.7530,-104.9962,39.7580,-104.9912&CRS=EPSG:4326&WIDTH=512&HEIGHT=512&LAYERS=DigitalGlobe:Imagery&FORMAT=image/png&cql_filter=featureId='098a113ee3f9743ec93a043f6ec5488e'

MGP request URL:

https://api.maxar.com/streaming/v1/ogc/wms?service=WMS&request=GetMap&version=1.3.0&BBOX=39.7530,-104.9962,39.7580,-104.9912&CRS=EPSG:4326&WIDTH=512&HEIGHT=512&LAYERS=Maxar:Imagery&FORMAT=image/png&cql_filter=featureId='098a113e-e3f9-743e-c93a-043f6ec5488e'

Learn more: OGC WMS User Guide

WMTS example​

WMTS Get Tile request​

SecureWatch request URL:

https://securewatch.maxar.com/earthservice/wmtsaccess?SERVICE=WMTS&VERSION=1.0.0&STYLE=&REQUEST=GetTile&CONNECTID={{CONNECTID}}&LAYER=DigitalGlobe:Imagery&FORMAT=image/jpeg&TileRow=18200&TileCol=27207&TileMatrixSet=EPSG:4326&TileMatrix=EPSG:4326:16&featureProfile=Consumer_Profile

MGP request URL:

https://api.maxar.com/streaming/v1/ogc/gwc/service/wmts?service=WMTS&request=GetTile&version=1.0.0&layer=Maxar:Imagery&format=image/jpeg&tileCol=27207&tileRow=18200&tileMatrixSet=EPSG:4326&tileMatrix=EPSG:4326:16

Learn more: OGC WMTS User Guide

Third-party integrations​

ESRI MGP Add-ins​

Integration examples​