Skip to content

Enhance MET to parse LAEA grids from the MET NetCDF file format #2809

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

While testing unrelated grid functionality in MET, @JohnHalleyGotway ran across an issue. While MET can write NetCDF output files for gridded data on an LAEA grid, it currently cannot read that grid specification back in. This issue is to fix that shortcoming by adding support for reading MET NetCDF files containing data on an LAEA grid.

Run the following commands to demonstrate regridding global data to the UKV LAEA grid and then running plot_data_plane to plot the result:

bin/regrid_data_plane \
$MET_TEST_INPUT/model_data/grib2/gfs/gfs.0p25.2022092400.f000.grib2  \
UKV \
TMP_Z2_UKV.nc \
-field 'name="TMP"; level="Z2";' \
-v 4

bin/plot_data_plane \
TMP_Z2_UKV.nc \
TMP_Z2_UKV.ps \
'name="TMP_Z2"; level="(*,*)";' \
-v 4

That produces this error message:

ERROR  : read_netcdf_grid_v3() -> Projection "Lambert Azimuthal Equal Area" not a currently supported type ("LatLon", "Mercator", "Lambert Conformal", "Polar Stereographic").

Time Estimate

4 hours

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

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 the next official version or Backlog of Development Ideas
  • For the next official version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement 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.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions