It would be good to minimise having to add ad-hoc data loaders for NWPs with different schemas as was this case here in ocf_datapipes, while there may be differences that mean different loaders may be appropriate e.g different coordinate systems, many of the NWPs can use a generic loader which would look similar to what we have for the ECMWF loader currently.
Given this it would be good to rename the ECMWF loader to a more generic name, reference that here and for any NWPs that can be in this generic format to use this loader. Two NWPs which fall into this category are GFS and MetOffice Global ("gfs", "mo_global") so can be added to the same nwp.py file as NWPs which can use this loader.
It would be good to minimise having to add ad-hoc data loaders for NWPs with different schemas as was this case here in ocf_datapipes, while there may be differences that mean different loaders may be appropriate e.g different coordinate systems, many of the NWPs can use a generic loader which would look similar to what we have for the ECMWF loader currently.
Given this it would be good to rename the ECMWF loader to a more generic name, reference that here and for any NWPs that can be in this generic format to use this loader. Two NWPs which fall into this category are GFS and MetOffice Global ("gfs", "mo_global") so can be added to the same nwp.py file as NWPs which can use this loader.