JPEG 2000 format instead of TIFF for a RASTER layer

[Frank Warmerdam]

Brant Anderson wrote:
> Okay.
>
> This time I compiled 'jasper' without the geo referencing 'geojasper' so
> now I am using plain Jasper.
> I then compiled GDAL with the new ungeofied (GeoJP2=no) Jasper library.
>
> Then I tried to view my map. The server didn't give an Internal Server
> Error this time! But a new problem is here. The images just don't show
> up. I viewed the JPEG2000 images with "Image Viewer 2" in Windows, and
> they appear just fine, so I know they are supposed to be there. The
> layer used for tiling uses the same shapes as the TIFF version did, so
> the Extent values should be proper.

Brant,

If you don't compile with the georeferencing enabled version of JasPer
then your map won't work because GDAL won't know where your .jp2 images
are.  The message that was causing the problem must be coming from somewhere
in the GDAL JasPer driver or in the JasPer library itself.  Just grep for it
and strip it out and rebuild.

 > Maybe someone could test it out on their system. That way I can find out
 > if it is a server configuration problem, or a syntax problem.

I downloaded the .map file and the jpeg2000 data and tested it on my
system.  It worked fine with "shp2img -m test.map -o out.png" once I
had adjusted the SHAPEPATH, and set STATUS to DEFAULT in the layer
in question.

I also checked the .jp2 files and they look find with reasonable
georeferencing.

Note all my testing was with a Kakadu based version of GDAL, not using JasPer.

Can you run gdalinfo on one of the .jp2 files yourself now that you have
switched to the non-geo JasPer version?  I think you will find the bounds
and coordinate system are no longer known.  Assuming that is true, you will
really need to use the geo enabled version of JasPer and ensure that the
debug message is removed.

If you are using the most recent "geo-JasPer" version and you can't figure out
how to get the problematic message out you should contact Andrey Kiselev
(dron at remotesensing.org should get to him) about it.  He maintains the
JasPer driver in GDAL.

Finally I would like to stress that the JasPer driver in GDAL has performance
issues.  It is very memory hungry for large images and is somewhat slower
than Kakadu.  Given the smallish size of your tiles you shouldn't have much
problem with the memory use.  In addition to the JasPer and Kakadu based
GDAL JPEG2000 drivers, the new ECW SDK 3.0 also supports JPEG2000 support and
is free.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent