pietern
This is a nice interactive one: http://rammb-slider.cira.colostate.edu/?sat=goes-16.
There is also an S3 bucket where you can find all data as soon as it is available: https://registry.opendata.aws/noaa-goes/.
But the fun part is receiving it in your backyard, of course ;)
1) Yes, this is DCS (Data Collection System) data. It's a very low bandwidth signal (300 or 1200 baud) that ground stations uplink to GOES on UHF. I found there are about 20k separate transmitters in some asset database I once found somewhere. Every one (or the set that's still active) transmits a tiny packet every N minutes (some every minute, others every 30 minutes). This data is also broadcast as part of the LRIT (GOES-15) and HRIT (GOES-16 and GOES-17) streams. There is no processing for this data in the goestools package yet, but you can get the originals and walk over the data. When I last looked at it, the format looked different per receiver, it is possible this is a per-vendor type of thing. Anyway, yes, you can get a copy of this data with the receiver described in the OP guide. See https://github.com/pietern/goestools/issues/11 for some more links.
2) AFAICT MODIS is a product derived from the Aqua and Terra satellites. Both are polar orbiting sats. You can look them up here https://www.wmo-sat.info/oscar/satellites/view/81 and it looks like they don't pack a "direct readout" transmitter, so you wouldn't be able to receive anything directly yourself. Compare this to the page for GOES-16 at https://www.wmo-sat.info/oscar/satellites/view/152 and you see there are a bunch of frequencies with details listed.
Next to this data, it also contains relayed images from GOES-15 (GOES-West), Himawari-8, EMWIN data, and NWS forecasts and plots.
Also beware that the guide is a little out of date:
1) the listed antenna is no longer available, but there are comparable ones for comparable or lower price, and
2) the SAWBird has been generally available for a couple of weeks.
And there's even a tiny Redis dependency (optional though) in the code to generate these results. In particular the collective communication library needs a rendezvous phase where all nodes connect to their peers. Using Redis for this is one of the options. See: https://github.com/facebookincubator/gloo/tree/master/gloo/r...