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.
Adam, How is this trajectory file created? I have been looking at your trajectory file, and I am not sure why it is not working. The underlying library in the IDV is complaining about: - not finding Latitude coordinate - not finding Longitude coordinate - lat/lon/time coord not found. But I am wondering if track.nc is the best template for a trajectory. Theoretically, this one should be better: https://geo-ide.noaa.gov/wiki/index.php?title=NODC_NetCDF_Trajectory_Template Can you try adhering to their suggestions? I am going to investigate on my end to ensure this is a better template. Best, Unidata IDV Support > The files have been uploaded: a single trajectory ncdf file and a multiple > trajectory ncdf file. > > - Adam > > > -----Original Message----- > From: Unidata IDV Support [mailto:address@hidden] > Sent: Friday, May 02, 2014 10:49 AM > To: Adam Houston > Cc: address@hidden > Subject: [IDV #IQR-639012]: Trajectories in NCDF format > > Adam, > > Can you upload your data here and let us know when it is uploaded? > > http://motherlode.ucar.edu/repository/alias/idvupload > > Best, > > Unidata IDV Support > > > Full Name: Adam Houston > > Email Address: address@hidden > > Organization: University of Nebraska - Lincoln Package Version: 4.1 > > Operating System: CentOS > > Hardware: > > Description of problem: I'm unable to get IDV to recognize NCDF trajectory > > files that I'm creating. I've verified that IDV recognizes a "track.nc" > > file available in one of the workshop packages but neither my own single > > trajectory file nor my own multiple trajectory file (this is what I really > > need to visualize) can be read. To the best of my knowledge I'm adhering > > to the CF Version 1.6 conventions (I've tested them in an online compliance > > checker). I've included both headers below. > > > > netcdf \2007finalinfo { > > dimensions: > > time = 6 ; > > trajid_strlen = 1 ; > > variables: > > char trajectory(trajid_strlen) ; > > trajectory:cf_role = "trajectory_id" ; int time(time) ; > > time:standard_name = "time" ; time:long_name = "time" ; time:units = > > "seconds since 1970-01-01 00:00:00" ; float lat(time) ; > > lat:standard_name = "latitude" ; lat:long_name = "latitude" ; > > lat:units = "degrees_north" ; float lon(time) ; lon:standard_name = > > "longitude" ; lon:long_name = "longitude" ; lon:units = "degrees_east" > > ; float z(time) ; z:standard_name = "altitude" ; z:long_name = "height > > above mean sea level" ; z:units = "m" ; > > > > // global attributes: > > :featureType = "trajectory" ; > > :Conventions = "CF-1.6" ; > > } > > > > ==== Multiple trajectories ==== > > > > netcdf \2007finalinfo { > > dimensions: > > obs = 28067 ; > > trajectory = 3252 ; > > trajid_strlen = 4 ; > > variables: > > char trajectory(trajectory, trajid_strlen) ; trajectory:cf_role = > > "trajectory_id" ; int rowSize(trajectory) ; rowSize:long_name = > > "number of obs for this trajectory" ; rowSize:sample_dimension = "obs" > > ; int time(obs) ; time:standard_name = "time" ; time:long_name = > > "time" ; time:units = "seconds since 1970-01-01 00:00:00" ; float > > lat(obs) ; lat:standard_name = "latitude" ; lat:long_name = "latitude" > > ; lat:units = "degrees_north" ; float lon(obs) ; lon:standard_name = > > "longitude" ; lon:long_name = "longitude" ; lon:units = "degrees_east" > > ; float z(obs) ; z:standard_name = "altitude" ; z:long_name = "height > > above mean sea level" ; z:units = "m" ; > > > > // global attributes: > > :featureType = "trajectory" ; > > :Conventions = "CF-1.6" ; > > } > > > > > > > > > Ticket Details > =================== > Ticket ID: IQR-639012 > Department: Support IDV > Priority: Normal > Status: Open > > Ticket Details =================== Ticket ID: IQR-639012 Department: Support IDV Priority: Normal Status: Open