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

[IDV #OBG-717641]: CF-compliant trajectories (again)



Hi Adam,

Nice to hear from you again. One immediate problem that stands out is the units
are inverted on the latitude and longitude variables. It should be
"degrees_north" for latitude and "degrees_east" for longitude. I'd also suggest
reading a previous blog entry on the topic. (I know the example is in Python,
but it should be fairly similar to IDL).

http://www.unidata.ucar.edu/blogs/developer/entry/ipynb_cookbooks_to_create_cf
http://nbviewer.jupyter.org/github/julienchastang/py-netcdf-cf-cookbooks/blob/master/traj.ipynb

Try to follow that example as closely as possible. I am at a conference this
week and also taking a bit of vacation, but I'll try to help you if you get
stuck again.

Best,

Unidata IDV Support

> Hey guys,
> 
> I'm resurrecting this issue from back in 2014.  I have a (new) NetCF-4, 
> CF-compliant trajectory file that I can't get into IDV.  I've done my best 
> (within reason) to match the format to that of the example traj.nc file, but 
> to no avail.  I've tried both the "track files" and "trajectory sounding 
> files" source types.  Incidentally, I can only read in the traj.nc as a 
> "trajectory sounding file" but, based on previous correspondence, this isn't 
> surprising.  In my last correspondence on this subject, the fix (for a 
> different file..that I can't find) was to add in a data variable (it was 
> previously just position variables).  This is not an issue with the new file.
> 
> As before, I'm creating this in IDL.  Previously, using Python was suggested 
> but I'm "not there yet".
> 
> Any help would, as always, be greatly appreciated!!!
> 
> - Adam
> 
> 


Ticket Details
===================
Ticket ID: OBG-717641
Department: Support IDV
Priority: Normal
Status: Closed
===================
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.



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.