Add ability to plot upper-air statistics on a z (height) coordinate

[davidturner53]

This is needed in both RAOB and AMDAR apps.

Need to be able to plot profiles of model-obsservation statistics on a vertical z coordinate (i.e., as a function of height above ground). This is very important to understand how the models are representing the planetary boundary layer.

I think this should only be done as part of the refactoring of the RAOB and AMDAR apps.

I would like to get an estimate of the amount of effort this would take.

[bonnystrong]

Dave says will be high once we are using Couchbase Ingest.

[bonnystrong]

This is being considered as new ingest is designed.

[JeffHamiltonNOAA]

Working on this as part of the 3D data model component

[bonnystrong]

Jeff will talk to Joe and Dave for input.

Randy: need to address TTL before start ingesting 3D data.

[JeffHamiltonNOAA]

Initial levels have been decided upon after conversation with Dave:

every 20 m, up to 200 m (10 levs) - 20, 40, 60, 80, 100, 120, 140, 160, 180, 200

then every 50 m, up to 500 m (8 levs) - 250, 300, 250, 300, 350, 400, 450, 500

then every 100 m, up to 2000 m (14 levs) - 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, 1500, 1600, 1700, 1800, 1900, 2000

then every 200 m, up to 5000 m (15 levs) - 2200, 2400, 2600, 2800…. 5000

We will go with this for now

[JeffHamiltonNOAA]

After discussion with the team and Dave, we have decided to increase the upper limit of this coordinate to include flight level data for compatible instruments. This may include referencing a "data quality" variable in the ingest process for some observations that may have data that high but of low confidence and quality (lidar for example). I'll work on trying to incorporate flight level data into this set (since flight levels are in feet and this is in meters) and bring it to the group.

[ian-noaa]

Blocked waiting on the cfgrib implementation in #226

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity.