question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

XMLHTTPRequest for IIIF info.json: User specified default image format?

See original GitHub issue

I have been using for a while arrays of info.json requests to load images into the OpenSeadragon viewer, similar to the example here: http://openseadragon.github.io/examples/tilesource-iiif/

This has worked well for most purposes, but now I have a new requirement where I need to preserve the bit depth of the original images in the viewer.world images. The original images are 16-bit depth tif files and using the Cantaloupe IIIF image server I can return 16-bit png and tif files using the IIIF image API image request

{scheme}://{server}{/prefix}/{identifier}/{region}/{size}/{rotation}/{quality}.{format}

by setting the {format} to png or tif

However, the image information request URI ( info.json ) does not provide a way to specify the default format, which is apparently jpg a format that does not support bit depth > 8

How do I go about specifying that the images to be loaded into OSD viewer should be of a particular format as defined in the IIIF image API?

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:1
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
azaroth42commented, Aug 25, 2017

That seems like a good enhancement to me. The reason we hard coded .jpg is that it’s the only required format in IIIF, and thus likely to be warm in caches. Thus we don’t have to worry about checking the info.json to see if other formats are also supported and the performance is likely to be better than picking an arbitrary format.

The proposed solution is excellent because it allows per-instance configuration, keeping jpg as the default in the absence of other requirements, such as those of @imoutsatsos 😃 Happy to review and/or provide advice for the IIIFTileSource part … not sure I have bandwidth at the moment to implement.

0reactions
iangilmancommented, Aug 28, 2017

@azaroth42 Great; sounds like we’re on the same page… good to have the backstory 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Developers - XMLHTTPRequest for IIIF info.json - Bountysource
XMLHTTPRequest for IIIF info.json: User specified default image format?
Read more >
Image API 3.0 - IIIF
The IIIF Image API specifies a web service that returns an image in response to a standard HTTP or HTTPS request. The URI...
Read more >
Presentation API 3.0 - IIIF
This document specifies this standardized description of the collection or compound object, using a JSON format. Many different rich and dynamic user ......
Read more >
Presentation API 2.1.1 - IIIF
Digital images are a container for much of the information content in the Web-based ... Given the wide variation of potential client user...
Read more >
Image API 2.1.1 - IIIF
The parameters of the Image Request URI include region, size, rotation, quality and format, which define the characteristics of the returned image. These...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found