The Oceans 2.0 API provides public access to Ocean Networks Canada's extensive data archive, via 6* discovery, 4 data delivery and 2 interoperability web services. The API provides programmatic access to:
- data products, (identical to those accessed interactively using the Ocean's 2.0 Data Search interface)
- scalar, and raw data for near-realtime applications.
A collection of services for obtaining all of the codes needed to successfully request data, via the data delivery services. The services use reductive filtering to return a list, in json format, of all of the items that meet the filter criteria defined in the url parameters. Codes returned from one service can be used in another service to refine the selection, for example, a deviceCategoryCode obtained from the deviceCategories service can be used as a filter on the locations service to find all locations that have instruments of that device category.
- locations - Find locations that have the data you are interested in and use the locationCode when requesting a data using the dataProductDelivery, scalardata or rawdata web services.
- devices - Find devices that have the data you are interested in and use the deviceCode when requesting a data using the dataProductDelivery web service.
- deployments - Find the locationCode, deviceCode, deviceCategoryCode, propertyCode and deployment dates and geographic locations of instrument deployments.
- deviceCategories - Find the device category of the data you are interested in and use the deviceCategoryCode when requesting a data using the dataProductDelivery, scalardata or rawdata web services.
- properties - Find devices that have the data you are interested in and use the propertyCode when requesting a data using the dataProductDelivery web service.
- dataProducts - Find data products and formats (extensions) are available for the locations, devices, device categories or properties of interest and use the dataProductCode and extension when requesting a data product using the dataProductDelivery web service.
Data Delivery Services
A collection of services which return data from the ONC archive, including
- An asynchronous service: dataProductDelivery service allows large amounts of customizable data to be delivered in a variety of formats. This delivery method is both flexible and scalable, but requires additional processing time on the server. By utilizing the Task Queue framework, an asynchronous programming pattern of multiple service calls is used to return the data.
- Two synchronous services: scalardata and rawdata services return data in the response payload, which supports near real-time access. Because this type of delivery method is optimized for speed, the services do not support resampling or aggregation and have a 100k record count limit.
- Direct file access service: archivefiles service returns archived files, using the filename, in the payload.
- dataProductDelivery - Request, run and download data products for locations or devices.
- scalardata - Get the most recent scalar data, or scalar data between two given dates for stations (locations) and device categories.
- rawdata - Get the most recent raw data from an instrument, or raw data between two given dates for stations (locations) and device categories.
- archivefiles - Find archived files available for a station (location) and device category, between two given dates, and download the files.
A collection of services that have standardized interfaces designed for sharing and data integration.
- ERDDAP (OPeNDAP) - coming soon
- SOS - Sensor Observation Service - coming soon
All of the services, with the exception of the interoperability services, require the use of a method and token. Only the scalardata, rawdata and archivefiles services support the responseType optional parameter.
Each Web Service has 1 or more methods outlined in the documentation. The method name is case sensitive.
All Web Services require a token. This can be generated, after logging in at http://data.oceannetworks.ca/Profile. Click the "Web Services" tab, then click "Generate Token"
Valid values are "json" and "jsonp". Defaults to "json".
All web service are method oriented and use the following Url pattern:
Please report all issues with the web services, documentation, samples and client libraries to the Oceans 2.0 Help Centre