Hi everyone,
I have seen crashes in libecwj2 when reading certain JPG2000 files as
well (on Linux). I have tracked it down to the bundled XML-handling
code in libecwj2 but have not had time to fully investigate.
But what I found was that if I turn off optimization when compiling
libecwj2 this bug
On May 23, 2013, at 12:37 PM, Frank Warmerdam wrote:
> John,
>
> In my experience the crashes with the ECW 3.3 library are not specific to
> recent versions of GDAL. I've run into them over the years.
Frank,
I was just curious about potential future problems with GDAL 1.10. If ECW runs
as w
Le jeudi 23 mai 2013 15:34:26, Julien Malik a écrit :
> Hello Even,
>
> On 05/22/2013 07:46 PM, Even Rouault wrote:
> > Frank's above suggestions are the way to go. Tamas' builds do include
> > MrSID support as a plugin (-mrsid.msi packages). But they also
> > include the OpenJPEG driver, whic
On Thu, May 23, 2013 at 9:07 AM, John Daniel wrote:
> Even,
> Is this crash specific to GDAL 1.10? We have been using the old ECW
> library for a couple of years with good success. It is a bit buggy. I never
> did get it running on Solaris. We are still on GDAL 1.9.2.
>
John,
In my experience t
Even,
Is this crash specific to GDAL 1.10? We have been using the old ECW library for
a couple of years with good success. It is a bit buggy. I never did get it
running on Solaris. We are still on GDAL 1.9.2.
I have been worried about this old ECW library blocking us from future updates.
We are
Thanks guys for the info and advise.
I was able to skip the JP2ECW driver and successfully open the file with
the JP2OpenJPEG driver. But the driver is quite slow, in some cases up to
20x slower than the JP2ECW driver loading the same amount of pixels on a
raster where both drivers work. Skipping
Hello Even,
On 05/22/2013 07:46 PM, Even Rouault wrote:
Frank's above suggestions are the way to go. Tamas' builds do include MrSID
support as a plugin (-mrsid.msi packages). But they also include the
OpenJPEG driver, which can successfully open this file and should be the next
driver used
Le mercredi 22 mai 2013 19:22:09, Frank Warmerdam a écrit :
> Dennis,
>
> Ah. In my experience the ECW SDK 3.3 JPEG2000 support is buggy and I was
> never really able to trace down the issues. I would encourage you to
> consider alternatives - one possibility is the MrSID SDK's JPEG2000
> suppor
Dennis,
I believe you can use Even's GDAL API Proxy to avoid crashes in third
party libraries. See:
http://trac.osgeo.org/gdal/ticket/4979
for more info.
kss
On Wed, May 22, 2013 at 11:22 AM, Frank Warmerdam wrote:
> Dennis,
>
> Ah. In my experience the ECW SDK 3.3 JPEG2000 support is buggy
Dennis,
Ah. In my experience the ECW SDK 3.3 JPEG2000 support is buggy and I was
never really able to trace down the issues. I would encourage you to
consider alternatives - one possibility is the MrSID SDK's JPEG2000
support. If Tamas's build includes MrSID support then all you need to do
is s
I'm using the stable 1.10 build from Tamas' site.
GDALIdentifyDriver on the file reports: "ERDAS JPEG2000 (SDK 3.x)"
When trying to open the file I get an AccessViolationException.
Cheers,
Dennis
On Wed, May 22, 2013 at 3:35 PM, Frank Warmerdam wrote:
> Dennis,
>
> There are several jpeg2000
Dennis,
There are several jpeg2000 drivers potentially available for gdal. Do you
know which you are using?
Best regards,
On May 22, 2013 5:20 AM, "Dennis Gocke" wrote:
> Hi,
>
> I’ve encountered a problem with Pleiades JP2 files from Astrium, GDAL
> crashes when opening the file.
>
> You sh
Hi,
I’ve encountered a problem with Pleiades JP2 files from Astrium, GDAL
crashes when opening the file.
You should be able to reproduce the the crash by downloading a sample
dataset from their page.
http://www.astrium-geo.com/en/23-sample-imagery
Optical Imagery->Pleiades->Pleiades Primary Prod
13 matches
Mail list logo
