To configure Infrastructure Map Server as WMS and/or WFS server
Change the Script name (the path) mapserver/mapagent/mapagent.fcgi to mapserver2012/mapagent/mapagent.fcgi.
The WFS Provider is currently for preview only. It may support connections to external WFS sources, but does not support connections to other Map Server WFS sources.
Symptom: Using the request=GetMap operation in Autodesk Map Server fails with an InvalidSRS exception, even though the request is well-formed and is using a valid EPSG code.
Background: The OGC WMS standard uses European Petroleum Standards Group designations for spatial reference systems (SRS's.) These take the form of EPSG:nnnn where nnnn is a number. For example, WGS 84 is represented as "EPSG:4326" and California zone 1 in US feet / NAD83 is "EPSG:2225" The coordinate system library used by Autodesk Map Server has only limited support for EPSG codes.
Solution: Autodesk Map Server overcomes this limited support by transforming the EPSG codes into OGC "Well Known Text" or WKT, which the coordinate system library can consume.
To enable Infrastructure Map Server - Web Map Service to use unsupported SRS codes
GEOGCS["WGS 84", DATUM["WGS_1984", SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]], TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]], UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9108"]], AXIS["Lat",NORTH],AXIS["Long",EAST],AUTHORITY["EPSG","4326"]]
Back up this file before making any changes.
<translate from="your:srs">your-wkt-string</translate>
In the line above, replace your:srs with the SRS that is exhibiting problems, and replace your-wkt-string with the WKT string for your SRS (as discussed in step 1). The results should look similar to the following example (truncated for simplicity):
<Define item="SRS.WKT.map"> <translate from="EPSG:21781">PROJCS["CH1903.LV03", ... </translate> <translate from="EPSG:9999">PROJCS["Troublesome.SRS", ... </translate> </Define>
You can put any number of <translate from=""></translate> elements into this definition. However, there is a memory and performance cost with using them, so it is best to define only those you need, and remove those that you do not need.