New Use Case: Cable transport verification: AOML Cable Transfer vs RTOFS output

[mrinalbiswas]

This new use case will duplicate the efforts of Todd Spindler's VLab-Redmine code, specifically its calculations for Florida Cable Transport using AOML Florida current as obs, RTOFS output as model forecasts.
It still needs to be determined if the graphical output currently produced and displayed at the site listed below need to be produced in this use case.
As a final step, these new data sources will be logged in the METplus Verification Datasets Guide.

This is part of the larger Marine layer Verification package integration, which is tracked in #800.

Describe the New Use Case

Provide a description of the new feature request here.

Use Case Name and Category

GridStat_StatAnalysis_fcstRTOFS_obsAOML_cable under marine_and_crosphere

Input Data

https://www.aoml.noaa.gov/phod/floridacurrent/index.php

Acceptance Testing

A successful output from this use case will duplicate ongoing efforts currently completed with Todd's VLab code.

Time Estimate

Approximately 3-5 days

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

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

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

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 Use Case 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 your changes. Merge branch into develop.
• Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
• Delete your fork or branch.
• Close this issue.