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.
Hello, Steve: This is great news. We will certainly have the adp routines in fine form by the beginning of the month. I'll be away from the 13th-17th of August, which lines up in an unfortunate way with your last week before what I assume is time off. However, I'm planning to keep Ruth Platner in the loop on this, and even if there are loose ends to tie up after you return I'm confident we will be able to make byte fly very soon. As we develop this I'll try, and I'm sure you will guide/suggest/etc. to mkae the resulting sotware maximally useful to other possible users. Heck, even if it's Fortran, it can be helpful, right? So, even though I'm sure you'll be mucho-busy for the next three weeks, I'll let you know every once in a while where we stand with the "adp stubs." Thanks for your help. John > ... > After that, I am fairly free until Aug 18-26 when I'll be out of town. > > I can probably help you most readily with the steps of programming > to create the GEMPAK file and write out the data etc. once you > have your adp stubs acessing the input data. > > The primary output to a GEMPAK file will be the fortran REAL data > array. GEMPAK is well versed with routines to query the data set to see > if a station has reported data at a time, so that you can merge > your archived data into the mix. >