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.
>From: Ryan May <address@hidden> >Organization: University of Oklahoma >Keywords: 200502101535.j1AFZ3v2029303 IDV netcdf sweep files Hi Ryan- >Setting the default data type unfortunately makes the file disappear >from the list unless I label it properly (which i deduced from the >code): ncswp.test.nc Actually, you just need to set the Data Source type (at top of chooser) to Netcdf Sweep files instead of the file filter. That will allow you to see all files without having to name accordingly. At this point, there is no netCDF "sniffer" to determine the type of file. We hope to be able to do this with the new netCDF work. >This allowed me to get it to open as radar file and exercise the radar >IO code paths, which led me to my next problem. It seems that the radar >netcdf IO code assumes that the moment fields are stored as short >values, since my original float values caused an exception at that point >and writing my data out as scaled shorts solved the problem. Now that >I've scaled the data, I can't seem to get the IDV to unscale it >properly. Also, it doesn't seem to notice what I have set as the >_FillValue to properly identify missing data. The code is pretty brain-dead as you have found. It does not support packed variables, nor does it account for missing data. I won't be able to look at a solution for this until next week, though. >I would be very interested in reviewing this in the hopes of making the >IDV a tool I can really use. Okay, I've cc'd Doug Lindholm who will contact you with the particulars. Don Murray 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.