Hi Dave- > >> (1) how to load and plot multiple COSMIC data files in one fell swoop (I > >> have a help request submitted to support-idv on that one-although I could > >> highlight a bunch of COSMIC data files from our RAMADDA server in Data > >> Choosers, Adding Source only loaded the first one on the list); > > > > If you select multiple files, you will see only one time (the nominal > > time). But if you load the data, you get the multiple times. Yuan is > > looking into showing all the times. > > I'm not sure that I follow. I can load files ("Add Source", right?) one > sounding at a time (which looks like the only way I can do it at the > moment--the problem that I'm hoping that using the RAMADDA server will > overcome), but then I have to plot them one at a time, too, and I still get > only one time per file because I can select only one data source at a time to > plot (or am I missing something?). Even though it was showing only one time for multiple files, it was really loading all times. With the latest nightly build, you should see all the times (and be able to subset them) and if there are multiple files, you'll see the DataSource name as Trajectory Soundings. > > > >> (2) read compressed (I think) AREA files acquired via the UNIWISC feed and > >> passed through the png2area decoder (the IDV won't read these, making > >> their accessibility via RAMADDA something a moot point); > > > > I'll look into this. Theoretically, you should be able to open these as > > Image Files (GINI), but it doesn't work. > > OK, thanks--being able to view this locally stored images would be a definite > boon. We're still working on this. Getting closer, but there's still some problem. > > > >> (3) figure out if, and if, how, to tell WXP to save files in NetCDF > >> format, and see if the IDV will read them (a question for Dan Vietor to > >> answer), because otherwise our METAR and syntopic and upper air point data > >> aren't very useful on RAMADDA, either. (This matters because the ADDE > >> servers of surface METAR data only make data available since 00Z of the > >> current day, which is an absurdly short time.) > > > > We still don't support the WXP format for netCDF data. > > That seems more like an issue for Dan to address. He's been reluctant to do > much about it because he doesn't perceive the NetCDF standard as being > stable. I'll ask him what he's been up to in this area. It's not finalized, but we might be able to fudge the existing format. > > > We are working on alternatives to ADDE, but it won't make the 2.8 release. > > I'll be interested to hear what you're brewing up. BTW, if you use relative times for the point data with ADDE, you can go back across the date boundary. It's just that for the absolute times, we just use the current day. Don Murray Ticket Details =================== Ticket ID: ZKJ-217366 Department: Support IDV Priority: Emergency Status: Open
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.