This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Bob: Generally, the GFS-80km has this pattern of time intervals for total precip: 6.000000 (0.000000,6.000000) = 6.000000 12.000000 (6.000000,12.000000) = 6.000000 18.000000 (12.000000,18.000000) = 6.000000 24.000000 (18.000000,24.000000) = 6.000000 30.000000 (24.000000,30.000000) = 6.000000 36.000000 (30.000000,36.000000) = 6.000000 42.000000 (36.000000,42.000000) = 6.000000 48.000000 (42.000000,48.000000) = 6.000000 54.000000 (48.000000,54.000000) = 6.000000 60.000000 (54.000000,60.000000) = 6.000000 66.000000 (60.000000,66.000000) = 6.000000 72.000000 (66.000000,72.000000) = 6.000000 78.000000 (72.000000,78.000000) = 6.000000 84.000000 (78.000000,84.000000) = 6.000000 90.000000 (84.000000,90.000000) = 6.000000 96.000000 (90.000000,96.000000) = 6.000000 102.000000 (96.000000,102.000000) = 6.000000 108.000000 (102.000000,108.000000) = 6.000000 114.000000 (108.000000,114.000000) = 6.000000 120.000000 (114.000000,120.000000) = 6.000000 126.000000 (120.000000,126.000000) = 6.000000 132.000000 (126.000000,132.000000) = 6.000000 138.000000 (132.000000,138.000000) = 6.000000 144.000000 (138.000000,144.000000) = 6.000000 150.000000 (144.000000,150.000000) = 6.000000 156.000000 (150.000000,156.000000) = 6.000000 162.000000 (156.000000,162.000000) = 6.000000 168.000000 (162.000000,168.000000) = 6.000000 174.000000 (168.000000,174.000000) = 6.000000 180.000000 (174.000000,180.000000) = 6.000000 192.000000 (180.000000,192.000000) = 12.000000 204.000000 (192.000000,204.000000) = 12.000000 216.000000 (204.000000,216.000000) = 12.000000 228.000000 (216.000000,228.000000) = 12.000000 240.000000 (228.000000,240.000000) = 12.000000 The TDS changes the name of the variable to reflect what the time interval length is. Since we have mixed 6 and 12 hour intervals, the name of the variable is "Total_precipitation_surface_Mixed_intervals_Accumulation". Im not sure why you might see Total_precipitation_surface_6_Hour_Accumulation, except perhaps the file has not finished updating (?), and the 12-hour forecasts come in late ?? Could you notify me as soon as you see such a thing? Also, i was wondering if you realized that the time intervals are mixed (6 and 12), and if it matters to you? John > Hello - > > I was looking at > http://www.unidata.ucar.edu/georesources/threddsRtModels.xml and I have > a question about the Total Precipitation field. It seems that at times > the most recent GFS 80km CONUS uses a field name of > 'Total_precipitation_surface_Mixed_intervals_Accumulation', while other > times, it uses 'Total_precipitation_surface_6_Hour_Accumulation'. > > The majority of the time, it seems like the field is > 'Total_precipitation_surface_Mixed_intervals_Accumulation'. Looking > back at older model runs, this is the field name that is used. This > appears to be the only field that changes names (2D or 3D). Is there a > reason why this field name changes? I have a McIDAS-V bundle that tries > loading in this field, and occasionally it fails when the field name is > 'Total_precipitation_surface_6_Hour_Accumulation', because my bundle is > looking for 'Total_precipitation_surface_Mixed_intervals_Accumulation'. > > Thanks - > Bob > > Ticket Details =================== Ticket ID: ULI-448464 Department: Support THREDDS Priority: Normal Status: Open