Exporting single target data
Single target values can be exported to a comma-separated values file (*.target.csv). The export file will contain the properties for each single target.
Single target data may be read from a data file or may arise from Echoview single target detection.
Generally,
- you perform the export on a single targets echogram (rather than a Sv echogram, TS echogram etc)
- the echogram should have at least one region defined and visible on the echogram
Note: Single target variables can be derived from multibeam target detection variables. When such a target.csv file is added to an EV file, its Dataflow object is created in a special way. See the Performance tip note for more information.
To export single targets for an echogram:
- On the Echogram menu, point to Export, and then click Single Target to CSV.
- On the export dialog box, specify the Export options.
- Click Export...
To export single targets for a region:
- Select the region.
- On the Shortcut menu (right-click), point to Export Region, and then click Single Targets....
To export single targets for a selection:
- Make a selection using any selection tool.
- On the Shortcut menu (right-click), point to Export Selection, and then click Single Target to CSV
- On the export dialog box, specify the Export options.
- Click Export...
Single target file format (*.target.csv)
Single target data for a selection, region or entire echogram can be exported into a .csv file. The .target prefix is added to the csv file extension (e.g., filename.target.csv) to identify single targets exports from other data exports.
The first line of the .csv file lists the variables that are exported (these will be used as column headings if the file is loaded into a spreadsheet program). Each subsequent line contains the value for each variable for each single target detection.
The single targets Analysis by Regions or by Cells or by Regions by Cells (*.csv) output a subset of the listed export variables.
Note: Exported single target values from complex single target data represent the magnitude of the power scaled by TS algorithm values (that account for TVG, two-way absorption and system and transducer constraints).
Variable |
Description |
Ping_date |
See Single targets variables and Automatically exported variables for descriptions. |
Ping_time |
|
Ping_milliseconds |
|
Target_on_axis_depth under Echogram depth mode |
|
Target_range |
|
TS_comp |
|
TS_uncomp |
|
Angle_minor_axis* |
|
Angle_major_axis* |
|
PulseLengthDeterminationLevel |
|
Samples_above_PLDL |
|
StandDev_angles_minor_axis |
|
StandDev_angles_major_axis |
|
PulseLength_normalized_6dB |
|
PulseLength_normalized_12dB |
|
PulseLength_normalized_18dB |
|
PulseLength_normalized_PLDL |
|
Pulse_start_normalized_6dB |
|
Pulse_start_normalized_12dB |
|
Pulse_start_normalized_18dB |
|
Pulse_start_normalized_PLDL |
|
Pulse_duration |
|
Target_true_depth |
|
Target_latitude |
|
Target_longitude |
|
Target_northing |
|
Target_easting |
|
Exclude_below_line_depth+ |
|
Target_length |
|
Target_length_uncompensated |
|
Target_length_manual |
|
Target_perimeter |
|
Target_perimeter_edge_midpoints |
|
Target_area |
|
Target_area_edge_midpoints |
|
Target_intensity_variation |
|
Target_compactness |
|
Target_compactness_edge_midpoints |
|
Target_thickness |
|
Target_length_across_beams |
|
Target_range_extent |
|
Ping number |
|
Target_class |
|
Target_orientation |
* For targets derived from multibeam data the angular position is derived for the geometric center of the multibeam target.
+ A value is exported if an Exclude below line is selected on the Analysis page of the Variable Properties dialog box. Otherwise, the value is set to the no data export value.
Notes:
- For targets derived from multibeam data, the existence of some exported variables relies on the selection of the target property on the Target page of the Variable Properties dialog of the Multibeam target detection virtual variable. Refer to Target properties from multibeam data for more information.
- To ensure that target data is exported accurately, your pings must be in consecutive temporal order.
- Single targets are exported in ping and depth order.
- When adding single target export data to an EV file consider the issues raised in Note: transducer geometry.