Level 1 data (velocity profilers): Difference between revisions

From Atomix
Line 103: Line 103:
| {{FontColor|fg=red|text=can't remember}}
| {{FontColor|fg=red|text=can't remember}}
|-
|-
| colspan="4" |  
| colspan="4" style="text-align:center; font-weight:bold; background-color:#f9eddd" | '''Optional variables for 5-beam ADCP'''<math>\dagger</math>
<math>\dagger\dagger</math> Variable required only when measuring in bursts e.g., 18 min of continuous measurements every hour.
|-
|}
| RVEL5
| radial_velocity_of_scatterers_toward_instrument_of_beam_5
| TIME, R_DIST5
| Units in m/s
|-
| colspan="4" | <math>\ddagger</math> Quality-control variable names are consistent for those onboard RDI Teleydyne ADCPs. {{FontColor|fg=white|bg=red|text= Not sure for Nortek, perhaps they use the same as their Vectors}} detailed in the [[Level_1_data_(velocity_point-measurements)#Variables|ADV Level 1 variables]].


<math>\ddagger</math> Quality-control variable names are consistent for those onboard RDI Teleydyne ADCPs. {{FontColor|fg=white|bg=red|text= Not sure for Nortek, perhaps they use the same as their Vectors}} detailed in the [[Level_1_data_(velocity_point-measurements)#Variables|ADV Level 1 variables]].
<math>\dagger</math> 5-beam ADCPs has the 5th beam usually pointing directly up with its own bin sampling height, and may also be sampled at a different rate. In these situations, the data must be stored in separate variables given the different dimensions assigned. Simply append the number 5 to the variable name (e.g., TIME5)
}
</div>
</div>



Revision as of 20:34, 15 December 2021

Page status: Draft
Author(s): Cynthia
Reviewer(s):
Comment:


{{#default_form:ReviewStage}} {{#arraymap:Draft|,|x||}} {{#arraymap:Velocity profilers|,|x||}}

The required dimensions and variables for the first processing level within NetCDF ATOMIX format for ADCP velocity measurements are described below. This processing level contains the raw measurements recorded by the instrument. If sampling is in burst mode, the measurements from individual bursts are appended together.

Only a few attributes for each variable are listed since the page's purpose is to describe the information layout within each NetCDF file. Please refer to the complete list for the additional attributes related to each variable.

Dimensions


Short name Standard name Dimensions Comments
TIME time TIME Units in Days since 1950-01-01T00:00:00Z
R_DIST distance_from_sensor_along_beams R_DIST along-beam bin centre distance (in meters) from the transducer 
N_BEAM unique_identifier_for_each_beam N_BEAM Array of 1 to number of beams (4 or 5 typically)
Optional dimensions
R_DIST5 distance_from_sensor_along_beam_5 R_DIST5 along-beam bin centre distance (in meters) from the 5th beam, which is usually aligned with vertical axis of the ADCP. 

Variables


Required variables

Short name Standard name Dimensions Comments and units
RVEL radial_velocity_of_scatterers_toward_instrument_in_each_beam TIME, R_DIST, N_BEAM Units in m/s
THETA beam_angle_from_instrument_z_axis TIME, N_BEAM Units in degrees, positive (usually ~20-30o)
BIN_SIZE instrument_measurement_volume_bin_size N_BEAM vertical size of the ADCP bins. Usually the same for all 4 beams, but 5th beam can vary.
BURST_NUMBER unique_identifier_for_each_burst TIME Integers of 1, 2, etc to designate which burst the velocities are associated with. Can set all to 1 if continuously sampled.
Platform motion variables
HEADING platform_yaw_angle TIME degrees, clockwise from true North
PITCH platform_pitch_angle TIME degrees
ROLL platform_roll_angle TIME degrees
Quality-control variables usually available with acoustic-Doppler instruments <math>\ddagger</math>
ABSI backscatter_intensity_from_each_acoustic_beam TIME, R_DIST, N_BEAM db
CORR correlation_magnitude_from_each_acoustic_beam TIME, R_DIST, N_BEAM can't remember
Optional variables for 5-beam ADCP<math>\dagger</math>
RVEL5 radial_velocity_of_scatterers_toward_instrument_of_beam_5 TIME, R_DIST5 Units in m/s
<math>\ddagger</math> Quality-control variable names are consistent for those onboard RDI Teleydyne ADCPs. Not sure for Nortek, perhaps they use the same as their Vectors detailed in the ADV Level 1 variables.

<math>\dagger</math> 5-beam ADCPs has the 5th beam usually pointing directly up with its own bin sampling height, and may also be sampled at a different rate. In these situations, the data must be stored in separate variables given the different dimensions assigned. Simply append the number 5 to the variable name (e.g., TIME5) }


Return to Dataset requirements for ADCP structure function

Go to Level 2 quality-controlled and segmented velocities