Integrate NOAA marine verification package into METplus

[j-opatz]

Replace italics below with details for this issue.

Describe the Task

On 12/17/20, DTC staff met with NOAA/EMC staff to discuss the transition of the existing EMC Marine Verification functionality into METplus. After successfully embodying tripolar coordinate python wrappers into METplus (#737), a meeting on 02/03/21 laid out the remaining packages.
This Issue will serve as the central issue for the package, while the individual components become subtasks. Code repo to mimic is on VLAB/redmine, project "EMC Verif Marine, emc-ocean-verification repo"

Time Estimate

2-4 weeks

Sub-Issues

Sub-issues should have GitHub issue numbers added as they are created; the descriptions are meant to be general

• Satellite package New Use Case: Satellite verification of sea surface temperature (GHRSST) against RTOFS output #1004
• Satellite package New Use Case: Satellite verification of sea surface salinity: SMOS vs RTOFS output #1116
• Satellite package New Use Case: Satellite verification of sea surface salinity: SMAP vs RTOFS output #1216
• Satellite package New Use Case: Satellite verification of sea surface salinity: AVISO vs RTOFS output HYCOM climo #1318
• Ocean fronts New Use Case:Ocean fronts demonstrating modified Hausdorff #1494
• Ice verification New Use Case: Ice cover/concentration use case, part of marine layer verification integration #834
• Cable transfer New Use Case: Cable transport verification: AOML Cable Transfer vs RTOFS output #1399

Relevant Deadlines

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

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

Projects and Milestone

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

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

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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[j-opatz]

To not continue to kick this issue further down the line, it is being closed. The remaining two use cases are listed here, and will be completed in the next beta