Dear Colleagues,
I'm just trying to get radiance data from GOES16 into 3DVAR. We rely on Advanced Baseline Imager data in netcdf files similar to those NOAA offers on Google and Amazon cloud platforms (https://data.nodc.noaa.gov/cgi-bin/iso? ... cdc:C01502). With GOES16, transmission changed from GVAR to GRB. Looking at the netcdf variables and metadata it seems they are now using NetCDF Climate and Forecast (CF) Metadata Conventions.
Stepping through the code of WRFDA version 4.1, it expects only data from GOES 13 to 15, although radiative transfer models are already prepared for GOES16. If one could introduce the calibration coefficients and zenith angle for GOES16 into WRFDA code, there would be still the problem that name conventions for the netcdf variables and metadata have changed.
So before joining the adventure to modify the codes (e.g. da_read_obs_ncgoesimg.inc) I'd like to ask if there is already some new interface for GOES16.
With best regards,
Thorsten Beisiegel
I'm just trying to get radiance data from GOES16 into 3DVAR. We rely on Advanced Baseline Imager data in netcdf files similar to those NOAA offers on Google and Amazon cloud platforms (https://data.nodc.noaa.gov/cgi-bin/iso? ... cdc:C01502). With GOES16, transmission changed from GVAR to GRB. Looking at the netcdf variables and metadata it seems they are now using NetCDF Climate and Forecast (CF) Metadata Conventions.
Stepping through the code of WRFDA version 4.1, it expects only data from GOES 13 to 15, although radiative transfer models are already prepared for GOES16. If one could introduce the calibration coefficients and zenith angle for GOES16 into WRFDA code, there would be still the problem that name conventions for the netcdf variables and metadata have changed.
So before joining the adventure to modify the codes (e.g. da_read_obs_ncgoesimg.inc) I'd like to ask if there is already some new interface for GOES16.
With best regards,
Thorsten Beisiegel