Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support mipmapped processing #66

Open
jonnor opened this issue Jun 5, 2016 · 2 comments
Open

Support mipmapped processing #66

jonnor opened this issue Jun 5, 2016 · 2 comments

Comments

@jonnor
Copy link
Member

jonnor commented Jun 5, 2016

Right now we only support taking a (url to) file blob as input.
This means that we always download and process the entire image, even if we're only interested in a subset of the image (requested output is based on a low-resolution crop of input).
GEGL has capability of doing mipmapped processing via the scale parameter of GeglProcessor, which we are not yet making use of.

But to optimize also the download/network aspects, we'd need to have a tiled mipmap representation of the image instead of just (urls to) file blobs.

This could for instance be done via ipld-image, which would require API consumers to make use of IPFS to use this capability. Since this is a significant addition, it may be best if imgflo-server expose a HTTP API to create the image representation from either a input URL, or even from a file.

http://iiif.io/api/image/2.0 is another alternative to consider

@jonnor
Copy link
Member Author

jonnor commented Jun 5, 2016

#67 and #58 would make this more capable.

@jonnor
Copy link
Member Author

jonnor commented Jun 5, 2016

To get some estimates of how much (or little) we'd save by this, will need #57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant