Web Map Service

Web Map Service
Name	Web Map Service
Developer	Open Geospatial Consortium
Released	1999
Latest release	1.3.0
Genre	Geospatial web service

Web Map Service Web Map Service is an interoperable internet protocol standard for producing spatially referenced maps as images and tiles, enabling interaction among systems such as ArcGIS, QGIS, MapServer, GeoServer, Google Maps. The standard, maintained by the Open Geospatial Consortium, specifies how clients like Leaflet (software), OpenLayers, Esri ArcGIS Server request rendered maps from servers such as MapServer and GeoServer for use in projects like OpenStreetMap, Natural Earth (data), Copernicus Programme. Widespread adoption links it to initiatives including INSPIRE, NASA WorldWind, USGS National Map, and platforms like Amazon Web Services and Microsoft Azure.

Overview

Originally developed by the Open Geospatial Consortium and standardized in 2000, the service defines a protocol for producing map images from spatial data stored in systems such as PostGIS, Oracle Spatial, Esri File Geodatabase, SpatiaLite. Implementations integrate with toolchains involving GDAL, PROJ, Mapnik, FDO (Feature Data Object), and coordinate reference systems like EPSG:4326 and EPSG:3857. The WMS model complements other OGC standards including Web Feature Service, Web Coverage Service, Catalogue Service for the Web, and links to cataloging initiatives like GeoServer community and datasets such as Landsat, Sentinel-2, SRTM.

Specification and Architecture

The specification defines request/response operations over protocols like HTTP, with XML-based metadata described using schemas related to ISO 19115, GML (Geography Markup Language), and bindings that echo patterns from SOAP, RESTful web services, and XML Schema. The architecture partitions concerns among clients like QGIS, servers like MapServer, proxies like NGINX, and tile caches such as MapProxy or Varnish, integrating standards like CSW and dependencies including XML, JSON, and coordinate transformations from PROJ.4. Profiles and versions (notably 1.1.1 and 1.3.0) address axis order issues debated in communities including OSGeo and projects like GeoNode.

Operations and Request Types

Core operations—GetCapabilities, GetMap, and GetFeatureInfo—are invoked via HTTP GET or POST and interoperate with clients such as OpenLayers, Leaflet (software), uDig, and servers such as GeoServer and MapServer. The GetCapabilities response references metadata frameworks like Dublin Core and coordinate systems like EPSG registry, while GetMap renders images in formats supported by libraries like libpng, libjpeg, and GDAL drivers; GetFeatureInfo bridges to data services including WFS and CSW. Extensions and vendor parameters appear in implementations by organizations such as Esri, Boundless (company), and research projects at NASA, USGS, European Space Agency.

Data Sources and Styling

WMS servers render data from vectors and rasters managed in sources such as PostGIS, GeoPackage, NetCDF, HDF5, Landsat, and Sentinel-1. Styling is specified using languages and formats including SLD (Styled Layer Descriptor), CSS (Cascading Style Sheets)-like approaches in Mapbox GL JS, and vendor styles in Esri ArcGIS Pro and QGIS; integration touches standards like ISO 19117 and tools like Mapnik, CartoCSS, and TileMill. Data provenance and attribution practices reference datasets such as OpenStreetMap and organizations like Natural Resources Canada and Ordnance Survey.

Implementations and Software

Open-source implementations include GeoServer, MapServer, QGIS Server, MapCache, and deegree, while commercial offerings come from Esri, Pitney Bowes, Hexagon Geospatial, and cloud services by Amazon Web Services and Google Cloud Platform. Libraries and toolkits that support WMS clients and servers include GDAL, Mapnik, Proj (library), and frameworks in languages supported by Python (programming language), Java, C++. Community and standards work is coordinated through organizations such as OSGeo, Open Geospatial Consortium, and projects like GeoNode, GeoServer community, and Boundless Desktop.

Use Cases and Applications

WMS underpins web mapping in applications ranging from government projects like USGS National Map and INSPIRE to academic efforts at NASA, European Space Agency, and NOAA. It supports environmental monitoring for programs such as Copernicus Programme, disaster response systems used by UN OCHA, and utilities mapping in corporations like Siemens. Other applications include historical cartography digitization linked to Library of Congress collections, cadastral mapping with agencies like Land Registry (United Kingdom), and mobile mapping in platforms built by companies like Mapbox and HERE Technologies.

Security, Performance, and Scalability

Operational concerns engage security frameworks like OAuth 2.0, TLS, and infrastructure components such as NGINX, HAProxy, and Kubernetes for scaling. Performance tuning relies on tile caching with systems like MapProxy and Varnish, pyramid storage using MBTiles or TileJSON, and cloud autoscaling offered by Amazon Web Services and Google Cloud Platform. Authentication and authorization schemes integrate with identity providers such as Keycloak, Auth0, and enterprise directories like Active Directory; resilience and monitoring often use tools like Prometheus, Grafana, and ELK Stack.

Category:Geographic information systems