Changes between Initial Version and Version 7 of Ticket #166


Ignore:
Timestamp:
10/10/17 13:13:57 (17 months ago)
Author:
zender
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #166 – Description

    initial v7  
    2929unsigned range using the valid_min, valid_max, or valid_range attributes.
    3030
    31 [Second paragraph on strings, not to be changed]
     31NetCDF does not support a character string type, so these must be
     32represented as character arrays. ...
     33[Remainder of second paragraph on strings, not to be changed]
    3234
    3335}}}
    … …  
    4850It is possible to treat the byte type as unsigned by using the NUG
    4951convention of indicating the unsigned range using the valid_min, valid_max,
    50 or valid_range attributes.
     52or valid_range attributes. This usage is deprecated except when the
     53version of netCDF being used does not support unsigned types.
    5154
    52552.2.2  Character Strings
    5356
    54 [Former paragraph on strings, unchanged]
     57NetCDF Classic format does not support a character string type, so these
     58must be represented as character arrays. ...
     59[Remainder of former paragraph on strings, unchanged]
    5560
    5661}}}