NOTE: This page is work in progress. == OGC WMS Driver == Primary goal of the project is to allow remote access to geospatial image data using WMS protocol. The driver will be compatible at least with version 1.3.0, 1.1.1 and 1.1.0 specifications. Secondary goal is to allow remote access using other WMS-like or tile protocols including WMS-C, TMS, TileService. === Details === * server address and parameters via xml file and embedded in dataset name * complete information in xml file * example1.xml {{{ 1.3.0 http://127.0.0.1/mapserv.cgi CRS:83 image/png layer1,layer2 style1,style2 -180.0 180.0 -90.0 90.0 0.01 0.01 -180.0 -90.0 256 256 /tmp/example1_cache }}} * dataset name {{{ WMS:example1.xml }}} * minimal information in xml file (other values extracted from GetCapabilities response / defaults) * example2.xml {{{ http://127.0.0.1/mapserv.cgi layer1,layer2 }}} * dataset name {{{ WMS:example2.xml }}} * minimal information in xml file, layers selection in dataset name * example3.xml {{{ http://127.0.0.1/mapserv.cgi }}} * dataset name {{{ WMS:example3.xml:Service,Layers=layer1,layer2,layer3 }}} * issue and parse GetCapabilities requests * provide simplified human-readable version for gdalinfo * store layer/style name, description, legend url, etc. in GDAL dataset meta-data fields * two image data access methods * tiled: data is requested in small blocks, cached * immediate: one request per RasterIO call, not cached === External links === * [http://www.opengeospatial.org/standards/wms#downloads OGC WMS Specification] * [http://wiki.osgeo.org/index.php/Tile_Map_Service_Specification TMS Specification] * [http://wiki.osgeo.org/index.php/WMS_Tiling_Client_Recommendation WMS Tiling Client Recommendation] === People === * Adam Nowacki (student) * email nowak@xpam.de * talk using irc.freenode.net, channel #gdal, nick Nowak * Daniel Morissette (mentor)