Describe the New Feature

For the NCAR/RAL I-WRF project, MET needs to be enhanced to directly read NetCDF WRF output files that are already on pressure levels. The breadth of the changes needed are not entirely clear at this time, but MET should be able to interrogate the input NetCDF files to automatically determine whether or not they satisfy the requirement of being reported on pressure levels. Another key question is how to handle the location of velocity points (i.e. winds) which are staggered one half grid points from the mass points. Should that data be processed on the velocity points as-is or automatically interpolated to the mass points?

Also consider automated derivation of wind speed. Is this needed?

Should this be a new file type handle this or should the existing file_type = NETCDF_PINT be expanded to include it? Perhaps add NETCDF_WRF?

Acceptance Testing

List input data types and sources.
Describe tests required for new functionality.

Time Estimate

2 weeks.

Sub-Issues

Consider breaking the new feature down into sub-issues.
None yet.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

7790013

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: @JohnHalleyGotway
• Select scientist(s) or no scientist required: Perhaps Jared?

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

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

New Feature 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 issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.