- In addition to the standard WMS URL parameters, the WMS service also supports many custom URL parameters. See Custom service URL parameters for details. Standard GetMap request URL parameters: WMS parameter info; BBOX. Specifies the bounding box of the requested image. Coordinates must be in the specified coordinate reference system.
- Enter the URL of the WMS service you wish to view (available from the WMS Services web page of the Geoscience Portal). type in a name for the WMS service. click the “WMS” radio button. if you know the WMS version number, choose it from the “Version” drop down list.
A Web Map Service (WMS) is a standard protocol developed by the Open Geospatial Consortium in 1999 for serving georeferenced map images over the Internet. These images are typically produced by a map server from data provided by a GIS database. – WMS is unique among online slot designers in that some of their Web and mobile slots are derived from land-based originals. Such is the case with Zeus. Williams has actually released three different Zeus titles, such was the popularity of this game.
The platform offers an application-programming interface (API) that provides developers with the ability to search, discover, assess and access data and information products such as maps, images, photos and documents.
Map Services
Note :
- A wide variety of map services is available on the Open Government Portal.
- More information on the Geospatial Standards and Operational Policies for Web Map Services (WMS)
- Information on the closing and the stopping updates of several Web Map Service (WMS)
| Service* | Description | Protocol | Language | Description and visualization on Open Government Portal |
|---|---|---|---|---|
| CBMT3978 / CBCT3978 | Canada Base Map – Transportation Service (tiled) / Carte de base du Canada - Transport (tuilé) | REST tiled, WMTS | English/ French | Available Soon |
| CBMT / CBCT | Canada Base Map – Transportation Service (WMS) / Carte de base du Canada - Transport (WMS) | WMS | English/ French | Available Soon |
| canvec_en / canvec_fr | Topographic data of Canada - CanVec Series / Données topographiques du Canada - Série CanVec | WMS | English/ French | View CanVec |
| railway_en / railway_fr | National Railway Network - NRWN - GeoBase Series / Réseau ferroviaire national - RFN - Série GéoBase | WMS | English/ French | View Railway |
| hydro_network_en / hydro_network_fr | National Hydro Network - NHN - GeoBase Series / Réseau hydrographique national - RHN - Série GéoBase | WMS | English/ French | View Hydro |
| arcticsdi_en | Canada Arctic SDI Base Map / Carte de base du Canada Arctic SDI | WMS | English | - |
| elevation_en / elevation_fr | Elevation Data Web Mapping Service – DEM – DSM / Service de cartographie Web pour les données d'élévation - MNE - MNS | WMS | English/ French | View Elevation |
| CBME_CBCE_HS_RO_3978 | The Canada Base Map - Elevation (CBME) (tiled) / Carte de base du Canada – Élévation (CBCE) (tuilé) | REST tiled | Bilingual | - |
| coverage_HRDEM_en / coverage_HRDEM_fr | Coverage of the high resolution digital elevation model (HRDEM) product - CanElevation Series / Couverture du produit Modèle numérique d'élévation haute résolution (MNEHR) - Série CanElevation | REST | English/ French | View Coverage HRDEM |
| NTS_SNRC | NTS grid / Grille SNRC | REST | Bilingual | Available Soon |
| UTM | UTM grid / Grille UTM | REST | Bilingual | Available Soon |
| Graticule | Grid of longitude and latitude lines / Quadrillage des lignes de longitude et latitude | REST | Bilingual | Available Soon |
*Copy link URL in a WMS Client, for example in GIS software and applications.
Open Government API
The Government of Canada aims to publish data in an open format and provide people with easy and reliable access to data, all while reducing barriers to entry, promoting innovation and eliminating unnecessary costs for businesses using the data.
Free Wms Server Url
Structured data is usually in the form of text but follows a specific format giving it machine readability. Some more complex formats may be in binary format such as maps and GIS related files. You will find many different formats in the Open Government Portal. More information on Working with Data and Application Programming Interfaces is available on the Open Government Portal.
GeoLocation API
Note: Please note that the service is also available via the https protocol.
Overview
The Geolocation service allows end users to get the geographic location of named features. The current service allows the location of following features:
- Street addresses
- Street names
- Streets intersection
- Place names such as towns, villages, municipalities, parks
- Natural geographical features such as lakes, islands, rivers, mountains
- Postal codes (FSA code only - first three characters)
- Map numbers from the National Topographic System (NTS)
For a complete description and request examples, please see the section Geolocation Service.
Delimitation Service
Description
The service provides access to geometry extents (delimitation) for various type of tessellation of the Canadian landmass. The service currently offers delimitations from the following coverages:
- Drainage Areas (detailed or generalized geometries)
- Landsat Footprints
- Map Sheets from the National Topographic System (NTS)
For a complete description and request examples, please see the section Delimitation Service.
Elevation API
End User Documentation
Elevation API provides information about the relief based on two data source:
Canadian Digital Elevation Model (CDEM)
Canadian Digital Surface Model (CDSM)
For a complete description and request examples, please see the section Elevation API.
Maps for HTML
Users have the ability to easily create their own customizable maps in a web browser. To create a map in your web page using open geospatial data, you simply write an HTML element, as follows:
The above HTML code will render a customizable, interactive map in most web browsers:
Further information about how to mark up an HTML document to create maps with the custom HTML map element can be found in the Maps for HTML - Tutorial.
Map Markup Language
MapML allows browsers to render and users to interact with maps directly, as illustrated above. Typical web services require specialized client software, but MapML is designed for use in the browser, to be consumed by the
MapML services
Discover Map Markup Language (MapML) services listed by projection.
For Further Information
Further information about MapML can be found in the specification. In order to receive community support with using the custom map element and MapML, please consider participating in the Maps for HTML Community Group and contributing via Github.
NapGen (NAP XML Generator)
Overview
NapGen generates NAP-conformant XML for a database.
NAP (North American Profile of ISO 19115:2003 — Geographic Information — Metadata) is a National Standard of Canada. It is a recommendation on organizing geographic information. NAP includes a schema which defines placeholders for data and their relationships.
With NapGen, you interactively navigate a tree of placeholders to map them to database data. NapGen then generates a NAP-conformant XML file for each database record and applies schema-based validation to the generated XML.
NapGen includes a tool - NAP File Validator. You can use it to validate an XML file according to the NAP schema.
Operating Environment
NapGen is web-based (served up by Apache running on 32-bit Windows 7 or XP).
You can use it with Google Chrome, Microsoft Internet Explorer, and Mozilla Firefox.
The supported DBMSes are Microsoft SQL Server, Oracle, and PostgreSQL.
Installation
To install NapGen, download the distribution zip, un-zip it, then click on the file aaaReadme.html.
The Open Geospatial Consortium, Inc. (OGC) Web Map Service (WMS) specification is an international specification for serving and consuming dynamic maps on the Web. WMS services are useful if you want to make your maps available online in an open, recognized way across different platforms and clients. Any client built to support the WMS specification can view and work with your service. Four versions of the WMS specification have been published so far. They are v1.0.0, v1.1.0, v1.1.1, and v1.3.0 (most recent).
Client applications work with a WMS service by appending parameters to the service's URL. WMS services published with ArcGIS Server support the following three operations:
- Request metadata about the service (GetCapabilities)
- Request a map image (GetMap)
- Request information about features in the map (GetFeatureInfo (optional))
It is not necessary for a WMS service to support all the operations. But one must support at least GetCapabilities and GetMap operations to be a 'Basic WMS', and support optional GetFeatureInfo operation to be a 'Queryable WMS'.
The maps returned by a WMS service are images only. They do not contain actual data. To expose your data as vector features through OGC specifications, publish a WFS service instead. To expose data as raster layers, publish a WCS service. You can publish both WFS and WCS services using ArcGIS Server 9.3.
You can learn more about WMS services at the Open Geospatial Consortium Web site. ESRI also maintains an Interoperability and Standards Web page detailing its support for OGC services in ArcGIS.
Publishing a WMS service in ArcGIS Server
There are two ways you can publish a WMS service using ArcGIS Server:
- Publish a map service with the WMS capability enabled. To publish a map service, you first need to create a map document.
- Publish an image service with the WMS capability enabled. To publish an image service, you need to have either a raster dataset or a compiled image service definition file from ArcGIS Image Server.
You can use either ArcGIS Server Manager or ArcCatalog to publish the service. If you need help with this step, see Publishing a GIS resource to the server.
When you publish your map or image service, you should enable the WMS capability by checking the box in the Capabilities list.
Notes:
- The number of layers in the map directly affects the amount of time it takes to initially create the WMS service or start it after it has been stopped. You may be able to reduce the startup time by removing or consolidating layers in the service.
- At ArcGIS Server 9.3, WMS services take advantage of a map cache if one is available. The map cache is only used when requesting the original projection, layer order, and layer visibility of the service. The cached tiles are resampled to fit the scale requested by the client, which can take some processing time and reduce the image quality. You'll see the most benefit using a cache if your WMS service has many layers or sophisticated symbology that would otherwise take a long time to draw dynamically. If you have just a few layers and simple symbology, you may get better performance without a cache.
After you publish the service, you can set further properties for the WMS service on the Capabilities tab of the Service Properties dialog box.
For a detailed walk-through of the process of creating a WMS service, see Tutorial: Publishing a WMS service.
Configuring WMS service properties
A WMS service's properties are reflected in its capabilities files so that whoever consumes the service can have a better understanding of the service publisher. When publishing a WMS service with system generated capabilities files (the default), it is recommended you populate the WMS service properties except for Name, Title and OnlineResource. The Name and Title service properties are pre-filled in with WMS and the name of the map service or image service, and OnlineResource is pre-filled in with the URL of the WMS service. In most cases you should not change those three properties.
To populate or modify WMS service properties, do the following:
- Stop the parent map or image service.
- Open the Service Properties and click the Capabilities tab.
- In the list of capabilities, find WMS. Make sure the box is checked, then click the letters WMS (be careful not to uncheck the box). You'll see some properties appear.
- Select 'Enter service properties below'. This means your service is going to use a system-generated capabilities file.
- Modify the service properties appropriately.
- Save and restart the parent map or image service.
Free Wms Service
Note: The OnlineResource field is necessary for a WMS client to communicate correctly with your WMS service. Usually its value is a URL and it should show up in the Web Access box of the Capabilities tab.
Configuring the SLD path or URL
Styled Layer Descriptors (SLDs) allow you to publish multiple styles for each WMS layer. If you are binding an SLD file to the current WMS service, you need to set the 'SLD path or URL' property to the URL, UNC path, or physical location of an SLD XML file. Learn more about working with SLDs.Securing WMS services
The security for an ArcGIS Server WMS service is managed by controlling the security of its parent map or image service. If a particular role, for example Planners, is denied access to a map, then Planners will not be able to access the map no matter whether they try to consume it through SOAP, representational state transfer (REST), or OGC (for example, WMS) interfaces. ArcGIS Server supports a number of different authentication schemes including HTTP-based authentication (Basic and Digest), Integrated Windows Authentication, and ArcGIS Server managed token-based authentication.
HTTP authentication and Integrated Windows Authentication
Services that are expected to be accessed via WMS interfaces should be secured using HTTP Basic, HTTP Digest or Integrated Windows Authentication. Most WMS clients (both non-ESRI as well as ESRI clients) will understand and work with these widespread standard authentication schemes.
ArcGIS Server managed token-based authentication
Although not recommended, a WMS service can still be secured using ArcGIS Server managed token-based authentication by using this type of authentication on its parent map or image service. Most third-party WMS clients will not be able to connect to WMS services secured in this way; but to make raw requests to WMS services protected by a token, you can get a valid token from the token service and append the token string as an extra parameter to the requests you send out. In other words, requests to a token-secured WMS service must use the following format: http://<WMS_service_url>?<standard WMS parameters>&token=<valid_tokenString>
Consuming WMS services
To connect to a WMS service, you need to know the URL. WMS services published with ArcGIS Server have this URL format:
Remember that the WMS capability is available for both map services and image services. This is why there are two options for the service type.
For example, if you have a folder Japan containing the map service Tokyo, running on myServer with the default instance arcgis, the URL of your WMS service would look like this:
If you have an image service IdahoImages running on myServer with the instance name of PublicLands, your URL for the WMS service would look like this:
Common WMS clients
A Web browser is the simplest client of a WMS service. WMS requests can be issued through HTTP, and the responses or exceptions are returned through the browser. WMS services support three operations: GetCapabilities, GetMap, and GetFeatureInfo. Through URL parameters, a client can use these operations to obtain metadata, maps, and feature information from the WMS service. These operations and parameters are detailed in the OGC WMS specifications.
ESRI WMS clients include ArcGIS Desktop (ArcCatalog and ArcMap), ArcExplorer, ArcGIS Server Web Application Developer Framework (ADF) for .NET, ArcGIS Server Web ADF for Java, and ESRI GIS Portal Toolkit Map Viewer.