SatDump does not separate images by channel - they're all in the same "Full Disk", "Mesoscale 1", etc directory. This PR allows Vitality GOES users to add a "filter" key to each image defined in abi.ini, meso.ini, and l2.ini - and therefore, make it compatible with a SatDump data source.
The filter key should match a short string that exists in the filename of a specific channel. For example, SatDump put 2 in the filename of Channel 2 images from the GOES satellites, so set filter = "_2_" in abi.ini to properly select these images. Example configs for using Vitality GOES can be found under /extra/config-satdump of this branch.
Note: This PR will not be merged until https://github.com/altillimity/SatDump/issues/170 is implemented. This PR will make Vitality GOES work with SatDump as-is, but I want to give the best guidance in my documentation for future SatDump compatibility. Depending on how SatDump implements the suggestion, this branch may never be merged into Vitality GOES
I'm impatient, and it makes SatDump work with Vitality GOES now. No matter how SatDump changes, this pull will likely still be beneficial.
The "standard" config for goesproc does not split the Himawari channels out into their own subdirectories, which would break Vitality GOES as-is. This pull fixes the issue
Additional documentation and examples will come before the next release
SatDump does not separate images by channel - they're all in the same "Full Disk", "Mesoscale 1", etc directory. This PR allows Vitality GOES users to add a "filter" key to each image defined in abi.ini, meso.ini, and l2.ini - and therefore, make it compatible with a SatDump data source.
The filter key should match a short string that exists in the filename of a specific channel. For example, SatDump put 2 in the filename of Channel 2 images from the GOES satellites, so set
filter = "_2_"
in abi.ini to properly select these images. Example configs for using Vitality GOES can be found under /extra/config-satdump of this branch.Note: This PR will not be merged until https://github.com/altillimity/SatDump/issues/170 is implemented. This PR will make Vitality GOES work with SatDump as-is, but I want to give the best guidance in my documentation for future SatDump compatibility. Depending on how SatDump implements the suggestion, this branch may never be merged into Vitality GOES