NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
> Yuan,
> Thanks for the link; I will try to construct a file using those
> recommendations.
> Believe it or not, the old file did open and display under the older
> version of IDV.
> -Al
>
Albert,
The GEON animal track data can be loaded as Point Data in the IDV. If you
use ncml to modify this dataset and add a few attribute, this dataset can be
loaded as track data. But, on the GEON-IDV webset, this dataset is loaded as a
point data, not as a track file.
If you can reproduce the display of your dataset in the earlier version
of the IDV, please send me a support email from that IDV and include the
bundle, I will take a closer look.
Thanks,
Yuan
> On 7/29/2010 1:21 PM, Unidata netCDF Java Support wrote:
> >>> Hi again Yuan,
> >>>
> >>> I found a web page for the GEON IDV which includes other float track
> >>> examples:
> >>>
> >>> http://geon.unavco.org/unavco/IDV_datasource_track.html
> >>>
> >>> I tried their netcdf examples, and found they did not work on IDVv2.9.
> >>> For example, the following does not work:
> >>>
> >>> http://geon.unavco.org/unavco/track/IDV_sample_track_data_for_animal.nc
> >>>
> >>> Hope this new bit of evidence is helpful
> >>>
> >>> Best,
> >>> Al Hermann
> >>>
> >> Albert,
> >> The problem is that our CDM library no longer recognize this dataset as
> >> the TRAJECTORY. I transferred this support ticket to another group to fix
> >> it.
> >>
> > Albert,
> > After checking this dataset, I will have to say this dataset is in
> > very bad shape. I doubted you can open it in the earlier version IDV.
> > Three major issues here: 1) lat/lon has a lot missing values, 2) additional
> > dimension DRIFTER1_10, 3)no convention.
> > Here is some information you should reference:
> >
> > https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions
> >
> > The dataset in the GEON link can be workable after adding some attributes.
> >
> > Yuan
> >
> >> John, the sample file is under /testdata/trajectory/testfloat10.nc.
> >>
> >> Yuan
> >>
> >>> On 7/28/2010 8:52 PM, Unidata IDV Support wrote:
> >>>
> >>>>> Hi,
> >>>>> I am an oceanographer using IDV for visualizing output from the Regional
> >>>>> Ocean Modeling System (ROMS). The model has provision for float
> >>>>> tracking, with float files output in netcdf format (which I then subset
> >>>>> using tools like Ferret). These used to be readable by idv as a "track
> >>>>> file" (specifically, by version 2.7u2), but the latest version (e.g.
> >>>>> 2.9) will not read them as a track file, or any other sort of file. Is
> >>>>> there some trick to using these with the latest release? Below is an
> >>>>> ncdump of the header information from a file which worked with 2.7u2.
> >>>>> Thanks for any guidance.
> >>>>> -Al Hermann
> >>>>>
> >>>>>
> >>>> Albert,
> >>>> Could you upload a sample file:
> >>>>
> >>>> http://motherlode.ucar.edu/repository/alias/idvupload
> >>>>
> >>>> Yuan
> >>>>
> >>>>
> >>>>>
> >>>>>> netcdf testfloat10 {
> >>>>>> dimensions:
> >>>>>> DRIFTER1_10 = 10 ;
> >>>>>> TIME = UNLIMITED ; // (7296 currently)
> >>>>>> variables:
> >>>>>> double DRIFTER1_10(DRIFTER1_10) ;
> >>>>>> DRIFTER1_10:point_spacing = "even" ;
> >>>>>> DRIFTER1_10:AXIS = "X" ;
> >>>>>> double TIME(TIME) ;
> >>>>>> float LON(TIME, DRIFTER1_10) ;
> >>>>>> LON:missing_value = 1.e+35f ;
> >>>>>> LON:_FillValue = 1.e+35f ;
> >>>>>> LON:long_name = "longitude of floats trajectories" ;
> >>>>>> LON:history = "From cgoa3_flt_40m" ;
> >>>>>> LON:units = "degree_east" ;
> >>>>>> float LAT(TIME, DRIFTER1_10) ;
> >>>>>> LAT:missing_value = 1.e+35f ;
> >>>>>> LAT:_FillValue = 1.e+35f ;
> >>>>>> LAT:long_name = "latitude of floats trajectories" ;
> >>>>>> LAT:history = "From cgoa3_flt_40m" ;
> >>>>>> LAT:units = "degree_north" ;
> >>>>>> float DEPTH(TIME, DRIFTER1_10) ;
> >>>>>> DEPTH:missing_value = 1.e+35f ;
> >>>>>> DEPTH:_FillValue = 1.e+35f ;
> >>>>>> DEPTH:long_name = "depth of floats trajectories" ;
> >>>>>> DEPTH:history = "From cgoa3_flt_40m" ;
> >>>>>> DEPTH:units = "meter" ;
> >>>>>> float TEMP(TIME, DRIFTER1_10) ;
> >>>>>> TEMP:missing_value = 1.e+35f ;
> >>>>>> TEMP:_FillValue = 1.e+35f ;
> >>>>>> TEMP:long_name = "potential temperature" ;
> >>>>>> TEMP:history = "From cgoa3_flt_40m" ;
> >>>>>> TEMP:units = "Celsius" ;
> >>>>>> float SALT(TIME, DRIFTER1_10) ;
> >>>>>> SALT:missing_value = 1.e+35f ;
> >>>>>> SALT:_FillValue = 1.e+35f ;
> >>>>>> SALT:long_name = "salinity" ;
> >>>>>> SALT:history = "From cgoa3_flt_40m" ;
> >>>>>> SALT:units = "PSU" ;
> >>>>>>
> >>>>>> // global attributes:
> >>>>>> :history = "FERRET V5.51 3-Jan-05" ;
> >>>>>> }
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>> Ticket Details
> >>>> ===================
> >>>> Ticket ID: GRJ-802576
> >>>> Department: Support IDV
> >>>> Priority: Normal
> >>>> Status: Open
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> > Ticket Details
> > ===================
> > Ticket ID: GRJ-802576
> > Department: Support IDV
> > Priority: Normal
> > Status: Closed
> >
> >
>
>
Ticket Details
===================
Ticket ID: GRJ-802576
Department: Support IDV
Priority: Normal
Status: Closed