openseadragon + IIPImage
IIPImage is an advanced high-performance image server and client
Brought to you by:
denis_pitzalis,
ruven
Hello,
I'm trying to display some images from IIPImage in Openseadragon using the deepzoom protocol.
I've setup a simple page with the viewer loading a single image, but I get the error in the subject.
If I call the url of the dzi manually, I get the following application/xml response, which seems correct:
This is the javascript used to configure Osd, where image is a .tif filename wih path (e.g.: /images/001/0001.tif):
function loadPlayer() {
viewer = OpenSeadragon({
id: "container",
prefixUrl:"images/" ,
tileSources: server + "?DeepZoom=" + image + ".dzi"
});
}
$(document).ready(function() {
loadPlayer();
});
May you help me please?
Thank you.
What error are you getting? Is there anything flagged up in your browser's dev tools?
And what exactly have you assigned to the variable "server" that you are passing to tileSources? tileSource should be given the server + path: something like "/fcgi-bin/iipsrv.fcgi?Deepzoom=/path/image.tif.dzi"
Hello, the error is:
Unable to open [object Object]: HTTP 0 attempting to load TileSource
In the firebug "net" panel, in the "xml" tab I get a syntax error:
XML Parsing Error: syntax error Location: moz-nullprincipal:{81a6de49-ecf2-4a96-82ae-c05264e1c5db} Line Number 1, Column 1:
Reload the page to get source for: http://xxx.xxx.xxx.xxx/img?DeepZoom=/images/052...
If I call the dzi from the url bar in the browser I get a xml as explained in the first post.
If you want I may send the link to my test page in a private message.
Thank you.
Kind Regards
Maybe this is the wrong place to post this, and if so, I apologize in advance, but here goes nothing:
I'm getting a similar error message when I attempt to access the Library of Congress's Chronicling America newspaper database in the customary way (i. e., by clicking links on a blog):
Unable to open [object Object]: HTTP 0 attempting to load TileSource
I get a similar message when I try to access Chronicling America by entering their website. However, I can usually get the document (i. e., the newspaper page) by clicking the PDF icon at the top of the viewer. Additionally, I can usually get an enlarged version of the newspaper page by clicking the scissors icon there. Also, remarkably, at least some of those links which lead to pages which I've clipped in the past seem to work on the viewer.
I also got that "Unable to open" message when I tried to access a map on the Library of Congress website.
I've e-mailed someone at the Library of Congress about this, and the contact person seemed to hint that the problem was on my end--that is, he asked me what my operating system was (Windows 11) and what browser I was using (Chrome, although after I first encountered the problem, I unsuccessfully experimented with Edge to see if I'd get a different result). I think he also said that no one else had complained about it. For all I know, that could just mean that there aren't very many "old newspaper nerds" who know about LOC's beautiful newspaper database.
Anyway, as folks say where I'm at now (Taiwan), "Zenmeban?" (how to manage?).
If you've read this far, thank you for your time and attention, and if the problem is on my end, or if it's intractable, the workarounds I mentioned above (especially the PDF one) should suffice.
Thanks, and again, I apologize if I've posted this in the wrong place,
Charlie Jack (Charles B. Jack)
Banqiao District, New Taipei City, Taiwan
I'm afraid that you are correct that this is not the right place to ask. From what I can see, the Library of Congress does not use either the IIPImage server or viewer. The software they use is the OpenSeaDragon viewer, so you could try asking for help on their help forums.
I'm sorry for the mistake! I mistakenly thought this was affiliated with OpenSeaDragon.
Again, I'm very sorry to inconvenience you, but thank you very much for your time and attention.
--Charlie Jack
No problem. By the way, I tried with a few images on the Chronicling America site and they all seem to work, so maybe it is indeed a problem at your end.
Thank you, sir, for the information!