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.
>From: Frank Colby <address@hidden> >Organization: . >Keywords: 200002141831.LAA22323 >Steve and/or Robb, > >I'm trying to run the dcnldn decoder, and not having much luck. I think >the problem is something I might be able to solve, but I need help. I >am receiving the nldn data, and putting it into files without any >problems, although I don't know what the format of the .nldn files is, >other than it's something I can't read with more. I would like to >decode the data into gempak files, and have put the decoder statement >copied from the ldm web page, suitably modified for our file structure. >I did get an entry into our log file, but all it indicates is that the >decoder started, found no data, and quit. That was more than 1 hour >ago. > >What I don't understand is what the various switches do in the decoder >action. I have tried dcnldn -h, but this doesn't give me anything, and >I don't seem to have any man pages for it. I tried searching the >searchable indices on the web, but can't find anything there either. I >found the help files, but the switch details aren't shown there either. >What am I missing? > >Frank > > Frank, On Jan 29, SUNY-Albany changed the naming of the NLDN products so the NLDN entry on the tutorial was wrong. I just updated that. Previously they were named YYJJJHHMMSS, and now are CCYYJJJHHMMSS. The file entry can just be: NLDN ^.* dcnldn....yadda-yadda Sorry about that... The decoder will create Gempak ship format files that can be viewed with ltglist, ltgmap or garp as I outlined last week. Steve Chiswell