SSEC forums

Hi Chris, I'm just getting back from leave and have been thinking about this for a couple days and would like to add to Kathy's response. This is just some extra information for anyone who is interested in this topic in the future. As Kathy said, we depend heavily on Xarray and Dask and there is a l...

Hi, This is actually a bug in Geo2Grid. It is very rare and we had a lot of trouble tracking it down, so congratulations? The good news is it should be fixed in a patch release of Geo2Grid that we haven't released yet (due to so few users running into this issue). If you could try downloading this g...

Last question, if I used the "--dtype float32 --no-enhance", the wrong standard name shouldn't affect the process right?

Correct. It should skip the enhancing/scaling part and store the "raw" (sunz/rayleigh) reflectance values.

In your composites config, you have standard_names like: standard_name: B01C Did you change these? I'm guessing these used to be `toa_bidirectional_reflectance`. Most enhancements are configured by standard_name. This way it is easy to say "all reflectances should be enhanced this way, all brig...

Thanks for the extra info. It looks like the path to the input data isn't correct. You specified "-f ../input" but Geo2Grid wasn't able to find any files in that directory or was not able to find that directory at all. Can you verify that there are ABI L1b NetCDF files in that directory?

Hi, Would it be possible for you to run Geo2Grid with an extra "-v" command line flag? Or you could attach the log file it created here. There isn't enough information in the provided output to debug this, but with the extra output (from -v or the log file) I might be able to make some gue...

As far as I remember there were no intentional changes to the sunz or rayleigh corrections in Satpy. One thing I'm noticing is the portion of your log that says: [2020-06-05 00:00:12,906] : PID 148 : DEBUG : satpy.writers : apply : Enhancement configuration options: [{'name': 'stretch', 'method': <f...

Changing the saved data type should not affect any corrections applied. The general data flow is: read -> resample -> corrections -> composite (ex. RGB) -> enhance/scale to fit "dtype" -> save to disk Resampling may move after corrections or after composites depending what is being done. C...

Hi there, You have two good options from what I can see: 1. Use the `--dtype float32` flag and the `--no-enhance` flag when generating geotiffs to produce floating point geotiffs with the real observed values. You should then be able to load these in to other programming languages as long as they su...

Hi Nik, Is the error message you are getting: pkg_resources.DistributionNotFound: The 'GDAL==3.0.2' distribution was not found and is required by the application To make direct calls to "gdal_merge.py" you'll need to "source" the Polar2Grid environment by doing: source $POLAR2GRI...