Bad detection of L93 / EPSG:2154 projection #1
Comments
|
Some useful links concerning this issue : http://www.digitalpreservation.gov/formats/fdd/fdd000300.shtml (TAB, MIF) |
kwrobot
pushed a commit
to aashish24/gdal-svn
that referenced
this issue
Jul 14, 2014
…ions (mapgears/mitab#1) git-svn-id: https://svn.osgeo.org/gdal/trunk/gdal@27527 f0d54148-0727-0410-94bb-9a71ac55c965
rouault
added a commit
to rouault/mitab
that referenced
this issue
Jul 14, 2014
…ions (mapgears#1, GDAL r27527)
rouault
added a commit
to rouault/mitab
that referenced
this issue
Jul 14, 2014
kwrobot
pushed a commit
to aashish24/gdal-svn
that referenced
this issue
Jul 14, 2014
git-svn-id: https://svn.osgeo.org/gdal/trunk/gdal@27528 f0d54148-0727-0410-94bb-9a71ac55c965
samalone
pushed a commit
to samalone/gdal-ios
that referenced
this issue
Oct 25, 2014
samalone
pushed a commit
to samalone/gdal-ios
that referenced
this issue
Oct 25, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When reading and writing Mapinfo files, there is a problem detecting Lambert 93 / EPSG:2154.
There are incompatibilities between Mapinfo and Mitab. Mapinfo saves values for SP1 Standard Parallel) and SP2 projection parameters in a way, and OGR (MiTAB) reads it differently in the resulting TAB file.
Attached is a patch inverting the order of SP1 and SP2 when reading and writing TAB files, only for L93/EPSG:2154. It is applicable on the MiTAB version which is included with gdal révision svn 25454.
Patch : https://gist.github.com/vpicavet/5569914
The text was updated successfully, but these errors were encountered: