Home

Current Data Products

ID	NEPTUNE Canada		ID	Interoperability Partners
1	Time Series Scalar Data		15	ISDM Data Product
2	Time Series Scalar Plot		16	PANGAEA Data Product
3	Borehole Temperature Time Series Plot		17	POKM Data Product
4	Log File
5	RDI ADCP Time Series
7	WAV Audio File
8	CSV With NaNs
9	RDI ADCP Daily Current Plot
10	RDI ADCP Daily Intensity Plot
11	RDI ADCP Daily Correlation Plot
12	RDI ADCP Daily Percent Good Plot
14	Video File
18	AGO Time Series Plot
19	BioSonics Time Series
20	Satlantic ISUS Time Series
21	Time Series Staircase Plot
22	Nortek Profiler Time Series
24	ASL AWCP Time Series
25	CSEM Receiver Time Series
26	RDI Wave Time Series
27	Satlantic Radiometer Time Series
33	COVIS Plume Imaging Raw Files
34	COVIS Diffuse Flow Raw Files
35	COVIS Plume Doppler Raw Files
36	RDI ADCP Ensemble-Averaged Time Series
40	COVIS Plume Imaging Time Series
41	COVIS Diffuse Flow Time Series
48	Kongsberg Mesotech Rotary Sonar Data Product - SWEEP
49	Nortek Profiler Daily Currents Plot
52	Imagenex Data Product
56	Time Series Scalar VPS Cast Data Product
57	Satlantic Radiometer VPS Cast Data Product
58	Nortek Time Series VPS Cast Data Product
59	Satlantic ISUS VPS Cast Data Product
60	ASL AWCP VPS Cast Data Product
61	Time Series Scalar Profile Plot
62	Nortek ADCP Ensemble-Averaged Time Series
63	Image Set raw.zip
64	Image Set bmp.zip
65	Kongsberg Mesotech Rotary Sonar Data Product - SCAN

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

Time-stamps: Time-stamps are always in UTC. For file-names and string dates, the format conforms to the ISO8601 convention: yyyymmddTHHMMSS. In some cases, the millisecond portion may be added: yyyymmddTHHMMSS.FFFZ. Numerical time-stamps within data product files may follow a different format as noted on the data product pages. For instances, numeric time-stamps within MAT files are in the MATLAB serial date format. When resampling, the time-stamps are generally taken from the the centre of the resample interval.

File-names: 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 search, files are named as DEVICECODE_SENSORNAME_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where:

• DEVICECODE is a descriptive string unique to each instrument.
• SENSORNAME is the sensor name as it appears in data search, and is only included if a single-sensor data product was requested.
• The first yyyymmddTHHMMSSZ is the time-stamp (ISO8601 format) of the first data record in the file. The second yyyymmddTHHMMSSZ is the last time-stamp of data in the file. If the data is continuous, this second time-stamp can be redundant, therefore it may be omitted for some data products (this behaviour will be phased out). The time span of the data within the file may be considerably less than than the requested search time span. Instrument site-level searches are limited to the selected instrument deployment: use the 'All Available' option when selecting the time range to search for all of the data for the selected instrument and site. Note that file-name time-stamps may also have millisecond information: yyyymmddTHHMMSS.FFFZ, where 'FFF' are the milliseconds (this feature will be phased out).
• 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 cast time range and direction here.
• EXT is the file extension.

For a location search, files are named as STATIONNAME_DEVICECATEGORY_SENSORNAME_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where

• STATIONNAME is the station name, including node and station names 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 combined together for a long record of data.
• 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.