Replace italics below with details for this issue.

Describe the New Feature

The IODA2NC tools provides one step in the processing chain to "evaluate the model on it's native domain" using observations ingested by the JEDI DA system. We now need to wrap it with METplus and then developed a use-case (#1204).

A description of the IODA2NC tool can be found here: https://met.readthedocs.io/en/main_v10.0/Users_Guide/reformat_point.html#ioda2nc-tool

Being there aren't too many settings, it would probably be good to include all command line options and configuration options (share/met/config/IODA2NcConfig_default)

Acceptance Testing

Start with using the current tool test data.
It might be good to also get some sample data from running JEDI on MPAS runs.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

needs to be in METplus v4.1.0

Funding Source

2702691

Define the Metadata

Assignee

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

Labels

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

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT 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, METdatadb, 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 Linked 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.