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.
Dave, The humidity variable has its dimensions in wrong order. In particular, station should before time. Currently, we have float humidity(time=90, station=1); but it should be float humidity(station=1, time=90); You may wish to inspect your data in toolsUI. Open the data in the feature type tab and make sure all the expected variables appear in the table at the bottom. Let us know if you have trouble. Best, Christian and Julien > Thanks for letting us know. -Dave > > address@hidden> wrote: > > > Dave, > > > > Actually, a solution here may not be completely immediate, and we will have > > to work with THREDDS/ncJava to get to the bottom of this. > > > > Stay tuned. > > > > Best, > > > > Unidata IDV Support > > > > > OK, that sounds good. Thanks for following up Christian. We'll see what > > the > > > IDV folks have to suggest. Sounds like it should be something small. > > > > > > -Dave > > > > > > address@hidden> wrote: > > > > > > > Hi Dave, > > > > > > > > The good news: > > > > > > > > Your file is fully CF-compliant. CF is the most widely-adopted and > > > > future-proof convention for storing NetCDF data, and is definitely the > > > > format you want going forward. > > > > > > > > Incidentally, you can verify that a point NetCDF file is CF-compliant > > > > using ToolsUI [1]. Launch ToolsUI and open the file in the > > > > FeatureTypes->PointFeature tab. If that succeeds, click the "Dataset > > Info" > > > > button at the top-right. Near the top of the window that pops up, you > > > > should see the line: > > > > _CoordSysBuilder = "ucar.nc2.dataset.conv.CF1Convention" > > > > > > > > The bad news: > > > > > > > > It appears that IDV cannot yet read this particular point data > > > > representation. I'm going to throw this issue back over the fence to > > the > > > > IDV team--perhaps they can be of more assistance. Apologies for the > > > > prolonged back-and-forth. > > > > > > > > Cheers, > > > > Christian > > > > > > > > [1] ftp://ftp.unidata.ucar.edu/pub/netcdf-java/v4.5/toolsUI-4.5.jar > > > > > > > > > > > > Ticket Details > > > > =================== > > > > Ticket ID: WON-355400 > > > > Department: Support IDV > > > > Priority: Normal > > > > Status: Open > > > > > > > > > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: WON-355400 > > Department: Support IDV > > Priority: Normal > > Status: Open > > > > > > Ticket Details =================== Ticket ID: WON-355400 Department: Support IDV Priority: Normal Status: Open