Export file formats

This section describes the format of files created by various Export menu commands (for exporting data). The following formats are covered:

Notes:

Echoview *.csv data exports have a space after every comma to improve readability. As a consequence the first data column contains no leading space but subsequent data columns do have a leading space. Leading spaces are ignored by Echoview when reading *.csv data files.
From Echoview 4.90 on, to achieve consistency for the decimal separator, date and times in export files, Echoview uses the format associated with the Windows Control Panel > Regional and Language Options setting - English (United States). This may affect users with a Regional and Language Options setting that significantly differs from English (United States) such that (exported) files may contain an unfamiliar decimal separator, or unfamiliar date or time format.
Some "text data CSV file formats" are supported as an exported data format and as a file format for adding to a fileset. There can be differences between the exported file and the equivalent "text data CSV file format". Such differences arise from the support for optional columns. Export file formats can include optional data columns. "Text data CSV files" (of any origin) can include optional data columns. When a file is added to a filest, optional columns are ignored unless stated otherwise by the "text data CSV file format".

See also: About exporting analyses

Echogram Data export files (.csv)

Data values (Sv values, TS values, dB values, linear values, Boolean values, angular positions, color values) can be exported from echograms to .csv files.

The first line of the .csv file lists the names of the variables that are exported (these will be used as column headings if the file is loaded into a spreadsheet program). No column heading is provided for the list of data values. Each subsequent line contains the value for each variable for a single ping and the data value for each sample in the ping.

Single beam, split beam and dual beam data value exports

Data can be exported for an entire echogram, a region, or a selection made using the vertical band tool . The following data are exported.

Variable	Description
Ping_index	Sequential ping number Note: Echoview numbers pings sequentially beginning with 0 for the first ping in an echogram.
Distance_GPS	nmi
Distance_vl	nmi
Ping_date	yyyy-mm-dd
Ping_time	hh:mm:ss
Ping_milliseconds	ms
Latitude	degrees
Longitude	degrees
Depth_start	m
Depth_stop	m
Range_start	m
Range_stop	m
Sample_count	Number of samples to follow
List of data values	Data value for each sample (separated by commas) Note: For "color" variables, the red, green and blue color intensities of each datapoint are exported as a single number. The exported number is a decimal representation of a six digit hexadecimal number 'bbggrr'; where 'bb' represents the intensity (0-255) of blue, 'gg' represents the intensity of green and 'rr' represents the intensity of red.

Notes:

When exporting data values for a region, the data output covers the bounding rectangle of the region. A special export value is output when the relevant point is outside the region.
For export of angular positions data, two angles are exported for each data point in the water column: minor-axis (alongship) angle, and major-axis (athwartship) angle.
The range and depth of each sample is not exported but can be calculated from exported data, see Calculating range and depth from exported data.
Single beam Sv data may also be exported in the Matlab format (*.mat).
Exported Sv, TS, angular position or linear values from vertical selections or whole echograms (but not regions) can be added as separate data files into an EV file and read as raw variables. These files will have an additional file extension describing the data type: .sv.csv, .ts.csv, .angles.csv, .linear.csv respectively.
The exported latitude and longitude values are the latitude and longitude of the GPS antenna at time of ping. As a result, the depth that is exported will only represent the line depth at the exported latitude and longitude if the transducer was located at the same point on the platform as the GPS antenna and was pointing straight down. The latitude and longitude of the line cannot be corrected for transducer geometry as lines are not related to a specific transducer or echogram.

Multibeam data value exports

Data values from all types of multibeam variable can be exported to .csv files. The export can be for an entire echogram or for a range of pings selected from the Export Data - Select Range of Pings for Export dialog box.

The first line of the file is a header row that contains the names of the variables that are exported (see below). The remaining lines contain the corresponding variables for a single ping.

Variable	Description
Ping_index	Sequential ping number Note: Echoview numbers pings sequentially beginning with 0 for the first ping in an echogram.
Distance_gps	Distance (nmi) from the first GPS fix in the data file
Distance_vl	Distance (nmi) travelled according to the vessel log at the time the ping was transmitted
Ping_date	The date (yyyy-mm-dd) on which the ping was transmitted
Ping_time	The time (hh:mm:ss) at which the ping was transmitted
Ping_milliseconds	The millisecond (0..999) at which the ping was transmitted
Latitude	The latitude (degrees) of the GPS antenna at the time the ping was transmitted
Longitude	The longitude (degrees) of the GPS antenna at the time the ping was transmitted
Heading	The heading of the platform at the time the ping was transmitted Note: Heading values are taken from the heading variable selected on the Attitude_page of the Platform Properties dialog box.
Range_start	Range (m) of the nearest sample in the ping (measured along the beam-axis)
Range_stop	Range (m) of the farthest sample in the ping (measured along the beam-axis)
Sector_angle	Angle (degrees) scribed between the outer edges of the two outer beams.
Number_of_beams	Number of beams in this ping
Samples_per_beam	Number of samples in each beam of this ping
Ping_mode	A number identifying the ping mode.
Variable_name	The name of the variable which was exported.
Full_sector_angle	The description of a beam subset.
Full_sector_beam_count
First_beam_number
Tilt_angle	The tilt angle of the beam.
Bearing_angle	The bearing angle of the beam.
Datafile_ping_number	The number, if any, asssigned to the ping in the original data file from which Echoview read the data.
List of datafile values	If and only if data is being exported from a raw variable of ping mode 3, 4 or 5 (H-, V-, S-mode) in Furuno .fsv files then certain values read from the data file will be exported here in a series of columns headed "datafile_X" where X is the name of the variable in the data file. Note: The Furuno FSV 30 (Research version) data format is not supported in Echoview 5.0.
Target_lock_beam	The number of the beam in the beam in the target-locked variable if any. Note: This is only exported from variables with ping mode 3 or 4 (H- or V- mode).
Ping_group	A number identifying the ping group . Note: This is only exported from variables with ping mode 3 or 4 or 5 (H- or V- or S- mode).
List of data values Note: No title in the header row of the file	On the remainder of this line, the data value for each sample arranged as follows (for x+1 samples and y+1 beams): <beam0 sample0>, <beam1 sample0> ... <beamy sample0>, <beam0 sample1>, <beam1 sample1> ... <beamy sample1>, ... <beam0 samplex>, <beam1 samplex> ... <beamy samplex> Notes: For "multibeam color" variables, the red, green and blue color intensities of each datapoint are exported as a single number. The exported number is a decimal representation of a six digit hexadecimal number 'bbggrr'; where 'bb' represents the intensity (0-255) of blue, 'gg' represents the intensity of green and 'rr' represents the intensity of red. For "multibeam boolean" variables, each datapoint is represented by 0 or 1 (for false and true respectively)

Notes:

The file extension provides information about the values that were exported:

Data type	File extension
magnitude (raw - not beamformed)	.csv+
phase (raw - not beamformed)	.csv
magnitude (beamformed)	.mag.mb.csv+
phase (beamformed)	.phase.mb.csv
Sv	.sv.mb.csv+
unspecified dB	.db.mb.csv
TS	.ts.mb.csv
Boolean	.boolean.mb.csv
color	.color.mb.csv

+Sv and magnitude variables may also be exported in Matlab format (*.mat) .

If and only if data is being exported from a raw variable of ping mode 3, 4 or 5 (H-, V-, S-mode) in Furuno .fsv files and that datafile contains target detections, then a separate file with the extension "(datafile targets).csv" will be exported which contains the target information. See Furuno .fsv files for more information.

Underlying data export files (.csv)

Underlying data can be exported to .csv files from most Echograms (a notable exception is variables produced by Echoview's beamformer).

Single beam, split beam and dual beam underlying data exports

Underlying data values from Sv, TS, angular position variables can be exported to .csv files. The export can be for an entire echogram or a selection made using the vertical band tool .

The first line of the .csv file lists the names of the six data properties that are exported (these will be used as column headings if the file is loaded into a spreadsheet program). No column heading is provided for the list of data values. Each subsequent line contains the value for each variable for a single ping and the underlying data value for each sample in the ping.

The following data are exported.

Data property	Description
Ping_index	Sequential ping number Note: Echoview numbers pings sequentially beginning with 0 for the first ping in an echogram.
Depth_start	m
Depth_stop	m
Range_start	m
Range_stop	m
Sample_count	Number of samples to follow
List of data values	Sample values (separated by commas)

Notes:

For export of angular positions data, two angles are exported for each data point in the water column: minor-axis (alongship) angle, and major-axis (athwartship) angle.
The range and depth of each sample is not exported but can be calculated from exported data, see Calculating range and depth from exported data.

Multibeam underlying data exports

Underlying data values from all multibeam variables not formed by Echoview's beamformer can be exported to .csv files. The export can be for an entire echogram or for a range of pings selected from the Export Underlying Data - Select Range of Pings for Export dialog box.

Data property	Description
Ping_index	Sequential ping number Note: Echoview numbers pings sequentially beginning with 0 for the first ping in an echogram.
Range_start	m
Range_stop	m
Sector_angle	The angle of the sample from the transducer axis
Number_of_beams	The number of beams in the multibeam echogram.
Samples_per_beam	Number of samples per beam in the echogram.
List of data values Note: No title in the header row of the file	Depending on the variable and echosounder from which the data was collected, data may consist of: magnitude data: signal strength of each sample. amplitude and phase data: alternating magnitude and phase information for each sample. in-phase and quadrature data: alternating in-phase and quadrature components of the complex voltage signal for each sample. The signal magnitude is the square root of the sum of the component squares and the phase is the trigonometric tangent of the quadrature to in-phase component ratios. To determine which format your echosounder stores, see Echosounder data files The data values are ordered as follows: each line contains the sample values for a whole ping. If the ping data is seen as a matrix with one column per beam and one row per distinct sample range, then the data are written one row at a time to the data file (on the one line). If the data are complex then the values are further, written as pairs (in-phase and quadrature values or magnitude and phase values respectively). Thus, samples are ordered from lowest range across each beam, i.e. they are reported in the following order: range0-beam0, range0-beam1, ... range0-beamN, range1-beam0, range1-beam1, ... range1-beamN, range2-beam0, range2-beam1, ... range2-beamN, rangeM-beam0, rangeM-beam1... rangeM-beamN for N-1 beams and M-1 ranges.

Notes:

Multibeam underlying data can only be exported if the ping mode is 2.

Bathymetric data export files (.csv)

Bathymetric data can be exported to .csv files. The export can be for an entire line or the part of a line that falls within a selection made using the vertical band tool .

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 a single ping.

The following data are exported.

Variable	Description
Ping_date	yyyy-mm-dd
Ping_time	hh:mm:ss
Ping_milliseconds	ms
Latitude	degrees (999.0 if unknown)
Longitude	degrees (999.0 if unknown)
Position_status	Position status of ping as follows: 1 = Interpolated position good 3 = Interpolated position uncertain 4 = Interpolated position unknown
Depth	meters
Line_status	Line status of ping as follows: 0 = Bad 1 = Good 2 = Unverified 3 = No line
Sound_speed	m/sec (only exported for sounder-detected bottoms)
Ping_status	Ping status (1-11)
Altitude	m (-9999.99 if unknown)
GPS_UTC_time	hh:mm:ss (-1 if unknown)

Example line

19930115,15:09:58.10,999.00000000, 999.00000000, 4,00000.0,3,5959,0,-9999.990000,-1

Multibeam bottom detections export files (.bottom.mb.csv)

Multibeam bottom detections data can be exported to .csv files. The export can be for an entire echogram or a specified ping range.

The following data are exported.

Variable	Description
Ping_number	a sequential ping number
Ping_date	yyyy-mm-dd
Ping_time	hh:mm:ss
Ping_milliseconds	ms
Major_axis_angle	degrees
Range	meters
Beam_number	a sequential beam number

Note: The multibeam bottom detection settings that produce the export data are specific to the EV file. You can preview the detected bottom and change the bottom detection settings. See Multibeam echograms - Multibeam bottom detection preview for more information.

GPS fixes export files (.gps.csv)

GPS data can be exported from a cruise track window or position GPS fixes table to a .gps.csv file.

The following data are exported.

Variable	Description
GPS_fix	A sequential fix number (Optional data*)
GPS_date	yyyy-mm-dd
GPS_time	hh:mm:ss
GPS_milliseconds	ms
Latitude	degrees
Longitude	degrees
NMEA	altitude data (Simrad files only) or any NMEA GPS-fix letter groups identified by Echoview (Optional data*)
GPS_status	GPS fix status, (Optional data) as follows: 0 = Good 1 = Bad 2 = Good (but position between the previous fix and this one is considered uncertain) 3 = Unknown (Echoview 3.10 and earlier only)
GPS_filename	Name of the data file from which the GPS fix is sourced.(Optional data) Note: This will be blank for GPS fixes that are not sourced from a data file.

Notes:

Files in this format (.gps.csv) can be added into an EV file and read by Echoview as a raw variable.*Optional data is ignored when the export file is added to a fileset.
The latitude/longitude location exported is for the GPS antenna, not the transducer. Refer to About transducer geometry and the Position page of the Platform Properties dialog box for more information.

Vessel log data export files (.log.csv)

Vessel log data can be exported from a vessel log table to a .log.csv file.

The first line of the .log.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 values for each variable for a single log point.

The following data are exported.

Variable	Description
Log_data	A sequential number
Log_date	yyyy-mm-dd
Log_time	hh:mm:ss
Log_milliseconds	ms
Log_distance	distance in nautical miles

Heading data export files (.heading.csv)

Heading data can be exported from a heading graph or heading table to a .heading.csv file.

The first line of the .heading.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 values for each variable for a single heading determination.

The following data are exported.

Variable	Description
Heading_data	A sequential number
Heading_date	yyyy-mm-dd
Heading_time	hh:mm:ss
Heading_milliseconds	ms
Bearing	degrees (output to 3 decimal places). Measured clockwise from north, i.e. 0 is north and 90 is east.

Note: Files in this format (.heading.csv) can be added into an EV file and read by Echoview as a raw variable.

Pitch data export files (.pitch.csv)

Pitch data can be exported from a pitch graph or pitch table to a .pitch.csv file.

The first line of the .pitch.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 values for each variable for a single roll determination.

The following data are exported.

Variable	Description
Pitch_data	A sequential number
Pitch_date	yyyy-mm-dd
Pitch_time	hh:mm:ss
Pitch_milliseconds	ms
Pitch_angle	degrees (output to 3 decimal places). Measured as a clockwise rotation of the minor axis about the major axis when viewed in the positive direction of the minor axis.

Note: Files in this format (.pitch.csv) can be added into an EV file and read by Echoview as a raw variable.

Roll data export files (.roll.csv)

Roll data can be exported from a roll graph or roll table to a .roll.csv file.

The first line of the .roll.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 values for each variable for a single roll determination.

The following data are exported.

Variable	Description
Roll_data	A sequential number
Roll_date	yyyy-mm-dd
Roll_time	hh:mm:ss
Roll_milliseconds	ms
Roll_angle	degrees (output to 3 decimal places). Measured as a clockwise rotation of the major axis about the minor axis when viewed in the positive direction of the minor axis.

Note: Files in this format (.roll.csv) can be added into an EV file and read by Echoview as a raw variable.

Frequency distribution export files (.csv)

The frequency distribution of the target strength of single targets within a selection or region on a single targets echogram can be exported to a .csv file.

The following data are exported.

Variable	Description
Region_name	Name assigned to region. Empty if export of a selection
Region_Classification	Classification of exported region. Empty if export of a selection
Attribute	Attribute that follows for each bin, either Bin_Count or Bin_TS_mean
Targets_Binned	See About analysis variables for descriptions
Targets_Failed_Thresholds
Targets_Failed_Filter
Targets_Excluded
Targets_Missed_Bins
Bin1 midpoint BinN midpoint	The first line then has the median TS value for each bin from the first to last bin Binning is determined by the Frequency distribution settings on the Analysis page of the Variable Properties dialog box

Example file

Region_name, Region_Classification, Attribute, Targets_Binned,Targets_Failed_Thresholds,Targets_Failed_Filter,Targets_Excluded,Targets_Missed_Bins,
-85.0, -75.0, -65.0, -55.0
"IntegrationRegion3", "unclassified", Bin_Count, 20, 3, 0, 7, 10, 5, 5, 5, 5
"IntegrationRegion3", "unclassified", Bin_TS_mean, 20, 3, 0, 7, 10, -82.3, -77.4, -65.0, -54.25

Tip: It is possible to view a graph of the frequency distribution prior to exporting.

Single target detection export files (.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.

Variable	Description
Ping_date	See Single targets variables for descriptions.
Ping_time
Ping_milliseconds
Target_depth and Target_range under Echogram depth mode - OR - Target range under Echogram range mode
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
Transmitted_pulse_length
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_area
Target_intensity_variation
Target_compactness
Target_thickness
Target_length_across_beams
Target_range_extent
Ping number
Target_class
Target_orientation

* For targets derived from multibeam data the angular postion 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.

Multibeam target export files (.targets.mb.csv)

Multibeam targets can be exported to a .csv file. The targets.mb prefix is added to the csv file extension (e.g. filename.targets.mb.csv) to identify multibeam targets exports from other data exports.

The first line of the file is a header row that contains the names of the variables that are exported (see below). Each additional row contains the corresponding variables for a single ping.

Variable	Description
Ping_index	Sequential ping number Note: In Echoview, pings are renumbered sequentially beginning with 0
Distance_gps	Distance (nmi) from the first GPS fix in the data file
Distance_vl	Vessel log (nmi) at the time the ping was transmitted
Ping_date	The date (yyyy-mm-dd) on which the ping was transmitted
Ping_time	The date (yyyy-mm-dd) on which the ping was transmitted
Ping_milliseconds	The date (yyyy-mm-dd) on which the ping was transmitted
Latitude	The latitude (degrees) of the GPS antenna at the time the ping was transmitted
Longitude	The longitude (degrees) of the GPS antenna at the time the ping was transmitted
Heading	The heading of the platform at the time the ping was transmitted Note: Heading values are taken from the heading source selected on the Attitude_page of the Platform Properties dialog box.
Range_start	Range (m) of the closest sample (measured along the beam-axis) in the operand variable.
Range_stop	Range (m) of the farthest sample (measured along the beam-axis) in the operand variable.
Sector_angle	Angle (degrees) scribed between the two outer beams in the operand variable.
Number_of_beams	Number of beams in each ping in the operand variable.
Number_of_targets	Number of targets in the ping.
Ping_mode	Ping mode of the multibeam target variable.
Variable_name	Name of multibeam target variable.
Datafile_ping_number	The number, if any, asssigned to the ping in the original data file from which Echoview read the data.
Target values Note: No title in the header row of the file	Five values are exported for each target: target range (m) target mean Sv (dB re 1m-1) target major-axis angle (degrees) target minor-axis angle (degrees) target status: 1 = excluded from the echogram by the thresholds on the Data page of the Variable Properties dialog box 0 = included on the echogram The values are exported as follows: <target 0 range>, <target 0 mean Sv >, <target 0 major-axis angle>, <target 0 minor-axis angle>, <target 0 status>, <target 1 range>, <target 1 mean Sv >, <target 1 major-axis angle>, <target 1 minor-axis angle>, <target 1 status>, ... <target n range>, <target n mean Sv >, <target n major-axis angle>, <target n minor-axis angle>, <target n status> For Number_of_targets=n+1.

Target length export files (.length.csv)

Target length data for a selection or entire echogram can be exported into a .csv file. The .length prefix is added to the csv file extension (e.g. filename.length.csv) to identify target length exports from other data exports.

Variable	Description
Ping_date	The date (yyyy-mm-dd) on which the ping was transmitted
Ping_time	The time (hh:mm:ss) at which the ping was transmitted
Ping_milliseconds	The millisecond (0..999) at which the ping was transmitted
Target_depth	See About Target_depth
Target_length	See About_Target_length
Target_length_uncompensated	See About_Target_length_uncompensated
Target_length_manual	See About_Target_length_manual
Exclude_below_line_depth	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.

EchoIMPACT export files (.nav and .sonar)

The .sonar format is a binary format specified by Quester Tangent Corporation for import into the EchoIMPACT software.

The .nav format contains one line of comma separated values for each GPS fix with the following values:

ID
GPS_fix
GPS_date
GPS_time
GPS_milliseconds
Latitude
Longitude
GPS_status

For example: $GPSON, 1, 2000-03-01, 00:00:01, 0.0, 0.00102301, 0.00102301, 1

Note: In Echoview version 4.70 and above, EchoImpact exports the range value for bottom detections. Earlier versions exported the depth+draft value. You will need to apply draft or other position offsets before loading into EchoIMPACT, or adjust for them in post-processing.

Georeferenced samples as 3D points export files (.points.csv)

You can export georeferenced sample data from acoustic variables.

Variable	Description
Ping_index	Ping number Note: In Echoview, pings are renumbered sequentially beginning with 0
Beam_index	The beam index number. Note: Only exported for multibeam data.
Latitude	The latitude (degrees) of the GPS antenna at the time the ping was transmitted.
Longitude	The longitude (degrees) of the GPS antenna at the time the ping was transmitted.
Depth	Depth of sample in meters.
Sample value	Sample value for the acoustic variable: Sv (dB re 1m-1) TS (dB) Angular position Minor (axis) in degrees Major (axis) in degrees

Notes:

Echoview does not include projection metadata (associated with the data) with the export. Any projection metadata should be recorded separately.
The *.points.csv column order may change in a future release of Echoview.

3D object analysis files (.csv)

You can export analyses of 3D objects from the Scene manager dialog box to .csv files.

See Exporting 3D objects for more information.

VRML world files (.wrl)

You can export an entire scene or individual 3D objects from a scene to the VRML world format (.wrl). This is an accepted standard format for representing 3D scenes and these files can be viewed using a supported VRML viewer outside of Echoview.

See Exporting 3D objects for more information.

Volume data set files (.dat and .raw)

You can export volume data set files for 3D regions in scenes.

See About inspecting 3D regions and Volume data set format for more information.

Text region inspection files (.csv)

You can export text region inspection files for 3D regions in scenes.

These are text files in the comma seperated variables (CSV) format.

The first row contains Header file entry names. The second row contains the Header file entry (paired) values. The next row is blank. The following rows are divided into row blocks separated by a blank rows. A row block contains the data for a node in the Z direction; columns represent the nodes in the X direction and rows represent the nodes in the Y direction (this is identical to the layout of the Data file in the volume data set).

See About Inspecting 3D regions for more information.

Echoview data export files (.eve)

You can export Echoview echogram data to the .eve format. This is a binary data format specified by Myriax for import into the Eonfusion software.

Eonfusion is powerful software for visualizing, exploring and analyzing and managing environmental research data. It offers exceptional features that enable the integration, juxtaposition and data mining of diverse spatio-temporal data sources.

For information about the variables and data you can specify to export in the .eve format refer to the Export to Eonfusion dialog box.

Refer to Exporting to Eonfusion for more screenshots of Eonfusion visualizations.