LLMpediaThe first transparent, open encyclopedia generated by LLMs

OGC Web Map Service

Generated by GPT-5-mini
⚠Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Goddard Earth Sciences Data and Information Services Center Hop 5
Expansion Funnel Raw 72 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted72
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
OGC Web Map Service
NameOGC Web Map Service
DeveloperOpen Geospatial Consortium
Released2000
Latest release1.3.0 (2006)

OGC Web Map Service The OGC Web Map Service is a standardized protocol for serving georeferenced map images over HTTP produced by a map rendering engine from spatial data. It enables interoperable requests between client software and server software developed by organizations such as the Open Geospatial Consortium, Esri, QGIS Project, MapServer (software), and GeoServer. Widely used across institutions including the United States Geological Survey, European Space Agency, NASA, United Nations, and World Bank, it underpins map delivery for applications in contexts like the Global Positioning System, Copernicus Programme, Landsat program, and MODIS.

Overview

The specification originated within the Open Geospatial Consortium as part of a broader push for spatial data interoperability alongside standards like Web Feature Service and Catalogue Service for the Web. It defines how clients such as OpenLayers, Leaflet integrations, and desktop systems like QGIS Project request rendered maps from servers such as GeoServer, MapServer (software), and proprietary platforms from Esri. Implementations support image formats used by projects including PNG, JPEG, and GeoTIFF to serve maps derived from data sources such as PostGIS, Oracle Spatial, Microsoft SQL Server, and GDAL/OGR-compatible rasters. The service is integral to initiatives like INSPIRE, National Spatial Data Infrastructure, European Environment Agency, and national mapping agencies including Ordnance Survey.

Specifications and Protocol

The architecture relies on HTTP methods defined by Hypertext Transfer Protocol and geospatial conventions formalized by the Open Geospatial Consortium. Core operations—GetCapabilities, GetMap, and GetFeatureInfo—are specified with parameters referencing coordinate reference systems like EPSG:4326 and EPSG:3857. The 1.3.0 profile aligns axis order handling with EPSG registry practices and interacts with specifications such as Web Coverage Service, Styled Layer Descriptor, and OGC Filter Encoding Standard. Security and transport considerations link to standards from IETF including RFC 7231 and authentication mechanisms influenced by OAuth 2.0 profiles used by agencies like USGS and platforms like GeoNode.

Operations and Parameters

GetCapabilities returns service metadata consumed by clients such as OpenLayers and ArcGIS Desktop; descriptions reference datasets hosted by repositories like Geonetwork and CKAN (software). GetMap accepts parameters including LAYERS, STYLES, CRS, BBOX, WIDTH, HEIGHT, FORMAT, and TRANSPARENT, mapping to imagery produced by engines like Mapnik or libraries such as PROJ and GDAL. GetFeatureInfo supplements raster output with attribute queries leveraged by systems like PostGIS and GeoServer’s WFS integration. Advanced parameters enable tiled delivery compatible with tile schemes used by Google Maps, Bing Maps, and OpenStreetMap tile servers, while vendor-specific extensions appear in products from Esri and MapInfo (Precisely).

Implementations and Software

Open-source servers implementing the standard include GeoServer, MapServer (software), deegree, MapProxy, and QGIS Server, each integrated into stacks using PostGIS, GDAL/OGR, and Apache HTTP Server. Proprietary implementations appear in Esri products such as ArcGIS Server and cloud services from Amazon Web Services used by organizations like NASA for mission data dissemination. Client libraries and viewers include OpenLayers, Leaflet, Cesium (software), ArcGIS API for JavaScript, and desktop GIS applications like QGIS Project and ArcGIS Pro, enabling workflows across research institutions like Scripps Institution of Oceanography and agencies such as NOAA.

Applications and Use Cases

WMS is deployed for thematic mapping in programs like Copernicus Programme and Landsat program, disaster response portals managed by United Nations agencies, environmental monitoring by the European Environment Agency, urban planning in municipal governments such as City of New York planning departments, and maritime charts distributed by International Hydrographic Organization members. It supports web mapping in open-data initiatives like OpenStreetMap and census cartography for agencies including United States Census Bureau. Scientific visualizations in projects at European Space Agency and NASA use WMS layers alongside services like Web Coverage Service and Sensor Observation Service.

Interoperability and Standards Integration

WMS interoperates with OGC family standards—Web Feature Service, Web Coverage Service, Catalogue Service for the Web, and Styled Layer Descriptor—and ties into broader internet standards from IETF and encoding formats like GML and GeoJSON. Integration with metadata initiatives such as ISO 19115 and discovery platforms including Geonetwork and CKAN (software) facilitates data reuse across institutions like European Environment Agency and United Nations programs. WMS conformance testing and validation are part of compliance frameworks used by the Open Geospatial Consortium and national spatial data infrastructures such as INSPIRE, ensuring compatibility among vendors including Esri, GeoServer, and MapServer (software).

Category:Geographic information systems