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.
Bryan, I made some fixes to the perl decoders that should solve all the problems. Would you want to test it on your machine? The modified decoders are in the UPC anonymous ftp decoders directory. ascii2nc buoy2nc metar2nc sao2nc syn2nc ua2nc ldmConnect The reason you might have been missing some of the reports is that they were put into the wrong file. Let me know how this works out. Robb... On Mon, 31 Jan 2000, Bryan G. White wrote: > Rob, > > I've got a Y2k problem and a I don't know what problem with metar2nc > > 1) Around 0z every day I get files created with "000" as the year.... > ie. 000013123_metar.nc. Must be the dreaded perl "2000 = 000" bug I've > been squashing in some of my programs. It only does this after 0z with > data that has a time stamp before ~2345z. > > I think the problem is around line #1558 with formating of the year > variable. > > 2) I can't get the ~23:45-23:59 hour obs to decode. It's vanishing in thin > air. I don't know what is going on. I manually decode a file that > has a 23:50 ob, but it isn't in the *metar_nc file. The file has obs from > before 0z and after 0z. It does decode the after 0z obs. > > It does however show up int the rawmetars.*.nc file. > > > Bryan > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================