issues: 303727896

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
303727896 MDU6SXNzdWUzMDM3Mjc4OTY= 1976 What's wrong with "conflicting" _FillValue and missing_value? 221526 closed 0     2 2018-03-09T05:21:27Z 2018-03-09T17:45:35Z 2018-03-09T17:45:35Z CONTRIBUTOR      

So this exception: ``` ValueError: Conflicting _FillValue and missing_value attrs on a variable 'MergedBaseReflectivityQC_altitude_above_msl': -999.0 vs. -99.0

Consider opening the offending dataset using decode_cf=False, correcting the attrs and decoding explicitly using xarray.decode_cf(). `` Why is having_FillValueandmissing_valuedifferent considered an error in decoding CF? It's perfectly CF-compliant, especially since_FillValueis a scalar (used by the netCDF library to initialize an array), andmissing_value` can be a vector (representing one or more undefined or invalid values).

This happens in this case because the source GRIB file has one value specified for "missing" (maps to missing_value) and another for "no coverage" (which has been mapped to _FillValue).

Is this a technical limitation? Or just something that needs an implementation?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1976/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables