Martin Yeo

Hi @marfel, we've just picked this up while doing some tidy-up. Sorry no-one ever got back to you, is this still an issue you would like solved?

Thanks @marfel for the intriguing offer, we're just waiting for our Iris-GRIB lead to have some time to consider this. Ping @lbdreyer

Hi @marfel, we'd love to take a look at your patched version. Although as you've guessed, the spare resource for Iris-GRIB is limited, so we might not end up incorporating...

Thanks @marfel 🙂 >... it seems I'm not allowed to push a new branch? Yes, the typical work pattern in GitHub is users to have their own copies of a...

Thanks very much @larsbarring! Resource permitting, we now have all we need to work on this

Can we be sure that this won't also affect situations where there genuinely shouldn't be a realization dimension? (I'm not arguing, we just rely on the wisdom of our users!)

@BHFock we're very sorry that this PR was lost for so long - there has been some lack of clarity about who looks after iris-grib in the past. We expect...

@SciTools/peloton: We believe this just needs some additions to: [`_grib_cf_map.py`](https://github.com/SciTools/iris-grib/blob/e10442b93d351752d36ac94ee7f110ef2b55c27d/iris_grib/_grib_cf_map.py). Thanks for bringing this to our attention! @mgange659 we would welcome a Pull Request, if you're up for it, but...

> I will start preparing a Pull Request with new table entries for GRIB2_TO_CF. Some of the MDDA parameters have officially agreed local codes. is there a need a new...

> I was referring to GRIB-2 Local Codes. These often have 'Number' settings in the range 192-254. Ah OK, thanks. iris-grib would not be the place to record such mappings,...