You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Release Notes {#RELEASE_NOTES}
1
+
qRelease Notes {#RELEASE_NOTES}
2
2
=============
3
3
4
4
\brief Release notes file for the netcdf-c package.
@@ -7,6 +7,10 @@ This file contains a high-level description of this package's evolution. Release
7
7
8
8
## 4.5.0 - TBD
9
9
10
+
*[Bug] Corrected an issue where older versions of curl might fail. See [GitHub #487](https://github.com/Unidata/netcdf-c/issues/487) for more information.
11
+
*[Enhancement] Added options to enable/disable `CDF5` support at configure time for autotools and cmake-based builds. The options are `--enable/disable-cdf5` and `ENABLE_CDF5`, respectively. See [Github #484](https://github.com/Unidata/netcdf-c/issues/484) for more information.
12
+
*[Bug Fix] Corrected an issue when subsetting a netcdf3 file via `nccopy -v/-V`. See [Github #425](https://github.com/Unidata/netcdf-c/issues/425) and [Github #463](https://github.com/Unidata/netcdf-c/issues/463) for more information.
13
+
*[Bug Fix] Corrected `--has-dap` and `--has-dap4` output for cmake-based builds. See [GitHub #473](https://github.com/Unidata/netcdf-c/pull/473) for more information.
10
14
*[Bug Fix] Corrected an issue where `NC_64BIT_DATA` files were being read incorrectly by ncdump, despite the data having been written correctly. See [GitHub #457](https://github.com/Unidata/netcdf-c/issues/457) for more information.
11
15
*[Bug Fix] Corrected a potential stack buffer overflow. See [GitHub #450](https://github.com/Unidata/netcdf-c/pull/450) for more information.
Copy file name to clipboardExpand all lines: docs/attribute_conventions.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,11 +25,14 @@ It is strongly recommended that applicable conventions be followed unless there
25
25
26
26
<p>
27
27
28
-
> It is not necessary to define your own _FillValue attribute for a variable if the default fill value for the type of the variable is adequate. However, use of the default fill value for data type byte is not recommended. Note that if you change the value of this attribute, the changed value applies only to subsequent writes; previously written data are not changed.
28
+
> If _FillValue is undefined, it is assumed that there are no unwritten data-values. Generic applications needing to write a value to represent undefined or missing values may use either `_FillValue` or `missing_value`for this purpose. It is legal (but not recommended) for the fill value to be within the valid range of the data.
29
29
30
30
<p>
31
31
32
-
> Generic applications often need to write a value to represent undefined or missing values. The fill value provides an appropriate value for this purpose because it is normally outside the valid range and therefore treated as missing when read by generic applications. It is legal (but not recommended) for the fill value to be within the valid range.
32
+
> Generic applications often need to write a value to represent undefined or missing values. The fill value provides an appropriate value for this purpose because it is normally outside the valid range and therefore treated as missing when read by generic applications. It is legal (but not recommended) for the fill value to be within the valid range.
33
+
34
+
> **Note that if you change the value of this attribute, the changed value applies only to subsequent writes; previously written data are not changed.**
35
+
33
36
34
37
`missing_value`
35
38
@@ -183,4 +186,3 @@ Using the following API calls will fail.
183
186
> The type of this attribute is NC_INT.
184
187
185
188
> This attribute is computed by using the HDF5 API to walk the file to look for attributes specific to netcdf-4. False negatives are possible for a small subset of netcdf-4 files, especially those not containing dimensions. False positives are only possible by deliberate modifications to an existing HDF5 file thru the HDF5 API. For files with the _NCProperties attribute, this attribute is redundant. For files created prior to the introduction of the _NCProperties attribute, this may be a useful indicator of the provenance of the file.
Copy file name to clipboardExpand all lines: docs/types.dox
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,10 @@ The atomic external types supported by the netCDF interface are:
22
22
- ::NC_UINT64 64-bit unsigned integer *
23
23
- ::NC_FLOAT 32-bit floating point
24
24
- ::NC_DOUBLE 64-bit floating point
25
-
- ::NC_STRING variable length character string *
25
+
- ::NC_STRING variable length character string +
26
26
27
-
\remark{* These types are available only for CDF5 (NC_CDF5) and netCDF-4 format (NC_NETCDF4) files. All the unsigned ints (except \ref NC_CHAR), the 64-bit ints, and string type are for CDF5 or netCDF-4 files only.}
27
+
\remark * These types are available only for CDF5 (NC_CDF5) and netCDF-4 format (NC_NETCDF4) files. All the unsigned ints (except \ref NC_CHAR) and the 64-bit ints are for CDF5 or netCDF-4 files only.
28
+
\remark + These types are available only for netCDF-4 (NC_NETCDF4) files.
28
29
29
30
These types were chosen to provide a reasonably wide range of
30
31
trade-offs between data precision and number of bits required for each
0 commit comments