Hi Kyle,
I can fix the files for myself... it is just the unwillingness of the
client that is the problem :)
I will discuss this option with them as well.
Regards
Niels
On 26-09-16 19:23, Kyle Wilcox wrote:
If you *really* can't change the contents of the binary datasets (this
would be quite easy with nco http://nco.sourceforge.net/ using
"ncatted"), can you use a small bit of NcML to add the "units"
attribute to the "depth" variable and access your dataset through the
NcML?
On Fri, Sep 23, 2016 at 8:51 AM Niels Charlier <niels@xxxxxxxxx
<mailto:niels@xxxxxxxxx>> wrote:
Hi,
Having another issue with one of our datasets. This time the cause of
the problem is the lack of a unit for "depth" in this data.
netcdf-java's DefaultConvention doesn't set the axis type to "Height"
(because it expects "m" for unit type in order to do that).
I cannot actually change the content of the binary datasets.
Would another convention solve this issue, and can I select the
convention programmatically? (then we can make it a config setting
from
geotools).
At first glance it doesn't look like the code for CF1Convention
would be
able to detect it.
Or how can we go around this using additional configuration?
Regards,
Niels
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
netcdf-java mailing list
netcdf-java@xxxxxxxxxxxxxxxx <mailto:netcdf-java@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
