Bugfix #2493 main_v11.0 aeronet3 lat lon elv

[hsoh-u]

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

bin/ascii2nc /d1/projects/METplus/discussions/1888/Discussion1888/20230309.lev15 test_aeronet.nc -format aeronetv3
OR
/d1/personal/hsoh/git/pull_request/MET_bugfix_2493_aeronet3_lat_lon_elv/bin/ascii2nc /d1/projects/METplus/discussions/1888/Discussion1888/20230309.lev15 test_aeronet.nc -format aeronetv3

python3 scripts/utility/print_pointnc2ascii.py test_aeronet.nc | awk ' {print $4, $5, $6, $2;}' | uniq -c | less
OR 
python3 /d1/personal/hsoh/git/pull_request/MET_bugfix_2493_aeronet3_lat_lon_elv/scripts/utility/print_pointnc2ascii.py test_aeronet.nc | awk ' {print $4, $5, $6, $2;}' | uniq -c | less

Result (the lat/lon for GSFC should be different from Tucson)

   <count><lat> <lon> <elv> <SiteName>
   3752 32.2330 -110.9530 779.0000 Tucson
   4536 38.9925 -76.8398 87.0000 GSFC
   2072 25.7320 -80.1633 10.0000 Key_Biscayne
   ...

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

• Do these changes include sufficient testing updates? [No]

The unit test exists.

• Will this PR result in changes to the test suite? [Yes]
  
  If yes, describe the new output and/or changes to the existing output:
  

Different lat/lon/elv at aeronet/20221202.v3.lev15.nc

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Development issue with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[jprestop]

@hsoh-u I have reviewed the changes to the code and have confirmed that the only differences that exist are expected:

file2: /data/output/met_test_output/aeronet/20221202.v3.lev15.nc
ERROR: found   104 differences in var hdr_elv                                - max abs: 769 
ERROR: found   104 differences in var hdr_lat                                - max abs: 15.5005 
ERROR: found   104 differences in var hdr_lon                                - max abs: 88.0175 

I approve this request.