Others may not even be aware that they are running into bandwidth constraints until too late--when they get the "429 Too Many Requests" error after their IP address has been blocked for overuse of RDA resources.
We want to help you get the data you need to do your work. But you will save time and bandwidth if you keep a few simple points in mind.
WRF does the dynamical downscaling for you. If you don't see any significant difference in WRF forecast quality with between the 0.25 and 1.0 degree GRIB input files, then you need only 1/16th the bandwidth! But, if your domain includes complex terrain, you will likely see better results with 0.25 degree input.
Use nested domains to downscale iteratively to the desired resolution. See the WRF Tutorial Nesting slide deck. You can use 1.0 degree data to initiate an 81 km 'parent' domain with 27 km and 9 km 'child' and 'grandchild' nested domains. You might use 0.25 degree data to initialize 27, 9, 3 km domains and nests.
|WRF nested grids.|
|Specified and relaxation zones (yellow/blue) of 5 WRF parent domain (green) grid points.|
(50*60)/(180*360) = 0.0463
Downloading only the subset of the global grid that you actually need saves you more than 95% of the bandwidth of transferring the entire GRIB file! You and your colleagues sharing the same IP address will be done 95% faster, reducing the number of concurrent data transfers on your local network.
[Aside: Check your download manager to request no more than 10 concurrent downloads at a time per user. If you don't, you will get the "429 Too Many Requests" error.]
Use the 'Get a Subset' option. As we say in Colorado, work faster and ski more!
OPeNDAP protocol. See these NCDC OPeNDAP URL syntax examples for formulating your own scripted requests.