Bugfix: Fix reading of upside-down CF-compliant NetCDF Rotated Lat/Lon data

[JohnHalleyGotway]

Describe the Problem

@mpm-meto sent a sample NetCDF file containing data originally generated by LFRic, but converted to a rotated lat/lon projection and stored in a CF-Compliant NetCDF file. When MET plots it, the data appears upside-down. The country outlines appears in the expected location but the data is plotted upside-down.

The left image is the upside down plot from Plot-Data-Plane. The middle image is the output from ncview. The right image is the plot from panoply:

Expected Behavior

MET should orient this rotated lat/lon data correctly. Please fix this functionality in both the main_v11.0 branch (for inclusion in MET 11.0.3 bugfix release) and in main_v11.1 (for inclusion in the 11.1.0 release).

To Reproduce

1. Download this sample data file:
   test_lfric_lam.nc.gz
2. Run plot_data_plane:

plot_data_plane test_lfric_lam.nc test_lfric_lam.ps 'name="t1p5m"; level="(*,*)";'

3. Observe the data being upside-down.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2799991

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

• Select Organization level Project for support of the current coordinated release
• Select Repository level Project for development toward the next official release or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  No impacts.

Bugfix 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 main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug 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 main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Organization level software support Project for the current coordinated release
  Select: Milestone as the next bugfix version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Development issue
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.

[JohnHalleyGotway]

@hsoh-u I see that you fixed this with PR #2595 in main_v11.1. Looks like we'd also like a fix in the main_v11.0 branch. Are you able to port over this fix to the main_v11.0 branch too?