mirror/netcdf-c
2
0
Fork 0
mirror of https://github.com/Unidata/netcdf-c.git synced 2025-01-30 16:10:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

fixed some refs

Browse Source
This commit is contained in:
edhartnett 2017-08-15 14:01:17 -06:00
parent 6b407dd38b
commit 40e53580b6
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/guide.dox
View File

@ -136,7 +136,8 @@ floating-point standard is used for floating-point data
representation. representation.
Descriptions of the overall structure of netCDF classic and 64-bit Descriptions of the overall structure of netCDF classic and 64-bit
offset files are provided later in this manual. See Structure. offset files are provided later in this manual. See
\ref file_structure_and_performance.
The details of the classic and 64-bit offset formats are described in The details of the classic and 64-bit offset formats are described in
an appendix. See File Format. However, users are discouraged from an appendix. See File Format. However, users are discouraged from
@ -258,7 +259,7 @@ designing and implementing netCDF, it is still possible to use the
netCDF interface to access data in inefficient ways: for example, by netCDF interface to access data in inefficient ways: for example, by
requesting a slice of data that requires a single value from each requesting a slice of data that requires a single value from each
record. Advice on how to use the interface efficiently is provided in record. Advice on how to use the interface efficiently is provided in
Structure. \ref file_structure_and_performance.
The use of HDF5 as a data format adds significant overhead in metadata The use of HDF5 as a data format adds significant overhead in metadata
operations, less so in data access operations. We continue to study operations, less so in data access operations. We continue to study
@ -318,8 +319,8 @@ one of the goals of netCDF is portable data, and some file systems
still can't deal with files larger than 2 GiB, it is best to keep still can't deal with files larger than 2 GiB, it is best to keep
files that must be portable below this limit. Nevertheless, it is files that must be portable below this limit. Nevertheless, it is
possible to create and access netCDF files larger than 2 GiB on possible to create and access netCDF files larger than 2 GiB on
platforms that provide support for such files (see Large File platforms that provide support for such files (see
Support). large_file_support).
The new 64-bit offset format allows large files, and makes it easy to The new 64-bit offset format allows large files, and makes it easy to
create to create fixed variables of about 4 GiB, and record variables create to create fixed variables of about 4 GiB, and record variables
@ -691,7 +692,7 @@ Attributes may be added to a netCDF dataset long after it is first
defined, so you don't have to anticipate all potentially useful defined, so you don't have to anticipate all potentially useful
attributes. However adding new attributes to an existing classic or attributes. However adding new attributes to an existing classic or
64-bit offset format dataset can incur the same expense as copying the 64-bit offset format dataset can incur the same expense as copying the
dataset. For a more extensive discussion see Structure. dataset. For a more extensive discussion see \ref file_structure_and_performance.
\section differences_atts_vars Differences between Attributes and Variables \section differences_atts_vars Differences between Attributes and Variables