Fix ASCII2NC logic for reading AERONET v3 data

[jprestop]

Describe the Problem

This issue arose with the METplus Discussion dtcenter/METplus#1888. When the user obtained AERONET version 3 data from the official site it was determined that the format was not consistent with the format of the data we currently use for our unit testing. Sample files from the new format and @hsoh-u's analysis of what would need to be done for this issue can be viewed within the Discussion at this post.

Expected Behavior

The MET code should be able to read AERONET v3 data obtained from the official site.

Environment

Describe your runtime environment:
1. Machine: not specific
2. OS: not specific
3. Software version number: all current releases

To Reproduce

Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Review the log file from Partha and read the data files he provided.

Relevant Deadlines

MET-11.0.0 Official Release (12/7 - 12/9)

Funding Source

2773542

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

[JohnHalleyGotway]

@hsoh-u please prioritize fixing this in the develop branch to be included in the MET version 11.0.0 release. Once it's fixed there, please port that fix over to the main_v10.1 branch. And we'll include it in any future MET-10.1 bugfix releases.