Re: [gdal-dev] pcs.csv values don't match spatialreference.org

2013-06-27 Thread David Strip
SInce posting this, I've learned that the pcs.csv is in degree.minutes, while the wkt is in decimal degrees, so that explains the pcs.csv. This still leaves the question as to why autoIdentifyEPSG won't return the value. On 6/26/2013 11:44 PM, David Strip wrote: I'm working with some files in M

[gdal-dev] pcs.csv values don't match spatialreference.org

2013-06-26 Thread David Strip
I'm working with some files in Maryland State Plane (US foot), and autoIdentifyEPSG is failing. I tracked it down to what I suspect is the problem - my files and spatialreference.org show the standard parallels as 38.3 and 39.45, with a latitude of origin at 37. the pcs.csv file shows