-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud cover from NOAA GOES-16 example #60
Conversation
interesting to see the cloud cover animation. Immediately I googled where the cloudiest places in the US are. Are the data provided on the daily scale? |
Oh good question! I was using
|
The main point of putting this quick remake example together was to test out how cloud cover would look on top of the river conditions visualization. Since this is just a prototype, I did not want to get bogged down in some of the challenges with building that pipeline (it's old and could use a makeover). As such, I just made some minor tweaks to this pipeline as a temporary way to get cloud cover + the gage conditions. I am not committing these changes because it would make this pipeline not able to function independently. So instead, I am recording my steps below. The key is that the dates you are using for the cloud data will need to exist in the time frame that the last river conditions build included (I used 2020-09-01 to 2020-09-30 for this example). cloud_timelapse.mp4First, I manually ported over data from
|
I also just tried a cloud moisture version (Cloud Moisture Imagery, product code = cloud_moisture_timelapse.mp4 |
I wanted to test out what cloud cover may look like with the river conditions visualization (request from Robert Mason & Athena Clark). I thought it would be best to test outside of that repo first because it is super complex and saw an opportunity to create a working example that could be leveraged to pull NOAA GOES data in the future.
cloud_timelapse.mp4
To build this cloud cover animation, you need to be on VPN (even though the NOAA AWS bucket is public,
aws.s3
R package requires credentials to work and our creds only work on VPN). Then run the following: