h0st1le has uploaded a patch.
Description:
In the ProjectionInfo() object the Equals() routine has the following description:
/// Gets a boolean that is true if the Esri WKT string created by the projections matches.
/// There are multiple ways to write the same projection, but the output Esri WKT string
/// should be a good indicator of whether or not they are the same.
The problem with this is it possible for various datasets to be using the same projection but use the OpenWKT string representation instead of the ESRI WKT. Additionally, issues may also arise with differences between the BIPM and American spelling (metre, meter), letter case's, and several other factors.
This patch remedies this by only comparing the actual values used to define the projection and disregards the naming conventions for each ProjectionInfo() altogether.
** A better fix may be to actually handle this in the ToEsriString() function, but that would require an extensive lookup, containing all possible naming discrepancies. Perhaps this could be yanked from a PostGIS installation or spatialreference.org? Open to ideas here...
Example shapefiles available for download here:
https://www.dropbox.com/s/psuvxrtavqq6vmo/examples_shapefiles.zip?dl=0