[mapserver-commits] r10215 - trunk/docs/en/optimization

[svn at osgeo.org]

Author: jmckenna
Date: 2010-06-08 12:33:43 -0400 (Tue, 08 Jun 2010)
New Revision: 10215

Modified:
   trunk/docs/en/optimization/debugging.txt
Log:
add brief mention of PROJ_DEBUG setting

Modified: trunk/docs/en/optimization/debugging.txt
===================================================================
--- trunk/docs/en/optimization/debugging.txt	2010-06-08 16:30:23 UTC (rev 10214)
+++ trunk/docs/en/optimization/debugging.txt	2010-06-08 16:33:43 UTC (rev 10215)
@@ -201,8 +201,27 @@
        ...
      END
    END
+   
+Step 4: Turn on PROJ_DEBUG (optional)
+------------------------------------
 
-Step 4: Test your Mapfile
+MapServer relies on the `PROJ.4 <http://trac.osgeo.org/proj/>`__ library to handle data projections, so
+you may wish to turn on PROJ debugging, to hopefully get more information back from the PROJ library.  
+You can trigger this PROJ output by setting the **PROJ_DEBUG** variable in your mapfile, 
+within the :ref:`MAP` object, such as:
+
+.. code-block:: mapfile
+
+   MAP
+     ...
+     CONFIG "PROJ_DEBUG" "ON"
+     ...
+     LAYER
+       ...
+     END
+   END
+
+Step 5: Test your Mapfile
 -------------------------
 
 Once you have set the *MS_ERRORFILE* and *DEBUG* level in your mapfile, you should now test
@@ -346,7 +365,7 @@
 .. HINT::
    You can check the attributes in the tileindex by executing "*ogrinfo -al*" on your data file
 
-Step 5: Check your Web Server Logs
+Step 6: Check your Web Server Logs
 ----------------------------------
 
 Once you have verified that there are no problems with you mapfile, next you should check your Web
@@ -416,7 +435,7 @@
 commandline, to make sure that MapServer loads properly.
 
 
-Step 6: Verify your Application Settings
+Step 7: Verify your Application Settings
 ----------------------------------------
 
 If you have verified that MapServer creates a valid map image through :ref:`shp2img`, you've checked