There are various ways to get a map to show up in someone's web browser. One way is for the server to send predrawn map images (or tiles) to the browser, another way is for the server to send a bunch of text and attributes that the browser draws, and a third way is to draw the map on the server at the time of request and send the browser the completed map image. This third way is what we'll discuss in this lesson. It's sometimes called a dynamic map service because, being drawn on the fly, it reflects the most recent picture of the data. Contrast this with the tiled map approach, which represents a static picture of the data taken at one point in time (when all the tiles were generated).
Advantages of dynamically drawn map services
Because dynamically drawn map services retrieve the data and draw it at the time of request, they are useful for gaining a situational awareness of the most recent state of the data. They may be the only reasonable way to depict many features that are changing at the same time (such as the positions of each vehicle in a large fleet). Dynamically drawn maps may also be the best solution at large scales where tiled maps become too cumbersome to generate, store, or maintain.
Maps dynamically drawn through WMS allow you to apply a wide range of symbols and styles using a concept called Styled Layer Descriptors (SLDs), which is described later in this lesson. If you enjoy using the QGIS authoring environment for your maps, you can export an SLD and import it into GeoServer, thereby allowing web users to apply the same styling that you configured on the desktop. Map layers drawn by the web browser may not be able to use symbols as complex as ones drawn by the server.
Disadvantages of dynamically drawn map services
Waiting for the server to draw the map can be a slow painful experience, especially if there are many layers to render. A wait time of 2 - 3 seconds that may be considered acceptable on the desktop may not be tolerated by edgy web map users who are neither knowledgeable nor sympathetic to the type of back end technology being used. People now expect every map to perform as fast as Google Maps and, without using tiles, this can be difficult to achieve.
Dynamically drawn services are also much more susceptible to overload than tiled services if you have many users deciding they want to see the map at the same time. This presents a paradox: you want your map to be useful, but the more exposure it gets, the slower it will run if the server technology is not scalable.
If you know you have a limited audience for your application (such as a small municipality, or a team of scientists), you may safely decide that the performance of your dynamically drawn map service is "good enough." This can spare you the work of generating and maintaining a tiled service.
Server software for dynamically drawn maps
In this course, you'll use GeoServer for drawing dynamic map services through WMS. Other FOSS software that can do this includes:
- Map Server - Sometimes called the "Minnesota Map Server," this was developed at the University of Minnesota in the 1990s.
- QGIS Server - This is a promising-looking extension for QGIS that allows you to publish your QGIS map directly through WMS. It is currently not available for Windows.
- Deegree - Java-based FOSS for GIS web services, born out of Germany in the early 2000s.
- Others? - Because WMS is an open specification, any developer with enough skill and gumption can develop server software that supports it. Have you used any other FOSS software for creating WMS? Let us know about it in the course forums.
Proprietary GIS software such as Esri ArcGIS for Server also supports WMS and other OGC specifications. Although Esri has their own format for map services, many of their clients have interoperability requirements mandating that their web services be available through WMS. Hence, when you publish a map service in ArcGIS for Server, you see a checkbox that can allow the service to speak through WMS specifications.