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: John Meyers <address@hidden> >Organization: Boston Museum of Science >Keywords: 200501312237.j0VMb4v2024457 IDV LAPS Hi John- >Thank you! I made the changes to the Nx/Ny variables and it loaded w/o >error but still did not plot. Then I modified it to output as a 2D >variable, and it worked like a charm! Still, I think IDV should be able >to interpret a 3D variable with one z level as a 2D variable, but I am >quite happy to modify the data to IDV's requirements. One day I will >put together a HOWTO on hacking LAPS to be Unidata friendly after I get >it all set myself. Thanks again. I'm working on a solution so that 2D vars at one level are plotted correctly. At one time, we did plot them at the surface, but then one of our users wanted to have the data plotted at the correct altitude (actually depth since it was an oceanographic data set) and when we made that change, I guess the other broke. In your case, you were specifying that they were at 1000 mb which they really aren't so they would plot incorrectly (if we could get them to plot). With 2D variables, you could also drape them over topography. We are working on adding better support from high resolution topography datasets. I've already made a change so they will be categorized as 2D variables but the plotting is still a problem. Don 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.