[mapserver-commits] r11304 - trunk/mapserver

[svn at osgeo.org]

Author: jmckenna
Date: 2011-03-22 14:37:43 -0700 (Tue, 22 Mar 2011)
New Revision: 11304

Modified:
   trunk/mapserver/MIGRATION_GUIDE.txt
Log:
minor formatting

Modified: trunk/mapserver/MIGRATION_GUIDE.txt
===================================================================
--- trunk/mapserver/MIGRATION_GUIDE.txt	2011-03-22 19:33:11 UTC (rev 11303)
+++ trunk/mapserver/MIGRATION_GUIDE.txt	2011-03-22 21:37:43 UTC (rev 11304)
@@ -268,7 +268,14 @@
 WFS 1.1 axis orientation
 ------------------------
 
-The axis order in previous versions of the WFS specifications was to always use easting (x or lon ) and northing (y or lat).  WMS 1.1 specifies that, depending on the particular SRS, the x axis may or may not be oriented West-to-East, and the y axis may or may not be oriented South-to-North. The WFS portrayal operation shall account for axis order. This affects some of the EPSG codes that were commonly used such as ESPG:4326.  The current implementation makes sure that coordinates returned to the server for the GetFeature request reflect the inverse axis orders for EPSG codes between 4000 and 5000.
+The axis order in previous versions of the WFS specifications was to always use 
+easting (x or lon ) and northing (y or lat).  WMS 1.1 specifies that, depending 
+on the particular SRS, the x axis may or may not be oriented West-to-East, and 
+the y axis may or may not be oriented South-to-North. The WFS portrayal operation 
+shall account for axis order. This affects some of the EPSG codes that were commonly 
+used such as ESPG:4326.  The current implementation makes sure that coordinates 
+returned to the server for the GetFeature request reflect the inverse axis orders 
+for EPSG codes between 4000 and 5000.
 
 -------------------------------------------------
 Change of mime-type for the imagemap outputformat