Changes between Version 2 and Version 3 of MapGuideRfc98

Timestamp:

Jun 21, 2010, 10:21:44 AM (14 years ago)

Author:

NormOlsen

Comment:

--

MapGuideRfc98

@@ -24 +24 @@
 == Overview ==
 
-CS-MAP Rfc 2 proposes to add three items to the coordinate system dictionary, and one item each to the Datums and Ellipsoid dictionaries.  (The format doesn't change, we'll be using currently unused holes in the structures.)  This RFC proposes to expose these new data values throught eh MgCoordinateSystem interface.  The items being added are EPSG code, Oracle SRID code, and the EPSG Quadrant code.
+CS-MAP RFC 2 proposes to add three items to the coordinate system dictionary, and one item each to the Datums and Ellipsoid dictionaries.  (The format doesn't change, we'll be using currently unused holes in the structures.)  This RFC proposes to expose these new data values through the MgCoordinateSystem interface.  The items being added are EPSG code, Oracle SRID code, and the EPSG Quadrant code.
 
 == Motivation ==
 
-The EPSG code and the Oracle SRID code are becomming frequently desired/referenced data items.  Conversion between CS-MAP key name and EPSG code is currently possible, but requires the use of the NameMapper which can be rather slow if one intends to map large segments of the EPSG code set.  While supported in the NameMapper, mapping between CS-MAP key names and Oracle SRID codes is not expsed through the interface.  Implementation of this RFC would, in conjunction with CS-MAP RFC 2, enable direct access to both codes using the MgCoordinateSystem interface.
+The EPSG code and the Oracle SRID code are becomming frequently desired/referenced data items.  Conversion between CS-MAP key name and EPSG code is currently possible, but requires the use of the NameMapper which can be painfully slow if one intends to map large segments of the EPSG code set.  While supported in the NameMapper, mapping between CS-MAP key names and Oracle SRID codes is not expsed through the MgCoordinateSystem interface.  Implementation of this RFC would, in conjunction with CS-MAP RFC 2, enable direct access to both codes using the MgCoordinateSystem interface.
 
-There exists a problem encountered when using the latest version of WMS specification.  This specification now requires strict adherence to the axis specifications in Coordinate Reference System (CRS) definitions.  CS-MAP RFC 2 calls for the addition to the coordinate system dictionary an quadrant value (using the same values as the standard CS-MAP quad parameter) which indicates what the EPSG definition indicates the axis specification to be.  Implementation of this RFC will expose this value through the MgCoordinateSystem interface.
+There exists a problem encountered when using the latest version of WMS specification.  This new specification now requires strict adherence to the axis specifications in Coordinate Reference System (CRS) definitions.  CS-MAP RFC 2 calls for the addition to the coordinate system dictionary an quadrant value (using the same values as the standard CS-MAP quad parameter) which indicates what the EPSG definition indicates the axis specification to be.  Implementation of this RFC will expose this value through the MgCoordinateSystem interface.
 
 == Proposed Solution ==