© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
A number issues with the current netCDF reader(s):
1) The lon,lat grid is assumed to be equidistant (in lon,lat space). It simply take the 'actual_range' attribute of the 'longitude' and 'latitude' variables and divides this by the 'dimension' to get a dx and dy. Thus it totally ignores the actual values of the 'longitude' and 'latitude' variables. This obviously breaks for non equidistant grids (do we need these?) and also silently gives the wrong answer if the 'actual_range' attribute is not up-to-date (for instance after running ncks).
2) The variables other than 'longitude' and 'latitude' are all assumed to be functions of the form f(lat,lon), i.e. it ignores the specified 'dimensions' of the variable. So, if a function is stored as f(lon,lat) it will garble the data without warning. Question again: do we only need f(lat,lon) variables?