Describe the Enhancement

This issue arose from an email from Ho-Chun Huang on April 7, 2023. Per Amy Huff, as of April 16 (previously April 9th), 2023, a change will be made to the quality flags for the smoke and dust AOD data provided in GOES 16/17 files.

Per Ho-Chun, what matters to Points2Grid Smoke and Dust AOD processing probably is the reverse values of the smoke/dust detection confidence (in ADP files) for the Smoke and Dust AOD (detection confidence =0 is now high quality Smoke/Dust AOD).

This issue is to update the Point2Grid algorithm for the next version of MET.

Please be aware that the GOES-East/West ABI Aerosol Detection Product (ADP) smoke/dust mask current (Baseline) algorithm is being updated to the Enterprise algorithm tomorrow, April 9:
https://www.ospo.noaa.gov/data/messages/2024/04/MSG_20240404_1823.html

The "Smoke" and "Dust" variables in the ADP output file will remain the same, but other key variables/flag values for processing smoke/dust detections will change, as outlined in the following table.  Please update your scripts!

This issue is to review the logic and documentation of the Point2Grid tool in MET:

• Determine whether these changes are indicated by an updated version number in the data files... or whether they are based strictly on the timestamp. Either way, remember to add a new unit test that demonstrates the updated processing logic. And remember to confirm that data prior to April 9, 2024 continue to be processed in the "correct" way.
• Confirm that the quality control confidence values are being parsed correctly from NEW files.
• Confirm that the quality control confidence values are being parsed correctly from OLD files.
• Remember to update the MET and METplus documentation, if needed.

Time Estimate

1 day?

Sub-Issues

Consider breaking the enhancement down into sub-issues.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2784543 UFS R2O

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 official version or Backlog of Development Ideas
• For the next official 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
  This may impact the output produced by existing METplus Use Cases.

Enhancement 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.