[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Support #KOM-880811]: chunksize, NC_STRING questions

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [Support #KOM-880811]: chunksize, NC_STRING questions
  • Date: Mon, 11 May 2009 07:53:09 -0600
Hi Charlie,

> The netCDF4 daily snapshots finally build on my development
> machines again, and support all the interfaces I need.
> This is good for many reasons, including that it allows me
> to easily use DAP on Debian-based machines (Debian lacks Opendap
> packages) via the DAP in libnetcdf mechanism.
> 
> Two questions:
> 
> 1. Is the prototype for chunksizep in nc_def_var_chunking()
> unnecessarily weak? Could you use
> 
> const size_t *chunksizep
> 
> instead of
> 
> size_t *chunksizep
> 
> ? (can chunksizep contents change during call?)

Yes, good catch!  The call shouldn't change the values of the chunk sizes.

> 2. What is (or will be) the syntax for indicating a netCDF4
> NC_STRING in CDL syntax?

There's an example in the source file ncdump/tst_string_data.cdl.

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: KOM-880811
Department: Support netCDF
Priority: Normal
Status: Closed