Thanks Evan but I am not quite sure I understand.
Are you saying that QGIS uses gdal built with a different MrSID SDK?
I have built GDAL using this version, MrSID_DSDK-9.0.0.3864-win32-vc11 from
LizardTech, which I think is the latest.
If it is then I am sure that QGIS will be using the same, in
Martin,
The difference is likely due to a different version of the MrSID SDK used to
compile the GDAL MrSID plugin/driver. According to the version of the SDK, a
different method is used to decode the projection information. I guess that the
one that leads to buggy result is the one that borrows c
Sorry Evan
Forgot the version dump
QGIS
---
GDAL 1.11.0, released 2014/04/16
Built GDAL
---
GDAL 1.11.0, released 2014/04/16
Seems to be the same?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Re-Warping-Issues-tp5157231p5157278.html
Sent from the GDAL -
Thanks for the quick reply Evan.
I have done what you asked and it gets a bit strange.
I ran gdalinfo from the QGIS bin directory and then on the alternate machine
ran gdalinfo from the 'pure gdal' bin directory on the same sid file.
There are some differences in the output particularly around the
Martin,
Could you paste the output of gdalinfo on the .sid file on both environments,
and each time indicate what 'gdalinfo --version' reports ? It might be possible
that the issue is at the source rather than at the warping.
Even
> I seem to be having a few warping problems using OGRCoordinateT
I seem to be having a few warping problems using OGRCoordinateTransformation as
the warped images do not appear to have the correct co-ordinates.
To establish what was going on I have come across a curious issue that may
indicate the problems that I am having.
On a separate machine I have QGIS 2
