Download OPeNDAP Software

Clients

Matlab: loaddap 3.7.0

Load data directly into Matlab from the command line or your own Matlab scripts.

The Matlab 2009 version has an installer for Windows XP that includes libdap, so all you need to do is grab the installer listed here. OS/X and Linux users need to install libdap separately.

Matlab 2009 Versions: OSX Mac Intel 32-bit ( libdap 3.9.3 for OS/X Intel 32-bit), Intel Mac 64-bit (snow leopard) libdap 3.9.3 for OS/X Intel 64-bit (snow leopard), XPWin32, Linux Linux i386 (libdap 3.9.3 required), ( libdap 3.9.3 for linux i386), Linux Linux x86_64 (libdap 3.9.3 required), ( libdap 3.9.3 for linux x86_64), More…

The 2007 and 2008 versions have installers for both Windows XP and OS/X that include libdap, so all you need to do is grab the installer listed here. Linux users need to get libdap separately.

Matlab 2007/2008 Versions: XPWin32, OSXMac PPC, Intel, Linux ix386/ix86_64/Fedora Core 8 (libdap 3.8.1 required) More…

Source Code

Note We have done a fair amount of work updating this client for use with the OPeNDAP/URI Matlab Ocean Data Toolbox. The toolbox is quite nice and provides interfaces for some widely used data sets and it's also only a small fraction of the total package - most of the package is the loaddap binary.

Matlab OPeNDAP Toolbox

This toolbox provides Graphical User Interfaces to access a number of ocean data sets via OPeNDAP as well as tools to plot the acquired data. The strength of these interfaces is that they expose complicated data sets (often multi-variable, multi-file data sets spread over a number of directories) in an easy to use interface, allowing the user to request only the subset of data -- parameters, spatial and temporal range and resolution -- relevant to his or her needs.

IDL Client 3.6.1

The OPeNDAP IDL Client is an IDL tool which provides access to OPeNDAP data in IDL. The IDL client now uses the OPeNDAP C API(Ocapi-1.4.3) in place of the Ocapi-1.33. This client was compiled with IDL 6.3. The behavior of the new IDL client remains consistent with previous versions of the client code.

download: Mac PPC More…

Source Code

Clients from other groups

Be sure to look at the growing list of DAP 2.0 compatible clients developed by other groups. If you know of a client that's not on our list, please tell us about it!

OPeNDAP Data Connector

The OPeNDAP Data Connector (ODC) is a Java application that allows you to search for and retrieve data sets published by OPeNDAP data servers. The ODC is your gateway to terabytes of scientific data and imagery.

Dec 2009Unfortunately, we are not able to provide support for the ODC at this time. If you are interested in helping with the software, we would love to hear from you! Contact us at support at opendap.org.

download 2.64:   Windows (38 MB), Unix/Linux (9.1 MB), Mac OS X

Java Run-time from SUN.

Linux instructions

Source Code: use Subversion (SVN) and checkout the module Java-OPeNDAP

Software development kits

OPeNDAP C API (oc) 1.0

Version 1.0 of oc fixes various bugs, including a client parameter bug and adds support for parameter merging. Doxygen generated documentation was added along with a missing function to the API. Non-autotest testing was removed as well as the executable property on the .c and .h files. And an OSX_Resource directory was added for mac osx builds and IDL code is now optional at compile time.

download:  Windows , Linux /ix386/Linux/Fedora Core 8, Linux /x86_64/Linux/Fedora Core 8, Mac /ix386/OS/X Mac /pc/OS/X More…

Source Code

DAP++ 3.9.3

This version is a minor upgrade from 3.9.2 and contains a fix for the Attribute parser so that quotation is preserved when attribute objects are both read and written. This version of libdap is binary-compatible with 3.9.2.

download: Linuxi386/Linux/Fedora Core 8, Linuxx86_64/Linux/Fedora Core 8, More…

Source Code

netCDF Client Library

The netCDF Client Library software has moved to Unidata and can now be found in the netCDF library software distribution!! The netCDF client library page contains more information and links to the new software. Also on that page are links to the old software distributions we released.

Java DAP 1.1.7

The Java DAP class library implements DAP 2.0. It is completely interoperable with the DAP++ library above, although it was written by developers at JPL and OSU. The library contains an implementation of the DAP 2.0 plus server specific classes. This software supports building servlets (the DAP++ library's server-side supports CGIs).

Note that version 1.1.7 contains some important organizational changes. Each of the distribution files will need to be unpacked (using jar) prior to use.

If you're upgrading from an older version, be sure to read the README file.

download: README, Binary (jar file) (426 KB), Source (jar file) (2.0 MB) Documentation (jar file) (1.4 MB)

Development Kits from other groups

There are several other Development Kits that provide APIs different from the one we designed and implemented in the DAP++ and Java DAP class libraries. Some are object oriented and some are functional. If you know of a SDK that's not on our list, please tell us about it!

OPeNDAP C API (Ocapi) 1.4.3

Support for the Ocapi is being phased out in favor of the OC API.

The OPeNDAP C API (OCAPI) is an OPeNDAP DAP 2.0 client implementation written in generic C. The goal of this implementation is to provide a C code base that can be compiled easily on any platform without the complexities found in C++. Version 1.4.3 is a source release plus binaries. This release fixed a buffer overflow error and duplicate attribute error. Removes outdated code and debugging messages.

download:  Windows , Linux /ix386/Linux/Fedora Core 8, Linux /x86_64/Linux/Fedora Core 8, More…

Source Code

Servers

Hyrax 1.6.1

Hyrax is the OPeNDAP 4 Data Server.

Version 1.6.1. This release includes support for NcML metadata processing and joinNew aggregations, new module implementations, and bug fixes. Please refer to the Hyrax page for more information

Comprehensive list of Data Handlers

OPeNDAP maintains, at varying levels, many different data handlers which work with the Hyrax (and CGI-based) data server. Some are widely used and we coordinate their release with the server packages. You can download those handlers from the Hyrax or CGI-based servers' pages. This page provides a listing of all the data handlers we provide, including those for which we provide binary builds, those that are released as source code only and those that are available from our source code repository.

If you have questions about any of the handlers, or an idea for a new handler, please contact us!

Server3 (aka CGI Server Base Software) 3.8.2

The version 3.8.2 release includes no new features for the CGI-based data server, but the security patch posted on 27 April 2007 has been applied, other fixes have been made and the Usage, ASCII and WWW form interface handlers have been updated for the latest version of libdap.

SQL Database Server and the Test Server 1.1.7

Serve data stored in a Relational Database. After installing the Web archive file in your servlet engine see the default web page for the dods servlet (http://your.host.name/dods) for configuration information, developers information, and API documentation.

As a bonus, the Relational Database Server also contains the Test Server. Use the Test Server to build data sources for use in testing your DAP-compatible client software.

download: Web Archive file (1.4 MB)

Source Code

Servers developed by other groups

There are several other data servers which use the DAP. The GrADS-DODS Server (GDS) provides subsetting and analysis services for any GrADS-readable data set. The Live Access Server (LAS) provides an easy way to set up a data portal for users that can't, or don't want to, use an analysis application such as MATLab or Ferret.

If you know of a server that's not on our list, please tell us about it!

OPeNDAP's Public Key

OPeNDAP's Public Key is available here.

We now (November 2007) sign all of our software releases using gpg and a key created just for this purpose. The public key is bound to the email address security at opendap.org. The address is 'real' in the sense that email sent there will be answered, although we ask that support questions be sent to the support at opendap.org address instead.

To verify a particular software package using its digital signature:

  • Import the security at opendap.org public key into your key ring (see the gpg documentation for help on that);
  • Download both the package and the .sig signature file and put them in the same directory; and
  • Run gpg --verify <signature file name> in the directory with those files.
The result should be a message telling you that the signature is valid, who signed it and when it was signed. If you don't get a message saying the signature is valid, double check that you have installed the public key correctly, have the file and its signature in the same directory and have not renamed the file (or signature). If, after that, you're still not getting a message that the signature is valid, please contact us.

Software Archive

The HTTP archive holds just about every piece of software we have ever released. Each release is held in a separate directory. Beta and final versions for each release are within those directories. Below are shortcuts to specific parts of the archive for people that want all of the source code without navigating through the pages specific to each of the clients, servers, et cetera.

Source, Binary, ODC.
Old DODS releases
By Release

Nightly Builds

We run a suite of builds every night. Each nightly build is created using code checked out from SVN. Mostly we use the nightly build process on our current release, although some other software, such as the current development code, is also built.

You can see the status of the most recent nightly build, although we do not run nightly builds on all of our platforms.

Subversion (SVN)

Another way to get source code is to use anonymous access to our SVN repository. In Spring of 2005 we switched from CVS to SVN. Our CVS repository required a login for read access as well as write access. Our SVN repository provides public read-only access without a password or login. You'll need an account for write-enabled access; email webmaster at opendap.org for more information. There are several ways that you can get software using svn.

  • You can use a web browser; visit the URL http://scm.opendap.org:8090/svn/. This is a good way to read over source code if you have specific questions about how a particular function has been implemented. Note that we're currently reorganizing the sources so there is some duplication in the repository. Email opendap-tech if you have questions about what's under active development and what's not.
  • You can use a web browser to view our Trac web site, which provides a browser-based interface to our svn repository.
  • You can use a variety of subversion clients to read from the repository. Generally, you will want to check out source code from the repository's 'trunk' using the URL "http://scm.opendap.org:8090/svn/trunk/." There are many subversion clients available and many plugins for IDEs.

Where to find specific software in the repository

There are many projects in our subversion repository, here are some:

  • libdap: The C++ DAP2 library.
  • libnc-dap: The C++ netCDF DAP2 Client Library.
  • ocapi: A pure C implementation of DAP2 for clients.

 i686/Linux/RH7.3 (1.0 MB), More…

Source Code

Item template end -->