At the moment, if a BUFR key is present but its value cannot be accessed an eccodes.KeyValueNotFoundError exception is thrown and pdbufr fails without giving details about e.g. the key name involved.
Naturally, pdbufr should not fail in this case, but if has to e.g. if it is a mandatory key (e.g. "edition") it should provide the users with a better error message.
At the moment, if a BUFR key is present but its value cannot be accessed an eccodes.KeyValueNotFoundError exception is thrown and pdbufr fails without giving details about e.g. the key name involved.
Naturally, pdbufr should not fail in this case, but if has to e.g. if it is a mandatory key (e.g. "edition") it should provide the users with a better error message.
Related to issue #46