Develop a class that supports reading both FCST and OBS from a IODA file to use with the new Pair-Stat tool

[DanielAdriaansen]

Describe the New Feature

In #3006 a new tool (Pair-Stat) is proposed to allow statistical verification of "already paired data". One example of this kind of data that should be supported by Pair-Stat is the IODA file format. IODA files contain an observation and a forecast value pair at various locations. This issue is to create a new class that reads IODA forecast and observation pairs and subsets them into existing pair data point classes so that a vector of pair data point objects can be derived to facilitate statistical scoring.

IODA files have many groups of objects, and it will be important to define the mapping of how a user can configure Pair-Stat to match the groups of objects to the pairs they want.

Acceptance Testing

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

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

This work must be completed by 12/30/2024

Funding Source

NRL METplus 7730022

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.Z Development project

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 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.

[JohnHalleyGotway]

Per @DanielAdriaansen see current sample data at: https://dtcenter.ucar.edu/dfiles/code/METplus/METplus_Data/v6.0/model_applications/data_assimilation/StatAnalysis_fcstGFS_HofX_obsIODAv2_PyEmbed/