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

Properly handle nulls #55

Open
bmschmidt opened this issue Nov 1, 2022 · 1 comment
Open

Properly handle nulls #55

bmschmidt opened this issue Nov 1, 2022 · 1 comment

Comments

@bmschmidt
Copy link
Collaborator

Right now, any data marked as NULL in the arrow file is being plotted with a value (usually 0). Short of just manually setting things to -999, a really easy solution to unpacking the bitmasks is not clear to me.

@bmschmidt
Copy link
Collaborator Author

One possibility we've been discussing is allowing the arrow files to declare and pass a null placeholder value as a uniform to the webgl shaders. In general this would be 0, but in cases where zero is meaningful, it could be defined as anything else that happens not to occur in the data. Arrow does not care what the value behind the null bitmask is, so it's kosher to just set it to whatever.

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