-
Notifications
You must be signed in to change notification settings - Fork 14
Description
There are currently three different Python converters in the ioda-converters repo related to OMPS total column ozone (TCO₃):
1. src/compo/ompsnm_o3_nc2ioda.py
2. src/compo/omps_o3_nm_h52ioda.py
3. src/hdf5/ozone_product_2ioda.py
We need to determine whether these scripts are ingesting data from different input formats or streams (e.g., BUFR vs. HDF5 vs. netCDF), or if they represent redundant pathways for the same data.
Can we refactor and consolidate these converters if they serve overlapping purposes, reducing duplication and easing maintenance?
⸻
TODO:
• Identify the data sources/formats expected by each of the three OMPS converters.
• Compare the variable mappings and metadata handling across the scripts.
• Determine if one converter can be generalized to support more or all relevant OMPS input formats.