༄ ODD PI 26.4 Objective 2: NAQFC optimized data delivery for AIR4US

[abarciauskas-bgse]

Motivation + Description

AIR4US is launching its beta portal in September. Stakeholders of the portal will benefit from efficient access, visualization and analysis for the dataset. NAQFC will be evaluated and its implementation will take into consideration the intended use of the dataset in the AIR4US portal as well as the extensibility of any proposed solution to the wider community.

Acceptance Criteria / Sub-tasks

• Coordination with AIR4US stakeholders
• Dataset and use case evaluation
• Design optimized representation and integration (e.g. virtual icechunk store)
• Prototype
• Implement + document

Resources

• Index NAQFC AQM (v7) O3 and PM2.5 72 Hour Forecasts #417

LOE

0.67 FTE for the PI

Dependencies

• AIR4US project leadership for direction on use case
• AIR4US front-end engineering for integration support
• Data services for data publication support

[Jeanne-le-Roux]

Is it possible to link this as the parent ticket? That would tie this effort back to the larger overall dataset integration objective for AIR4US.

[sharkinsspatial]

@abarciauskas-bgse I don't have rights to link issues from external this external repo but in order to support proper dimension naming for NAQFC I created this ticket mpiannucci/gribberish#152 and this PR mpiannucci/gribberish#179

[sharkinsspatial]

@siddharth0248 I'm just doing initial test runs for the NAQFC data. There is different model output for Conus, Hawaii and Alaska (which use LCC, Mercator and Polar Stereographic grids respectively). I'll need to make some updates to Gribberish to support these other grids but I just wanted to clarify our eventual store structure here which would be

• naqfc_aqmv7_o3_conus
• naqfc_aqmv7_o3_hi
• naqfc_aqmv7_o3_ak
• naqfc_aqmv7_pm25_conus
• naqfc_aqmv7_pm25_hi
• naqfc_aqmv7_pm25_ak