Add additional projection names

[brucedechant]

The following alternative and abbreviated projection names are missing:

1)  AE - Abbreviation for Albers_Conic_Equal_Area
2)  Cassini-Soldner - Alternative spelling
3)  Equidistant_Cylindrical
4)  LCC - Abbreviation for Lambert Conformal Conic
5)  LM - Abbreviation for Lambert Conformal Conic
6)  Lambert Conformal Conic - Alternative spelling
7)  Lambert_Conformal_Conic
8)  Lambert Conic Conformal
9)  Lambert_Conic_Conformal_1SP
10) Lambert_Conic_Conformal_2SP_Belgium
11) Lambert_Conic_Conformal_West_Orientated
12) Miller - Abbreviation for Miller_Cylindrical
13) Oblique_Mercator
14) Swiss - Swiss_Oblique_Cylindrical
15) TM - Abbreviations for Transverse_Mercator
16) UTM - Abbreviation for Transverse Mercator

Some of the above names are needed because the EQUAL() macro only does a simple case insensitive comparison. It should also ignore white space, "-", "_", and "," so that more matches can be found.

[brucedechant]

Updated file

[brucedechant]

Updated file

[brucedechant]

Updated file

[brucedechant]

Updated file

[warmerdam]

Bruce,

Can you provide some supporting detail on why these alternate projection names are valid? Are they "autodesk wkt"? If so, perhaps we need a morphFromADSK() and morphToADSK() methods as we do for ESRI. Alternatively we could have OGRSpatialReference::Fixup() method try to cleanup these non-standard names and set them to the standard values.

What I don't want to do is have all parts of the code have to understand many variations on the projection names.

I'm setting this as a 1.4.2 milestone since I don't think we can address it for 1.4.1. If the changes are quite broad we may need to limit the changes to 1.5.0.

[brucedechant]

Autodesk has several customers that have run into this while trying the open source release of MapGuide. The test suite of OGC WKTs from various sources (ESRI, EPSG, Autodesk, Oracle, etc...) have some of these alternative spellings.

[warmerdam]

Bruce,

To take a next step on this, I would like a variety of sample WKT input that you feel ought to work, and information on where it came from. I think the best approach would be further improvements to the Fixup() method that your code could use to try and normalize an OGRSpatialReference before it is used with code such as exportToProj4().

It seems these changes are substantial and disruptive enough that for now I think they should only be done in trunk, so I'm changing the milestone to 1.5.0.

[warmerdam]

Closing for lack of followup.