-
Notifications
You must be signed in to change notification settings - Fork 62
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
Proposed Recipes for kerchunking National Water Model gridded 1km output #224
Comments
@sharkinsspatial did I capture this correctly? |
Looks good @rsignell-usgs 👍 I'll link this back to the main list in #208 |
I have a series of notebooks I've used to kerchunk the 1km gridded data:
|
Okay, this is embarrassing: I thought when I looked a few months ago on AWS open data these 1km NWM NetCDF files had not been converted to Zarr. But I just looked again, and the Zarr datasets are there! Was this just done recently perhaps? Why isn't there an egg-on-face emoticon? 😕 This dataset was useful for testing out big kerchunk use cases, but it will be more compelling to find a different one that hasn't already been zarrified, so closing this. |
Dataset Name
The National Water Model CONUS Retrospective 1km gridded output, LDASOUT variables
Dataset URL
https://registry.opendata.aws/nwm-archive/
Description
The NOAA National Water Model Retrospective dataset contains input and output from multi-decade CONUS retrospective simulations. These simulations used meteorological input fields from meteorological retrospective datasets.
License
Unknown
Data Format
NetCDF
Data Format (other)
No response
Access protocol
S3
Source File Organization
One time step per file. 3 hourly output. 1 spatial chunk for entire CONUS.
Example URLs
Authorization
No; data are fully public
Transformation / Processing
Files should be concatenated along the time dimension
Target Format
Reference Filesystem (Kerchunk)
Comments
I have a working notebook to kerchunk these files using Dask:
https://nbviewer.org/gist/3c178532adffef5201af3fb0a970a05a
This is part of the AWS ARCO project: #208
The text was updated successfully, but these errors were encountered: