Yes, I see half a pixel difference between GeoTIFF and GML georeferencing.
Luke
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Tester-with-ERDAS-needed-tp5079161p5079750.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
I've tried both geographic and projected tiffs. The original tiffs were a mix
of very small test data (8bit, single band, 100 cols x 100 rows) and fairly
large Worldview-2 16bit pan and multispectral scenes.
All of the output jp2s have only a single uuid box.
Sorry, I'm usually very good at brea
I've tried to replicate with ERDAS Imagine 2013, but the resulting JP2s are
georeferenced correctly in ArcMap and GDAL 1.10 (before r26485). This was
with "Embed GeoTIFF" checked and "Embed GML" unchecked in the ERDAS Imagine
export options dialog.
Perhaps the 2nd GeoTIFF JP2Box is a bug in earlie
Yes, redirection and exit code setting works when the gdal_ECW_JP2ECW.dll is
built against ECW/JP2 v.5.0 SDK (didn't test v.4x).
Luke
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Gdalinfo-does-not-print-into-file-on-Windows-tp5078239p5078379.html
Sent from the
Disabling the ECW plugin also enables setting a non-zero exit code
(http://trac.osgeo.org/gdal/ticket/4830)
Luke
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Gdalinfo-does-not-print-into-file-on-Windows-tp5078239p5078377.html
Sent from the GDAL - Dev mailing l
If you're installing gdal from ubuntugis, why not install the python bindings
from there also?
sudo apt-get install python-gdal
If this is not an option due to the use of virtualenv, as a workaround until
pypi gets updated you could script the download of the .deb (i.e on 64bit
12.04
https://laun
A workaround to your 2nd question is to set the GDAL_PAM_PROXY_DIR
environment variable, either permanently or on the commandline before you
call gdalinfo.
set GDAL_PAM_PROXY_DIR=%TEMP%
gdalinfo -stats some.ntf
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-Worki
>> The python function needs to accept three arguments, error class, error
code
>> and error message.
>>
>> i.e.
>> from osgeo import gdal
>> def f(err_class, err_code, msg):
>> print err_class, err_code, msg
>>
>> gdal.PushErrorHandler(f)
>
>Reviewing the Python bindings code, I see no eviden
The python function needs to accept three arguments, error class, error code
and error message.
i.e.
from osgeo import gdal
def f(err_class, err_code, msg):
print err_class, err_code, msg
gdal.PushErrorHandler(f)
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/gdal
