Web Mapping Services Overview (1/7)

Part 1: What is a WMS?

A Web Map Service (WMS) is an OGC (Open Geospatial Consortium) specification that “defines a common interface for disseminating digital maps, rendered from spatial data, across the Internet. WMS supports the networked interchange of web based map layers, which are generally rendered in a digital image such as JPEG, GIF, PNG, etc.”1

In English, a WMS is computer language (script) that tells a server, “gimme your map!” The server then responds by sending an image file to your (the client’s) browser (e.g., Firefox, etc.). It is important to note that a WMS is not a map mash-up or a slippy map, which are increasingly the norm of interactive web maps made for public consumption. For information on how those work, see Part 2.

A Web Map Service is a script. A WMS server is the piece of software that actually responds to the script and sends you your requested image. Examples of this software include MapServer (open source) and ArcIMS (proprietary). The term server is commonly used to also mean the physical computer running the server software, but technically, the computer is the host. The server is the software program that serves clients from the host.

A metaphorical diagram of server-client architecture


A standard WMS script consists of three different types of JavaScript requests (“can I have this please?”) made by a browser to a server.2 Each request is in the form of a URL (web address) that specifies the server and what information is being requested from it—what’s referred to as REST (REpresentational State Transfer) style. Two of the requests are required, and the third is optional.

The first request, GetCapabilities, asks the server for information about what it has to offer. It’s like asking to see the menu at a restaurant where everything is a-la-carte. The server gives you an answer in XML: I have these data layers and can give you this many tiles at once in these styles, etc.

The next thing that has to happen to make your map work is a GetMap request. This is like giving the waiter your order. The request includes a list of parameters that include the layer names, styles, a coordinate reference system, bounding coordinates of the map to be returned, the width and height of the map, and some other optional ones.3

The third type of request, GetFeatureInfo, is optional, and only works on layers that are queryable, meaning that it contains features with data you can access. This is something that is often set up to be triggered by clicking on a feature on the map, and the info that gets returned is shown in some kind of pop-up window or panel.

The end result of a WMS is a layer rendered in a client’s browser. Now, if you want the client to be able to do stuff to that layer—say, turn it on and off, move it around, zoom in and out, put other layers on top of it, etc.—you need a bit more JavaScript. In the bad old days of 2004, all this sort of script was custom-built, so you usually didn’t mess with it unless you were a professional programmer. But then along came Google Maps, raster tiles, and web map APIs.4


1Wright, D., Dwyer, N., Cummins, V., eds. 2011. Coastal Infomatics: Web Atlas Design and Implementation.New York: Information Science Reference.

2de La Beaujardiere, J. (ed.) 2005. Web Map Service. OGC 04-024, version 1.3. Open Geospatial Consortium Inc.

32012. Web Map Service. Wikipedia. Accessed June 21, 2012. <http://en.wikipedia.org/wiki/Web_map_service>