OGC Web Map Server Development

* Note: this approach is now deprecated as OGC WMS server capabilities are supported by MapServer as of version 3.5

Concepts that will be covered:

OGC-compliance of GCDB dataset
thin client browser
MapServer implementation

Supporting Specifications / Documentation

Course relevance: Computer Visualization as a spatial data analysis techinque. Todo

Carry on w/ reference to last paper
Talk about GeoGratis / CEONet approaches
Lead into OGC distributed spatial computing approach

underlying dataset

filter /rendering service

Mapserver devel
Building an OGC-compliant spatial data server

Capabilities

Map

Feature Info

OGC Required Input	Example	UMN MapServer Equivalent	Example
WMTVER	1.0.0	None	None
REQUEST	capabilities	mode	map
LAYERS	gcdb_allpts	layers	gcdb_allpts
STYLES	POINTS	TYPE	POINT
SRS	EPSG:4326	PROJECTION	geographic
BBOX	-131.877638,76.309046,-96.972061,55.407591	mapext	-131.877638+76.309046+-96.972061+55.407591
WIDTH	300	mapsize	300+n
HEIGHT	150	mapsize	n+150
FORMAT	GIF	None	None

The table above illustrates how OGC amd UMN MapServer variables are interchangeable. The key here is to write a wrapper to handle an incoming OGC style request and render it via the MapServer service. getCapabilities requests do not require MapServer; in this case, the wrapper shall redirect the request to the capabilities XML file.

capabilities.xml

Sample requests

Web Mapping / Spatial Data Warehousing Home