Describe the New Feature

As of 10/25/22 - Identified as CRITICAL for Met Office:

MET assumes a spherical Earth. The EUMETNET (radar) dataset is on a Lambert Azimuthal Equal Area grid, which uses an ellipsoidal Earth. Randy already has some code for latlon_to_xy. The xy_to_latlon code still needs to be implemented, and the code needs to be implemented in MET (and tested accordingly).

Acceptance Testing

Same data is located on Cheyenne:
/gpfs/fs1/p/ral/jntp/AF/gswr/eumetnet (in HDF5 format)

This data can be moved to a more convenient location. Some sample data has already been shared with Randy.

Tests will need to be done to make sure the Lambert Azimuthal Equal Area projection is working as anticipated (will work with Randy to establish necessary tests).

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.
No sub-issues required.

Relevant Deadlines

Goal is to target the met-10.1.0_beta1 release scheduled for 5/13/21.

Funding Source

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: Randy B
• Select scientist(s) or no scientist required: Michelle H

Labels

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

Projects and Milestone

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

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

New Feature 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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.