Skip to main content

Hyrax

Hyrax is the next generation server from OPeNDAP. It utilizes a modular design that employs a light weight Java servlet (aka OLFS) to provide the public-accessible client interface, and a back-end daemon, the BES, to handle the heavy lifting. The BES uses the same handlers that are used with Server3 (also know as the CGI Server) but loads those at run time. See Hyrax configuration documentation and design documentation for detailed information about the server.

Benefits:

  • The servlet architecture is faster, more robust, and more secure than CGI invoked Perl scripts.
  • A single installation can handle multiple data representations (hdf4, hdf5, netcdf, etc.)
  • THREDDS catalog functionality.
  • A prototype SOAP interface for OPeNDAP data services.

Read about the Back End Server (BES).

Read about the OPeNDAP Lightweight Front-end Servlet (OLFS).

Hyrax documentation

This page provides a single place to get all of the packages that make up Hyrax and a simple way to find out which versions of those packages work together correctly. It's possible to get each of the packages from their own page, too.

All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Other software you will need: Java, Tomcat, and optionally Apache.

Hyrax 1.6.1(Updated 04 June 2010)

The 1.6.1 release:

  • NcML Module: Hyrax now supports a significant portion of the NcML 2.2 language with the new NcML Module. With this module, a data provider can augment datasets served on their local Hyrax server in the following ways:
    • Add, modify, or remove both attributes and variables
    • Combine multiple datasets into a single data set using "union" or "joinNew" aggregations. (Other NcML aggregation types are in progress).
    Please also see: Wiki documentation for the NcML Module.
  • Automatically generated THREDDS catalogs now have a 'file' service
  • Improvements to the netCDF file response (Hyrax 1.5 introduced netCDF as a return type for Hyrax).
  • HDF5 now has support for HDF EOS and a special mode for CF 1.0 compliant files.
  • HDF4 Bug fixes for HDF EOS.
  • Bug fixes and feature additions (Beta Release)

Binaries

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

If you're interested in the new HDF-EOS features added to the HDF4 handler, please see the HDF4 handler page.

Java Java
If you are updating from an older version of Hyrax (older than Hyrax 1.5.0) you will need to update your olfs.xml file! See $CATALINA_HOME/webapps/opendap/initialContent/olfs.xml for the default olfs.xml for Hyrax 1.6.1. For more detailed information see the Hyrax Configuration Documentation
Linux Linux (CentOS 5.2) x86_64 RPMs
Linux Linux (CentOS 5.2) i386 RPMs

Source code

Version 1.6.1:
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Contributed builds

Version 1.6.1
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.6.0 beta (Updated 08 Feb 2010)

The 1.6.0 beta release:

  • This is a beta release; binary builds will be made available soon.
  • NCML: Hyrax now suports NcML. Wit the NcML handler you can add new attributes and variables to any of data sets served with Hyrax. The initial version of the NcML handler also supports aggregations of multiple files into a single data set.
  • Automatically generated THREDDS catalogs now have a 'file' service
  • Improvements to the netCDF file response (Hyrax 1.5 introduced netCDF as a return type for Hyrax).
  • HDF5 now has support for HDF EOS and a special mode for CF 1.0 compliant files.
  • HDF4 Bug fixes for HDF EOS.
  • Bug fixes and feature additions (Beta Release)

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
If you are updating from an older version of Hyrax (older than Hyrax 1.5.0) you will need to update your olfs.xml file! See $CATALINA_HOME/webapps/opendap/initialContent/olfs.xml for the default olfs.xml for Hyrax 1.6.0. For more detailed information see the Hyrax Configuration Documentation

Source code

Version 1.6.0 beta:
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Contributed builds

Version 1.6.0 beta
Contributed: Sharing your binary builds for those operating systems not available here.

HDF4 and HDF5 with new HDF-EOS and HDF-EOS2 Support (Updated October 14; October 6 2009)

October 14, 2009: Added missing header file 'HDFEOS.h' to source distribution for the hdf4 handler.

This is a special source-only release of the HDF4 and HDF5 handlers including new features implemented by The HDF Group.

This version of the HDF4/5 handlers presents information stored in HDF-EOS and HDF-EOS2 files in a far more friendly way than the previous handlers. The resulting data sets are much easier for client to process and users to understand and, well, use.

Because this source code requires the HDF-EOS2 libraries and because those are not available in RPM form, we are releasing this software as a source-only release. In the future, the features will be part of every release, but data providers will still need to use the source releases and build the code, to get these features.

Here's some more information about the modifications compiled by developers at The HDF Group:

Source code

Handler with HDF-EOS/2 support for Hyrax 1.5.2+:
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Hyrax 1.5.2 final (Updated 15 June 2009)

The 1.5.2 final release:

  • This update from 1.5.1 includes fixes for the attribute values shown in the DDX response - extraneous double quotes are that were added for the DAS print representation are no longer included in the DDX response.
  • NetCDF Fileout fix The 1.5.2 release includes an important fix for the netcdf fileout feature. The software was not bulding correct files from HDF4 data sets and was instead reusing dimensions in ways that made for some very confusing data files! It now works correctly.
  • The 1.5.1 update from 1.5.0 includes a fix to libdap so that Attribute quoting is properly handled when attribute objects are cached by the server and a fix so that the HDF4 handler takes advantage of this fix. Also, it is now possible to disable the HDF4 handler's caching of objects by setting the HDF4.CacheDir parameter in the bes.conf file to the empty string (""). The new version of libdap is binary-compatible with the 1.5.0 handlers.
  • NetCDF File Out Capability. (BES &OLFS). Get data back from Hyrax packaged in a NetCDF file!
  • New THREDDS implementation. (OLFS)
    • Minimal configuration - works out of the box with zero configuration, although if you are updating from an older version of Hyrax you will need to update your olfs.xml file to get things working (see Java section below).
    • Fast
    • Scalable
    • Presentation views (HTML pages) generated using XSLT
  • Simple robot blocker. (OLFS)
    • Supports a list of individual IP's to block.
    • Supports a list of regex's to block ranges of IP addresses.
  • The netCDF handler now mimics the TDS's handler when returning strings (Arrays of NC_CHAR). These are now packaged in a DAP String and a string_length attribute is added to the variable. Rank N arrays of NC_CHAR are now represented at rank N-1 arrays of DAP string, where each is no longer than string_length characters. This change was made as part of the NC-DAP project's effort to make DAP4 more usable/conformant with the CDM.
  • New BES interface (BES &OLFS)
    • new XML command/response set
    • OLFS contains new java API for the BES
    • Allows multiple BES commands to be combined in a single request transaction.
  • New Linux binary builds. We have decided to switch from using Fedora Core releases for the binary builds and instead use CentOS. The RPMs we are distributing for this release of Hyrax have been built on CentOS 5.2. We have chosen CentOS because it has a longer release cycle than Fedora Core making the resulting packages more likely to work with older third-party software such as libcurl and libxml2.
  • Bug fixes and feature additions (Beta Release)
  • Bug fixes and feature additions (Final Release)

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
If you are updating from an older version of Hyrax you will need to update your olfs.xml file! See $CATALINA_HOME/webapps/opendap/initialContent/olfs.xml for the default olfs.xml for Hyrax 1.5.0/1.5.1. For more detailed information see the Hyrax Configuration Documentation
Linux Linux (CentOS 5.2) x64_86 RPMs
Linux Linux (CentOS 5.2) i386 RPMs

Source code

Version 1.5.2 final:
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Contributed builds

Version 1.5.2 final
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.4.2 (27 June 2008)

Updated 23 July: We have fixed some issues with support for CF conventions in the HDF5 handler. The new version is 1.2.3 and is available here.

The 1.4.2 release :

  • The 1.4.2 release is a bug fix release only, there are no new features in the server. A problem with the hdf4 handler was fixed but this fix requires the latest libdap which in turn requires the latest bes which means all of the handlers must be recompiled (the freeform sources require a slight change), hence a new release of Hyrax.

If you're updating from 1.3.x the notes for the 1.4.1 are probably worth a quick read:

  • Bug fixes and feature additions
  • Significant speed improvements for large data transfers (Details Here and Here.)
  • Tested and approved for Tomcat 1.6.x
  • Improved Error Messaging.
  • XSLT based directory and error pages allow site administrators to customize Hyrax for visual integration with existing sites. (More Here)
  • A spelling correction for the MaximumHeapSize parameter in bes.conf has been made which requires that you correct the spelling of that parameter in your existing BES configuration file before you can start the new BES.
    • Old spelling: MaximunHeapSize
    • New Spelling: MaximumHeapSize
    If this is not corrected you will receive the error: BES: unable to start properly because can not determine memory keys. when you attempt to start the BES.

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
Linux Linux (Fedora Core 8) x64_86 RPMs
Linux Linux (Fedora Core 8) i386 RPMs
OS/X MAC OS/X 10.4
Please let us know if you need OS/X binaries (support at opendap.org).
 

Source code

Version 1.4.2:
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Soap Test Client

We also have SoapTestClient available for this release.
It provides an example for people that wish to try the SOAP interface to have an example of how to use it.

Contributed builds

Version 1.4.2
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.4.1 (29 February 2008, updated 14 April 2008)

Note: 26 June 2008: We're working on an update to this code to include some fixes in libdap, bes and hdf4. The fixes for HDF4 are important because we're found a problem when reading from certain files that contain multiple SDSs where several of the SDSs have the same name. Unfortunately, the fix for the HDF4 handler (version 3.7.9) will not build or run with libdap 3.8.0 and bes-3.6.1. We'll have an updated page here shortly but we want to get this fix out soon and didn't want there to be too much confusion regarding the differing versions of the HDF4 handler and the software required to build and run it. The binaries and source versions below do not contain the HDF4 fix but do work together. See the HDF4 handler page for the latest version of the handler.

The 1.4.1 release :

  • The 1.4.1 release is a bug fix release only, there are no new features. A problem with the BES was fixed and released as version 3.6.1. This fix is important enough to warrant a new BES version, but the new version is compatible with the old binaries and has no new features, so it is a drop-in replacement for version 3.6.0. If you already have Hyrax 1.4.0 installed and running, you can download the BES 3.6.1 source or binary distribution and use either of those with the other Hyrax components you have already installed.
  • Bug fixes and feature additions
  • Significant speed improvements for large data transfers (Details Here and Here.)
  • Tested and approved for Tomcat 1.6.x
  • Improved Error Messaging.
  • XSLT based directory and error pages allow site administrators to customize Hyrax for visual integration with existing sites. (More Here)

  • A spelling correction for the MaximumHeapSize parameter in bes.conf has been made which requires that you correct the spelling of that parameter in your existing BES configuration file before you can start the new BES.

    • Old spelling: MaximunHeapSize
    • New Spelling: MaximumHeapSize

If this is not corrected you will receive the error: BES: unable to start properly because can not determine memory keys. when you attempt to start the BES.

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
Linux Linux (Fedora Core 8) x64_86 RPMs
Linux Linux (Fedora Core 6) i386 RPMs

Source code

Version 1.4.1 :
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Soap Test Client

We also have SoapTestClient available for this release.
It provides an example for people that wish to try the SOAP interface to have an example of how to use it.

Contributed builds

Version 1.4.1
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.3.1 (3 December 2007)

The 1.3.1 release is a bug fix release:

  • The memory footprint has been reduced to address issues on small or medium sized machines.
  • Binaries installed from the RPM packages now store run-time files where most system administrators expect them to be stored.

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
OS/X MAC OS/X 10.4
Linux Linux (Fedora Core 6) i386 RPMs

Source code

Version 1.3.1 :
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Soap Test Client

We also have SoapTestClient available for this release.
It provides an example for people that wish to try the SOAP interface to have an example of how to use it.

Contributed builds

Version 1.3.1
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.3.0 (14 November 2007)

This 1.3.0 release features:

  • Bug fixes
  • Hyrax control script: Simplifies starting and stopping Hyrax when running the BES and the OLFS on the same machine.
  • Compression support: Unix compress (.Z) is now supported.
  • Signed distributions: Our software distributions are now signed using a public/private key pair. See Public Key for more information.

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
OS/X MAC OS/X 10.4
Linux Linux (Fedora Core 6) x64_86 RPMs
Linux Linux (Fedora Core 6) i386 RPMs

Source code

Version 1.3.0 :
Note: All of our software downloads are signed using GPG. Ask us for the public key if you want to verify the signatures.

Soap Test Client

We also have SoapTestClient available for this release.
It provides an example for people that wish to try the SOAP interface to have an example of how to use it.

Contributed builds

Version 1.3.0
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.2.1 (14 May, updated 21 May 2007)

This 1.2.1 release features:

  • Improved support for compressed files: The support for compressed data files has been completely revamped to be more efficient and safer. The cache used for the decompressed files has also be completely re-implemented.
  • Bug fixes
  • These fixes address important security issues which were found in the BES software. Sites running Hyrax should upgrade as soon as practical.
  • Updated (21 May) the BES and OLFS (to versions 3.5.1 and 1.2.3, resp.) to include a fix for a transmission problem that affects some large 32 bit floating point arrays.

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
OS/X MAC OS/X 10.4

Source code

Version 1.2.1 :

Note: Because of changes in the BES' binary interface, you will need to rebuild not only the BES itself, but also all of the handlers. You can use the existing libdap and OFLS binaries.

Soap Test Client

We also have SoapTestClient available for this release.It provides an example for people that wish to try the SOAP interface to have an example of how to use it. Source code: SoapTestClient-1.0.0.src.jar; and binary: SoapTestClient-1.0.0.jar

Contributed builds

Version 1.2.1
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.2 (23 April 2007, updated on 3 May 2007)

This 1.2 release features:

  • Support for multiple BES's: Data providers may configure a single Hyrax installation to work with multiple BES's.
  • The OLFS dispatch code has been refactored to allow 3rd party dispatch handlers to be added simply by modifying the configuration and adding the java class files to the Tomcat library directory.
  • An update on the 27th to include a fix for a concurrency problem we found in the OLFS.
  • An update on May 3rd to include bug fixes for the BES.

ATTENTION:

For those of you that already have Hyrax this change will render your current olfs.xml obsolete. You have two options, either:

Remove the directory $CATALINA_HOME/content/opendap. Restarting Tomcat will cause it to be recreated with a new compatible olfs.xml file.

OR

Copy the file from the web application:

cp $CATALINA_HOME/webapps/opendap/initialContent/olfs.xml $CATALINA_HOME/content/opendap

You will want (need?) to read the new configuration documents to localize your new installation:

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
Linux Linux (Fedora Core 4) i386 RPMs

Source code

Version 1.2 :

Soap Test Client

We also have SoapTestClient available for this release.It provides an example for people that wish to try the SOAP interface to have an example of how to use it. Source code: SoapTestClient-1.0.0.src.jar; and binary: SoapTestClient-1.0.0.jar

Contributed builds

Version 1.2
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax documentation is now available here.

Hyrax 1.1 (14 March 2007)

This 1.1 release features:

  • Lots of Bug fixes (see closed Hyrax 1.1 tickets)
  • A new 'install' for the handlers (general purpose, hdf4, netcdf and freeform) that installs sample data and updates the bes.conf file so that Hyrax runs 'out of the box.'

Binaries

Individual Binaries will be added when they are available.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
Linux Linux (Fedora Core 4) i386 RPMs
Linux Linux (Fedora Core 5) x86_64 RPMs

Source code

Version 1.1 :

Soap Test Client

We also have SoapTestClient available for this release.It provides an example for people that wish to try the SOAP interface to have an example of how to use it. Source code: SoapTestClient-1.0.0.src.jar; and binary: SoapTestClient-1.0.0.jar

Contributed builds

Version 1.1
Contributed: Sharing your binary builds for those operating systems not available here.

Hyrax 1.0.2 (beta) (14 Feb. 2007)

Version 1.0.2 is a beta release of the software.

As of this release the name of the server is changed from Server4 to Hyrax.

This 1.0.2 release features:

  • Bug fixes (Tickets: 767, 784, 789, 793, and others)
  • Partial implementation of logging (Ticket 785)
  • Improved documentation regarding shared libraries. (Ticket 780)
  • The BES and the data handlers come with test data and will work and serve data immediately after an install using the default configuration. (Ticket 764)

Binaries

Note 5 March 2008: We are no longer listing the binaries for any of the beta releases. The packages are still on our site, however, if you need them.

What to get: You will need the OLFS (which is a Java binary and runs on any computer with Java 1.5) and one set of the BES, dap-server and one or more data handlers. We're including libdap here as well to cut down on the amount of hunting around you need to do; libdap is required for all of our software written in C++ (which includes the BES and the handlers).

Java Java
Linux Linux (Fedora Core 4) i386 RPMs
Linux Linux (Fedora Core 5) x86_64 RPMs

Source code

Version 1.0.2 :

Soap Test Client

We also have SoapTestClient available for this release.It provides an example for people that wish to try the SOAP interface to have an example of how to use it. Source code: SoapTestClient-0.1.4-src.jar; and binary: SoapTestClient-0.1.4.jar

Contributed builds

Version 1.0.2
Contributed: Sharing your binary builds for those operating systems not available here.

Server4 Software 1.0.1 (beta) ( 3 Jan 2007)

Version 1.0.1. is a beta release of the software.

The 1.0.1 release adds support for:
  • HTTP/1.1 persistent connections.
  • Improved OPeNDAP directory response.
  • Prototype SOAP Interface.
  • Server UUID on top level directory for improved web searchability.
  • Persistent content (configurations, user supplied documents/web pages, etc.).
  • Improved internal efficiency via BES client connection pooling.

Binaries

For the current beta release, binaries will be added when they are available.

You need the Java Web Archive file unless you plan to build the OLFS from the Java source:
JavaOLFS (Requires Java 1.5. Tested against Tomcat 5.5)
OLFS jar file Unpack using 'jar -xvf filename' and follow the instructions in the README file.

You will also need:

Java 1.5
Tomcat 5

Source code

Version 1.0.1 :
Required: libdap 3.7.4; Optional (but highly desired): dap-server 3.7.2

Soap Test Client

We also have SoapTestClient available for this release.It provides an example for people that wish to try the SOAP interface to have an example of how to use it. Source code: SoapTestClient-0.1.4-src.jar; and binary: SoapTestClient-0.1.4.jar

Contributed builds

Version 1.0.1
Contributed: Sharing your binary builds for those operating systems not available here.

Server4 Software 0.9.1 (alpha) (18 Sept 2006)

Version 0.9.1. This is a source-only alpha release of the software, which means that a significant set of features are complete, but we think that other features should be added to server before it's ready for everyone. We're making this alpha release for those who want to experiment with the new server and for those who want to help us with its development.

What's been added to the server. First, the server now supports fancier THREDDS catalogs. The catalogs can now be customized with hand written catalogs superseding the automatically generated ones. The catalogs also now support 'inheritance' so THREDDS attributes added to parent catalogs will show up also in child catalogs, even the automatically generated ones. Other features include a lighter front end, generation of the ASCII, HTML form and Info responses in the back end (where access to data can be exploited to optimize that activity; this also means that front ends can be built without any DAP-aware code, making them much 'lighter') and support for HTTP/1.1 client-side caching. All of the software components have other fixes and improvements; see their pages or NEWS/README/INSTALL files.

Binaries

There are no binaries yet; the current release is a source-only alpha release.

You need the Java Web Archive file unless you plan to build the OLFS from the Java source:
JavaOLFS (Requires Java 1.5. Tested against Tomcat 5.5)
OLFS jar file Unpack using 'jar -xvf filename' and follow the instructions in the README file.

Note: the OLFS jar file was corrupted; we will have a rebuilt copy early in the week of 6 Nov. Until then you'll need to build the OLFS from source (see the links below)

You will also need:

Java 1.5
Tomcat 5

Source code

Version 0.9.1 :
Required: libdap 3.7.2; Optional (but highly desired): dap-server 3.7.1

Contributed builds

Version 0.9.1
Contributed: Sharing your binary builds for those operating systems not available here.

Server4 Software 0.8.0 (alpha) (17 July 2006)

Version 0.8.0 is the first public release of the Server4 software. This is a source-only alpha release of the software, which means that a significant set of features are complete, but we think that other features should be added to server before it's ready for everyone. We're making this alpha release for those who want to experiment with the new server and for those who want to help us with its development.

Binaries

There are no binaries yet; the current release is a source-only alpha release.

You need the Java Web Archive file unless you plan to build the OLFS from the Java source:
JavaOLFS (Requires Java 1.5. Tested against Tomcat 5.5)
OLFS Web Archive file (6.4 MB)

You will also need:

libdap 3.7
Java 1.5
Tomcat 5

Source code

Version 0.8.0 :
Required: libdap 3.7.1

Contributed builds

Version 0.8.0
Contributed: Sharing your binary builds for those operating systems not available here.

This material is based upon work supported by the National Science Foundation under Grant No. 0430822. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF). Support for the development of Hyrax has also come from NASA and NOAA.