{
  "id": "web-map-service",
  "title": "Web Map Service",
  "lang": "en",
  "source_lang": "en",
  "summary": "Web Map Service is an open standard for requesting georeferenced map images from servers, allowing geographic information from different sources to be displayed together.",
  "category": "geography",
  "subcategory": "",
  "type": "concept",
  "aliases": [
    "WMS",
    "OGC Web Map Service"
  ],
  "generated_at": "2026-11-04",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/web-map-service/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/web-map-service/",
      "json": "https://aiwiki.page/zh/web-map-service.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "Web Map Service (WMS) is an international standard for requesting georeferenced map images from a server over a network. Developed by the Open Geospatial Consortium (OGC), it defines how a client requests a map by specifying geographic layers, an area of interest, a coordinate reference system, an image size, and a rendering style. The server produces a visual representation of the requested geographic information, usually as a PNG or JPEG image. WMS allows applications to display maps from independently operated services without requiring direct access to their underlying datasets."
    },
    {
      "heading": "Purpose and operating model",
      "text": "WMS separates the storage and rendering of geographic information from its display. A server manages data and cartographic rules; a client requests a particular view and displays the returned image. Clients include desktop geographic information systems, browser-based mapping applications, and other software that consumes geographic services.\n\nThe underlying data may include vector features, such as roads and administrative boundaries, or raster data, such as aerial imagery and elevation grids. Although these sources differ structurally, a WMS can present them through the same request interface.\n\nA typical interaction proceeds as follows:\n\n- The client requests a description of the service and its available layers.\n- A user or application selects layers, styles, a geographic extent, and an output size.\n- The client submits a map request.\n- The server retrieves and renders the relevant data.\n- The client displays the returned image.\n\nA client can combine images from several servers when their coordinate systems and geographic extents are compatible. Transparent backgrounds allow one service’s roads, boundaries, or other thematic content to appear over another service’s background map.\n\nWMS standardizes the request and response interface, not the internal database, rendering software, or data-storage format."
    },
    {
      "heading": "Development and standardization",
      "text": "WMS emerged from late-1990s efforts to make web mapping systems interoperable. Before common interfaces became established, applications often depended on proprietary protocols or custom integrations to obtain maps from remote systems.\n\nOGC published WMS 1.0.0 in 2000. Subsequent versions refined service descriptions, request parameters, and coordinate-system handling. Two widely encountered versions are 1.1.1 and 1.3.0. WMS 1.3.0, published in 2004, became the basis of ISO 19128:2005, Geographic information — Web map server interface.\n\nVersion differences remain operationally important. A request written for one version cannot always be used unchanged with another, particularly because coordinate-system parameter names and coordinate-axis conventions differ."
    },
    {
      "heading": "Core operations",
      "text": "The basic WMS interface defines two mandatory operations, GetCapabilities and GetMap, and an optional operation, GetFeatureInfo.\n\nGetCapabilities\n\nGetCapabilities returns a machine-readable description of the service, normally encoded in XML. This capabilities document describes such information as:\n\n- Service identification, provider details, and access conditions.\n- Supported operations and response formats.\n- Available layers and their titles.\n- Supported coordinate reference systems and geographic extents.\n- Available styles.\n- Additional dimensions, such as time or elevation, where supported.\n\nLayers can be organized in a hierarchy. Some entries serve mainly as organizational groups, while named layers can be requested for display. Properties may be inherited through the layer hierarchy, so clients must interpret the document rather than treating every layer entry as independent.\n\nThe capabilities document is a description of what the service offers, not a download of its geographic datasets.\n\nGetMap\n\nGetMap requests a rendered map for a specified geographic extent. Important parameters include:\n\nParameter | Function\nSERVICE | Identifies the service type as WMS.\nVERSION | Specifies the WMS version.\nREQUEST | Identifies the operation as GetMap.\nLAYERS | Lists the layers to render, in drawing order.\nSTYLES | Specifies a style for each requested layer; empty entries request default styles.\nCRS or SRS | Identifies the coordinate reference system, depending on the WMS version.\nBBOX | Defines the requested geographic bounding box.\nWIDTH, HEIGHT | Define the output image dimensions in pixels.\nFORMAT | Specifies the output media type, such as image/png.\nTRANSPARENT | Requests a transparent background where supported by the format.\n\nServers commonly return raster images, but WMS is not intrinsically restricted to a single image encoding. The capabilities document advertises the supported formats.\n\nThe geographic extent and pixel dimensions together determine the image’s ground resolution. A larger output image covering the same extent requests finer sampling, although it cannot create detail absent from the source data.\n\nGetFeatureInfo\n\nGetFeatureInfo optionally returns information associated with a location in a map. A client typically sends this request after a user clicks on the displayed image. The request includes the relevant map context, the layers to query, and the pixel location.\n\nResponses may contain attributes, descriptive text, or other information in formats advertised by the server. Only layers marked as queryable support this operation.\n\nDespite its name, GetFeatureInfo is not a general feature-download interface. Its results and structure depend on the server, source data, and supported response formats. A response may describe a vector feature or report information about a raster location."
    },
    {
      "heading": "Coordinate systems and axis order",
      "text": "Correct handling of a coordinate reference system is essential to WMS interoperability. The same area can be expressed using geographic coordinates or a projected system based on a map projection. A server may support several systems and transform its source data into the requested one during rendering.\n\nA major difference between WMS versions concerns axis order:\n\n- WMS 1.1.1 uses SRS to identify the coordinate system and conventionally represents geographic bounding boxes in longitude–latitude order.\n- WMS 1.3.0 uses CRS and follows the axis order defined by the referenced coordinate system.\n\nFor example, in WMS 1.3.0, EPSG:4326 uses latitude–longitude axis order. Its bounding box therefore lists minimum latitude, minimum longitude, maximum latitude, and maximum longitude. By contrast, CRS:84 uses longitude–latitude order.\n\nConfusing these conventions can produce an empty image, an error, or a map of the wrong location. Clients must interpret the WMS version and the selected coordinate system together.\n\nEven when coordinate handling is correct, layers may not align perfectly because of differences in source accuracy, geodetic datums, transformation methods, or generalization."
    },
    {
      "heading": "Styling and multidimensional data",
      "text": "Cartographic styling\n\nWMS delivers a portrayal of data rather than merely exposing its geometry or values. Colors, symbols, labels, classification rules, and scale-dependent visibility determine the resulting cartography.\n\nA server can advertise several named styles for one layer. For example, an elevation dataset might be displayed as shaded relief or elevation bands. The same geographic features can therefore support different visual interpretations.\n\nThe Styled Layer Descriptor (SLD) specification extends styling capabilities by allowing clients to describe or reference styling rules where the service supports them. Client-defined styling is not a universal capability of every WMS implementation.\n\nTime and elevation\n\nWMS can describe dimensions beyond horizontal position. Services may advertise a TIME dimension for observations or forecasts and an ELEVATION dimension for vertical levels.\n\nFor example, a meteorological service may provide a layer for a selected forecast time and atmospheric pressure level. These dimensions enable repeated requests for different slices of a dataset, including map animations. Their availability, valid values, and interpretation depend on the service description."
    },
    {
      "heading": "Relationship to other geospatial services",
      "text": "WMS primarily answers the question: What should a map of this area look like? Related standards address different needs.\n\n- Web Feature Service (WFS) provides access to geographic features and their properties, supporting uses that require feature geometry and attributes.\n- Web Coverage Service (WCS) provides access to coverages, such as gridded measurements, where obtaining data values is more important than obtaining a rendered portrayal.\n- Web Map Tile Service (WMTS) serves map tiles through defined tile matrix sets. Fixed tile grids and scales facilitate caching and reuse.\n\nA WMS image made from a numerical elevation grid is not equivalent to downloading that grid. Colors may encode elevation classes or shaded relief, and the image may no longer preserve the original numerical values. This distinction matters for quantitative spatial analysis.\n\nWMS clients can request small, tile-shaped images, and WMS deployments can use caching. However, requesting rectangular images from WMS does not by itself make the service a WMTS."
    },
    {
      "heading": "Applications and implementations",
      "text": "WMS is widely used to distribute reference maps and thematic layers across organizational boundaries. Applications include environmental monitoring, land-use planning, geological mapping, infrastructure management, and disaster-response mapping.\n\nA planning application, for example, can display locally managed parcel boundaries alongside remotely maintained flood zones and protected areas. Each provider retains control of its data and rendering while users see the layers in a shared map view.\n\nCommon software supporting WMS includes GeoServer, MapServer, QGIS Server, and ArcGIS Server. Desktop clients such as QGIS and ArcGIS Pro can consume WMS layers.\n\nInteroperability does not require identical-looking maps across implementations. Rendering engines, fonts, label placement, data quality, and styling choices can produce different results even when servers comply with the same interface."
    },
    {
      "heading": "Limitations and operational considerations",
      "text": "Rendering cost and latency. Dynamic requests may require database queries, coordinate transformations, raster resampling, and label placement. Large images, complex styles, or many simultaneous requests can increase response times.\n\nLimited access to source data. An image generally does not expose feature geometry, full attribute tables, or original raster values. Access to a WMS therefore does not imply access to its underlying datasets.\n\nScale and resolution constraints. Layers may be intended for particular map scales. Enlarging an image or requesting a smaller extent does not guarantee additional detail. Cartographic generalization and scale-dependent rendering can change which features appear.\n\nVariable optional capabilities. Servers differ in supported coordinate systems, image formats, query responses, dimensions, and styling extensions. Clients cannot assume that every WMS offers every optional function.\n\nCaching and freshness. Cached images can improve performance but may lag behind changes in source data. Requests with many combinations of extent, size, style, and time also reduce cache reuse.\n\nAccess and licensing. The protocol does not grant permission to reuse a map or its source data. Authentication, licensing, attribution, and usage restrictions remain separate concerns. Nor does WMS alone define a complete security framework; deployment-level controls govern access to protected services.\n\nPresentation consistency. Combining independent services can produce conflicting symbols, labels, update dates, or classification schemes. Successful image overlay establishes technical compatibility, not necessarily semantic or cartographic consistency."
    }
  ],
  "links": [
    "map",
    "open-geospatial-consortium",
    "geographic-information-system",
    "geospatial-vector-data",
    "raster-data",
    "coordinate-reference-system",
    "map-projection",
    "cartography",
    "spatial-analysis",
    "land-use-planning",
    "cartographic-generalization"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}