We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The bounds cannot be set by the user, and sometimes the bounds written by mitab are not the ones we want.
With this patch, when exporting a tab file, mitab looks for a bound corresponding to the projection, defined in two tables :
Patch : https://gist.github.com/vpicavet/5569987
This bug is related to #2 and patches should be applicated in this order :
$ patch -p1 < mitab-L93-EPSG2154.patch $ patch -p1 < mitab-precision.patch $ patch -p1 < mitab-userProvidedBounds.patch
The patch has been tested against the mitab version in GDAL svn 25454
The text was updated successfully, but these errors were encountered:
MITAB: add MITAB_BOUNDS_FILE to specify a file with projection bounds (…
73ef8a1
…mapgears/mitab#3) git-svn-id: https://svn.osgeo.org/gdal/trunk/gdal@27564 f0d54148-0727-0410-94bb-9a71ac55c965
e40f3b0
…mapgears/mitab#3)
No branches or pull requests
The bounds cannot be set by the user, and sometimes the bounds written by mitab are not the ones we want.
With this patch, when exporting a tab file, mitab looks for a bound corresponding to the projection, defined in two tables :
Patch :
https://gist.github.com/vpicavet/5569987
This bug is related to #2 and patches should be applicated in this order :
$ patch -p1 < mitab-L93-EPSG2154.patch
$ patch -p1 < mitab-precision.patch
$ patch -p1 < mitab-userProvidedBounds.patch
The patch has been tested against the mitab version in GDAL svn 25454
The text was updated successfully, but these errors were encountered: