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.
shengting, > We are receiving a lot of data, but not in a format human readable. I recall > that in the installation instruction, we are supposed to put such lines: > > export PATH=$HOME/decoders:$HOME/util:$HOME/bin:$PATH > export MANPATH=$HOME/share/man:SysManPath > > in the .bash_profile. Does this have anything to do with that? Most of the data-products on the Unidata IDD are in binary format and are usually processed by an analysis and display package (e.g., McIDAS, GEMPAK) into a form that the analysis and display package can use. Some of the products, however, are textual (e.g., the "IDS|DDPLUS" feed). We supply the McIDAS and GEMPAK packages on our website, but which package you use is entirely up to you. The packages we supply have instructions on how to interface it with the LDM. > But I don't see any files/directories with names "decoders" and "util" in the > $HOME directory. Could you advise us on that? If you wish, I can put you in touch with someone who can advise you on the various analysis and display packages. Regards, Steve Emmerson Ticket Details =================== Ticket ID: CMI-630638 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.