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.
Hi Randy- > I talked with folks working on the KOUN dual pole. One person, John > Krause, said the files are pretty much a home-brew. John suggested I > use NCDump. He said they have no interest in developing a convention yet. Thanks for following up on this. That's the way many people write netCDF - home brew with no convention and then they wonder why other programs can't read them in. The only way then to look at the data is generically because there is no standard metadata for a program to use (like where is this located?). It's better to consider these issues from the start rather than wait until you have a huge archive of randomly formatted files. It's taken the modelling community a long time to realize the importance of standards and now most (except WRF) conform to the CF conventions. This has made huge gains in collaborative research and data sharing. If you want to look at the files generically in the IDV, then you can set the Data Type for the File chooser to be VisAD Form files (end of the list. (you'll have to gunzip them first). Then pick the variable you want in the Field Selector and use the Omni Control. You can use the Mappings buttons to map whatever variable you want to the different axes/display types. (I used Azimuth->Cyl Az, Gate -> CylRad, Kdp->RGB) But, the display will not be geolocated and you will not be able to overlay any other types of data (except the similar files). Don Murray Ticket Details =================== Ticket ID: RGX-739687 Department: Support IDV Priority: Normal Status: Open