AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.07.23 22:15 "[Tiff] JPEG2000 codec", by Roger Leigh
2017.07.24 00:34 "Re: [Tiff] JPEG2000 codec", by Kemp Watson
2017.07.24 15:46 "Re: [Tiff] JPEG2000 codec", by Bob Friesenhahn
2017.07.24 16:16 "Re: [Tiff] JPEG2000 codec", by Roger Leigh
2017.07.24 16:51 "Re: [Tiff] JPEG2000 codec", by Kemp Watson
2017.07.24 19:39 "Re: [Tiff] JPEG2000 codec", by Bob Friesenhahn
2017.07.24 21:49 "Re: [Tiff] JPEG2000 codec", by Bob Friesenhahn
2017.07.25 01:12 "Re: [Tiff] JPEG2000 codec", by Kemp Watson

2017.07.24 16:16 "Re: [Tiff] JPEG2000 codec", by Roger Leigh

On 24/07/17 16:46, Bob Friesenhahn wrote:

On Mon, 24 Jul 2017, Leonard Rosenthol wrote:

> As with Kemp – I would ask the obvious question…
>
> WHY?
>

> JP2K already has an excellent (and ISO standardized!) file format to > go along with the codecs. Why would you want to put it inside a

> proprietary file format like TIFF??

Perhaps one reason would be that the freely available JP2K libraries do not adequately support these features. JP2K in TIFF at least allows scaling up the image to any image size supported by TIFF/BigTIFF (virtually unlimited) by using reasonably sized strips or tiles, and allows using any existing TIFF tags.

To answer all the questions, my purpose is for reading and writing of "big" digital pathology images, which might well include existing Aperio files, or conversion or creation of new files in a similar format. The format itself would be OME-TIFF.

We might well use standard J2K files as well, but we embed other metadata in the OME-TIFF, and support multiple images in TIFF which can use different compression formats etc., which makes using TIFF have some advantages over J2K.

Regards,
Roger