Changes between Version 2 and Version 3 of MapGuideRfc95

Timestamp:

06/11/10 23:08:44 (15 years ago)

Author:

liuar

Comment:

--

MapGuideRfc95

@@ -20 +20 @@
 == Overview ==
 
-Enhance the WMS 1.3.0 implmentation of MapGuide according to OGC WMS 1.3.0 specification. The goal is to make sure MapGuide could pass the OGC certification for WMS 1.3.0 and 1.1.1 (http://cite.opengeospatial.org)
+Enhance the WMS 1.3.0 implmentation of MapGuide according to OGC WMS 1.3.0 specification. The goal is to make sure MapGuide could pass the OGC certification for WMS 1.3.0 and 1.1.1 (http://cite.opengeospatial.org).
 
 == Motivation ==
@@ -27 +27 @@
 
 == Proposed Solution ==
-Here are some proposed solution for two main changes in WMS 1.3.0
+Here are some proposed solution for two main changes in WMS 1.3.0.
 
 One significant change in WMS 1.3.0 is the axis orientation. In order to align with the definitions from the EPSG database, OGC WMS 1.3.0 specification reversed the axis sequence for some EPSG code include EPSG:4326. Which means for some EPSG CRS, the meaning of (x,y) is changed from (lon,lat) to (lat,lon) or even other orientations. 
 
-Some new API added in order to adapt the axis orientation issue in WMS 1.3.0
+Some new API added in order to adapt the axis orientation issue in WMS 1.3.0.
 
-CS_MAP will provide an API to obtain the axis orientation for one particular ESPG CRS
+CS_MAP will provide an API to obtain the axis orientation for one particular ESPG CRS.
 {{{
 // Parameter   nVendor=MgCoordinateSystemCodeFormat::Epsg
@@ -50 +50 @@
 }}}
 
-It is necessary for MapGuide implement an API ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in GetMap and GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat)
+It is necessary for MapGuide implement an API ProcessBoundingBoxAxes to handle different axis orientation for the bounding box parameter in GetMap and GetFeatureInfo operation. For example: change (lat,lon) back to (lon,lat).
 
 {{{
@@ -67 +67 @@
 The other important change in WMS 1.3.0 specification is the CRS namespace. WMS 1.3.0 specification introduced two more CRS namespaces besides EPSG, they are CRS namespace which in the form specified by ISO 19111 and  AUTO2 namespace is used for "automatic" coordinate reference systems.
 
-In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in OgcWmsService.config
+In order to pass the OGC certification, the CRS CRS:84 must be supported. There's a workaround that it could be predefined in OgcWmsService.config.
 
 {{{