3 | | 1. Turn on debugging. As of MapServer 3.7 the MAP, LAYER and CLASS objects have a DEBUG keyword. If you include a DEBUG keyword in objects giving problems following by a greater than zero number, then various debugging output about the map, layer or class may be generated. The quality and quantity of debugging output varies widely. Note: Using MS4.0.1 I discovered that the correct syntax for DEBUG is simply DEBUG ON/OFF. Attempting to use DEBUG 5, etc. in a map file results in addtional bugs. Very confusing. |
4 | | 2. Some additional debugging can be turned on from GDAL and OGR by setting the CPL_DEBUG environment variable to on. Similarly additional PROJ.4 debug info can be produced by setting PROJ_DEBUG to ON. |
5 | | 3. Use shp2img? from the commandline to test your map file if possible. It is often much easier to debug problems without the extra complications of the web environment. |
| 3 | 1. Use [http://www.mapserver.org/utilities/shp2img.html shp2img] from the commandline to test your map file if possible. It is often much easier to debug problems without the extra complications of the web environment. |
| 4 | 2. Turn on debugging. As of MapServer 3.7 the MAP, LAYER and CLASS objects have a DEBUG keyword. If you include a DEBUG keyword in objects giving problems following by a greater than zero number, then various debugging output about the map, layer or class may be generated. The quality and quantity of debugging output varies widely. Note: Using MS4.0.1 I discovered that the correct syntax for DEBUG is simply DEBUG ON/OFF. Attempting to use DEBUG 5, etc. in a map file results in addtional bugs. Very confusing. |
| 5 | 3. Some additional debugging can be turned on from GDAL and OGR by setting the CPL_DEBUG environment variable to on. Similarly additional PROJ.4 debug info can be produced by setting PROJ_DEBUG to ON. |