-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add Gridded VIIRS from the NOAA AWS bucket and more #164
base: develop
Are you sure you want to change the base?
Add Gridded VIIRS from the NOAA AWS bucket and more #164
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you run the pre-commit hooks?
How long does it take to get a small amount of data (for test)?
just a few seconds at most |
Not quite sure how to do that. Can you provide a little instruction? |
I added back in the NRT data. Seems the AWS server didn't have a the latest data from the past 3 years. in the NRT data we don't have the 0.05 data but we do have the 0.1 and 0.25 degree data. |
|
Sweet, do you want a write a test? I can give it a go if not. |
Thanks! Added it and got these rolling. Seems the tests are failing but in unrelated spots where the code was changed |
since sat_name doesn't get set
as long as have at least one
since nothing to return, unlike mfdataset, where we still have something as long as there is at least one file that does exist
Current NDVI failure seems to be an issue decoding the times in current xarray (works in my local older version) pydata/xarray#8957 TIMEOFDAY variable is the offender. |
ds.TIMEOFDAY <xarray.DataArray 'TIMEOFDAY' (time: 1, latitude: 3600, longitude: 7200)> [25920000 values with dtype=datetime64[ns]] Coordinates: * latitude (latitude) float32 89.97 89.93 89.88 ... -89.88 -89.93 -89.97 * longitude (longitude) float32 -180.0 -179.9 -179.9 ... 179.9 179.9 180.0 * time (time) datetime64[ns] 2023-01-01 Attributes: scale_factor: 0.01 add_offset: 0.0 long_name: Time since Start of Data Day valid_range: [ 0 2399] _FillValue: -9999 grid_mapping: crs
@bbakernoaa besides the question of whether the module names need to have |
sure where you like me to add these? |
It could be in module docstring at the top (probably best), or in the docstring of the function that gets the data, or some combination. Or send me or point me to the relevant info and I can put it in. |
Added a new function to stream data from AWS from the noaa-jpss bucket into xarray for monetio. This should be useful for satellite comparisons.
It can handle both SNPP and NOAA20 satellites as well as varying resolutions (0.05, 0.1, 0.25 degree) and different time aggregations that are preprocessed by NESDIS (daily, weekly, monthly).
Data availability is from 2012 -> current.
to use:
@angehung5