MapDotNet UX Web Services now offer an OGC-compliant basic WMS service. This service can be consumed by MapDotNet RIM applications by using a tile layer with a WMSTileRequestor. It can also be consumed by third-party software. WMS is a standard way to "publish" maps so that other parties can build applications that display them. WMS request URLs will have a base URL with the following form
http://localhost/MapDotNetUX[your product version]/OGC/wms.ashx?map=Sample&
where the URL references the path OGC/wms.ashx within the web services site and includes the query string parameter map=[map ID] and a trailing '&'. This URL therefore references the "Sample" map on the local MapDotNet UX instance. (Note that for WMS tile layers in Silverlight or WPF applications, you would not use "localhost" as the server reference.)
WMS versions 1.1.1 and 1.3.0 are supported. Supported operations are GetMap and GetCapabilities.
When you do a GetCapabilities request against a MapDotNet UX map, the entire map is offered as a WMS layer named “Default”. If the “Default” layer is requested in a call to GetMap, the map will be rendered with every MapDotNet map layer having the visibility specified in the map file. The individual MapDotNet UX map layers are offered as nested layers within the “Default” layer. Instead of requesting the “Default” layer, these layers can be requested individually. MapDotNet UX maps will always be made available for WMS in both their specified projection and in WGS 84 (EPSG:4326, and, under WMS 1.3.0, CRS:84 also). Note that the QuantumGIS client does not recognize the “EPSG:3857” code used to refer to Spherical Mercator in our sample map.There are two optional metadata tags that can be used to affect how a MapDotNet UX map is available using WMS.
1. A MapDotNet UX map or layer can have a “WMS Abstract” metadata key. This is used to provide a WMS abstract as in the screen shot above.
2. A MapDotNet UX map can have a “WMS Extents” metadata tag. If present, this is used for the bounding box returned by GetCapabilities, otherwise the map’s InitialExtents property is used. A WMS GetMap response is not allowed to render features that are not within its specified extents, therefore you may want to use “WMS Extents” to provide a larger bounding box than specified in the map’s initial extents.
Disable the WMS service by modifying permissions on the OGC folder or by removing it.