Top Menu


ERDDAP is a free and open-source Java “servlet” that converts and serves a variety of scientific datasets using a uniform interface. ERDDAP is focused primarily on serving gridded or tabular (e.g. time-series, profile) datasets which are commonly stored on the server as NetCDF files, and it can serve data in a large number of formats as well as generate plots and maps of requested data. Together, ERDDAP and NetCDF allow data, metadata, and data attribution information to be efficiently and conveniently distributed..

ERDDAP has a standard browser interface that facilitates searching for, converting, and plotting data, and is built using a RESTful machine-to-machine API. All information about every request is contained in the URL of each request, which makes it easy to automate searching for and using data in other applications like Python, R, JavaScript, or MATLAB. Proficient users can also build their own custom interfaces. Many organizations (including NOAA, NASA, and USGS) are now running ERDDAP servers to serve their data, and the ERDDAP principal developer and user community have created user guides, instruction videos, and code examples to facilitate access by new users.

The OOI ERDDAP server provides a simple, consistent way to download subsets of OOI datasets in common file formats and make profile plots and maps.

OOI Uncabled Data ERDDAP Server

What is available on this server?

  • Datasets are created ONLY if the instrument is actively deployed in the water, and data exists in the OOI system within the deployment window for the stream.
  • The first server to come online contains uncabled, telemetered data from moorings and gliders. The cabled, streaming data server is coming soon.

How do I use ERDDAP?

  • You can find video tutorials and an ERDDAP table of contents here, and additional information on the landing page here.
  • More OOI video tutorials and manuals will be added over time.

Additional Information:

  • More than one timestamp is included in the data records (including instrument time, platform time, ingestion time, etc.). The variable “time (UTC)” is the standardized, preferred timestamp to use when creating time series.
  • Parameter names for the same underlying variable may be different depending on which dataset is chosen, based on whether that dataset contains a derived (L2) data product or a simple L1 data product. This is due to an identified parameter consolidation issue that will be fixed. For example:
    1. sci_water_temp in the ctdgv_m_glider_instrument stream (this is the L1 temperature data product produced by the glider CTD instrument)
    2. ctdgv_m_glider_instrument-sci_water_temp in the flort_m_glider_instrument stream (this is the same L1 temperature product, but delivered via the fluorometer because it is used in creating an L2 product)
  • When a new ERDDAP code deployment takes place, it will be at least 30 minutes before the template changes propagate through the front-end server.

Open Access:

  • The repository that contains the development code for the OOI ERDDAP server has been made publicly available here. It is read-only and does not require authentication. You can navigate the projects by clicking on the name and going to the “Browse” heading. If you want to clone the repository you can just execute the following command:
    git clone