Hi,
I'm increasingly seeing IIIF (International Image Interoperability Framework) as a standard for serving images from repositories, tileservers, etc -- especially for maps.
(eg Klokan offer an IIIF hosting service, and use it as part of the stack for their Georeferencer; National Library of Wales for their map projects, etc.)
Are people aware of IIIF ?
Does it have advantages ?
In the medium term, would aiming for an IIIF-compatible interface to the proposed Wikimaps tileserver, or even main Commons itself, make any sense ?
With the Structured Data initiative for Commons now in the works, does it make sense to make sure that there are properties baked in for everything that would be needed to support IIIF? Also, to provide for any functionality that could potentially be exposed through IIIF?
I see that there are going to be quite a lot of Wikidata people at the Europeana Tech meeting in Paris on Thursday and Friday this week; and also several presentations that will touch on IIIF.
Is it worth trying to put together a heads-up for Wikidata people coming to this cold, as a background briefing on IIIF, and why these talks/posters might be interesting to them?
As people with much more map experience than me, can I therefore ask people on this list what they think of IIIF, and whether it is worth getting on to our radar?
Thanks,
James.
My zoomviewer for commons is based on IIF (check it out on File:Chicago. jpg for example) Daniel On Feb 9, 2015 4:05 AM, "James Heald" j.heald@ucl.ac.uk wrote:
Hi,
I'm increasingly seeing IIIF (International Image Interoperability Framework) as a standard for serving images from repositories, tileservers, etc -- especially for maps.
(eg Klokan offer an IIIF hosting service, and use it as part of the stack for their Georeferencer; National Library of Wales for their map projects, etc.)
Are people aware of IIIF ?
Does it have advantages ?
In the medium term, would aiming for an IIIF-compatible interface to the proposed Wikimaps tileserver, or even main Commons itself, make any sense ?
With the Structured Data initiative for Commons now in the works, does it make sense to make sure that there are properties baked in for everything that would be needed to support IIIF? Also, to provide for any functionality that could potentially be exposed through IIIF?
I see that there are going to be quite a lot of Wikidata people at the Europeana Tech meeting in Paris on Thursday and Friday this week; and also several presentations that will touch on IIIF.
Is it worth trying to put together a heads-up for Wikidata people coming to this cold, as a background briefing on IIIF, and why these talks/posters might be interesting to them?
As people with much more map experience than me, can I therefore ask people on this list what they think of IIIF, and whether it is worth getting on to our radar?
Thanks,
James.
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Nice!
So how integrated is the hosting for that with the rest of Commons?
I imagine it's managing its own tileset? But is that similar to what eg MapWarper needs to do? Does it make sense to try to add an IIIF interface provision layer to Commons as core functionality, for all such services?
(Would that risk creating horrible potential additional processing costs for the Commons hardware to cope with?)
Also, how much of the IIIF spec are you implementing? Just the tileserving? Or the full ability to be ableto request crops, rotations, overlays, annotations, etc ?
Really interested.
Thanks,
James.
On 09/02/2015 13:02, Daniel Schwen wrote:
My zoomviewer for commons is based on IIF (check it out on File:Chicago. jpg for example) Daniel On Feb 9, 2015 4:05 AM, "James Heald" j.heald@ucl.ac.uk wrote:
Hi,
I'm increasingly seeing IIIF (International Image Interoperability Framework) as a standard for serving images from repositories, tileservers, etc -- especially for maps.
(eg Klokan offer an IIIF hosting service, and use it as part of the stack for their Georeferencer; National Library of Wales for their map projects, etc.)
Are people aware of IIIF ?
Does it have advantages ?
In the medium term, would aiming for an IIIF-compatible interface to the proposed Wikimaps tileserver, or even main Commons itself, make any sense ?
With the Structured Data initiative for Commons now in the works, does it make sense to make sure that there are properties baked in for everything that would be needed to support IIIF? Also, to provide for any functionality that could potentially be exposed through IIIF?
I see that there are going to be quite a lot of Wikidata people at the Europeana Tech meeting in Paris on Thursday and Friday this week; and also several presentations that will touch on IIIF.
Is it worth trying to put together a heads-up for Wikidata people coming to this cold, as a background briefing on IIIF, and why these talks/posters might be interesting to them?
As people with much more map experience than me, can I therefore ask people on this list what they think of IIIF, and whether it is worth getting on to our radar?
Thanks,
James.
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
I'm generating a multiresolution TIF image for every file that is being requested (implicitly this is a "tile set"). There is no integration. The labs instance pulls the full res images via http. The processing is done with VIPS, which is what the WMF servers are using as well nowadays. I'd guess there would be non-trivial costs, but not orders of magnitude more than we already handle. The tool is currently strictly for incrementally streaming high resolution images. It might make sense to integrate it with the image annotator gadget and have the annotation appear in the zoomed view as well. I'm using the IIP Javascript and Flash clients. There really wasn't much to "implement" for me. The whole work was wrapping the downloading and processing in an AJAXy way. Daniel
On Mon, Feb 9, 2015 at 6:19 AM, James Heald j.heald@ucl.ac.uk wrote:
Nice!
So how integrated is the hosting for that with the rest of Commons?
I imagine it's managing its own tileset? But is that similar to what eg MapWarper needs to do? Does it make sense to try to add an IIIF interface provision layer to Commons as core functionality, for all such services?
(Would that risk creating horrible potential additional processing costs for the Commons hardware to cope with?)
Also, how much of the IIIF spec are you implementing? Just the tileserving? Or the full ability to be ableto request crops, rotations, overlays, annotations, etc ?
Really interested.
Thanks,
James.
On 09/02/2015 13:02, Daniel Schwen wrote:
My zoomviewer for commons is based on IIF (check it out on File:Chicago. jpg for example) Daniel On Feb 9, 2015 4:05 AM, "James Heald" j.heald@ucl.ac.uk wrote:
Hi,
I'm increasingly seeing IIIF (International Image Interoperability Framework) as a standard for serving images from repositories, tileservers, etc -- especially for maps.
(eg Klokan offer an IIIF hosting service, and use it as part of the stack for their Georeferencer; National Library of Wales for their map projects, etc.)
Are people aware of IIIF ?
Does it have advantages ?
In the medium term, would aiming for an IIIF-compatible interface to the proposed Wikimaps tileserver, or even main Commons itself, make any sense ?
With the Structured Data initiative for Commons now in the works, does it make sense to make sure that there are properties baked in for everything that would be needed to support IIIF? Also, to provide for any functionality that could potentially be exposed through IIIF?
I see that there are going to be quite a lot of Wikidata people at the Europeana Tech meeting in Paris on Thursday and Friday this week; and also several presentations that will touch on IIIF.
Is it worth trying to put together a heads-up for Wikidata people coming to this cold, as a background briefing on IIIF, and why these talks/posters might be interesting to them?
As people with much more map experience than me, can I therefore ask people on this list what they think of IIIF, and whether it is worth getting on to our radar?
Thanks,
James.
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Created https://phabricator.wikimedia.org/T89552 to keep track of this. CCing the multimedia people, they are probably interested in this too.
Maarten
Daniel Schwen schreef op 9-2-2015 om 14:47:
I'm generating a multiresolution TIF image for every file that is being requested (implicitly this is a "tile set"). There is no integration. The labs instance pulls the full res images via http. The processing is done with VIPS, which is what the WMF servers are using as well nowadays. I'd guess there would be non-trivial costs, but not orders of magnitude more than we already handle. The tool is currently strictly for incrementally streaming high resolution images. It might make sense to integrate it with the image annotator gadget and have the annotation appear in the zoomed view as well. I'm using the IIP Javascript and Flash clients. There really wasn't much to "implement" for me. The whole work was wrapping the downloading and processing in an AJAXy way. Daniel
On Mon, Feb 9, 2015 at 6:19 AM, James Heald j.heald@ucl.ac.uk wrote:
Nice!
So how integrated is the hosting for that with the rest of Commons?
I imagine it's managing its own tileset? But is that similar to what eg MapWarper needs to do? Does it make sense to try to add an IIIF interface provision layer to Commons as core functionality, for all such services?
(Would that risk creating horrible potential additional processing costs for the Commons hardware to cope with?)
Also, how much of the IIIF spec are you implementing? Just the tileserving? Or the full ability to be ableto request crops, rotations, overlays, annotations, etc ?
Really interested.
Thanks,
James.On 09/02/2015 13:02, Daniel Schwen wrote:
My zoomviewer for commons is based on IIF (check it out on File:Chicago. jpg for example) Daniel On Feb 9, 2015 4:05 AM, "James Heald" j.heald@ucl.ac.uk wrote:
Hi,
I'm increasingly seeing IIIF (International Image Interoperability Framework) as a standard for serving images from repositories, tileservers, etc -- especially for maps.
(eg Klokan offer an IIIF hosting service, and use it as part of the stack for their Georeferencer; National Library of Wales for their map projects, etc.)
Are people aware of IIIF ?
Does it have advantages ?
In the medium term, would aiming for an IIIF-compatible interface to the proposed Wikimaps tileserver, or even main Commons itself, make any sense ?
With the Structured Data initiative for Commons now in the works, does it make sense to make sure that there are properties baked in for everything that would be needed to support IIIF? Also, to provide for any functionality that could potentially be exposed through IIIF?
I see that there are going to be quite a lot of Wikidata people at the Europeana Tech meeting in Paris on Thursday and Friday this week; and also several presentations that will touch on IIIF.
Is it worth trying to put together a heads-up for Wikidata people coming to this cold, as a background briefing on IIIF, and why these talks/posters might be interesting to them?
As people with much more map experience than me, can I therefore ask people on this list what they think of IIIF, and whether it is worth getting on to our radar?
Thanks,
James.
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps
Wikimaps mailing list Wikimaps@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimaps