NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Thredds Folks, I have a set of GRIB1 files that contain two cycles, (06 & 12 UTC) with a series of (43 +1hr) forecasts for each, merged in the same file. http://nomads.ncdc.noaa.gov/thredds/dodsC/srrsgrb/200810/20081003/srrsgrb_023_20081003_0000_000.grb.html http://nomads.ncdc.noaa.gov/thredds/fileServer/srrsgrb/200810/20081003/srrsgrb_023_20081003_0000_000.grb It seems like both /dodsC and /ncServer cannot detect the existence of the two cycles and only offer 1 time axis (0:1:48) ~ Is there a way, other than splitting apart the file into two on disk, to allow specification of both cycle & forecast time axis from these services? I realize the OpenDAP constraint consists of [t][z][y][x] is this the unavoidable limitation? Same thing with a GRIB2 convert. These files are not TDS aggregations. Running TDS v.3.16.41 Any advice would be appreciated. -- Dan Swank <dan.swank@xxxxxxxx> NOMADS Project: Software & Data Management Contractor - STG, Incorporated Veach-Baley Federal Building 151 Patton Avenue Asheville, NC 28801-5001 Phone: 828-271-4007
thredds archives: