Opened 13 years ago
Closed 13 years ago
#1813 closed defect (invalid)
RFC 94 Upgrade -- Add missing Geodetic API
| Reported by: | NormOlsen | Owned by: | NormOlsen |
|---|---|---|---|
| Priority: | high | Milestone: | 2.3 |
| Component: | General | Version: | 2.2.0 |
| Severity: | minor | Keywords: | Geodetic Path |
| Cc: | Hugues.Wisniewski@…, NormOlsen | External ID: |
Description
It was recently discovered that the implementaion of RFC 94, completed a year ago, is missing a required API. Specifically, an API which returns the name of the geodetic path definition used when a geodetic transformation was generated from an explicit geodetic path definition. The API is rather simple, simply return a STRING which contains the name of the definition which is now available in the CsMap geodetic transformation definition structure.
This API is needed to complete other development work.
Note:
See TracTickets
for help on using tickets.
Oops! Mis-communication. The required API does indeed exist (see updated Trac 1787). However, the missing method is actually a method of the MgCoordinateSystemTransform object, and it returns a reference counted pointer to an MgCoordinateSystemGeodeticPath object.
A null pointer is returned if the geodetic portion of the MgCoordinateSystemTransformation object was 'not' derived from an explicit geodetic path specification.