New Use Case: Demonstration of forecast and observation files on UGRID, verified on supported grid

[j-opatz]

Describe the New Use Case

In our continued support of the Met Office, this use case will serve as a demonstration of the UGRID capabilities as they currently stand, with the opportunity for future updates to modify the use case to showcase future added capability or desired scenarios.

For the initial use case, we will use data provided by the Met Office that has both the forecast and observation datasets on a UGRID. Those will be interpolated to a standard grid, using the methods indicated by Met Office.

Use Case Name and Category

This will fall under the Unstructured Grids category. Name will be determined later via data provided.

Input Data

Input data and variable field for testing to be provided by Met Office

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here

Time Estimate

3 days, when work begins

Sub-Issues

Consider breaking the new feature down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

This use case is tied to the Met Office project and should conclude no later than July 31st. Ideally, this would be completed before the end of Q3.

Funding Source

PRJ014176

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)
• Select privacy

Milestone and Projects

• Select Milestone as a METplus-Wrappers-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METplus-Wrappers-X.Y.Z version, select the METplus-Wrappers-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 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.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• 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: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
• 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.

[robdarvell]

I have tried to upload using the Google form some data in which you can hopefully test things out. The files are timestamped by initialisation time. There is more data than is required. I have just hopefully included t1p5m (surface temperature).
The file from 00Z on the 31st Aug can be treated as the forecasts and then within the 12Z on the 31st should be the Observation (Truth) T+0 data to verify the T+12 forecast from 00Z and then T+24 which would verify against the 00Z on the 01st Sep file.

Hopefully they are what you were looking for.
Rob

[robdarvell]

If I have this right, then the metadata_map would look something like the following:
ugrid_metadata_map = [
{ key = "dim_face"; val = "nMesh2d_face"; },
{ key = "dim_time"; val = "time_counter"; },
{ key = "dim_vert"; val = "pressure_levels"; }, // optional
{ key = "lat_face"; val = "Mesh2d_face_y"; },
{ key = "lon_face"; val = "Mesh2d_face_x"; },
{ key = "vert_face"; val = "nMesh2d_face"; }, // optional
{ key = "time"; val = "time_instant"; }
];

[j-opatz]

Thanks @robdarvell! I was able to successfully download the data you provided, and I'll be taking a look at it as development on the use case ramps up.