Changes between Initial Version and Version 1 of Ticket #83
- Timestamp:
- 11/29/10 08:23:42 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified Ticket #83 – Description
initial v1 1 The RFC 2 implementation included the conversion of all datum transformation definitions (previously maintained in the Datum D Ictionary) to the new form of datum transformations as defined by a record in the datum transformation dictionary. This appears to work fine for geodetic transformation definitions included in the standard CsMap distribution.1 The RFC 2 implementation included the conversion of all datum transformation definitions (previously maintained in the Datum Dictionary) to the new form of datum transformations as defined by a record in the Geodetic Transformation Dictionary. This appears to work fine for geodetic transformation definitions included in the standard CsMap distribution. 2 2 3 However, it is often the case where end users of applications using the CsMap library have created custom datum definitions (implying a custom geodetic transformation). It would be nice if the CsMap distribution included a/some fe taure(s) which would support the automatic conversion of such datum definitions to the the Geodetic Transformation dictionary format.3 However, it is often the case where end users of applications using the CsMap library have created custom datum definitions (implying a custom geodetic transformation). It would be nice if the CsMap distribution included a/some feature(s) which would support the automatic conversion of such datum definitions to the Geodetic Transformation dictionary format.
