Changes between Initial Version and Version 7 of Ticket #166
- Timestamp:
- 10/10/17 13:13:57 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #166 – Description
initial v7 29 29 unsigned range using the valid_min, valid_max, or valid_range attributes. 30 30 31 [Second paragraph on strings, not to be changed] 31 NetCDF does not support a character string type, so these must be 32 represented as character arrays. ... 33 [Remainder of second paragraph on strings, not to be changed] 32 34 33 35 }}} … … 48 50 It is possible to treat the byte type as unsigned by using the NUG 49 51 convention of indicating the unsigned range using the valid_min, valid_max, 50 or valid_range attributes. 52 or valid_range attributes. This usage is deprecated except when the 53 version of netCDF being used does not support unsigned types. 51 54 52 55 2.2.2 Character Strings 53 56 54 [Former paragraph on strings, unchanged] 57 NetCDF Classic format does not support a character string type, so these 58 must be represented as character arrays. ... 59 [Remainder of former paragraph on strings, unchanged] 55 60 56 61 }}}