Describe the Problem

In the use case for CyclonePlotter (CyclonePlotter_fcstGFS_obsGFS_OPC), Guang Ping found that any cyclone path that crosses the prime meridian will produce a line that wraps around the entire globe. This is partly due to where the map projection cuts the globe (e.g. the unconnected parts of the globe), but as indicated by this Stack Overflow Question, the main culprit is probably the longitudes.

More specifically, we need to make CyclonePlotter identify those tracks that have longitude leaps from 359 to 2 and reset it to a continuous path (i.e. 359 to 362).

Expected Behavior

The successful fix of this issue will produce a global map of cyclone tracks that do not create a global-crossing track.

Environment

Describe your runtime environment:
1. Machine: Hera, reproduced on Kiowa
2. OS: Linux
3. METplus 4.0.0

To Reproduce

Describe the steps to reproduce the behavior:
1. Run the use case CyclonePlotter_fcstGFS_obsGFS_OPC
2. View the .ps file output from CyclonePlotter

Relevant Deadlines

NONE

Funding Source

2788881

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 PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, 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 Linked issues
  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 Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.