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 signed types #370
Comments
Thanks for opening the issue! Yes, this should be feasible (we do cast int -> uint for geotiff). There are two approaches I see.
I think the the latter is my preferred solution. The conversion logic would then be shared regardless of the pixel source. This way the sources shouldn't get out of sync. I'll take a look into adding this. |
Just seeing this but I think we can just update the shaders' handling without casting anything? Is there something blocking this that I'm missing (very possible)? viv/src/layers/XRLayer/XRLayer.js Line 30 in 855d29b
We just need to add Lines 12 to 38 in a21b080
|
Nope, sounds totally reasonable! I just assumed we needed to cast because that is what the tiff source did. |
In some of the images, we have data type in
<i2
and that generated an error in vizarr:@manzt mentioned that it was possible to do data casting with geotiff (see here), and it will be great if we can have this generally available for vizarr as well.
The text was updated successfully, but these errors were encountered: