[mapserver-commits] r8907 - trunk/docs/ogc

[svn at osgeo.org]

Author: assefa
Date: 2009-04-14 09:38:45 -0400 (Tue, 14 Apr 2009)
New Revision: 8907

Modified:
   trunk/docs/ogc/wms_server.txt
Log:
add examples of CRS usage

Modified: trunk/docs/ogc/wms_server.txt
===================================================================
--- trunk/docs/ogc/wms_server.txt	2009-04-14 13:37:47 UTC (rev 8906)
+++ trunk/docs/ogc/wms_server.txt	2009-04-14 13:38:45 UTC (rev 8907)
@@ -605,6 +605,7 @@
 
 - the axis changes
 - the introduction of new coordinate reference systems
+- the use of CRS parameter (instead of SRS)
 
 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.  The current implementation 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.
 
@@ -620,7 +621,16 @@
 - AUTO2:420004 (WGS 84 / Auto Equirectangular)
 - AUTO2:420005 (WGS 84 / Auto Mollweide)
 
+Example of requests
+-------------------
 
+Users can use the CRS:84 coordinate system and order the BBOX coordinates as long/lat: 
+- ...&CRS=CRS:84&BBOX=-180.0,-90.0,180.0,90.0&...
+
+Users can also use the ESPG:4326 coordinates and use the axis odering of lat/long:
+- ...&EPSG:4326&BBOX=-90.0,-180.0,90,180.0&...
+
+
 Some  Missing features 
 ----------------------