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

[IDV #LEH-376488]: 4D import



it turns out the IDV is not yet supporting an ensemble dimension. we will get 
back to you when we know more about when that might be supported.

> No problem!  I've added the AxisType attribute to the "model" dimension and 
> the global attribute, Conventions, but that didn't quite seem to fix the 
> issue.  I'll look through the CF conventions some more and see what I can 
> find.  The "Model" dimension is representative of the GCM scenario that 
> produced the data: 1-112 models in the CMIP3 climate projection dataset.
> 
> -----Original Message-----
> From: Unidata netCDF Java Support [mailto:address@hidden
> Sent: Friday, March 12, 2010 1:15 PM
> To: Traynham, Lee/AUS
> Cc: address@hidden
> Subject: [IDV #LEH-376488]: 4D import
> 
> sorry, i didnt realize you submitted 2 files. the other file's problem is the 
> model dimension, which the IDV doesnt recognize. Is this an ensemble run? 
> Assuming yes, add :_AxisType = "Ensemble" attribute to the model coordinate 
> variable.
> 
> also you need to add a global attribute :Conventions = "CF-1.4" to be CF 
> conformant.
> 
> > Dear support,
> >
> > The file that I inquired about *does* have a time coordinate variable 
> > (please see the attached zip file).  I had also included a sample netCDF 
> > java file created using one of the scripts from your website tutorial, 
> > because it also couldn't be imported so I could see how that would be an 
> > issue for it, but it was not the file of interest. I will double check the 
> > CF conventions again. I'm still looking for resolution on this if you could 
> > provide some insight...
> >
> > Thanks,
> >
> > Lee Traynham, EIT
> > CH2M Hill
> > 12301 Research Blvd., Bldg. 4
> > Suite 250
> > Austin, Texas 78759
> > Office: (512) 453-1980 ext. 259
> > Fax: (512) 453-4109
> >
> >
> > -----Original Message-----
> > From: Unidata netCDF Java Support [mailto:address@hidden
> > Sent: Friday, March 12, 2010 10:46 AM
> > To: Traynham, Lee/AUS
> > Subject: [IDV #LEH-376488]: 4D import
> >
> > The problem with this file is that it doesnt have a time coordinate 
> > variable.
> > In general, you should follow the CF conventions when writing a file:
> >
> > http://cf-pcmdi.llnl.gov/
> >
> > also see:
> >
> > http://www.unidata.ucar.edu/software/netcdf/docs/BestPractices.html
> >
> >
> > > Dear IDV,
> > >
> > > I am having trouble importing a 4D netCDF file into the IDV for viewing.
> > > The file has dimensions of time, lat, lon, and a model ID (int).
> > >
> > > Is it possible to view such a file in IDV?  My read through the message
> > > boards indicates that this should be doable, but I've tried to import as
> > > both a "Grid File" and as a "netCDF file" and not had success with either.
> > >
> > > I've attached a sample of the file that is of interest, as well as a 4D
> > > file created using the netCDF Java tutorial code, "Pres_temp_4D_wr.java".
> > > The files were both generated using the netCDF Java library. I am not
> > > able to load either in the IDV.
> > >
> > > Please let me know if I need to provide additional info to resolve this.
> > >
> > > Thanks for your time,
> > >
> > > Lee Traynham, EIT
> > > CH2M Hill
> > > 12301 Research Blvd., Bldg. 4
> > > Suite 250
> > > Austin, Texas 78759
> > > Office: (512) 453-1980 ext. 259
> > > Fax: (512) 453-4109
> > >
> > > [cid:address@hidden
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: LEH-376488
> > Department: Support netCDF Java
> > Priority: Normal
> > Status: Open
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: LEH-376488
> Department: Support netCDF Java
> Priority: Normal
> Status: Open
> 
> 


Ticket Details
===================
Ticket ID: LEH-376488
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.