Le mercredi 06 août 2014 20:38:55, John_Lunzer a écrit :
> The documentation states that Python automatically calls GDALAllRegister()
> when the GDAL module is imported. Is there any way to disable this or to
> tell GDAL to use a specific driver when loading JPEG2000 compressed images?
You can do
The documentation states that Python automatically calls GDALAllRegister()
when the GDAL module is imported. Is there any way to disable this or to
tell GDAL to use a specific driver when loading JPEG2000 compressed images?
Even Rouault-2 wrote
> Le mercredi 06 août 2014 20:16:57, John_Lunzer a é
Le mercredi 06 août 2014 20:16:57, John_Lunzer a écrit :
> They are listed as C8, which means JPEG2000 compression.
That must be it. JPEG2000 decompression takes some time, and that can be more
or less slow depending on the underlying driver used. Do you have JP2KAK,
JP2ECW, JP2OPENJPEG, JP2MrSI
They are listed as C8, which means JPEG2000 compression.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/NITF-read-slow-in-python-tp5155297p5155304.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
gdal-dev mai
Le mercredi 06 août 2014 19:36:44, John_Lunzer a écrit :
> I have some not so big NITF files (1x7000 16bit) that I am reading
> using Python. Using the ReadAsArray() method of the data opened via
> gdal.Open() it takes about 50 seconds to load a single band. Reading this
> same file in GeoTIFF
I have some not so big NITF files (1x7000 16bit) that I am reading using
Python. Using the ReadAsArray() method of the data opened via gdal.Open() it
takes about 50 seconds to load a single band. Reading this same file in
GeoTIFF format takes about 2.7 seconds by comparison.
Does anyone have
Hello again,
Because of few customer cases I had to look this GeoTIFF/CT_Mercator
issue once again, this time in depth.
I studied how three software packages write GeoTIFFs as well as how
they read different combination of keys. These software are
GeoMedia Professional 06.01.11.13
ArcGIS Desktop
