Add Lake Champlain USGS Water level data provider for coastal model t…

[jduckerOWP]

Add Lake Champlain USGS Water level data provider for coastal model t…

[Short description explaining the high-level reason for the pull request]

Additions

• @PhilMiller to include a data provider BMI to evaluate full coupling of the SCHISM Lake Champlain formulation, which includes two-way coupling of T-Route and offshore water levels forced by the USGS water level observation gauge upstream of the Lake Champlain domain.

Removals

-

Changes

-

Testing

1.

Screenshots

Notes

-

Todos

-

Checklist

• [ ] PR has an informative and human-readable title
• [ ] Changes are limited to a single goal (no scope creep)
• [ ] Code can be automatically merged (no conflicts)
• [ ] Code follows project standards (link if applicable)
• [ ] Passes all existing automated tests
• [ ] Any change in functionality is tested
• [ ] New functions are documented (with a description, list of inputs, and expected output)
• [ ] Placeholder code is flagged / future todos are captured in comments
• [ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• [ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

1.

Target Environment support

• [ ] Linux

[jduckerOWP]

@PhilMiller Here is the BMI development of the USGS water level gauge data provider for you to test and evaluate SCHISM in a fully coupled NextGen formulation. I'll be happy to address any questions or concerns you may have. Keep in mind that I'm only proposing a new repository potential for "BMI water level data providers" but I'll be happy to discuss this accordingly with how the model engine team wants to move forward with that data provider integration into the NextGen framework.