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.
Robb, I found a small bug in the syn2nc decoder that affects the nc filename and nominal time that gets generated for each report. The problem is related to the decoding of the "obs time" group(9hhmm) that a few reports have. What happens is that once a report that has one of these groups is found, the $mm (minutes) part gets used for the rest of the life of the decoder until the next report with one of these groups changes it. This causes many of the reports to get the wrong time (hour) and filename. $mm is used in theTime() to determine the nominal report time and filename. The way to fix this would be to undefine the value of $mm after (or before) each report. I did that, and went a bit further to force all reports into the hourly file/time found in the WMO header or hour part of the "AAXX ddhhw" line. In other words, if a site reports a 9hhmm group, it still saves the time_obs value, but uses the bulletin hour (with minutes=0) for setting the nominal time and getting the filename. In general I think it's better to group the reports this way, you get much fewer "stragglers" in files that are an hour or two off. And since you have time_obs for those that report it, your app can always calculate the difference of time_obs and time_nominal to see if it is large. Let me know if you want me to send the changes... -jim -- Jim Cowie Software Engineer WITI Corporation address@hidden 3300 Mitchell Lane Boulder, CO 80301 (303) 497-8584