Update references to the Gulf of America

[JohnHalleyGotway]

Describe the Task

As discussed during METplus NOAA User Telecon on March 3, 2025 (see notes) and confirmed via email afterwards, the MET repository should be updated based on the Gulf of America name change. Similar changes have already been made in the NOAA/EVS repository and can be used as a reference.

The location of the changes include:

Docs: descriptions could be modified:
./docs/Users_Guide/appendixB.rst:* GLF.poly for the Gulf of Mexico
./docs/Users_Guide/appendixB.rst:* GMC.poly for the Gulf of Mexico Coast

Data: GMC could be renamed as GAC.
./data/poly/NCEP_masks/GMC_mask.nc
./data/poly/GMC.poly
./data/poly/ncep_vx_regions.pdf

Time Estimate

2 hours

Sub-Issues

Consider breaking the task down into sub-issues.
None needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2783544 NOAA R2O METplus?

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 a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

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

Task 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) and Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.