NAD83_to_HPGN GeodeticTransformation falsely claims to be EPSG::1474

[ravenAtSafe]

EPSG::1474 is Alabama specific, whereas this composite grid transformation covers all US territory, and doesn't even list Alabama first.

[Norm Olsen]

In the rush to get RFC-2 done in time, the generalized NAD83_to_HARN transformation got the EPSG code number of 1474 as it is the first of the several EPSG NAD83_to_NAD83(HARN) coordinate operation variations. This is an EPSG "Coordinate Operation" code, and is perfectly valid for Alabama. This is true even as the Alabama HPGN files are indeed the second file listed, but any geography within the coverage of the Alabama data files would indeed be converted by using the Alabama file set as the first file set listed is AZ and there is no chance for any conflict with Alabama geography.

Generally, tying up all the loose ends with regard to the two new dictionaries invented to implement RFC-2 has never been accomplished. This is complicated further by the implementation of RFC-7 which required the invention of 48hpgn.l?s data file set.

A significant effort is needed to: 1> Verify all EPSG number assignments 2> Add Geodetic transformations to the NameMapper, 3> Add Geodetic Paths to the NameMapper. 4> Assign EPSG datum codes, and then Coordinate Operation code values, to the geodtic transformation and geodetic path dictionaries. 5> Add testing procedures to regularly check that definitions are correctly defined and matched with EPSG counterparts.

Currently, the EPSG codes in the Geodetic Transformation and Geodetic Path dictionaries are for information only and are not used in the coordinate conversion engine. The above effort would require a month of developer time and the funding necessary to support such. As that is not likely to be forthcoming any time soon, this is, unfortunately, a "won't fix" issue.