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.
Pavel, Please see: http://www.unidata.ucar.edu/packages/gempak/tutorial/pqact/decoders.tbl and http://www.unidata.ucar.edu/packages/gempak/examples/examples.html These should be a great help to you.. -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On 10 Jan 2003, Pavel Byles wrote: > Jeff, > how about the HDS in UNIDATA. From that I should be able to figure out > how to store the others. > > Pavel > > On Fri, 2003-01-10 at 17:51, Jeff Weber wrote: > > Pavel, > > > > The UNIDATA feed consists of many feedtypes. > > > > See: > > > > http://my.unidata.ucar.edu/content/software/ldm/feedtypes/index.html > > > > So there is no single action for the UNIDATA feed. > > > > We do not post these actions because everyone does things differently, > > some products are not wanted by all, so they act upon the feed > > differently. Also, I am not certain which application you are planning on > > using to utilize this data, you have mentioned both MCIDAS and GEMPAK, so > > that would create different actions as well. > > > > I am more than happy to give you any and all are actions, but it would be > > in your best interest to know what you want first, or if disc space is not > > an issue at all, or is latencies, you can act on everything...but I > > suspect you are probably not using global metars, all the models, etc on a > > daily basis..but I do not know. > > > > If you can tell me what you are hoping to ingest/decode/file I can send > > the appropriate entries... > > > > Cheers, > > > > -Jeff > > ____________________________ _____________________ > > Jeff Weber address@hidden > > Unidata Support PH:303-497-8676 > > COMET Case Study Library FX:303-497-8690 > > University Corp for Atmospheric Research 3300 Mitchell Ln > > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > > ________________________________________ ______________________ > > > > On 10 Jan 2003, Pavel Byles wrote: > > > > > Yes, running the notifyme command shows that I am allowed on cornell's > > > atm.geo.nsf.gov feed for UNIDATA. > > > > > > All I need is the entry for the pqact.conf. > > > > > > Thankyou > > > Pavel Byles > > > > > > On Thu, 2003-01-09 at 14:33, Jeff Weber wrote: > > > > Pavel, > > > > > > > > Execute from ldm machine: > > > > > > > > notifyme -vl - -h atm.geo.nsf.gov -f UNIDATA -o 15000 > > > > > > > > and let me know what you see... > > > > > > > > This will let you know if you are "allowed" that feed group. > > > > > > > > If you see data scrolling, then the allow is valid. > > > > > > > > To see the feedtypes and aliased "feedgroups" go to: > > > > > > > > http://my.unidata.ucar.edu/content/software/ldm/feedtypes/index.html > > > > > > > > Thank you, > > > > > > > > -Jeff > > > > ____________________________ _____________________ > > > > Jeff Weber address@hidden > > > > Unidata Support PH:303-497-8676 > > > > COMET Case Study Library FX:303-497-8690 > > > > University Corp for Atmospheric Research 3300 Mitchell Ln > > > > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > > > > ________________________________________ ______________________ > > > > > > > > On Thu, 9 Jan 2003, Byles, Pavel O wrote: > > > > > > > > > Jeff, > > > > > we are recieving data from atm.geo.nsf.gov. Should I change it back to > > > > > snow.nrcc.cornell.edu? > > > > > We are getting both NEXRAD and UNIDATA according to the ldmd.conf. > > > > > But I > > > > > don't see where the UNIDATA data is coming in. > > > > > Is that because there is no allow for us on the atm.geo.nsf.gov > > > > > server or is > > > > > this incorrect: > > > > > > > > > > request UNIDATA ".*" atm.geo.nsf.gov > > > > > > > > > > Pavel > > > > > > > > > > > > > > > > >