[mapserver-commits] r11663 - trunk/docs/en/ogc

[svn at osgeo.org]

Author: assefa
Date: 2011-05-06 07:27:28 -0700 (Fri, 06 May 2011)
New Revision: 11663

Modified:
   trunk/docs/en/ogc/wms_server.txt
Log:
change sentese to use inverted axis

Modified: trunk/docs/en/ogc/wms_server.txt
===================================================================
--- trunk/docs/en/ogc/wms_server.txt	2011-05-06 13:29:25 UTC (rev 11662)
+++ trunk/docs/en/ogc/wms_server.txt	2011-05-06 14:27:28 UTC (rev 11663)
@@ -610,7 +610,7 @@
 
 The axis order in previous versions of the WMS specifications was to always use easting (x or lon ) and northing (y or lat).  WMS 1.3.0 specifies that, depending on the particular CRS, 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 WMS portrayal operation shall account for axis order. This affects some of the EPSG codes that were commonly used such as ESPG:4326.  MapServer 5.x makes sure that coordinates passed to the server (as part of the GetMap BBOX parameter) as well as those advertised in the capabilities document reflect the inverse axe orders for EPSG codes between 4000 and 5000.
 
-MapServer 6.0 and up holds a list of epsg codes with north-south axis orientation. It is currently based on EPSG database version 7.6. It is also possible to define the axis order at build time for a specific ESPG code(see #3582). This allows for example to use the "normal" axis order for some of EPSG codes between 4000 and 5000. 
+MapServer 6.0 and up holds a list of epsg codes with inverted axis order. It is currently based on EPSG database version 7.6. It is also possible to define the axis order at build time for a specific ESPG code(see #3582). This allows for example to use the "normal" axis order for some of EPSG codes between 4000 and 5000. 
 
 In addition, the WMS 1.3.0 defines a series of new coordinate system. These are the once that are currently supported 
 in MapServer: