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.
Stonie, The CAT_ types are all in the $GEMPAK/source/programs/gui/nmap2 routines. The time line for categories in nmap_tmln.c. My assumption is that you would be better in creating CAT_RBK and specific datatype.tbl entries for each type of product. The CAT_VGF has the additional capability of the user Browse dirctory, and so would likely be convoluted to add times as well. Steve Chiswell >From: Stonie Cooper <address@hidden> >Organization: Planetary Data, Incorporated >Keywords: 200403231923.i2NJNvrV023504 >If I were to make CAT_VGF time sync capable, or create a new datatype >(CAT_RBK?) . . . is that a huge undertaking? Should I just ignore this >project? If it's not that big of deal, give me a pointer in the right >direction, and I'll take a crack at it. > >On Tuesday 23 March 2004 19:13, Unidata Support wrote: >> Stonie, >> >> The CAT_VGF datatype does not have any time synchronization at this >> point. There isn't a way to vary the VGF per frame- eg the VGF's >> selected will display on all frames. >> >> Steve Chiswell >> Unidata User Support >> >> >From: Stonie Cooper <address@hidden> >> >Organization: Planetary Data, Incorporated >> >Keywords: 200403231830.i2NIUFrV000371 >> > >> >Steve, >> > >> >I've been beating around an issue, and before I waste too much more time, >> > I wanted to run by you what I was looking to do. >> > >> >With the CCB preserved from our NRS, we shoot the RedBook through the >> > redbook to vgf decoder, and store in directories for each product. The >> > resulting file ends up in a YYYYMMDD_HHNN.vgf naming format. For >> > example, if I do an ls on $OBS/redbook/obs_snow_cover/, I see: >> > >> >20040312_1200.vgf >> >20040313_1200.vgf >> >20040314_1200.vgf >> >20040315_1200.vgf >> >20040316_1200.vgf >> >20040317_1200.vgf >> >20040318_1200.vgf >> >20040319_1200.vgf >> >20040320_1200.vgf >> >20040321_1200.vgf >> >20040322_1200.vgf >> >20040323_1200.vgf >> > >> >And that's pretty much how the other 191 products are stored. >> > >> >I was trying to set the datatype.tbl up so that each VGF would be a data >> > type where the date/time would have meaning . . . such that all the files >> > in a VGF product directory would represent a tick on an NMAP2 timeline, >> > can be loaded as a loop, and would get properly updated when layered on >> > an image product. >> > >> >Off and on since 5.6.c.1, I've been playing with this . . . albeit not >> >seriously . . . but I would like to complete this little task. >> > >> >Am I out to lunch? >> >-- >> >Stonie R. Cooper >> >Planetary Data, Incorporated >> >(402) 727-6599 >> >> -- >> *************************************************************************** >>* < Unidata User Support UCAR Unidata >> Program < (303)497-8643 >> P.O. Box 3000 < address@hidden >> --------------------------------------------------------------------------- >>- < Unidata WWW Service >> --------------------------------------------------------------------------- >>- < NOTE: All email exchanges with Unidata User Support are recorded in the >> Unidata inquiry tracking system and then made publically 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. > >-- >Stonie R. Cooper >Planetary Data, Incorporated >(402) 727-6599 > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.