Carl

After starting RPI-TIG I get this message/ error. Running on Pi4 with goestools running any thoughts? @elafargue elafargue Starting TIG stack in the background ERROR: Couldn't connect to Docker daemon...

> This should give you a A to Z guide: https://github.com/elafargue/rpi-tig > The setup includes provisioning files for goestools Is this assuming Docker is already installed on the pi?

Quick json file addition allows it to work, though your imagery has extra black space surrounding the earth and will have to have cropping adjusted to the json as well...

What software are you decoding with? I noticed some use the prefix FY_2x while the file you sent has FY-2x_

appears that the issue may be on the https://server7.sky-map.org site after all, not having an SSL certificate. Short-term fix? Change your browser settings on your local browser, in this case,...

@pietern I sent you an email on the Himawari 9 update on 11/28/22 The HRIT Manager at NOAA had some questions about the new product ID for Himawari 9 Carl

The change to the goes-proc.conf works just fine and renames all Himawari products to the new satellite name. Himawari-9 ``` # Images relayed from Himawari-9 After Dec 13th 2022. [[handler]]...

I'll just chime in: the output file structure by channel rather than by Full Disk, Meso 1 Meso 2 like this sure would make my Sanchez scripts easier to run...

 Yes, you need to add GOES 18 paths and imagery to your exiting configs. ``` [paths] GOES16 = E:/Satellite Imagery GOES16Arch = H:/GOES_16_2020_2021_2022 GOES17 = E:/Satellite Imagery GOESWEST GOES18...

Also note that my I config.ini has extra settings that you probably do not have, I am using Vitality GOES for other imagery as well Carl usradioguy.om