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

[netCDF #VBJ-219273]: OC 2.0 binaries for win32

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: [netCDF #VBJ-219273]: OC 2.0 binaries for win32
  • Date: Sat, 09 Jul 2016 16:23:50 -0600
The oc design would work fine for dap4.
but I decided that if no one was using (or would use)
the oc library alone, then wny bother maintaining a separate
unused library?
=Dennis


On 7/7/2016 10:51 AM, James Gallagher wrote:
> New Client Reply: OC 2.0 binaries for win32
>
> Thanks for the heads up.
>
> Is there a problem with the OC design or is it just easier to add DAP4
> directly to netcdf-c?
>
> James
>
> On July 7, 2016 at 10:16:07 AM, Unidata netCDF Support (
> address@hidden) wrote:
>
> The situation is this. Some time ago I moved oc to the unidata
> git hub repository (https://github.com/Unidata/oc).
> It has since become clear that no one is using that library, so
> effectively it has been folded into the netcdf-c library
> (https://github.com/Unidata/netcdf-c) and the oc repo is pretty much
> stable.
> With respect to DAP4, I am (slowly) adding DAP4 support to the
> netcdf-c library, but not using oc.
> My recommendation is that you use the netcdf-c library with netcdf-4
> support turned off. That will give a minimal c library that supports
> dap2 and netcdf-3 (which is necessary for dap2 support). The netcdf-c
> library has much better documentation than oc, and the API is quite
> usable.
>
> =Dennis Heimbigner
> Unidata
>
>
> Ticket Details
> ===================
> Ticket ID: VBJ-219273
> Department: Support netCDF
> Priority: High
> Status: Closed
> ===================
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available through
> the web. If you do not want to have your interactions made available in
> this way, you must let us know in each email you send to us.
>
>



Ticket Details
===================
Ticket ID: VBJ-219273
Department: Support netCDF
Priority: High
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.