Closed huanglangwen closed 2 years ago
In ecCodes you can set the key "missingValue" to some other value (rather than the default 9999) to make sure it does not interfere with actual field values. For example 1.0e36
Thank you! But setting missingValue
to the grib file has a lot of overheads as we have 100GB+ grib files and there's no way to set it inplace. I'm wondering if cfgrib can provide an option to override the missingValue
setting like the grib_get_data -m
does.
Thank you for this report - indeed, I think we need to make a change in the internals of cfgrib to use an 'out of range' missing value indicator. Stay tuned!
Fixed - same resolution as for #313
When loading grib files with values around 9999, those values are masked to np.nan by cfgrib in the following line:
https://github.com/ecmwf/cfgrib/blob/0834b19d56ab2a817cc5a3309149806afdcf0ced/cfgrib/dataset.py#L358
Is there a way to set missing values manually to avoid this case?
Thanks a lot!