[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #DWG-532724]: NetCDF files with multiple vertical coordinate systems in IDV

> Yuan,
> Thank you for the response.  I am hoping to get some more answers about the
> options you have proposed.  I don't believe we will be recreating these
> files so modification sounds like the best option or finding another
> software package to display this information.
> 
> - How would you go about modifying this file with ncml?
> - What errors need to be corrected to get IDV to read this?
> - Is there another suggested software package to visualize these data?
> 
> Thank you for your reply.
> 
> Bryan
> 

In general, all WRF nc files are not CF complaint. The trick is in the NetCDF 
Java library that does some additional work to make it better CF shaped.

So, if you compare this file with others, I noticed missing variable ZNW and 
ZNU, these two are used to create the GeoZ coordinates. After carefully check, 
I don't think
the ncml is able to change the file. You can stop by my office if you need 
additional info.


Yuan

> address@hidden> wrote:
> 
> > > I have a netCDF dataset generated from WRF that I am trying to plot in
> > IDV,
> > > but I am struggling with a few things.
> > >
> > > - The netCDF files have multiple vertical coordinate systems in one
> > > file, and it seems that IDV doesn't know how to deal with that.  I can
> > run
> > > a "ncdump -h" on the files and see that there are variables that aren't
> > > plottable from the field selector, but definitely present in the netCDF
> > > files.  Is there a way to modify the IDV or the netCDF file to help it
> > > understand the other coordinate systems?
> >
> > Hi Bryan,
> >
> > I briefly checked the file from your drive, and I hate to say this is a
> > very
> > badly formatted netCDF file. So many error in the attributes and
> > coordinates, this
> > is why you can not see some of the fields in the field selector.
> >
> > You have three options here: 1) recreate the file with better information.
> > 2) using
> > ncml to modify the file, 3) convert the file to other unstagger format. It
> > is very inefficient
> > to let the IDV do the unstagger process.
> >
> >
> > > - The coordinates I currently have are eta coordinates (native WRF
> > > coordinates from the output I have) and then pressure
> > > coordinates have been
> > > added (linked file; below signature).  I want to be able to plot the
> > > pressure coordinates variables as well.  The pressure coordinates are
> > > listed as "vlevs" in the netCDF file.  I do have netCDF commands
> > > available
> > > from a terminal if that is necessary.
> > > - I don't know how much difference it makes, but I also have another
> > > file with theta coordinates and yet another with thetaE coordinates as
> > > well.  I will need to work those out some time soon too.
> > > - Also, when I try to aggregate these netCDF files over time with IDV,
> > > it doesn't work when I use one of the selection options (aggregated WRF
> > > netCDF files by Time) but the other works (aggregate Grids by Time).  Is
> > > this a bug, or is the netCDF file I am using non-standard for WRF output?
> >
> > This is not a standard WRF output, this is why aggregation not working.
> >
> >
> > Yuan
> > >
> > > Any thoughts on how to make IDV take these files in?  If you would prefer
> > > to have a meeting about this to see what I have and what happens, I am
> > more
> > > than happy to do that, just set up a time that works out for us in
> > > GCalendar.
> > >
> > > Thanks for any insights.
> > > Bryan
> > > ?
> > > wrfout_d01_18_12_2012_18.00.00_pres
> > > <https://drive.google.com/a/ucar.edu/file/d/
> > 0BwAYX88KH9wDUVFiVWJERE9SeGc/view?usp=drive_web>
> > > ?
> > >
> > >
> > > --
> > > Bryan Guarente
> > > Instructional Designer/Meteorologist
> > > The COMET Program
> > > Boulder, CO
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: DWG-532724
> > Department: Support IDV
> > Priority: Normal
> > 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.
> >
> >
> >
> 
> 
> --
> Bryan Guarente
> Instructional Designer/Meteorologist
> The COMET Program
> Boulder, CO
> 
> 


Ticket Details
===================
Ticket ID: DWG-532724
Department: Support IDV
Priority: Normal
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.