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

Do not use auto HDF5 fill value for netcdf-derived variables #283

Merged
merged 1 commit into from
Jan 25, 2023

Conversation

martindurant
Copy link
Member

@martindurant martindurant commented Jan 24, 2023

fixes #284

@rsignell-usgs
Copy link
Collaborator

Okay to merge? Or do you want a review or more testing?

@martindurant
Copy link
Member Author

I'm OK to merge it, but if there are any case studies likely to be tried in the next few days, I would wait.

@rsignell-usgs
Copy link
Collaborator

@pnorton-usgs, are there any other tests you might have handy?

@pnorton-usgs
Copy link

I re-kerchunked our National Hydrologic Model output and verified that the HDF5 fill value is no longer used in the output json. The datatypes that were being converted to float are now remaining integers. Thanks for the quick fix on this one!

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

Successfully merging this pull request may close these issues.

NetCDF int32 getting promoted to float64 after kerchunk
3 participants