Data Products
Here's the place to learn and talk about our data products – both current and future.
Featured Data Product
New data products include: Kongsberg Rotary
(sweep and scan), Time Series Scalar Profile Plot (only available for profiling devices), Nortek ADCP Ensemble-Averaged MAT and NetCDF.
The resolution of all PNG data products has been increased to 300 DPI. In addition, all plots are now available in vectorized PDF format. Human-tuned and colour-blind compatible colour schemes are now being used.
Current Data Products
ID |
NEPTUNE Canada |
|
ID |
Interoperability Partners |
|---|---|---|---|---|
1 |
|
15 |
||
2 |
|
16 |
||
3 |
|
17 |
||
4 |
|
|
|
|
5 |
|
|
|
|
7 |
|
|
|
|
8 |
[CSV With NaNs] |
|
|
|
9 |
|
|
|
|
10 |
|
|
|
|
11 |
|
|
|
|
12 |
|
|
|
|
14 |
|
|
|
|
18 |
|
|
|
|
19 |
|
|
|
|
20 |
|
|
|
|
21 |
|
|
|
|
22 |
|
|
|
|
24 |
|
|
|
|
25 |
|
|
|
|
26 |
|
|
|
|
27 |
|
|
|
|
33 |
|
|
|
|
34 |
|
|
|
|
35 |
|
|
|
|
36 |
|
|
|
|
40 |
|
|
|
|
41 |
|
|
|
|
48 |
|
|
|
|
49 |
|
|
|
|
52 |
|
|
|
|
56 |
|
|
|
|
57 |
|
|
|
|
58 |
|
|
|
|
59 |
|
|
|
|
60 |
|
|
|
|
61 |
|
|
|
|
62 |
|
|
|
|
63 |
|
|
|
|
64 |
|
|
|
|
65 |
|
|
|
Metadata
Metadata reports are now available with many different data products, including the scalar data products. These PDF reports are produced automatically when a data search is completed and are made available via a link adjacent to the data, see step 3 in data search help. The reports contain extensive information about the data, including instrument location, deployment, calibration, data quality and data gaps.
Conventions
Timestamps: Timestamps are always in UTC. For file-names and string dates, the format conforms to the ISO8601 convention: yyyymmddTHHMMSS.FFFZ. In some cases, the millisecond portion is omitted. Numerical timestamps within data product files may follow a different format as noted on the data product pages. For instances, numeric timestamps within MAT files are in the MATLAB serial date format.
Filenames: Note that the underscore character, "_", is used to separate the components of the names. It is also used to replace any spaces in the name to maintain compatibility. File breaks occur for many reasons, including configuration or device changes (location search only), plus some data products have daily file breaks.
For an instrument type search, files are named as DEVICECODE_SENSORCODE_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where:
- DEVICECODE is a descriptive string unique to each instrument.
- SENSORCODE is a string unique to each sensor, and is only included if a single-sensor data product was requested.
- The first yyyymmddTHHMMSSZ is the timestamp (ISO8601 format) which represents the start date from which the data was searched for. The first data within the file may occur some time after this date. The second yyyymmddTHHMMSSZ is optional. It is the end date up to which data is searched for. These timestamps may have millisecond information: yyyymmddTHHMMSS.FFFZ, where 'FFF' are the milliseconds.
- MODE is optional text which allows files to be differentiated, as necessary, when they refer to the same device and share the same extension. For instance, the VPS cast products supply the end date here.
- EXT is the file extension.
For location search, files are named as STATIONNAME_DEVICECATEGORY_SENSORNAME_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where
- STATIONNAME is the station name, including site tree nodes separated by dashes, for example: BarkleyCanyon-VPSUpperSlope.
- DEVICECATEGORY is the device category, such as 'CTD'. If there is more than one device in the category, the file will contain multiple devices.
- SENSORNAME is the sensor name and is omitted for a device-level data product that contains multiple sensors.
- yyyymmddTHHMMSSZ, MODE and EXT are as above.
File formats
Additional resources for available file formats is available here.
If you have any data product related questions or would like to see additional data products, please [let us know].
