Consider updating the GRIB2C library version prior to the MET-13.0.0 release

[JohnHalleyGotway]

Describe the Task

In June 2026, @mpm-meto reported unexpected behavior when processing some GRIB2 data file for the WP-MIP project. For some, like this ecmf data, linking to g2c compiled with AEC support is sufficient. However, with others, like these babj and kwbc data sources, it is not.

Further investigation suggests that the problem may lie upstream the G2C library which MET calls to decode GRIB2 files. For this issue, prior to the final MET-13.0.0 release, check on the status of NCEPLIBS-g2c#617:

• If the issue is fixed and made available via a release, update the version of G2C lib used by MET's compile_MET_all.sh script.
  • Remember to rebuild METbaseimage to include the updated version.
  • Test to confirm that MET is able to properly process the babj and kwbc data linked above.
• If the issue is NOT fixed, recommend adding details to the release notes and/or upgrade instructions. Also consider whether any other code changes to check for this undesired result are warranted.

Time Estimate

1 day?

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

Must be done prior to the MET-13.0.0 release.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  None.

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y Development project for development toward the next coordinated release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.