Changes between Version 2 and Version 3 of CsMapRfc3

Timestamp:

Jun 21, 2010, 11:04:41 AM (14 years ago)

Author:

Norm Olsen

Comment:

--

CsMapRfc3

@@ -31 +31 @@
 Mapping large portions of the EPSG or Oracle code sets through the NameMapper can be painfully slow.  Thus, this change will enable a very quick and easy way to build an association between CS-MAP key names and EPSG and Oracle code values.
 
-CS-MAP has, for many years, ignored the axis specification of official Coordinate Reference System (CRS) definitions as adhereing to the definitions precisely often produced undesireable results (i.e. maps that would be rotated and mirrored in host graphic display systems) adn ensuing service calls.  It is now becomming necessary when dealing with certain exchange formats to use the officially blessed axes orientations.  Placing the officially blessed axes orientation in the coordinate system definition enables a reliable and maintainable means of accessing both the CS-MAP quad code and the officially blessed quad code, comparing them, and acting accordingly when exporting/importing to/from certain data storage mechanisms.
+CS-MAP has, for many years, ignored the axis specification of official Coordinate Reference System (CRS) definitions as adhereing to the definitions precisely often produced undesireable results (i.e. maps that would be rotated and mirrored in host graphic display systems) and ensuing service calls.  It is now becomming necessary when dealing with certain exchange formats to use the officially blessed axes orientations.  Placing the officially blessed axes orientation in the coordinate system definition enables a reliable and maintainable means of accessing both the CS-MAP quad code and the officially blessed quad code, comparing them, and acting accordingly when exporting/importing to/from certain data storage mechanisms.
 
 == Proposed Solution ==
@@ -39 +39 @@
 == Implications ==
 
-Any code which references the currently unused elements in the three dictionary structures will not compile after this change.  This should not be a problem as CS-MAP has nevber used them, never provided any interface to them, never documented them, and CS-MAP has always forced these values to the default value of zero.
+Any code which references the currently unused elements in the three dictionary structures will not compile after this change.  This should not be a problem as CS-MAP has never used them, never provided any interface to them, never documented them, and CS-MAP has always forced these values to the default value of zero.
 
 == Test Plan ==
 
-TestN of the ConsoleTestCpp application, which currently compares the definition of elemnets which the NameMapper says are the same, will be modified to verify that the EPSG code, Oracle SRID, EPSG Quadrant codes are consistent with the NameMapper and the current version of the EPSG Parameter Dataaset.
+TestN of the ConsoleTestCpp application, which currently compares the elements of definitions which the NameMapper says are the same, will be modified to verify that the EPSG code, Oracle SRID, EPSG Quadrant codes are consistent with the NameMapper and the current version of the EPSG Parameter Dataaset.
 
 == Funding/Resources ==