New Use Case: Satellite Altimetry data #2383
Description
Describe the New Use Case
EMC needs to be able to read satellite altimetry data in order to verify significant wave height in GFS-wave and GEFS-wave forecasts. Satellite Altimetry data is in netCDF format. A python wrapper, similar to what was created for the scatterometer Use Case, perhaps!
Use Case Name and Category
Use case name is unknown for now, but should follow:
PointStat_fcstGFS_obsJASON3_satelliteAltimetry
Input Data
JASON-3, SARAL/ALTIKA, and Sentinel-6a are satellite altimetry datasets.
Data can be obtained from PO.DAAC (NASA). https://github.com/podaac/data-subscriber has code to read their altimeter data and more (pull out region, time, etc). Global would be good, since GFS-wave and GEFS-wave are global models.
Contact @AliciaBentley-NOAA for questions about input data and who should perform the Release Acceptance Testing step.
Acceptance Testing
Success of this use case will be two things: a successful run through METplus with the datasets listed above, and meaningful output for EMC that they can utilize.
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
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 CYCLE ASSIGNMENT label
- Select Milestone as the next official version or Future Versions
Define Related Issue(s)
Consider the impact to the other METplus components.
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.
- Add any new Python packages to the METplus Components Python Requirements table.
- 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 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.