Ocean Networks Canada: Data Access & Oceans 3.0

Marine scientists, oceanographers, and research data managers use Ocean Networks Canada (ONC) to discover and analyze continuous data from subsea cabled observatories, mobile platforms, and coastal monitoring arrays. Unlike episodic ship cruises, ONC delivers continuous seafloor power and telemetry to observe marine processes—including seismic tremors, tsunamis, ocean acidification, and benthic ecosystems—in real time. This guide explains what Ocean Networks Canada is, who governs it, how to navigate Oceans 3.0, how to query datasets via Python, and how it compares to ERDDAP and EMODnet.

What it is

Ocean Networks Canada (ONC) is a Major Research Facility of Canada hosted by the University of Victoria (UVic) in British Columbia. Serving as a Decade Implementing Partner for the United Nations Decade of Ocean Science for Sustainable Development (2021–2030), ONC operates deep-sea and coastal observatories across Canada’s Pacific, Atlantic, and Arctic coasts, plus sensor systems in the Southern Ocean.

Traditional oceanography relies on research ships and battery moorings that offer temporary snapshots or delayed retrieval. In contrast, ONC connects underwater instruments via subsea fiber-optic cables, delivering continuous power and communications to more than 12,000 ocean sensors, hydrophones, and subsea cameras.

Observational streams flow into ONC’s digital repository, Oceans 3.0 (upgraded from Oceans 2.0). Operating as an open-access data hub, Oceans 3.0 delivers petabytes of sensor data, acoustic audio, and video to over 70,000 registered users worldwide.

Who runs it and what it covers

Ocean Networks Canada is operated by the University of Victoria in British Columbia. Core funding is provided by the Canada Foundation for Innovation (CFI) Major Science Initiatives Fund, the Government of Canada, and British Columbia. Administrative headquarters reside in the Ocean-Climate Building at UVic, while marine engineering and instrument maintenance run out of the Marine Technology Centre in North Saanich.

ONC’s observing assets cover four operational domains:

Pacific Cabled Observatories: NEPTUNE features an 840-kilometer fiber loop across the Juan de Fuca plate down to 2,600 meters. VENUS operates cabled nodes in the Salish Sea to examine coastal hypoxia, mixing, and benthic dynamics.
Arctic Observing Facilities: An Arctic cabled observatory at Cambridge Bay, Nunavut, monitors sea ice thickness, water properties, and underwater sound.
Atlantic Deployments: Installations in the Bay of Fundy track extreme tidal currents, sediment transport, and marine energy dynamics.
Mobile and Coastal Assets: Coastal radar systems, weather stations, ferry sensors, autonomous underwater vehicles (AUVs), and remotely operated vehicles (ROVs).

Instruments stream over 120 data product types, including CTD, ADCP, seismometers, bottom pressure recorders, biogeochemical sensors, and hydrophones. All datasets are bound to standardized spatial and parameter metadata conforming to international standards.

How to search or use it

Ocean Networks Canada provides data access through its web portal (Oceans 3.0 Data Search) and programmatic REST web services. The following seven steps outline data discovery and extraction:

Access the Data Search Portal: Visit data.oceannetworks.ca/DataSearch. Browsing metadata is open; downloading files or obtaining API tokens requires signing in via the top-right link.
Navigate the Data Source Selection Tree: Use the left navigation tree to explore observing platforms geographically and structurally (for example, expanding Cabled Observatories → Pacific → Salish Sea → Saanich Inlet → Saanich Inlet Central Node). Alternatively, use the location and instrument search bars.
Filter by Device Category: Select the instrument category. Standard category codes include CTD (temperature, salinity, depth), ADCP (current velocity), HYDROPHONE (underwater sound), and BPR (bottom pressure recorders).
Define Temporal Boundaries: Specify start (dateFrom) and end (dateTo) timestamps in Universal Coordinated Time (UTC).
Select Data Product Type and Configure Options: Choose your format (such as TSSP scalar plots, CSV, NetCDF, or FLAC audio). Configure Data Product Options (DPOs), including quality flags and resampling intervals.
Queue and Download Files: Submit the request to Oceans 3.0. Retrieve completed archives containing data files, logs, and provenance metadata from the download queue.
Automate Retrieval via the Python Client: Install the official onc package (pip install onc) and query endpoints with your personal API token:

from onc import ONC

onc = ONC("YOUR_API_TOKEN_HERE")
categories = onc.getDeviceCategories({"locationCode": "SIEN"})

params = {
    "locationCode": "SIEN",
    "deviceCategoryCode": "CTD",
    "dataProductCode": "TSSP",
    "extension": "png",
    "dateFrom": "2024-01-01T00:00:00.000Z",
    "dateTo": "2024-01-01T06:00:00.000Z",
    "dpo_qualityControl": "1",
    "dpo_resample": "15m",
}
onc.orderDataProduct(params, downloadResultsOnly=True)

This automated access supports FAIR data principles through standardized machine-actionable endpoints and provenance records.

Strengths and limits

Evaluating Ocean Networks Canada involves balancing its technical capabilities against physical and logistical constraints:

Continuous Real-Time Data: Uninterrupted power and telemetry enable continuous sampling at high frequencies, capturing episodic events—such as seismic tremors and turbidity flows—that ship cruises miss.
Co-Located Interdisciplinary Arrays: Cabled nodes host diverse instruments at identical coordinates, letting researchers correlate benthic biology, hydrography, seismology, and acoustics.
Automated Quality Control: Oceans 3.0 processes raw hex streams into over 120 data products, applying automated quality checks and flagging suspect points.
Geographic Concentration: Infrastructure is concentrated along Canada’s Pacific margin, the Salish Sea, and select Arctic/Atlantic outposts. Basin-scale studies require broader observing programs.
Subsea Infrastructure Vulnerabilities: Seafloor cables face hazards from fishing trawls, turbidity flows, and seismic slumps. Repairs require specialized ROV ships, creating occasional downtime.
Platform-Specific Vocabulary: Programmatic access requires learning ONC-specific codes for locations, device categories, and product options rather than generic coordinates.
Substantial Data Volume: High-bandwidth hydrophones and cameras generate terabytes of raw data, requiring local storage and processing pipelines.

Alternatives

Researchers often combine ONC with other major marine observing initiatives and data middleware:

Platform / Network	Geographic Scope	Primary Architecture	Data Access and Protocols	Primary Use Case / Best For
Ocean Networks Canada (ONC)	Canadian Pacific, Arctic, Atlantic; Southern Ocean	Cabled seafloor nodes, mobile ROVs, coastal radar	Oceans 3.0 portal, REST API, Python (`onc`), R	Continuous cabled time series and benthic monitoring
Ocean Observatories Initiative (OOI)	US Northeast Pacific, Atlantic coastal/global arrays	Cabled loops, moored buoys, profiling gliders	OOI Portal, M2M API, ERDDAP	Multi-scale US continental margin and physical profiling
ERDDAP Data Servers	Global (deployed by NOAA, IOOS, regional nodes)	Distributed data server middleware	RESTful HTTP requests, OpenDAP, griddap, tabledap	Standardized data subsetting and cross-system integration
European Marine Observation and Data Network (EMODnet)	Pan-European marine waters	Federated network linking national oceanographic centers	OGC web services (WMS, WFS), thematic portals	Harmonized regional marine planning and environmental data
Argo Float Program	Global open oceans (0–2,000 m)	Autonomous profiling robotic floats	Global Data Assembly Centres (GDACs), NetCDF	Global upper-ocean temperature and salinity monitoring

For US continental margin studies, the Ocean Observatories Initiative provides complementary cabled arrays. For global climate research, the Argo Float Program delivers vertical temperature and salinity profiles across ocean basins.

Architecturally, ONC operates as an integrated primary facility, while ERDDAP provides middleware harmonizing diverse databases via tabledap and griddap protocols. Similarly, EMODnet aggregates pan-European marine data across national institutions. In practice, researchers often ingest ONC streams into ERDDAP servers.

FAQ

What is the difference between Oceans 2.0 and Oceans 3.0?

Oceans 2.0 was ONC’s legacy software infrastructure for sensor data ingestion. Oceans 3.0 is a modernized platform featuring an improved search portal, automated quality control pipelines, and a faster REST web services API with official Python (onc) and R client packages.

Is Ocean Networks Canada data free to access?

Yes. Ocean Networks Canada maintains an open-access data policy. All sensor observations, acoustic audio files, and underwater video can be discovered, searched, and downloaded at no cost. User registration is required only to queue batch orders and obtain API access tokens.

How do researchers cite data retrieved from Ocean Networks Canada?

Researchers must cite ONC datasets using the persistent Digital Object Identifier (DOI) assigned to the specific observatory, node, or sensor deployment. Citations should credit Ocean Networks Canada, name UVic as host, include the DOI link, and state the access date.

Does Ocean Networks Canada support ERDDAP integration?

Yes. While ONC delivers data via its Oceans 3.0 API, data products are routinely converted into CF-compliant NetCDF files. Regional ocean networks, such as CIOOS, harvest these files and serve them via ERDDAP endpoints for federated querying.

What programming languages are officially supported for automated ONC data access?

Ocean Networks Canada maintains official client packages for Python (onc on PyPI) and R (onc.api on CRAN). Researchers can also query RESTful endpoints directly using MATLAB, Julia, or curl scripts.

Sources

Ocean Networks Canada: About ONC. University of Victoria. Checked 2026-11-08. https://www.oceannetworks.ca/about-onc/
Ocean Networks Canada: Oceans 3.0 API Documentation (onc Python Client v2.6.0). Checked 2026-11-08. https://oceannetworkscanada.github.io/api-python-client/
Ocean Networks Canada: Oceans 3.0 Data Search Portal. Checked 2026-11-08. https://data.oceannetworks.ca/DataSearch
National Oceanic and Atmospheric Administration: ERDDAP Data Server Overview. NOAA CoastWatch. Checked 2026-11-08. https://coastwatch.pfeg.noaa.gov/erddap/index.html
European Commission: European Marine Observation and Data Network (EMODnet). Checked 2026-11-08. https://emodnet.ec.europa.eu/en