Can we also add a similar function to preprocess the camx data for PM2.5 values? It will do similar preprocessing with the data as the other function does with camx_met data.
this is what the file looks like in the original:
<xarray.Dataset>
Dimensions: (TSTEP: 120, LAY: 1, ROW: 80, COL: 80, VAR: 9, DATE-TIME: 2)
Dimensions without coordinates: TSTEP, LAY, ROW, COL, VAR, DATE-TIME
Data variables:
P10 (TSTEP, LAY, ROW, COL) float32 ...
P25 (TSTEP, LAY, ROW, COL) float32 ...
TFLAG (TSTEP, VAR, DATE-TIME) int32 ...
Attributes: (12/34)
IOAPI_VERSION: $Id: @(#) ioapi library version 3.0 $ ...
EXEC_ID: ???????????????? ...
FTYPE: 1
CDATE: 2023297
CTIME: 82541
WDATE: 2023297
... ...
GDNAM: ????????????????
UPNAM: CAMXMETOU
VAR-LIST: P10 P25
FILEDESC: I/O API formatted CAMx AVRG output ...
HISTORY: Wed Oct 25 08:23:00 2023: ncrcat camxout.2023.10.24.nc ca...
NCO: netCDF Operators version 4.9.1 (Homepage = http://nco.sf/....
<xarray.Dataset>
Dimensions: (latitude: 80, longitude: 80, time: 24, lag: 5)
Coordinates:
* latitude (latitude) float64 28.19 28.2 28.21 28.22 ... 28.96 28.97 28.98
* longitude (longitude) float64 76.84 76.85 76.86 76.87 ... 77.61 77.62 77.63
* time (time) datetime64[ns] 2023-10-25T05:30:00 ... 2023-10-26T04:30:00
* lag (lag) int64 -1 0 1 2 3
Data variables:
PM10 (lag, time, latitude, longitude) float64 nan nan ... 48.45 48.45
PM2.5 (lag, time, latitude, longitude) float64 nan nan ... 46.77 46.77
Attributes: (12/34)
IOAPI_VERSION: $Id: @(#) ioapi library version 3.0 $ ...
EXEC_ID: ???????????????? ...
FTYPE: 1
CDATE: 2023297
CTIME: 82541
WDATE: 2023297
... ...
GDNAM: ????????????????
UPNAM: CAMXMETOU
VAR-LIST: P10 P25
FILEDESC: I/O API formatted CAMx AVRG output ...
HISTORY: Wed Oct 25 08:23:00 2023: ncrcat camxout.2023.10.24.nc ca...
NCO: netCDF Operators version 4.9.1 (Homepage = http://nco.sf/....