Evaluating High Throughput #JPEG2000 (#HTJ2K) as a Drop-In Replacement for JPEG2000 with #IIIF (via @Thorsted):

https://journal.code4lib.org/articles/17596

#code4lib @general

Evaluating HTJ2K as a Drop-In Replacement for JPEG2000 with IIIF

JPEG2000 is a widely adopted open standard for images in cultural heritage, both for delivering access and for creating preservation files that are losslessly compressed. Recently, a new extension to JPEG2000 has been developed by the JPEG Committee: “High Throughput JPEG2000,” better known as HTJ2K. HTJ2K promises faster encoding and decoding speeds compared to traditional [...]

The Code4Lib Journal

Pleasantly surprised a non-paywalled version of the High-throughput #JPEG2000 standard is available here:

https://www.itu.int/rec/T-REC-T.814-201906-I/en

Lots more useful info at the (always excellent) Library of Congress "Sustainability of Digital Formats" site:

https://loc.gov/preservation/digital/formats/fdd/fdd000566.shtml

T.814 : Information technology - JPEG 2000 image coding system: High-throughput JPEG 2000

At a first glance both the codestream syntax and the #JPH file format are relatively minor variations on #JP2, so I think it would be good to add support to #Jpylyzer at some point. Won't make any promises when I'll get round to this, but I created this issue as a reminder:

https://github.com/openpreserve/jpylyzer/issues/197

Support for High Throughput JPEG 2000 (JPH format) · Issue #197 · openpreserve/jpylyzer

Standard: https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.814-201906-I!!PDF-E&type=items This is largely identical to JP2, with some relatively minor deviations. Codestream syntax is also...

GitHub
@bitsgalore I need to spend some time and test compatibility. The article briefly mentioned this at the end, sounds like we need to learn more.