[gdal-dev] GDAL 1.10 JP2000 Problem/Crash

[John Daniel]

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 testing Kakadu right now. If ECW has problems in GDAL 1.10, that would be important to know.

Are there any issues with Kakadu and GDAL 1.10? I'm worried about the way GDAL links directly to Kakadu object files instead of using the library.

Thanks

John Daniel
Software Engineer
Stinger Ghaffarian Technologies (SGT, Inc.)
Contractor to the U.S. Geological Survey (USGS)
Earth Resources Observation and Science (EROS) Center
47914 252nd Street
Sioux Falls, South Dakota 57198
Phone: 905.240.2953
Mobile: 905.442.9385
Skype: 303.586.1987
Email: jdaniel at usgs.gov

On May 22, 2013, at 12:46 PM, Even Rouault <even.rouault at mines-paris.org> wrote:

> 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
>> support.  If Tamas's build includes MrSID support then all you need to do
>> is set the GDAL_SKIP environment variable to JP2ECW which would make GDAL
>> skip the ECW based driver.   If Tamas hasn't built with MrSID then it falls
>> to you to build GDAL which can be somewhat complicated.
> 
> I can replicate the crash with the JP2ECW driver with ECW SDK 3.3. It occurs 
> actually in the SDK itself, not in GDAL, so nothing that we can really do 
> about that (except using GDAL API Proxy, see below). Newer versions of the SDK 
> don't produce this crash.