Trajectory sampler for IODA file: step-1

[metdyn]

Description

Step-1 to enable MAPL_HistoryTrajectoryMod to sampler IODA files

• Feature request: Update trajectory sampler to read IODA files for AIST #2144

Completed Step-1:

• sort the Time series in IODA file together with lat/lon arrays
• utilize the trajectory module

ExtDataDriver.x can run and generate NC output:

netcdf sondes.20201214_2010z {
dimensions:
        lev = 4 ;
        time = UNLIMITED ; // (66408 currently)
variables:
        double lev(lev) ;
                lev:coordinate = "eta" ;
                lev:long_name = "vertical level" ;
                lev:positive = "down" ;
                lev:standard_name = "model_layers" ;
                lev:units = "layer" ;
        float time(time) ;
                time:begin_date = 20201214 ;
                time:begin_time = 201000 ;
                time:long_name = "time" ;
                time:time_increment = 30000 ;
                time:units = "minutes since 2020-12-14 20:10:00" ;
        double longitude(time) ;
                longitude:long_name = "longitude" ;
                longitude:units = "degrees_east" ;
        double latitude(time) ;
                latitude:long_name = "latitude" ;
                latitude:units = "degrees_east" ;
        float var2(time) ;
                var2:_FillValue = 1.e+15f ;
                var2:long_name = "time" ;
                var2:missing_value = 1.e+15f ;
                var2:units = "days" ;
                var2:valid_range = -1.e+15f, 1.e+15f ;
        float var3(lev, time) ;
                var3:_FillValue = 1.e+15f ;
                var3:long_name = "time" ;
                var3:missing_value = 1.e+15f ;
                var3:units = "days" ;
                var3:valid_range = -1.e+15f, 1.e+15f ;
}

netcdf sondes.20201214_2010z {
dimensions:
        lev = 4 ;
        time = UNLIMITED ; // (66408 currently)
variables:
        double lev(lev) ;
                lev:coordinate = "eta" ;
                lev:long_name = "vertical level" ;
                lev:positive = "down" ;
                lev:standard_name = "model_layers" ;
                lev:units = "layer" ;
        float time(time) ;
                time:begin_date = 20201214 ;
                time:begin_time = 201000 ;
                time:long_name = "time" ;
                time:time_increment = 30000 ;
                time:units = "minutes since 2020-12-14 20:10:00" ;
        double longitude(time) ;
                longitude:long_name = "longitude" ;
                longitude:units = "degrees_east" ;
        double latitude(time) ;
                latitude:long_name = "latitude" ;
                latitude:units = "degrees_east" ;
        float var2(time) ;
                var2:valid_range = -1.e+15f, 1.e+15f ;
        float var3(lev, time) ;

data:

 lev = 1, 2, 3, 4 ;

 time = 81.18333, 81.18333, 81.41666, 81.86667, 81.86667, 82.2, 83.68333,
    83.75, 84.05, 84.05, 84.08334, 84.23333, 84.9, 85.43333, 86.41666,
    86.41666, 86.73333, 87.53333, 88.6, 89.95, 90.2, 90.2, 90.38333,
    90.76667, 90.76667, 90.85, 91.16666, 91.38333, 91.45, 91.71667, 91.71667,

 longitude = 174.979995727539, 174.979995727539, 174.979858398438,
    174.979553222656, 174.979553222656, 174.979309082031, 174.978881835938,

 latitude = -40.9000015258789, -40.9000015258789, -40.9004402160645,
    -40.9010696411133, -40.9010696411133, -40.9013710021973,

 var2 = 100, 100, 100, …

Related Issue

Motivation and Context

How Has This Been Tested?

run ExtDataDriver.x with HISTORY1.rc

COLLECTIONS:
sondes
::
GRID_LABELS:
::
sondes.template: '%y4%m2%d2_%h2%n2z.nc4',
sondes.format: 'CFIO',
sondes.sampler_spec: ioda_loc_stream
sondes.track_file: x0044.sondes.2020-12-14T21:00:00Z.nc4
sondes.nc_Index: Location
sondes.nc_Time: MetaData/dateTime
sondes.nc_Longitude: MetaData/longitude
sondes.nc_Latitude: MetaData/latitude
sondes.frequency: 030000,
sondes.duration: 000000,
sondes.regrid_method: 'BILINEAR' ,
sondes.fields: 'var2', 'Root'
'var3', 'Root'

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Trivial change (affects only documentation or cleanup)

Checklist:

• I have tested this change with a run of GEOSgcm (if non-trivial)
• I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
• I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog