Fix Stat-Analysis aggregation of the neighborhood statistics line types.

[JohnHalleyGotway]

Describe the Problem

This issue was raised via GitHub discussion dtcenter/METplus#1826. The aggregation of the NBRCTC line types by Stat-Analysis does not work as expected.

Please provide this bugfix for the main_v10.0, main_v10.1, and develop branches.

Expected Behavior

Stat-Analysis should be able to aggregate multiple NBRCTC lines and write an output .stat file by running -job aggregate -line_type NBRCTC -out_stat out.stat.

Environment

Describe your runtime environment:
1. Machine: Replicated on Mac laptop
2. OS: MacOS
3. Software version number(s): main_v10.0, main_v10.1, and develop branches

To Reproduce

Describe the steps to reproduce the behavior:

1. Run MET version 10.0 or later:

stat_analysis -lookin grid_stat_APCP_12_120000L_20050807_120000V.txt \
-job aggregate -line_type NBRCTC -out_stat out_stat.txt

Using: grid_stat_APCP_12_120000L_20050807_120000V.txt

2. Observe the runtime error:

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Abort trap: 6

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: None needed

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
  No impacts.

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.