RDI ADCP Time Series
Data files for Teledyne RDI ADCPs are described here. Ancillary data (e.g., temperature, pitch, roll) are also available independently, through scalar data products, see time series scalar data and time series scalar plots.
Oceans 3.0 API filter: dataProductCode=RADCPTS
Revision History
- 2020304: netCDF file format update: added ancillary data (e.g. Beam Velocity, Correlations, Intensity), apply compression, and change format to netcdf4 classic.
- 20180501: New options added for three-beam solutions, screening and fish detection.
- 20150903: RDI files now use corrected heading/pitch/roll as specified by site and sitedevice meta data. RDI files with Earth co-ord data are rotated to the corrected heading or apply magnetic declination. These changes do not change the MAT/PNG/NC/PDF data products produced from RDI files other than the compassHeading/pitch/roll values within the MAT/NC files. These changes will allow RDI files to be made available.
- 20150601: Added bin-mapping options (None, nearest vertical, linear).
- 20150228: Depth cell / bin mapping added to correct range and velocity for tilt.
- 20141222: Heading correction rework (affecting ENU / uvw velocities): handle sites with null positions, mobile sensors, autonomous deployments, and better documentation of processing was done to the data.
- 20130317: Bug fixes, including making the number of dimensions of data structures fixed (trailing singleton dimensions are always dropped in MATLAB however).
- 20110328: NetCDF, CF1.5 compliant product released.
- 20110202: Correction for determination of ENU (with respect to true North) velocities. Prior code assumed ADCP was downward-facing. Updated code uses orientation or instrument to convert to ENU coordinates.
- 20100521: Derived backscatter added to MAT contents.
- 20100513: Initial NetCDF product released for RDI ADCPs, available in CF-1.4 compliant format.
- 20100218: MAT contents made more complete and descriptive
- 20091208: Initial RDI and MAT products released
Formats
This data is available as processed data in MAT and NETCDF formats. Content descriptions and example files are provided below.
Manufacturer's Raw Binary Format: .RDI Files
This binary format is specific to the manufacturer. Direct access to RDI files may be restricted until verified versions are available. When using Teledyne-RDI data acquisition software, data is normally stored in this way. Although we use custom-built drivers to communicate with our instruments, we can use the raw data in the log file to produce the RDI file which can be interpreted by Teledyne-RDI post-processing software. These files are usually pre-generated and stored in the archive for fast retrieval, otherwise they are made on the fly like most other data products.
To produce the file, the following requirements apply:
- A new RDI file is started at the beginning of each day, when the maximum records per file is exceeded, or when the driver is restarted (this should account for configuration changes, site changes, etc).
- Only records with valid checksums are included.
- The instrument date/time field is replaced using the NEPTUNE timestamp at the beginning of the log file (since this timestamp is more accurate than the instrument clock), and the checksum is recalculated.
- For Beam or Instrument co-ordinate data, heading/pitch/roll (EH/EP/ER) data in the variable length data header are replaced as specified by site and sitedevice metadata (replacing the often unreliable onboard compass) (the EZ sensor source value is changed to manual for each). For Earth co-ordinate data, only the heading is updated with the value from the site and sitedevice metadata, if the internal compass sensor is used, it is corrected for magnetic declination, else if the internal heading value is set manually, it is left alone. Also for Earth data, because the heading has changed, the North/South current velocities are rotated to the new heading. These changes do not change the velocities in the MAT/PNG/NC/PDF data products produced from RDI files, other than the compassHeading/pitch/roll values within the MAT/NC files. The original magnetic compass, pitch and roll maybe replaced by these fixed or external sensor values, however, users can access the original sensor data via scalar data products and services.
For users' information and interest, the site and sitedevice information is available through the device details pages, for example: http://dmas.uvic.ca/DeviceListing?DeviceId=20003. This information is also included in the metadata report that accompanies most data products.
This format is further described in the manufacturer's documentation.
The Teledyne-RDI software to read RDI files (winADCP) is available through their website, although it is not obvious how to download. There are also some questionable sites offering downloads that don't go anywhere except to potential malware. Users can request access through the Teledyne Marine Download Portal: https://tm-portal.force.com/TMsoftwareportal/s/ As always you can contact us for support, through the main website, on Oceans 3.0 or here: Contact Support.
Example: RDIADCP75WH17432_20131113T000000.000Z.rdi
Oceans 3.0 API filter: extension=rdi
Processed Data
ADCP Velocity Computation: Correction and Rotation to East-North-Up Co-ordinate System, Three-beam Solutions and Screening
MAT Files
MAT files (v7) can be opened using MathWorks MATLAB 7.0 or later. The file contains four structures: meta, adcp, config, and units. For short duration searches (less than one day) or short duration data returned, the files will be concatenated, otherwise, expect one file per RDI file. (RDI files can break in the middle of a day due to data quantity limits or configuration changes, otherwise there is one file per day. RDI files are used as a processing intermediary format.)
adcp: structure containing the ADCP data, having the following fields.
range: vector of distance to each bin centre. If bin mapping compensation for tilt is active, then the bins are moved so that ADCP.range is now the vertical range to the corrected bin centres (ADCP.range values are not changed by bin-mapping). See adcp.processingComments to see if bin mapping was applied. To calculate the depth of each velocity bin, use the following:
if strcmp(Config.orient, 'Up')
binDepth = Meta.depth - ADCP.range;
else
binDepth = Meta.depth + ADCP.range;
end
- corr: 3D matrix, correlation time-series for each bin
- intens: 3D matrix, intensity time-series for each bin (also known as received signal strength intensity or RSSI, multiply by 0.45 dB/count to convert to a relative dB scale)
- velocity: 3D matrix, corresponds directly to output of instrument and so depends on configuration coordinate system
- percentGood: 3D matrix, percent good time-series for each bin
- ens: vector, ensemble number (replaced ensFirst for averaged products)
- ensFirst: vector of the first ensemble number in an ensemble average (averaged products only, replaces ens).
- compassHeading: vector, containing the EH values from the RDI files. This is either the fixed value from site and sitedevice headings (if not null), or values from an assigned true heading mobile position sensor. If neither, then it defaults to the magnetic compass heading data.
- pitch: vector, containing the EP values from the RDI files. This is either the fixed value from site and sitedevice headings (if not null), or values from an assigned true heading mobile position sensor. If neither, then it defaults to the onboard pitch sensor data.
- roll: vector, containing the ER values from the RDI files. This is either the fixed value from site and sitedevice headings (if not null), or values from an assigned true heading mobile position sensor. If neither, then it defaults to the onboard roll sensor data.
- time: vector, timestamp in datenum format (obtained from time the reading reached the shore station)
- temperature: vector, temperature time-series
- salinity: vector salinity time-series, (may contain constant values depending on device configuration)
- pressure: vector, pressure time-series. From RDI manual: "Contains the pressure of the water at the transducer head relative to one atmosphere (sea level). Output is in
decapascals". Converted to decibar. Can be a fixed value depending on configuration and hardware. In the binary RDI files and raw data streams, negative pressure values wrap - this isn't documented. In winADCP, negative values are truncated to zeroes, while in our data products and parsers we unwrap them to express the negative values (negative pressures should only occur in test or erroneous data). - depth: vector, depth of the device below the water surface as measured by the device for each ping. Can be set to a fixed value by the ED command / device attribute. For fixed deployments, this value is replaced in the RDI file by our code with the site depth plus offset, which is also reported as meta.depth. If not a fixed location deployment where the device is autonomous or mobile, this value is unaltered. It will vary with the tide and movement.
- soundSpeed: vector speed of sound time-series, (may contain constant values depending on device configuration)
- uMagnetic (optional): 2D matrix, East velocity relative to magnetic North
- vMagnetic (optional): 2D matrix, North velocity relative to magnetic North
- processingCommments: a string documenting all of the processing steps done to produce adcp.u/v/w. Use
char(adcp.processingComments)
to print out the text. - processingOptions: a structure with the data product option set that was requested and what was actually done (not all options are available and maybe overriden at run time, this will be explained in the processingComments).
- velocity_sourceInfo: a string describing the source of data in adcp.velocity
- uvw_sourceInfo: a string describing the resulting final, rotated data in adcp.u/v/w
- magneticDeclination: value that can be applied to correct the compassHeading to true North
- binMappingOption: bin-mapping method applied as determined by the data product option chosen and data available.
- u: 2D matrix, East velocity relative to True North
- v: 2D matrix, North velocity relative to True North
- w: 2D matrix, Upward Velocity
- u_std, v_std, w_std: standard deviations for ensemble averaged u,v,w (averaged products only)
- u_count, v_count, w_count: the number of ensembles/pings that contributed to u,v,w (averaged products only). Differs from pingsPerEnsemble in that it accounts for filtered / NaN-ed data
- velocityError: 2D matrix, computed using RDI algorithm
- backscatter: 3D matrix based on received signal strength intensity (adcp.intensity), compensated for two-way spreading (20LogR) and absorption. Equation based on Gostiaux and van Haren ("Extracting Meaningful Information from Uncalibrated Backscattered Echo Intensity Data, Journal of Atomsheric and Oceanic Technology, 72, 943-949, 2010). The absorption computation follows Ainslie and Malcolm ("A simplified formula for viscous and chemical absorption in sea water", Journal of the Acoustical Society of America, 103(3), 1671-1672, 1998). Absorption coefficient based on mean depth, temperature and salinity in adcp structure.
- meanBackscatter: same as above, except averaged over the four beams to create a 2D matrix. Averaging is done by converting to standard intensity, averaging, then converting back to decibels.
config: structure containing ADCP configuration details, where some field names are appended with '_XX' to represent the corresponding configuration command (beneficial for experienced RDI ADCP users).
- fwVer: CPU firmware version
- fwRev: CPU firmware revision
- sysCfg: hardware configuration definition
- freq: frequency
- beamPattern: convex or concave
- orient: orientation (e.g.,'Up' indicates transducers are looking upward)
- beamAngle: beam angle
- janusCfg: description of Janus Configuration
- lagLength: time period between sound pulses
- nbeams: number of beams
- nbins_WN: number of bins
- npings_WP: number of pings per ensemble
- cellSize_WS: length per cell
- profilingMode: sigal processing mode
- corrThresh_WC: correlation threshold
- codeReps: code repetitions in transmit pulse
- percentGoodMin_WG: percent good threshold
- errVelThreshold_WE: error velocity threshold
- timePing_TP: time between pings within ensemble
- coord_EX: coordinate transformation processing parameters
- coordSys: coordinate system (evaluated from coord_EX)
- headingAlign_EA: correction factor for physical heading misalignment
- headingBias_EB: correction factor for electrical/magnetic heading bias
- heading_EH: manual setting of the heading from device attributes (not in RDI file, added after)
- sensorSrc_EZ: defines selected source of environmental sensor data
- sensorAvail: defines available sources of environmental sensor data
- bin1Dist: distance to the middle of the first depth cell
- transmitLength_WT: length of the transmit pulse
- falseTrgt_WA: false target threshold
- transmitLagDistance: distance between pulse repetitions
- cpuSN: CPU board SN
- sysBndwdth_WB: bandwidth setting (narrow or wide)
- sysPower_CQ: system power setting
- instSN: instrument serial number
- ensInterval: ensemble interval
- ambiguityVelocity_WV: radial ambiguity velocity (not in RDI, added after)
- soundAbsorptionCoefficient: sound absorption coefficient used for computing backscatter
units: structure containing unit of measure for fields in structures above. For instance, units.pressure='decibar'.
For details about the configuration parameters, refer to the manufacturer documentation (especially the WorkHorse Commands and Output Data Format manual).
Example: RDIADCP75WH3808_20101106T000225.mat
Oceans 3.0 API filter: extension=mat
NETCDF Files
NetCDF is a machine-independent data format offered by numerous institutions, particularly within the earth and ocean science communities. Additional resources are noted here. For short duration searches (less than one day) or short duration data returned, the files will be concatenated, otherwise, expect one file per RDI file. (RDI files can break in the middle of a day due to data quantity limits or configuration changes, otherwise there is one file per day. RDI files are used as a processing intermediary format.)
The RDI NetCDF file is extracted from the data contained in the above MAT file. The NetCDF file contains the following main variables: u, v, w, time, binmap_depth, where the binmap_depth variable here is distinct from the pressure sensor measurement in the MAT file (adcp.depth). When there is bin-mapping performed on the data, the binmap_depth is calculated as meta.depth - adcp.range; it is the approximate water depth at which the measurement bins are located. If bin-mapping is 'none', then the binmap_depth and the depth are equal. depth is calculated as meta.depth - adcp.backscatterVerticalRange, which is the range corrected for tilt. depth is used to plot the beam-averaged backscatter and any other beam-averaged values that are not bin-mapped. The structure and content of the netCDF file is very similar to that of the MAT file, including the variable naming. The RDI and Nortek netCDF files are intended to be very similar, even interchangeable with the same structure and definitions.
The NetCDF files are intended to be in compliance with the CF-1.7 standard. Depending on the compliance checker that is used the data may not meet this standard for the following reasons: The units dB are not defined, and the feature type of the data is not defined.
Oceans 3.0 API filter: extension=nc
Example: RDIADCP75WH17575_20130314T194500Z_20130502T164500Z-Ensemble900s_binMapNearest.nc
>> ncdisp('C:\Users\ONC\Test\RDIADCP75WH17575_20130314T194500Z_20130502T164500Z-Ensemble900s_binMapNearest.nc')
Source:
C:\Users\ONC\Test\RDIADCP75WH17575_20130314T194500Z_20130502T164500Z-Ensemble900s_binMapNearest.nc
Format:
netcdf4_classic
Global Attributes:
Conventions = 'CF-1.7'
title = 'Ocean Networks Canada Teledyne-RDI ADCP Data'
institution = 'Ocean Networks Canada'
source = 'Fixed-position Teledyne-RDI ADCP 75 kHz'
references = 'https://www.oceannetworks.ca/'
comment = 'Detailed documentation: https://wiki.oceannetworks.ca/display/DP/5'
history = 'Includes data extracted from raw output, minimally processed, and processed data'
processing_comments = 'adcp.velocity(1:3,:,:) contains velocity data relative to the co-ordinate system 'Earth'. acdp.velocity(4,:,:) is the RDI error velocity. adcp.u/v/w are processed velocities relative to true East/North/up, respectively. This device does not have a mobile heading sensor or a fixed heading; using onboard magnetic compass for heading (magnetic declination will be applied). Overriding requested option: correlation screening cannot be applied to Earth co-ordinate data that has already been bin-mapped. Beam range bins were corrected for tilt by nearest vertical bin-mapping (RDI method) onboard the device (new pitch/roll values not applied). Average or fixed tilt is 57.1483 degrees (for information only, averages are not used in correction). adcp.range is the vertical range to the corrected bin centres. Error velocity screening not applied to Earth co-ordinate data unchanged; screening applied onboard used a more stringent threshold than the user selected value. Device-supplied adcp.u/v/w unchanged from RDI file data (adcp.velocity); heading rotation correction done in post-processed RDI file.adcp.backscatter (relative volume backscattter) calculated from 0.45*adcp.intens + 20*log10(adcp.range) + 2*config.soundAbsorptionCoefficient*adcp.range, adcp.meanBackscatter calculated by beam-averaging the volume backscatter (accounting for dB scale). adcp.meanBackscatter and adcp.backscatter have units of relative dB. Ensemble file created by box-car average resampling to a ensemble interval of 900 seconds (raw data ensemble interval: 3.7 seconds). adcp.intens was average normally, while adcp.backscatter and adcp.meanBackscatter were averaged by first converting the logarithmic dB scale to linear, averaging, then converting back.For information on the various processing steps applied, see https://wiki.oceannetworks.ca/display/DP/5. '
CREATION_DATE = '20210927T201853Z in QA'
time_coverage_start = '20130314T195230Z'
time_coverage_end = '20130502T163730Z'
device_id = 23066
device_heading = NaN
platform_depth = -20
site_name = 'MTC NEPTUNE Integration Lab'
device_name = 'RDI Workhorse Long Ranger ADCP 75 kHz (17575)'
location_name = 'Marine Technology Centre'
search_id = 875050
firmware_version = 50
firmware_revision = 40
frequency = 75
beam_pattern = 'Convex'
orientation = 'Up'
beam_angle = 20
adcp_setup_CQ_sysPower = 255
adcp_setup_TE_ensemble_interval_sec = 900
adcp_setup_TP_time_ping_sec = 0
adcp_setup_WA_false_target_threshold = 255
adcp_setup_WB_system_bandwidth = 0
adcp_setup_WC_correlation_threshold = 0
adcp_setup_WE_error_threshold = 0
adcp_setup_WE_blanking_distance_meters = 7.04
adcp_setup_WG_percent_good_minimum = 0
adcp_setup_WN_number_bins = 80
adcp_setup_WP_number_pings = 1
adcp_setup_WS_cell_size_meters = 8
adcp_setup_WT_transmit_length = 8.25
Dimensions:
time = 4692
depth = 80
latitude = 1
longitude = 1
Variables:
time
Size: 4692x1
Dimensions: time
Datatype: double
Attributes:
sdn_parameter_name = 'time'
long_name = 'time'
units = 'days since 19700101T000000Z'
axis = 'T'
calendar = 'gregorian'
binmap_depth
Size: 80x1
Dimensions: depth
Datatype: single
Attributes:
sdn_parameter_name = 'depth'
long_name = 'water depth of final velocity measurement bins'
units = 'meters'
axis = 'Z'
positive = 'down'
comment = 'Water depth for the u (east), v (north), w (up), velocityError seawater velocity bins, accounting for bin-mapping'
depth
Size: 80x1
Dimensions: depth
Datatype: single
Attributes:
sdn_parameter_name = 'depth'
long_name = 'water depth of beam-averaged measurement bins, tilt-corrected'
units = 'meters'
axis = 'Z'
positive = 'down'
comment = 'Water depth of measurement bins corrected for tilt, applies to meanBackscatter (beam-averaged backscatter)'
range
Size: 80x1
Dimensions: depth
Datatype: single
Attributes:
sdn_parameter_name = 'range'
long_name = 'range from transducer'
units = 'meters'
axis = 'Z'
comment = 'Range of measurement bins from the transducer, applies to all parameters except: u, v, w, velocityError when bin-mapping is on'
latitude
Size: 1x1
Dimensions: latitude
Datatype: single
Attributes:
sdn_parameter_name = 'latitude'
long_name = 'latitude'
units = 'degrees_north'
axis = 'Y'
longitude
Size: 1x1
Dimensions: longitude
Datatype: single
Attributes:
sdn_parameter_name = 'longitude'
long_name = 'longitude'
units = 'degrees_east'
axis = 'X'
u
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'eastward_sea_water_velocity'
long_name = 'eastward sea water velocity'
units = 'meters/second'
_FillValue = -9999999
v
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'northward_sea_water_velocity'
long_name = 'northward sea water velocity'
units = 'meters/second'
_FillValue = -9999999
w
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'upward_sea_water_velocity'
long_name = 'upward sea water velocity'
units = 'meters/second'
_FillValue = -9999999
velocityError
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'indicative_error_from_multibeam_acoustic_doppler_velocity_profiler_in_sea_water'
long_name = 'acoustic doppler current profiler error velocity'
units = 'meters/second'
_FillValue = -9999999
meanBackscatter
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_nam = 'sound_intensity_level_in_water'
long_name = 'acoustic doppler current profiler beam-averaged corrected acoustic backscatter'
units = 'dB'
_FillValue = -9999999
comment = 'beam averaged and corrected for two-way beam spreading and attenuation, not bin-mapped, use with tilt-corrected water depth'
intens_beam1
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'signal_intensity_from_multibeam_acoustic_doppler_velocity_sensor_in_sea_water'
long_name = 'acoustic doppler current profiler return signal strength intensity beam 1'
units = 'counts'
_FillValue = -9999999
intens_beam2
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'signal_intensity_from_multibeam_acoustic_doppler_velocity_sensor_in_sea_water'
long_name = 'acoustic doppler current profiler return signal strength intensity beam 2'
units = 'counts'
_FillValue = -9999999
intens_beam3
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'signal_intensity_from_multibeam_acoustic_doppler_velocity_sensor_in_sea_water'
long_name = 'acoustic doppler current profiler return signal strength intensity beam 3'
units = 'counts'
_FillValue = -9999999
intens_beam4
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'signal_intensity_from_multibeam_acoustic_doppler_velocity_sensor_in_sea_water'
long_name = 'acoustic doppler current profiler return signal strength intensity beam 4'
units = 'counts'
_FillValue = -9999999
corr_beam1
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'beam_consistency_indicator_from_multibeam_acoustic_doppler_velocity_profiler_in_sea_water'
long_name = 'acoustic doppler current profiler correlation magnitude beam 1'
units = 'counts'
_FillValue = -9999999
corr_beam2
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'beam_consistency_indicator_from_multibeam_acoustic_doppler_velocity_profiler_in_sea_water'
long_name = 'acoustic doppler current profiler correlation magnitude beam 2'
units = 'counts'
_FillValue = -9999999
corr_beam3
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'beam_consistency_indicator_from_multibeam_acoustic_doppler_velocity_profiler_in_sea_water'
long_name = 'acoustic doppler current profiler correlation magnitude beam 3'
units = 'counts'
_FillValue = -9999999
corr_beam4
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'beam_consistency_indicator_from_multibeam_acoustic_doppler_velocity_profiler_in_sea_water'
long_name = 'acoustic doppler current profiler correlation magnitude beam 4'
units = 'counts'
_FillValue = -9999999
percentGood_beam1
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'proportion_of_acceptable_signal_returns_from_acoustic_instrument_in_sea_water'
long_name = 'acoustic doppler current profiler percent good beam 1'
units = 'percent'
_FillValue = -9999999
percentGood_beam2
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'proportion_of_acceptable_signal_returns_from_acoustic_instrument_in_sea_water'
long_name = 'acoustic doppler current profiler percent good beam 2'
units = 'percent'
_FillValue = -9999999
percentGood_beam3
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'proportion_of_acceptable_signal_returns_from_acoustic_instrument_in_sea_water'
long_name = 'acoustic doppler current profiler percent good beam 3'
units = 'percent'
_FillValue = -9999999
percentGood_beam4
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'proportion_of_acceptable_signal_returns_from_acoustic_instrument_in_sea_water'
long_name = 'acoustic doppler current profiler percent good beam 4'
units = 'percent'
_FillValue = -9999999
velocity_beam1
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'radial_sea_water_velocity_away_from_instrument'
long_name = 'radial velocity beam 1'
units = 'meters/second'
_FillValue = -9999999
velocity_beam2
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'radial_sea_water_velocity_away_from_instrument'
long_name = 'radial velocity beam 2'
units = 'meters/second'
_FillValue = -9999999
velocity_beam3
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'radial_sea_water_velocity_away_from_instrument'
long_name = 'radial velocity beam 3'
units = 'meters/second'
_FillValue = -9999999
velocity_beam4
Size: 80x4692
Dimensions: depth,time
Datatype: single
Attributes:
sdn_parameter_name = 'radial_sea_water_velocity_away_from_instrument'
long_name = 'radial velocity beam 4'
units = 'meters/second'
_FillValue = -9999999
temperature
Size: 4692x1
Dimensions: time
Datatype: single
Attributes:
sdn_parameter_name = 'sea_water_temperature'
long_name = 'sea water temperature'
units = 'K'
_FillValue = -9999999
pitch
Size: 4692x1
Dimensions: time
Datatype: single
Attributes:
sdn_parameter_name = 'platform_pitch_angle'
long_name = 'pitch'
units = 'degrees'
_FillValue = -9999999
roll
Size: 4692x1
Dimensions: time
Datatype: single
Attributes:
sdn_parameter_name = 'platform_roll_angle'
long_name = 'roll'
units = 'degrees'
_FillValue = -9999999 |
Above example may be out of date. Recent changes include: added compass heading, updated units. |
Discussion
To comment on this product, click Add Comment below.