You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
The geocat reader is cannot load the hdf geocat files for 2 reasons:
The netcdf4 engine currently needs to be specified for xarray so that geocat hdf files currently being generated can read with xarray.
The time units (for example, the metadata for the variable scan_line_time) are not cf compliant. They are currently
units="seconds_since_jan_1_"
Solution (to assist in reading data from current geocat files):
Add an __init__ to the GEOCATFileHandler so that xarray_kwargs can be passed through the reader_kwargs when the scene is loaded:
Set the defaults of these arguments to {"engine": "netcdf4", "decode_times": False} which will still allow users to set decode_times and engines as needed if the units are changed in the geocat software.
Workflow Changes
As I understand this, it will not affect backward compatibility. It might force the addition of future reader_kwargs if the geocat software package is updated.
Additional context
The question of updating the metadata for the units has been presented to the geocat team. However, this software is already in use by many teams and it appears that this bug in the metadata has not been reported. In the end, it would be nice if this reader could work regardless of the final decision by the team concerning the units metadata. Old files will have this unit specification and the software has been in use for a while.
The text was updated successfully, but these errors were encountered:
joleenf
added a commit
to joleenf/satpy
that referenced
this issue
Jun 12, 2023
Feature Request
Problem:
The geocat reader is cannot load the hdf geocat files for 2 reasons:
units="seconds_since_jan_1_"
Solution (to assist in reading data from current geocat files):
Add an
__init__
to the GEOCATFileHandler so that xarray_kwargs can be passed through the reader_kwargs when the scene is loaded:Set the defaults of these arguments to {"engine": "netcdf4", "decode_times": False} which will still allow users to set decode_times and engines as needed if the units are changed in the geocat software.
Workflow Changes
As I understand this, it will not affect backward compatibility. It might force the addition of future reader_kwargs if the geocat software package is updated.
Additional context
The question of updating the metadata for the units has been presented to the geocat team. However, this software is already in use by many teams and it appears that this bug in the metadata has not been reported. In the end, it would be nice if this reader could work regardless of the final decision by the team concerning the units metadata. Old files will have this unit specification and the software has been in use for a while.
The text was updated successfully, but these errors were encountered: