Consistent EDR parameter metadata for NWP

[chris-little]

@ShaneMill1
In our work so far, we typically have used cfgrib to defined the parameter metadata because that is the default GRIB decoder for Xarray. However, some NWS data uses local GRIB2 tables to define some of these attributes which causes cfgrib to read the parameter name as "unknown". For that case, we have used either GDAL or Rasterio to define the parameter metadata, or a new tool developed by MDL called Grib2io because those tools contain the NWS parameters.

Each of these tools handle the parameter names a little differently. I personally like how cfgrib handles the metadata (being based on eccodes), but I have yet to figure out how to add the local tables to cfgrib to get it to work with all NWS data.

--

@tomkralidis
We are setting up our public pygeoapi EDR and Zarr production. How are you defining parameter metadata? id’s, names etc. I would like some consistency if possible between NWP EDRs. We should discuss with RODEO EDR folks as well.

--