Bugfix: MET maps a polar stereographics projection to the wrong places

[hsoh-u]

Replace italics below with details for this issue.

Describe the Problem

Provide a clear and concise description of the bug here.

The plot_data_plane recognizes the polar stereographics as following from seneca:/d1/personal/jopatz/workbench/tripolar/ice_observation/seaice_conc_daily_nh_1978_v04r00.nc

DEBUG 4: Stereographic Grid Data:
DEBUG 4:   hemisphere: N
DEBUG 4:    scale_lat: 90
DEBUG 4:      lat_pin: 31.0423
DEBUG 4:      lon_pin: 11.6796
DEBUG 4:        x_pin: 0
DEBUG 4:        y_pin: 0
DEBUG 4:   lon_orient: -135
DEBUG 4:         d_km: 25
DEBUG 4:        dy_km: -25
DEBUG 4:         r_km: 6371.2
DEBUG 4:           nx: 304
DEBUG 4:           ny: 448

Nothing wrong with the recognized parameters for the polar stereographics. But the produced image by plot_data_planne is different from the plot by IDV below.

In order to fix this problem, we need more information for the polar stereographics projection (when to apply a negative D_km, etc).

Expected Behavior

Provide a clear and concise description of what you expected to happen here.
The plot by IDV

The adjusted projection with using set_attr_grid="stereo 304 448 31.0423 11.6796 -135 -25 6378.273 90. N"; produces the following images

from

./plot_data_plane /d1/personal/jopatz/workbench/tripolar/ice_observation/seaice_conc_daily_nh_1978_v04r00.nc [nccf_polar_ugrid.ps](http://nccf_polar_ugrid.ps/) 'name="cdr_seaice_conc"; level="(0,*,*)"; set_attr_grid="stereo 304 448 31.0423 11.6796 -135 -25 6378.273 90. N";' -v 4

Environment

Describe your runtime environment:
1. Machine: Linux Workstation (seneca)
2. OS: RedHat Linux
3. Software version number(s)

To Reproduce

Describe the steps to reproduce the behavior:
1. Go to 'seneca'
2. Find the latest nightly build
3. Run the following command
4. Check the produced image

bin/plot_data_plane /d1/personal/jopatz/workbench/tripolar/ice_observation/seaice_conc_daily_nh_1978_v04r00.nc seaice_polar_projection.ps 'name="cdr_seaice_conc"; level="(0,*,*)";' -v 4

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

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as the next bugfix version
• Select Coordinated METplus-X.Y Support project for support of the current coordinated release
• Select MET-X.Y.Z Development project for development toward the next official release

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

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: Milestone as the next bugfix version
  Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
• 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: Milestone as the next official version
  Select: MET-X.Y.Z Development project for development toward the next official release
• Close this issue.