-
Notifications
You must be signed in to change notification settings - Fork 7
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
Won't work without SMinSampleValue/SMaxSampleValue #1
Comments
What version of IIP are you using ? |
Version 0.9.9. I tried this with my own .tif, as well as the IIP sample image (http://merovingio.c2rmf.cnrs.fr/iipimage/PalaisDuLouvre.tif). Both returned an invalid response. I had to remove "&obj=min-max-sample-values" from the request url in order to get a valid response (and some other minor changes to make that work so that only options.minMaxValues is used) I did sort of figure out the minMaxValues parameter. For my grayscale, 8-level image, I created my layer with minMaxValues=[[340,341]] or as [[0,1]], didn't make any difference as far as I could tell. I don't know what those values are for, so maybe it's something I didn't notice. |
The minmax values are only available in the dev or 1.0 versions of iipsrv and for an 8bit image, they should normally be set to 0,255. Basically they allow you to extract a photometric slice of the input data, which is useful for floating point or high bit depth images. |
I recommend you to use my fork of this repo. I adjusted everything to support IIP 0.9.9 and fixed some issues. |
@ageblade It's perfect! Would you submit pull request so it can be added to main repository? I almost tried to recreate the same fixes you made. Might need a version number if it's incompatible with leaflet1.0. |
Hi gents, |
Hi @ebertin , |
Thanks @denics! Please note that the stand-alone version of |
I've been trying to get this to run with a file that does not have these values, no luck. I'm not sure what would be valid values to put in for the minMaxValues option either. Appreciate any information!
The text was updated successfully, but these errors were encountered: