[ncl-talk] NCL and NetCDF4 attributes: NC_STRING vs NC_CHAR problem
David Brown
dbrown at ucar.edu
Fri Jul 31 13:54:11 MDT 2015
Hi Christian,
If you are outputting NetCDF4 only to take advantage of its
compression abilities and are not using advanced type features of
NetCDF4 then you can use the NetCDF4Classic format. Otherwise we do
not currently have a way to specify that attributes be written using
the NC_CHAR type with NetCDF4. We can certainly add this as an option
but it will probably not happen immediately.
-dave
On Fri, Jul 31, 2015 at 8:34 AM, Christian Pagé
<page.christian at gmail.com> wrote:
> Dear all,
>
> I am creating NetCDF4 files using NCL, and when I read a NetCDF3 file with a
> variable and its attributes, and then I write this variable with attributes
> in a NetCDF4 output file, I get NC_STRING as the attribute type and not
> NC_CHAR. This causes problem for some tools regarding CF-convention. For
> example NCO reports that NC_STRING is not supported in the CF-convention and
> it will be omitted.
>
> Is there any way to force NCL to output attributes in NetCDF4 files as
> NC_CHAR instead of NC_STRING?
>
> Thanks!
>
> Best regards,
>
> Christian Pagé
>
>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk at ucar.edu
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
More information about the ncl-talk
mailing list