Text data files

Text data files in Echoview are comma-separated values (.csv) used to:

  • Add external data to a fileset (for example GPS fixes, single targets, lines); or
  • Export raw or derived data values from Echoview.

This page defines the core CSV formats and their stable, reference format definitions (extensions, Fileset support, row granularity, units/no-data conventions, and—where applicable—required/optional columns). Other topics link here for format details so we avoid duplicate definitions.

Looking for time series analysis to CSV? CSVs produced by Interval analysis operators are documented in the Time series analysis CSV section below.

Looking for analysis exporters? CSVs produced by analysis exporters (columns vary by domain and settings—e.g., Intervals/Regions/Cells, tall vs wide layouts, frequency bins) are documented in the Analysis exporter CSVs section below.

Core formats fall into two categories:

  • Fileset-compatible — can be added to a fileset and used as input variables.
  • Export-only — produced for downstream analysis, visualization, or archiving.

Each format entry includes:

  • Extensions (e.g., *.sv.csv, *.target.csv)
  • Add to a fileset? Fileset-compatible or Export-only
  • Row granularity (per ping, per sample, per target, etc.)
  • Required and Optional columns
  • Units & no-data conventions
  • Export method (where to find the command)

Notes:

  • Measurement exporters with unique formats: Measurements – complex data, Measurements – georeferenced samples, and Measurements – underlying data are documented in their own sections. Measurements – CSV is an alternate export entry point that writes the same CSV structure as the operand variable (it does not define a separate CSV format). The advantage of the exporter is that it allows you to specify, record, and repeat an export.

Conventions:

  • CSV is read/written as UTF-8.
  • A header row is required. Column order is not important; unrecognized columns are ignored (exception: the TS substitution operator can reference extra custom columns in Single target CSVs).
  • Times are UTC. Recommended formats: yyyy-MM-dd and HH:mm:ss (optional milliseconds).
  • Ping numbering: Unless otherwise noted, Ping_index values are renumbered by Echoview beginning at 0.
  • No-data values: unless a format section says otherwise, no-data values export as -9.9e+37.

Note: For a categorized list of all exportable file types in Echoview (including image, HAC, MATLAB, and other non-CSV formats), see Export file formats. This page focuses on CSV structure only.

For instructions on exporting from graphs, tables, and echograms, see Exporting data or underlying data. For exporter-driven CSVs (Intervals/Regions/Cells, spectra, etc.) see Analysis CSV exporters. See also About data types for an overview of variable types referenced by these CSVs.

On this page:

Quick reference: Measurement exporters with CSV formats

Measurement exporters: These are alternate export entry points. In general, they do not define new CSV formats—they write the same CSV structures (e.g., column definitions, header naming conventions) described on this page, based on the data type of the operand. Measurement exporters offer the advantages of repeatability and a record of a data export, with settings to control measurement ranges and file size.

Measurement exporter Writes CSV format of… Documented in Notes
Measurements – CSV Same format as the linked variable Core CSV formats (this page) No unique format - file format is guided by the data type of the operand (including time series collections). This measurement exporter handles both echogram and time series data. See also: Use of Measurements - CSV.
Measurements – complex data Complex data CSV Complex data Real/Imaginary components, export-only.
Measurements – georeferenced samples Georeferenced samples (3D points) Georeferenced samples Per-sample Lat/Lon/Depth; export-only.
Measurements – underlying data Raw underlying sample stream (device/linear units) Measurements – underlying data Minimal header; export-only; only available for variables that expose an underlying stream.

Working with text data files

When adding a CSV file to a fileset, Echoview uses the header row to identify recognized fields. A header row is required. Column order is not important; unrecognized columns are ignored unless otherwise documented for a specific format.

CSV files may be created manually or generated by external applications, provided they conform to the definitions below.

Date and time: Times are interpreted as UTC. Use unambiguous formats. Recommended: yyyy-MM-dd for dates and HH:mm:ss for times (optionally with milliseconds).

General conventions:

  • Use a period (.) as the decimal separator. Avoid thousands separators.
  • Quoted fields are supported when needed (for example, values containing commas).
  • When navigation is unavailable, Latitude / Longitude may be present with a no-data values (commonly 999.0). Treat these as no position.

Notes:

  • Some exports include optional columns. If added to a fileset, unrecognized columns are ignored.
  • Prior to Echoview 4.90, a bug affected the interpretation of field names in CSV files. This may impact EV files created before 4.90 that reference those names. See Echoview 4.90 bug fix documentation.
  • See also About exporting data.

Tip: Only formats marked as Fileset-compatible can be added to a fileset by creating a new fileset and adding the file to the Filesets window. See the quick reference table for fileset support.

Core CSV formats

Format Extension(s) Add to a fileset? Notes
Bottom points *.bottom.points.csv No Seafloor detections (points)
Complex data *.complex.csv No Wideband and pulse-compressed
Current velocity *.currentvelocity.csv Yes Fileset-compatible
Depth values *.depth.csv Yes Sampled line depths (export)
Georeferenced samples (3D points) *.sv.points.csv
*.ts.points.csv
*.db.points.csv
*.power.points.csv
*.sv.mb.points.csv
*.angles.mb.points.csv 		No Includes Lat/Lon/Depth
GPS fix data *.gps.csv Yes Fileset-compatible
Heading *.heading.csv Yes Bearing time series
Length data *.length.csv Yes Length/time series
Line data *.line.csv Yes Ping-by-ping line depths
Matrix data (multibeam) *.sv.mmb.csv
*.ts.mmb.csv
*.angle.mmb.csv
*.db.mmb.csv
 No One row per ping; flattened matrix
Multibeam magnitude *.mag.mb.csv No Beamformed magnitude (export)
Multibeam phase *.phase.mb.csv No Beamformed phase (export)
Multibeam Sv *.sv.mb.csv No Formed-beam Sv (export)
Multibeam targets *.targets.mb.csv No Detections/metrics (export)
Pitch *.pitch.csv Yes Pitch time series
Power data *.power.csv No Raw power in dB (export)
Region log book *.regions.csv No Metadata list; same suffix as summary
Roll *.roll.csv Yes Roll time series
Single beam data *.sv.csv
*.ts.csv
*.angles.csv
*.linear.csv
*.boolean.csv
*.db.csv
 Yes Sample-based (fileset-compatible)
Single target detections *.target.csv Yes One row per target
Speed *.speed.csv Yes Speed-through-water
Time series collection *.table.csv Yes Authored externally and added to a fileset, or exported from a time series collection variable (for example, the output of the Collate time series operator or transmission characteristics collections). Represents a multi-series table. To export a single time series, derive a time series with Time series select and export that variable.
Transect definitions *.transect.csv Yes Restorable definitions
Transmission time series select *.csv No Transducer transmission characteristic voltage/current/impedance/phase; legacy “Impedance statistic”
Underlying data *.csv No Raw underlying sample stream (device/linear units); minimal header; only for variables that expose an underlying stream
Unspecified time series *.custom.csv No Export from Time series select (output type: Unspecified time series); time-stamped values with status; export-only.
Vessel logs *.logs.csv No Distance log (export)

Time series analysis CSV

Time series analysis Domain(s) Row granularity Output Layout Add to fileset? Notes
Analysis time series (*.analysis.csv) Intervals Per interval Tall No Time series of a specified analysis variable within a specified interval.
Calibration time series (*.calibration.csv) Intervals Per interval Tall No Time series of a specified calibration setting within a specified interval.

Bottom points (*.bottom.points.csv)

Description: Spatial point detections of the seafloor derived from single-beam or multibeam data. Each row is one bottom detection. Export-only (not able to be added to a fileset).

Export methods:

  • Dataflow window: Right-click a Bottom classification variable and select Export, To CSV….
  • Table: With the Bottom classification table open, choose Table menu, Export to CSV...

Typical columns:

  • Ping_index — Ping associated with the detection
  • Sample_index — Sample index of the detection
  • Depth_m — Bottom depth (m)

Optional columns:

  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Latitude, Longitude — Geographic coordinates (°)
  • Beam_index — Beam number (for multibeam)

Use case: Mapping bottom topography, validating bottom-detection performance, or exporting spatial references for external GIS/analysis tools.

Notes: Coordinates refer to the GPS antenna position (if available). Column order is not important; unrecognized columns are ignored. This format is not supported for addition to filesets.

See also: Exporting data or underlying data

Complex data (*.complex.csv)

Description: Exports the Real and Imaginary components of complex-valued sample data from wideband or pulse-compressed variables. Applies to complex Sv, complex TS, complex angular position, and complex power dB. Each record provides ping metadata plus a list of sample values for one component (Real or Imaginary). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click a complex data or pulse-compressed complex data variable, then choose Export, Complex Data Values.... Region-based and selection exports are supported.
  • Dataflow Toolbox: Drag a Measurements – complex data exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click the exporter to write the file (this Measurement exporter writes the same CSV format described in this section).
  • Echogram: With a complex data or pulse-compressed data variable echogram activated, select the Echogram menu, then Export, Complex Data...
  • Table: With the Complex variable table window activated, select the Table menu, then Export to CSV...

Typical columns:

  • Ping_index — Sequential ping number (starting at 0)
  • Component — Real or Imaginary (two rows per ping, one per component)
  • Distance_gps, Distance_vl — Cumulative distances (nmi; optional)
  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Latitude, Longitude — GPS antenna position (°; optional)
  • Depth_start, Depth_stop — Ping depth bounds (m)
  • Range_start, Range_stop — Range bounds (m)
  • Sample_count — Number of samples in the ping
  • Data values… — Comma-separated Real or Imaginary sample values (linear units), appended after the metadata

Use case: External signal processing where full phase and amplitude are required (e.g., beamforming, matched filtering, coherence analysis).

Notes: Values are in linear units (not dB). Exclusion lines are honored; excluded samples export as no data. If the number of data values does not match Sample_count, the ping is ignored. Column order is not important; unrecognized columns are ignored. See also Exporting complex data.

Current velocity (*.currentvelocity.csv)

Description: Sample-based velocity values (one row per ping) exported from a current-velocity variable. Fileset-compatible; can be added to a fileset as a raw Current velocity variable.

Export methods:

  • Dataflow window: Right-click the current velocity variable in the Dataflow window, then choose Export, To CSV….
  • Echogram: With the current velocity echogram activated, click on the Echogram menu, then Export, Velocity Values to CSV...
  • Table: While the current velocity table is activated, click on the Table menu, select Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Ping_index — Sequential ping number
  • Distance_gps, Distance_vl — Cumulative distances (nmi) from GPS and vessel log
  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Latitude, Longitude — Position (°) of the ping
  • Depth_start, Depth_stop — Ping depth bounds (m)
  • Range_start, Range_stop — Range from transducer (m)
  • Sample_count — Number of depth samples in the ping
  • Data values… — Current velocity samples (m·s-1), one per depth sample; count = Sample_count

Use case: Add to a fileset/export water-column velocity profiles for comparison with external sensors/models, QA of derived velocities, or downstream flow and transport analyses.

Notes:

  • Rows follow the standard convention: metadata fields first, then the list of sample values. Column order is not important; unrecognized columns are ignored.
  • If the number of data values does not match Sample_count, that ping is ignored.
  • Exclusion lines are honored; excluded samples export as no data (e.g., -9.9e+37).
  • Units are m·s-1. Sign convention follows the source instrument/data; Echoview does not change sign on export.

Depth (*.depth.csv)

Description: Time-stamped depth measurements (meters). Files in this format can be added to a fileset and used as a raw Depth time-series variable.

Export methods:

  • Dataflow window: Right-click a Depth variable in the Dataflow window, then select Export, Data Values...
  • Graph: With the depth variable Graph window activated, select the Graph menu, Export Data Values...
  • Table: With the depth variable Table window activated, select the Table menu, Export Data Values...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Depth_index — Sequential index
  • Depth_date — yyyy-MM-dd
  • Depth_time — HH:mm:ss
  • Depth_milliseconds — 0–999
  • Depth_meters — Depth value (m)
  • Depth_status — Status for the measurement between this value and the next

Use case: Trend and QC platform/transducer depth; use as a driver for depth-aware processing or overlays.

Notes: This is a time-series format (support by filesets). To export or round-trip line depths by ping, use Line data (*.line.csv). Also exportable to *.evd.

Georeferenced samples (3D points) (*.sv.points.csv, *.ts.points.csv, etc.)

Description: Exports sample-level 3D points with geographic coordinates from acoustic variables. Each row corresponds to one sample and can include latitude, longitude, depth, altitude, and related metadata. Supports single-beam and multibeam variables. Export-only (not supported by filesets).

Export methods:

  • Echogram: Open the echogram of an acoustic variable, select Echogram from the menu, then Export, Georeferenced Samples (Region-based and selection exports are supported.)
  • Dataflow Toolbox: Drag a Measurements – georeferenced samples exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click the exporter to write the file (this Measurement exporter writes the same CSV format described in this section).

Typical columns:

  • Ping_index — Ping index
  • Latitude — Geographic latitude (°)
  • Longitude — Geographic longitude (°)
  • Depth — Sample depth (m)
  • Altitude — Height above the seafloor (m)
  • Sample_value — Backscatter/intensity value

Optional columns:

  • Beam_index — Beam number (multibeam only)
  • Sample_index — Sample number along the beam
  • Range_m — Slant range to sample (m)
  • Region_ID — Region label when exporting by region
  • Date, Time, Milliseconds — UTC timestamp fields
  • Distance_gps, Distance_vl — Cumulative distances (nmi)

Use case: Create GIS/3D point clouds for mapping, spatial analysis, and custom downstream processing.

Notes:

  • Saved with patterns such as *.sv.points.csv, *.ts.points.csv, *.db.points.csv, *.power.points.csv (single beam) and *.sv.mb.points.csv, *.angles.mb.points.csv, *.mag.mb.points.csv, *.phase.mb.points.csv (multibeam).
  • Supports wideband and pulse-compressed data where applicable.
  • Excluded samples (see the variable’s Analysis page) are not exported.
  • An empty file often indicates no valid GPS data during the export period.
  • Coordinate reference/projection metadata is not included; record CRS/projection separately if needed for GIS.
  • Files can be large; for very dense outputs use scripting tools rather than spreadsheets.

See also: Exporting Georeferenced samples

GPS fix data (*.gps.csv)

Description: Exports timestamped position fixes from GPS-derived position variables. Commonly used to reconstruct vessel tracklines, map acoustic data, or associate spatial metadata with external datasets. Fileset-compatible (can be added to a fileset as a raw GPS position variable).

Export methods:

  • Dataflow window: Right-click a position variable in the Dataflow window, then select Export, To CSV...
  • Cruisetrack: With the position variable's Cruisetrack window activated, click on the Cruisetrack menu, Export GPS Fixes to CSV...
  • Table: With the position variable's Table window activated, click on the Table menu, Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • GPS_date — Date (yyyy-MM-dd)
  • GPS_time — Time (HH:mm:ss)
  • GPS_milliseconds — Millisecond component (0–999)
  • Latitude — Latitude of GPS antenna (°)
  • Longitude — Longitude of GPS antenna (°)

Optional columns:

  • GPS_fix — Sequential fix number
  • NMEA — Raw NMEA content or altitude (device/format dependent)
  • GPS_status — Quality of fix (0 = Good, 1 = Bad, 2 = Uncertain)
  • GPS_filename — Source file name (blank for virtual variables)
  • Distance — Cumulative track distance (nmi)

Use case: Reconstruct navigation tracks, identify GPS dropouts, and align spatial data with ping-based variables.

Notes:

  • Times are UTC. When added to a fileset, unrecognized columns are ignored.
  • Latitude/longitude refer to the GPS antenna location, not the transducer. See About transducer geometry.

Heading (*.heading.csv)

Description: Time-stamped heading values from heading variables. Files in this format are fileset-compatible and can be added to a fileset as a raw Heading variable.

Export methods:

  • Dataflow window: Right-click the Heading variable and choose Export, To CSV...
  • Graph: With the heading graph open, choose Graph menu, Export to CSV...
  • Table: With the heading table open, choose Table menu, Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Heading_index — Sequential index
  • Heading_date — Date (yyyy-MM-dd)
  • Heading_time — Time (HH:mm:ss)
  • Heading_milliseconds — Millisecond component (0–999)
  • Heading_degrees — Heading (0–359.999°), measured clockwise from true north
  • Heading_status — Status for the segment between this value and the next

Use case: Vessel orientation monitoring, beam direction corrections, and movement-aware filtering.

Notes:

  • Also exportable to *.evd (Echoview Data File) format.
  • Status semantics mirror other time-series status values in Echoview and can be used for filtering/weighting.
  • Heading values come from the heading source selected on the platform’s Attitude page.

See also: Exporting Heading data

Interval analysis data (*.analysis.csv)

Description: Time-stamped analysis results for a specified analysis variable over a specified time/ ping interval. Types of Interval analysis include: Bottom feature, Sv analysis (Sv and Echometric variables) and Single target analysis variables. The grid spacing for the interval may be set in the operator or the operand.

Export methods:

  • Dataflow window: Right-click a Interval analysis variable in the Dataflow window and choose Export, To CSV…
  • Table: With the Interval analysis table active, choose Table menu. Export to CSV…
  • Graph: With the Interval analysis graph active, choose Graph menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Specify an Analysis time series Operand it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Analysis_variable_index — Sequential index
  • Analysis_variable_date — Date (yyyy-MM-dd)
  • Analysis_variable_time — Time (HH:mm:ss)
  • Analysis_variable_milliseconds — Millisecond component (0–999)
  • Analysis_variable— Value (unit)
  • Analysis_variable_status — Status for the measurement between this value and the next

Use case: Interval analysis of echogram data, output as a time series. Display options include graph, table, alongtrack (bubbleplot or line segment), collate to collection and export to CSV.

Consistent summaries across survey segments for comparison, trend analysis, reporting, or QA.

Notes: The exact column set depends on the input variable and operator. A header row identifies fields; unrecognized/extra columns are ignored on re-use. Times are UTC.

See also: About exporting data

Interval analysis - Calibration (*.calibration.csv)

Description: Time-series export from the Interval analysis – Calibration operator. Each CSV contains one selected parameter (e.g., sound speed, absorption) with one row per analysis interval. Export-only (can't be added to a fileset).

Export methods:

  • Dataflow window: Right-click the Calibration time series variable and choose Export, To CSV….
  • Graph: With the Calibration variable graph open, choose Graph menu, Export to CSV...
  • Table: With the Calibration variable table open, choose Table menu, Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Calibration_variable_index — Sequential index
  • Calibration_variable_date — Date (yyyy-MM-dd)
  • Calibration_variable_time — Time (HH:mm:ss)
  • Calibration_variable_milliseconds — Millisecond component (0–999)
  • Calibration_variable— Value (unit)
  • Calibration_variable_status — Status for the segment between this value and the next

Example filename: Calibration [SoundSpeed].calibration.csv

Use case: Long-term calibration QA and environmental consistency checks across surveys.

Notes: Times are UTC. Column order is not important; unrecognized columns are ignored.

Length data (*.length.csv)

Description: Time-stamped length measurements (e.g., cable out, tow-body depth, layback proxy). Files in this format can be added to a fileset as a raw Length variable for graphing and analysis.

Export methods:

  • Dataflow window: Right-click a Length variable and choose Export, To CSV…
  • Table: With the Length table active, choose Table menu, Export to CSV…
  • Graph: With the Length graph active, choose Graph menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Length_index — Sequential index
  • Length_date — Date (yyyy-MM-dd)
  • Length_time — Time (HH:mm:ss)
  • Length_milliseconds — Millisecond component (0–999)
  • Length_meters — Length value (m)
  • Length_status — Status for the segment between this value and the next

Use case: QC and documentation of length time series and downstream calculations such as catenary/tow-depth modeling and layback corrections.

Notes:

  • Units are meters; adjust display units on variable properties if needed.
  • Status codes follow standard time-series semantics (e.g., Good/Bad/Uncertain) and can be used for filtering or weighting.
  • Also exportable to *.evd (Echoview Data File) format.

See also: Exporting Length data

Line data (*.line.csv)

Description: Time-stamped depth values from a line variable, one row per ping. Files in this format can be added to a fileset as a raw line variable.

Export methods:

  • Echogram (whole line): Open an acoustic variable echogram, then select Echogram from the menu, select Export…, Line…, Export… to save as *.line.csv
  • Echogram (partial line): Open an acoustic variable echogram, make a selection using the Vertical band tool. Right-click the selection, and on the Shortcut menu, choose select Export Selection, Line..., Export... to save as *.line.csv

Typical columns:

  • Line_depth — Depth (m) of the line at the ping
  • Line_date — yyyy-MM-dd
  • Line_time — HH:mm:ss
  • Line_milliseconds — 0–999
  • Status — Status of the segment between this value and the next

Use case: Round-trip editable or algorithmic lines for QA, documentation of tracked surfaces (e.g., seabed, school top), or reuse in other EV files.

Notes:

  • Dataflow window, select line, right-click and on the Shortcut menu, Export, Data values… produces *.depth.csv (time-series export), not *.line.csv
  • The Table and Graph menus do not include “Export to CSV…” for lines; use the Echogram method above
  • *.line.csv supports round-tripping and can be added to a fileset as a raw line variable

See also: Exporting Line data

Matrix data (*.sv.mmb.csv, *.ts.mmb.csv, *.angle.mmb.csv, *.db.mmb.csv)

Description: Exports per-ping, matrix-style data from multibeam variables. Each row contains the full beam × sample matrix for a single ping (flattened into columns). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click a multibeam matrix variable in the Dataflow window or on an echogram and choose Export, To CSV…. Files include an .mmb infix to indicate multibeam matrix content.
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (this Measurement exporter writes the same CSV format described in this section and respects regions/selections).
  • Table: With the Table view window activated, select Table menu, Export to CSV...

Typical columns:

  • Ping_index — Sequential ping number
  • Beam_count — Number of formed beams in the ping
  • Sample_count — Samples per beam
  • Flattened matrix values… — One column per matrix cell, typically headed by beam/sample indices (e.g., Beam_1_Sample_1, …, Beam_B_Sample_S)

Optional columns:

  • Distance_gps, Distance_vl
  • Ping_date, Ping_time, Ping_milliseconds
  • Latitude, Longitude
  • Range_start, Range_stop

Use case: External processing in Python/MATLAB/R (beamforming QA, custom mosaics, per-beam filtering) where full per-ping matrices are required.

Notes:

  • Files can be very wide (many columns). Spreadsheet applications may truncate columns; use scripting tools for reliability.
  • Units depend on the variable type: *.sv.mmb.csv (Sv, dB re 1 m–1), *.ts.mmb.csv (TS, dB), *.angle.mmb.csv (degrees), *.db.mmb.csv (unspecified dB).
  • Column order may vary. Rely on headers (Beam_#_Sample_#) plus Beam_count/Sample_count to reshape to 2D.
  • Exclusion lines are honored; excluded samples export as no data (e.g., -9.9e+37).
  • If you need georeferenced point clouds instead of matrices, see Georeferenced samples (*.mb.points.csv).

See also: Exporting Matrix data

Multibeam magnitude (*.mag.mb.csv)

Description: Exports per-sample magnitude values from multibeam variables. Each row identifies a ping/beam/sample and its magnitude. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click a multibeam magnitude variable in the Dataflow window or on an echogram and choose Export, To CSV….
  • Echogram: With the multibeam magnitude echogram activated, select Echogram menu, Export, Magnitude Value to CSV...
  • Table: With the multibeam magnitude table window activated, select Table menu, Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Ping_index — Ping number
  • Beam_index — Beam number
  • Sample_index — Sample number along the beam
  • Magnitude — Linear magnitude (unitless)

Optional columns:

  • Ping_date, Ping_time, Ping_milliseconds
  • Distance_gps, Distance_vl
  • Latitude, Longitude
  • Depth — Sample depth (m)
  • Range_start, Range_stop — Range bounds for the ping (m)
  • Angle_along, Angle_athwart — Beam orientation angles (°; if available)

Use case: Beam-by-beam QA, custom detection/thresholding, and workflows that require per-sample magnitudes (rather than dB values or georeferenced points).

Notes:

  • Values are linear magnitude (unitless). For dB matrix exports see Matrix data (*.db.mmb.csv).
  • Exclusion lines are honored; excluded samples export as no data (e.g., -9.9e+37).
  • For georeferenced 3D point exports (with per-sample lat/lon/depth), see Georeferenced samples (*.mag.mb.points.csv).

See also: Matrix data, Georeferenced samples, Exporting Complex data

Multibeam phase (*.phase.mb.csv)

Description: Exports per-ping phase values from multibeam (formed-beam) variables. Each row begins with ping metadata, then lists phase values for all samples across all beams. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click the multibeam phase variable in the Dataflow window and choose Export, To CSV….
  • Echogram: With the multibeam phase echogram active, choose Echogram menu, Export, Phase Value to CSV….
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Ping_index — Sequential ping number
  • Number_of_beams — Count of formed beams in this ping
  • Samples_per_beam — Number of range samples per beam
  • Range_start, Range_stop — Along-beam range bounds (m)
  • Data values — Headerless list of phase values appended after metadata; length = Number_of_beams × Samples_per_beam. Ordered by range within each beam across beams.

Optional columns:

  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Distance_gps, Distance_vl — Cumulative distances (nmi)
  • Latitude, Longitude, Heading — Position/orientation at ping time
  • Beam/sector descriptors as available — e.g., Sector_angle, Full_sector_angle, Full_sector_beam_count, First_beam_number, Tilt_angle, Bearing_angle, Ping_mode, Variable_name

Use case: External processing that requires phase information (e.g., phase unwrapping, interferometry, beamforming QA, coherence analysis).

Notes:

  • Saved with extension .phase.mb.csv. Column order (for metadata) is not important.
  • Exclusion lines are honored; excluded samples export as no data (e.g., -9.9e+37).
  • Very long rows can challenge spreadsheet apps; use scripting tools for reliability.
  • Phase units follow the source variable; check the variable’s Details dialog.

Multibeam Sv (*.sv.mb.csv)

Description: Exports formed-beam Sv (dB re 1 m–1) from a multibeam variable. Each row represents one ping and includes metadata followed by Sv values for all beams × samples. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click a Multibeam Sv variable and choose Export, To CSV….
  • Echogram: With the multibeam Sv echogram active, choose Echogram menu, Export, Sv Values to CSV….
  • Table: With the multibeam Sv table open, choose Table menu, Export to CSV….
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window, configure in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described here and respects regions/selections).

Typical columns (per ping):

  • Ping_index — Sequential ping number
  • Number_of_beams — Count of formed beams in this ping
  • Samples_per_beam — Number of range samples per beam
  • Range_start, Range_stop — Along-beam range bounds (m)
  • Data values… — Headerless list of Sv values appended after metadata; length = Number_of_beams × Samples_per_beam. Ordered by range within each beam, across beams.

Optional columns:

  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Distance_gps, Distance_vl — Cumulative distances (nmi)
  • Latitude, Longitude — GPS antenna position (°)
  • Beam/sector descriptors where available (e.g., Sector_angle, First_beam_number, Ping_mode).

Use case: Compact, per-ping multibeam Sv for external processing (e.g., mosaicking, per-beam QA) with full beam×sample coverage.

Notes:

  • Saved with extension .sv.mb.csv; distinct from Matrix formats (e.g., *.sv.mmb.csv).
  • Column order for metadata is not important. Times are UTC. Exclusion lines are honored; excluded samples export as no data (e.g., -9.9e+37).
  • Very long rows can challenge spreadsheet apps; use scripting tools for reliability.

See also: Multibeam magnitude, Multibeam phase, Georeferenced samples, Matrix data

Multibeam targets (*.targets.mb.csv)

Description: Exports one row per detection from a multibeam target-detection variable. Each record includes acoustic attributes and (where available) spatial/positional metadata. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click a multibeam target detection variable in the Dataflow window, on the Shortcut menu, select Export, To CSV….
  • Echogram: With the multibeam target detection echogram open, go to the Echogram menu, select Export, Multibeam target to CSV...
  • Table: With the multibeam target detection table open, go to the Table menu, select Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window, configure in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described here and respects regions/selections).

Typical columns:

  • Ping_index — Ping number for the detection
  • Beam_index — Beam (or sector) number
  • Range_m — Slant range to target (m)
  • Depth_m — Estimated target depth (m)
  • TS_dB — Target strength (dB)
  • Angle_along_deg, Angle_athwart_deg — Along-/athwart-ship angles (°)

Optional columns:

  • X_m, Y_m, Z_m — Cartesian coordinates relative to the transducer
  • Latitude, Longitude — Geographic position (°)
  • Ping_date, Ping_time, Ping_milliseconds — UTC timestamp fields
  • Sample_index — Sample index associated with the detection
  • Distance_gps, Distance_vl — Cumulative distances (nmi)
  • Region_ID — Region label when exporting by region
  • Status — Detection/segment status (if provided)

Use case: Per-target analysis (TS distributions, spatial clustering), ground-truth comparisons, and 3D visualization/track-association workflows.

Notes:

  • Saved with extension .targets.mb.csv.
  • Coordinate and angle conventions follow the source data/instrument; confirm sign conventions before combining with external geometry.
  • Presence of GPS/Cartesian fields depends on available navigation and geometry data for the ping/beam.
  • For per-sample (non-detection) exports see Multibeam magnitude or Georeferenced samples.

Pitch (*.pitch.csv)

Description: Contains time-stamped pitch values. Files in this format are fileset-compatible and can be added to a fileset as a raw Pitch variable for graphing and analysis.

Export methods:

  • Dataflow window: Right-click a pitch variable in the Dataflow window and choose Export, To CSV…
  • Graph: With the pitch graph active, choose Graph menu, Export to CSV…
  • Table: With the pitch table active, choose Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Pitch_index — Sequential index for each record
  • Pitch_date — Date (yyyy-MM-dd)
  • Pitch_time — Time (HH:mm:ss)
  • Pitch_milliseconds — Millisecond component (0–999)
  • Pitch_angle — Pitch in degrees
  • Pitch_status — Status for the segment between this value and the next

Use case: Motion compensation and QA (e.g., correcting beam geometry, filtering data collected during excessive bow-up/bow-down).

Notes:

  • Also exportable to *.evd (Echoview Data File) format.
  • Sign and angle conventions follow the source instrument/setup.

See also: Exporting Pitch data

Power data (*.power.csv)

Description: Exports single-beam power values (in dB), one row per ping with metadata followed by the list of sample values. Useful for inspecting unprocessed signal strength or exporting sample-by-sample power to external tools. Not supported by filesets as a raw variable in Echoview.

Export methods:

  • Dataflow window: Right-click a power variable (raw or virtual) and choose Export, To CSV…, then click Export….
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (this Measurement exporter writes the same CSV format described in this section and respects regions/selections).
  • Echogram: From an open power echogram, choose Echogram menu, Export, Power Values to CSV…, then click Export….
  • Table: From an open power table, choose Table menu, Export to CSV….

Typical columns:

  • Ping_index — Sequential ping number (starts at 0)
  • Ping_date — Date (yyyy-MM-dd)
  • Ping_time — Time (HH:mm:ss)
  • Depth_start, Depth_stop — Depth (m) of nearest/farthest sample
  • Range_start, Range_stop — Along-beam range (m) of nearest/farthest sample
  • Sample_count — Number of following sample values
  • List of data values… — Power for each sample (dB), comma-separated, ordered from nearest to farthest range (no column header)

Optional columns:

  • Ping_milliseconds — Millisecond component (0–999)
  • Distance_gps, Distance_vl — Cumulative distances (nmi)
  • Latitude, Longitude — GPS antenna position at ping time (°)

Use case: Quicklook QA of raw backscatter, troubleshooting calibration/TVG effects, and providing inputs to custom signal-processing workflows.

Notes:

  • Latitude/longitude refer to the GPS antenna position at ping time.
  • Per-sample range/depth can be derived from the header fields if needed.
  • Range_start, Range_stop, and Sample_count may change on every ping (row).
  • If the number of sample values following Sample_count is not exactly Sample_count, the ping is treated as invalid and ignored (appears as a no-data gap).
  • range(n) = Range_start + (n + 0.5) * (Range_stop - Range_start) / Sample_count, where n = 0 … Sample_count − 1.

Region log book (*.regions.csv)

Description: Exports a log-style summary of region metadata for the active echogram (or a selection of pings). Each row describes one region and includes identifiers, time span, start/end position, classification, and notes. Export-only (not supported by filesets).

Export methods:

  • Echogram: With an echogram active, choose Echogram menu, Export, Regions, Log Book…, then click Export….

Typical columns:

  • Region_ID — Unique identifier (creation order)
  • Region_name — Region label (if any)
  • Region_type — See region type
  • Region_class — See region class
  • Date_s, Time_s — First-ping timestamp
  • Lat_s, Lon_s — Latitude/longitude at start ping
  • Date_e, Time_e — Last-ping timestamp
  • Lat_e, Lon_e — Latitude/longitude at end ping
  • Log_distance_s, Log_distance_e — Vessel-log distance (nmi) at start/end

Optional columns:

  • Region_notes — Notes from the Region Browser

Use case: Reporting and QA of region extents, timing, positions, and classifications; documenting survey annotations outside Echoview.

Notes:

  • Saved as *.regions.csv (the Save dialog autofills the extension).
  • Positions reflect the GPS antenna, not the transducer. See About transducer geometry.

See also: Exporting Regions log book data

Roll data (*.roll.csv)

Description: Time-stamped roll angle measurements from attitude sensors (rotation about the vessel’s longitudinal axis). Files in this format can be added to a fileset and used as raw Roll variables in Echoview.

Export methods:

  • Dataflow window: Right-click a roll variable and choose Export, To CSV…
  • Graph: Open a roll graph, choose Graph menu, Export to CSV…
  • Table: Open a roll table, choose Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Roll_index — Sequential index
  • Roll_date — Date (yyyy-MM-dd)
  • Roll_time — Time (HH:mm:ss)
  • Roll_milliseconds — Millisecond component (0–999)
  • Roll_angle — Roll angle in degrees (to three decimals)
  • Roll_status — Status of the segment between this value and the next

Use case: Motion compensation and QA (e.g., beam-steering, stabilization, and filtering), and documenting platform attitude alongside acoustic measurements.

Notes:

  • Roll is measured as a clockwise rotation of the major axis about the minor axis.
  • Also exportable to *.evd (Echoview Data File) format.

See also: Exporting Roll data

Single beam data (*.sv.csv, *.ts.csv, *.angles.csv, *.db.csv, *.linear.csv, *.boolean.csv)

Description: Sample-based values from single-beam (including split/dual beam) variables. One row per ping: ping metadata first, followed by all sample values for that ping. This same structure applies to Sv, TS, Angles, Unspecified dB, Linear, and Boolean variants. Files with these extensions are fileset-compatible and can be added to a fileset as raw variables in Echoview.

Export methods:

  • Sv echogram: With an Sv echogram active, select Echogram menu, Export, Sv Values to CSV…
  • TS echogram: With a TS echogram active, select Echogram menu, Export, TS Values to CSV…
  • Dataflow window: Right-click the Sv/TS/Angles/Unspecified dB/Linear/Boolean variable and choose Export, To CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns (per ping):

  • Ping_index — Sequential ping number (starts at 0)
  • Distance_gps — Distance from first GPS fix (nmi)
  • Distance_vl — Vessel-log distance at ping time (nmi)
  • Ping_date (yyyy-MM-dd), Ping_time (HH:mm:ss), Ping_milliseconds
  • Latitude, Longitude — GPS position at ping time (°; if available)
  • Depth_start, Depth_stop — Depth range spanned by the samples (m)
  • Range_start, Range_stop — Along-beam range of nearest/farthest sample (m)
  • Sample_count — Number of samples that follow
  • List of data values — The sample values for this ping, written on the same line:
    〈sample0〉, 〈sample1〉, …, 〈sampleN〉

Optional columns:

  • Latitude, Longitude, Distance_gps, Distance_vl — Included when navigation/log data are available

Use case: Round-trip raw sample data for QC or editing; export for external processing (e.g., custom gridding, denoising, thresholding) while preserving per-ping metadata.

Notes:

  • Units are not written into the file. For Sv: dB re 1 m-1; for TS: dB re 1 m2; for Angles: degrees; for Unspecified dB: dB (semantics depend on the source variable); for Linear: linear values (unit depends on source; often unitless); for Boolean: 0 or 1.
  • Units are not embedded in the CSV; consult the source variable’s Details and calibration/TVG context for interpretation.
  • If the number of sample values does not match Sample_count, the ping is ignored.
  • Exclusion lines are honored; excluded samples export as no data.
  • Range_start, Range_stop, and Sample_count may change on every ping (row).
  • range(n) = Range_start + (n + 0.5) * (Range_stop - Range_start) / Sample_count, where n = 0 … Sample_count − 1.

See also: About exporting data

Single target detections (*.target.csv)

Description: One row per detected single target from a single-beam echogram. Includes timestamp, range/depth, target strength (compensated and uncompensated), angle metrics, and (when available) geolocation. Files in this format are fileset-compatible and can be added to a fileset as raw Single targets variables.

Export methods:

  • Dataflow window: right-click a Single targets variable, Export, To CSV…
  • Echogram: With a single targets echogram activated, go to Echogram menu, Export, Single Targets to CSV…
  • Table: With a single targets table activated, go to Table menu, Export to CSV...
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Ping_date, Ping_time, Ping_milliseconds
  • Target_range, Target_on_axis_depth
  • TS_comp, TS_uncomp
  • Angle_minor_axis, Angle_major_axis
  • Pulse/beam metrics (e.g., PulseLengthDeterminationLevel, Beam_compensation, normalized widths)

Optional columns:

  • Target_latitude, Target_longitude
  • Sample_index, Ping_index, or detection/processing flags (instrument- and settings-dependent)
  • Target_length (if available), Beam_compensation, and other operator-specific metrics
  • Target_length_m — Estimated target length (m) when length estimation is enabled for the Single targets variable; availability depends on instrument/processing settings.

Use case: Per-target analyses (TS distributions, clustering), QA of detection settings, and associating detections with biological or net sample data.

Notes:

  • Exact column names vary with instrument and detection settings; a header row is always included.
  • This format is distinct from Multibeam targets (*.targets.mb.csv), which use different fields.
  • For best results (e.g., fish tracking), targets should appear in ascending range within each ping.
  • Exported files don’t record transducer vertical offset or echogram mode. When adding to a fileset, depth/range may differ from the original display unless you set the same Echogram mode and transducer vertical offset used at export.
  • Files made with releases prior to ~4.90 may lack Target_range. Re-export with a current version, or duplicate Target_on_axis_depth as Target_range when range ≡ depth.
  • Target_length_m is only written when the Single targets processing includes length estimation.

See also: About exporting data, Multibeam targets

Speed data (*.speed.csv)

Description: Time-stamped platform speed values. Files in this format are fileset-compatible and can be added to a fileset as raw Speed variables for graphing and analysis.

Export methods:

  • Dataflow window: Right-click a speed variable in the Dataflow window, select Export, To CSV…
  • Graph: With the speed Graph open, select Graph menu, Export to CSV…
  • Table: With the speed Table open, select Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Speed_index — Sequential index
  • Speed_date — Date (yyyy-MM-dd)
  • Speed_time — Time (HH:mm:ss)
  • Speed_milliseconds — Millisecond component (0–999)
  • Speed_meters_per_second — Speed value (m·s-1)
  • Speed_status — Status for the segment between this value and the next

Use case: QC of vessel/platform motion, deriving along-track metrics, and aligning speed with acoustic summaries or navigation for downstream analysis.

Notes:

  • Status code semantics match other time-series variables and can be used for filtering/weighting.
  • This CSV can be added to a fileset; unrecognized extra columns (if any) are ignored.

See also: Exporting Speed data

Time series collection (*.table.csv)

Description: A CSV file that defines a multi-column time series collection. The file can be authored externally with extension *.table.csv and then added to a fileset. This type of file is exported for time series collection variables.

Fileset: Add the CSV to a fileset. Double-click the collection to open it as a table.

Derivations: From a Time series collection (raw or virtual), you can derive additional variables with operators when you want to work with individual series or construct new collections:

  • Time series select — outputs a virtual time series (when Standard data type is used) or virtual unspecified time series (when Unspecified data type is used). The output represents a single series from the collection. This virtual time series can be exported to CSV (for example, *.custom.csv for Unspecified data).
  • Collate time series — outputs a virtual time series collection by combining multiple time series. The resulting collection can be exported to CSV from the dataflow object or the table.

Typical columns (per row):

  • Index — Measurement index (zero-based)
  • Date — Recommended yyyy-MM-dd
  • Time — Recommended HH:mm:ss
  • <Series name>_value — Name of the series value column, with _value required as a cue to indicate that the column contains series values; e.g., Depth_m_value, Temperature_C_value.

Optional columns:

  • Milliseconds — Millisecond component (0–999). If blank, defaults to 0.
  • <Series name>_status — Status for the segment to the next sample (per series), when provided _status is required to cue that the column contains status values related to the indicated series. If blank, defaults to 3 (Good).

Use case: Bring multiple external time-stamped series into a single table for viewing or for deriving standard Unspecified time series variables (via Custom time series select) that you can graph, analyze, and export like other time series.

Notes:

  • Time series collections can be exported directly to CSV using Measurements – CSV or the Export data command from the dataflow object or table. To export a single time series, derive a Time series select variable and export that variable.
  • Columns are defined entirely by your header row. Column order is not important; unrecognized columns are ignored.
  • Units are not inferred from the file. Set units and interpolation for derived series on the operator’s Time Series Properties dialog.
  • Follow general date/time and data-column rules for text data files.

See also: Time series collection and Custom time series collection data file.

Transect definitions (*.transect.csv)

Description: Defines the individual transects within a transect group. Each row describes one transect (IDs, start/end in time and/or ping index). Files in this format can be imported to recreate a transect group.

Export methods:

  • Dataflow window: Right-click a Transect group and choose Export, Transect Definitions…
  • Table: From the transect group Table menu, select Export Transect Definitions…

Typical columns:

  • Transect_ID
  • Transect_name
  • Start_time (yyyy-MM-dd:HH:mm:sss)
  • Stop_time (yyyy-MM-dd:HH:mm:sss)
  • Notes — User notes

Use case: Share or restore standardized transect boundaries for consistent analysis across projects, reproducible reporting, and collaboration.

Notes:

  • To restore definitions, select the transect group and choose Import… to load a *.transect.csv.
  • Column order is not important; unrecognized columns are ignored. Times are UTC where present.
  • Notes may be viewed on the Transect Goup Properties dialog box, they are not exported or displayed on the Table view.

See also: Exporting Transect data

Transmission time series (*.csv)

Description: Time-stamped values exported from a Transmission time series select operator applied to a Transmission time series collection. You choose the Component (e.g., voltage, current, impedance, phase) and Statistic (e.g., mean, median, max) in the operator’s properties. Each row is one measurement at a given time. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click the Transmission time series select variable and choose Export, To CSV…
  • Graph: With the variable’s Graph view active, select Graph menu, Export to CSV…
  • Table: With the variable’s Table view active, select Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Index — Sequential measurement index
  • Date — yyyy-MM-dd
  • Time — HH:mm:ss
  • Milliseconds — 0–999
  • Value — Selected component/statistic value (units depend on component; e.g., Ω, V, A, °)
  • Status — Segment status between this value and the next

Use case: Export transmission-chain telemetry for QA, instrument health checks, and post-processing (e.g., trending source voltage, transducer impedance magnitude, or phase through time).

Notes:

  • Column headers may reflect your selected Component/Statistic (for example, the value column header may include the component name and unit).
  • This CSV is not supported by filesets as a raw Transmission time series variable. To assemble or exchange multiple series, use a Time series collection CSV workflow.
  • Exporting impedance statistics.

See also: About time series data types, Transmission time series select operator, Transmission time series collection

Underlying data (*.csv)

Description: Exports the operand’s raw underlying samples in device/linear units. This is a low-level dump intended for troubleshooting or external processing. It uses a minimal header and then appends all sample values for each ping. Export-only (not supported by filesets).

Export methods:

  • Dataflow Toolbox: Drag a Measurements – underlying data exporter onto the Dataflow window, set the operand (e.g., a Power variable), configure properties, then double-click the exporter to write the file.

Typical columns (per ping):

  • Ping_index — Sequential ping number
  • Depth_start, Depth_stop — Depth bounds (m)
  • Range_start, Range_stop — Along-beam range bounds (m)
  • Sample_count — Number of following sample values
  • List of raw sample values… — Device/linear units (typically integers), appended after the metadata

Units & formats: Values are the instrument’s raw/linear samples (often integer counts), not dB. Timestamp, navigation, and distance fields are generally not written. Column order is not important; the sample list length must match Sample_count for the ping to be valid.

Notes:

  • Only variables that expose an “underlying” stream can be linked to this exporter. Many derived/virtual variables, multibeam/formed-beam products, or wideband complex variables will not present an underlying stream.
  • For wideband/complex data, use Measurements – complex data. For georeferenced 3D points, use Measurements – georeferenced samples.
  • Saved as *.csv (no special suffix). If you want to distinguish these files by name, consider a naming convention such as *.underlying.csv in your workflow.

Unspecified time series (*.custom.csv)

Description: Export from a Time series select virtual variable when the output type is Virtual unspecified time series. Each row contains one time-stamped measurement with status. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: Right-click the Time series select variable and choose Export, To CSV…
  • Graph: With the variable’s Graph view active: Graph menu, Export to CSV…
  • Table: With the variable’s Table view active: Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • <Var>_index — Sequential row index
  • <Var>_date — Date (yyyy-MM-dd)
  • <Var>_time — Time (HH:mm:ss)
  • <Var>_milliseconds — Millisecond component (0–999)
  • <Var>_value — Measurement values (header may include a user-defined Unit name)
  • <Var>_status — Status code for the segment between this value and the next

Use case: Export arbitrary or derived time-series measurements (e.g., selections from a collection, custom calculations) for downstream analysis, QC, and joining with other datasets.

Notes:

  • Column headers are prefixed by the variable name; special characters are sanitized (e.g., Select [X] → Select_[X]_…).
  • If a Unit name is set on the variable’s Time series properties, it is appended to the value column header.
  • For the Unspecified data type, “no data” exports as -9.9e+37. Choosing a standard type (e.g., Depth) may use that type’s conventional no-data value.
  • This is distinct from a Time series collection CSV (*.table.csv), which is format for multi-series tables support by filesets.

See also: About time series data, Time series select operator, Time series collections (*.table.csv)

Vessel log data (*.logs.csv)

Description: Time-stamped vessel log distance. Each row is a log point with the cumulative distance traveled (nautical miles). Export-only (not supported by filesets). Values correspond to Distance_vl seen on echograms and in other CSV exports.

Export methods:

  • Dataflow window: Right-click a Vessel logs variable and choose Export, To CSV…
  • Graph: With the Vessel log variable’s Graph view active, go to Graph menu, Export to CSV…
  • Table: With the Vessel log variable’s Table view active, go to Table menu, Export to CSV…
  • Dataflow Toolbox: Drag a Measurements – CSV exporter onto the Dataflow window. Configure it in the Exporter Properties dialog, then double-click to write the file (writes the same CSV format described in this section and respects regions/selections).

Typical columns:

  • Distance_index — Sequential index for each record
  • Distance_date — Date (yyyy-MM-dd)
  • Distance_time — Time (HH:mm:ss)
  • Distance_milliseconds — Millisecond component (0–999)
  • Distance_nautical_miles — Cumulative vessel log distance (nmi)
  • Distance_status — Status for the segment between this value and the next (e.g., 3 = Good)

Use case: Along-track calculations, distance-based binning (e.g., cells by nmi), QC of navigation sensors, and joining with other exports that reference Distance_vl.

Notes:

  • Files are saved as *.logs.csv and are not supported by filesets as raw variables.
  • Distances are cumulative nautical miles along the vessel track; interpretation of gaps/pauses depends on the source log.

See also: Exporting Vessel log data

Analysis exporter CSVs

Exporter Domain(s) Row granularity Output Layout Notes
Fish track analysis (*.csv) Regions / Cells Per domain (aggregates) Tall Track/target metrics aggregated by domain; single or multi-file.
Frequency distribution (*.csv) Regions / Cells Per domain × bin Tall TS/Sv histograms; one row per bin.
ICES region summary (*.ices.csv) Regions Per region Fixed Standardized ICES CSV; fixed column set.
Sv integration (*.csv) Intervals / Regions / Cells / Transects Per domain unit Tall Typical fields include NASC/Sv summaries; respects lines & masks.
Vegetation analysis (*.csv) Intervals Per interval Tall Uses Vegetation & Bottom lines; canopy/bottom stats.
Wideband frequency response (*.csv) Intervals / Regions / Cells Per domain × frequency Tall or Wide Sv/TS vs frequency; supports binned spectra and multi-file modes.
Wideband frequency response — Single targets (*.csv) Single targets Per target × frequency Tall or Wide Per-target spectra (wideband only).

Fish track analysis (*.csv)

Description: Exports fish-track analyses from a Single targets variable that contains fish tracks. Supports two Analysis domain modes: Regions and Cells. The exact columns depend on the domain and the Output format you choose (Spreadsheet format – single file vs Spreadsheet format – multiple files) and on which Analysis variables are selected (globally or overridden on the exporter). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag a Fish track analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns (vary by domain & output format):

  • Regions (single file, summaries per region) — identifiers and bounds plus selected analysis variables, e.g.:
    • Region_ID, Region_class, Date_s, Time_s, Date_e, Time_e
    • Track/target metrics such as Num_tracks, Num_targets, TS_mean, Track_speed_mean, durations/areas as applicable
  • Cells (single file, summaries per cell) — grid keys and bounds plus selected analysis variables, e.g.:
    • Cell_row, Cell_col, SampleDepthUpper_m, SampleDepthLower_m, LogDistance, LogTime
    • Track/target metrics such as Num_tracks, Num_targets, TS_mean, etc.
  • Multiple files (per-target rows) — one row per single target within the domain, broadly a subset of the Single target detections CSV with additional fields, e.g.:
    • TS_comp, TS_uncomp, Target_range, Target_on_axis_depth, angle metrics
    • Domain/context fields such as Region_ID or Cell_row/Cell_col
    • Additional region altitude fields: Region_bottom_altitude_max, Region_bottom_altitude_mean, Region_bottom_altitude_min, Region_top_altitude_max, Region_top_altitude_mean, Region_top_altitude_min

Use case: Standardized fish-track outputs for reporting and downstream analysis, either as per-domain summaries (Regions/Cells) or per-target detail files scoped by domain.

Notes:

  • Exports are constrained to regions or cells overlapping transects in the assigned Transect group; see Transects and export analyses.
  • For per-target (multiple files) output, the file largely mirrors the Single target detections CSV with added region altitude fields (listed above).
  • If you generate tracks from *.target.csv files added to a fileset, enable Output empty single target pings before exporting those CSVs to preserve ping numbering for tracking settings.
  • When any track contains a single target with no position, speed/direction analysis variables may use the special value -9999; see Special export values.
  • Cells exports use the grid configured on the operand’s Grid page. Times are UTC.

See also: Exporting fish track analyses, About detecting fish tracks, Single target detections (*.target.csv)

Frequency distribution analysis (*.csv)

Description: Exports target-strength (TS) frequency distributions from Single targets data over a chosen analysis domain. Each output represents binned TS statistics for the domain (e.g., per region, per cell). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag a Frequency distribution analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns: (Spreadsheet format)

  • Domain identifiers — e.g., Region_ID / Cell_row, Cell_col, or interval start/end time and ping indices
  • Bounds/metadata — e.g., sample depth or range bounds for the domain, optional position/log summaries
  • Bin descriptors — e.g., TS_bin_lower_dB, TS_bin_upper_dB (or bin center/width depending on settings)
  • Bin metrics — e.g., Count (targets per bin). Some configurations may also include proportions or cumulative values.

Optional columns:

  • Region_class / SA_category (when exporting by region classes)
  • Additional effort/context fields depending on the analysis domain

Use case: Characterize TS distributions (histograms) by region/cell for species discrimination, QA of detection settings, or downstream statistical analysis.

Notes: The column set and labels depend on the exporter’s configuration (Analysis domain; Spreadsheet vs Database format). Spreadsheet format writes a single CSV; Database format writes multiple normalized tables. Times are UTC.

See also: TS Frequency Distribution export · Single target detections

ICES analysis CSV (*.csv)

Description: Exports ICES-ready summaries from a single-beam Sv variable. The column set depends on the chosen Analysis domain (e.g., Cells, Region classes by cells). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag an ICES analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns: CSV with grouped header/record sections followed by Data rows.

  • Header sections: Instrument, Calibration, DataAcquisition, DataProcessing, Cruise.
  • Data rows (per cell or per region-class×cell) commonly include:
    • LogDistance, LogTime, LogLatitude, LogLongitude, LogOrigin, LogValidity
    • SampleChannelDepthUpper, SampleChannelDepthLower
    • SamplePingAxisInterval, SamplePingAxisIntervalType, SamplePingAxisIntervalUnit
    • SampleSvThreshold
    • InstrumentID, CalibrationID, DataAcquisitionID, DataProcessingID, CruiseLocalID
    • DataSaCategory (species/region class), DataType (A=Mean Sv, C=NASC, D=ABC or PRC_*), DataUnit (dbm-1, m2nmi-2, m2/m2), DataValue

Use case: Produce ICES-compatible summaries (cells or region-classes by cells) for submissions, comparability across surveys, QA, and downstream analysis.

Notes:

  • Shortcut menu, Export…, Analysis… writes the .csv; Shortcut menu, Export…, Settings… writes a .txt of the exporter configuration.
  • The save dialog creates a standard .csv. Using a filename ending with .ices.csv is optional.
  • Cells domain uses the echogram grid (configure on the variable’s Grid page). Region classes by cells requires regions with Type = Analysis and visible region classes.
  • Global options such as Output empty cells can be overridden per exporter.

See also: Exporting ICES CSV data, ICES acoustic trawl survey database

Sv integration (*.csv)

Description: Exports integrated/summary metrics (e.g., NASC, ABC, mean Sv) computed over a chosen analysis domain (Regions, Cells, Transects, or Region classes by cells). Replaces the former “Region summaries” export. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag an Sv integration exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns (vary by domain):

  • Identifiers — e.g., Region_ID, Transect_ID, Cell_row, Cell_col
  • Position & timing — e.g., Lat_s, Lon_s, Date_s, Time_s, Lat_e, Lon_e, Date_e, Time_e, Log_distance_s, Log_distance_e
  • Bounds / geometry — e.g., SampleDepthUpper_m, SampleDepthLower_m, Range_start_m, Range_stop_m
  • Metrics — e.g., Sv_mean_dB, NASC_m2nmi2, ABC_m2m2, counts/areas/durations as applicable

Optional columns:

  • Region_class / SA_category (when exporting by region class)
  • Effort/context fields such as Ping_count, Sample_count, Cell_area_m2, Cell_duration_s (domain-dependent)

Use case: Producing standardized summaries for mapping, biomass proxies, and downstream analysis (per-region, per-cell, per-transect comparisons).

Notes:

  • Saved as a standard .csv; column set depends on the chosen analysis domain and exporter settings.
  • For a log-style list of region metadata, see Region log book. For ICES-formatted outputs, see ICES analysis CSV.

Vegetation analysis (*.csv)

Description: Exports interval-based metrics that describe vegetation height and related line statistics between a Vegetation line and a Bottom line over a single-beam acoustic variable. Each row represents one analysis interval (time- or ping-based). Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag a Vegetation analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns:

  • Process_ID — Export process identifier (see Process_ID)
  • Interval — Interval number (starts at 1; numbering follows the echogram grid and related settings)
  • Ping_S, Ping_E — Start/end pings of the interval
  • Date_M — Date (yyyyMMdd) of the middle ping
  • Time_M — Time (HH:mm:ss.ssss) of the middle ping
  • Lat_M, Lon_M — Latitude/Longitude (°) of the middle ping
  • Bottom_line_depth_mean, Bottom_line_depth_min, Bottom_line_depth_max — Bottom line depth stats (m)
  • Vegetation_line_depth_mean, Vegetation_line_depth_min, Vegetation_line_depth_max — Vegetation line depth stats (m)
  • Vegetation_line_height_mean, Vegetation_line_height_min, Vegetation_line_height_max — Vegetation height (m) between Bottom and Vegetation lines
  • Vegetation_line_height_standDev — Standard deviation of vegetation height (m)
  • Pings_With_Vegetation — Count of pings with vegetation in the interval
  • Samples_in_Domain — Number of samples whose midpoints fall inside the analysis domain
  • Samples_above_min_threshold — Count of domain samples above the variable’s Minimum threshold

Optional columns:

  • Transect_ID, Transect_name — Included when a transect group is assigned

Use case: Quantify vegetation canopy height and variability along track, produce interval summaries for mapping/monitoring, and compare vegetation metrics across transects or time windows.

Notes:

  • Intervals are defined by Time/Ping and spacing (Time between intervals) on the variable’s Analysis page. Numbering can start from the first ping in the echogram or be aligned with transects (see Grid settings).
  • Values of -9.9e+37 are exported when the Bottom line is above the Vegetation line or when a statistic cannot be calculated. For Lat_M/Lon_M, 999 may be exported when there is no vegetation line.
  • Missing/crossed line segments and samples excluded by Exclusion lines or Data page thresholds are treated as no data and do not contribute to statistics.
  • Only samples whose midpoints are inside the domain between the Vegetation and Bottom lines are counted in Samples_in_Domain and Samples_above_min_threshold (behavior changed in Echoview 15).
  • Exporter settings (e.g., Use local analysis variables, Output empty cells) can override EV-file global Export page options.

See also: Exporting a vegetation analysis, Detecting a vegetation boundary, Threshold offset

Wideband frequency response (*.csv)

Description: Exports wideband frequency response summaries (e.g., Sv or TS as a function of frequency) over a chosen analysis domain such as Intervals, Regions, or Cells. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag a Wideband frequency response analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns (depend on settings):

  • Domain identifiers — e.g., Region_ID / Cell_row, Cell_col / interval start–end time & pings
  • Frequency descriptor — either per-row Frequency_Hz (tall format) or one column per frequency bin (wide format)
  • Response metrics — e.g., Sv_dB or TS_dB at each frequency; additional summary fields per domain as configured

Optional columns:

  • Region_class / SA_category (when exporting by region classes)
  • Bounds/effort context (e.g., depth/range bounds, sample/ping counts) depending on domain & exporter options

Use case: Compare spectral response across space/time domains for species discrimination, QA, and downstream modelling.

Notes: Column layout (tall vs wide; binning, spacing, and frequency range) is controlled by the exporter settings. Times are UTC. See Exporter Properties for configuration details.

Wideband frequency response – Single targets (*.csv)

Description: Exports per-target wideband frequency responses from a Single targets variable (e.g., TS vs frequency for each detection), optionally grouped by domain. Export-only (not supported by filesets).

Export methods:

  • Dataflow window: From the Dataflow Toolbox, drag a Wideband frequency response - Single targets analysis exporter to the Dataflow window, specify an operand variable and other properties, Double-click the exporter to export.

Typical columns (depend on settings):

  • Target_ID (or time/ping/row keys) and optional domain keys (e.g., Region_ID, Cell_row, Cell_col)
  • Frequency descriptor — either per-row Frequency_Hz (tall format) or one column per frequency bin (wide format)
  • Response metrics — e.g., TS_dB (or other configured metric) at each frequency

Optional columns:

  • Target context (e.g., Target_range, Target_on_axis_depth, angles) where available
  • Bounds/effort fields depending on domain & exporter options

Use case: Spectral characterization of individual detections for classification, calibration checks, and research analyses.

Notes: Output shape (tall vs wide) and frequency binning are controlled by the exporter settings. This exporter focuses on per-target spectra; for domain-level spectra use Wideband frequency response. See Exporter Properties for configuration details.

Echoview Help file 16.0.179 for Echoview 16, 31 January 2026

Copyright © Echoview Software Pty Ltd 2026. All rights reserved. Echoview is a registered trademark of Echoview Software Pty Ltd. Other brands and trademarks are the property of their respective owners.

Please report any errors or omissions to support@echoview.com.