Some display, export and other options in Echoview take transducer geometry into account and others do not. This page lists some common display and export options and describes whether or not they take transducer geometry into account. This page is broken into the following sections:
Note: If you want to know whether transducer geometry is applied to a display or export option that is not listed on this page, contact Echoview support.
Many exports from Echoview include latitude and longitude values. The table below defines whether the exported values have been corrected for transducer geometry or are the latitude/longitude of the GPS antenna at time of ping.
|
Export type |
Latitude/longitude values exported |
Implications |
|
Data value exports (including Sv, TS, Angular position, underlying data) |
Latitude/longitude of GPS antenna at time of ping |
|
|
Latitude/longitude of GPS antenna at time of ping |
Exported depth is not at the exported latitude/longitude coordinates unless the transducer was located at the same point on the platform as the GPS antenna and was pointing straight down |
|
|
Analysis by regions and cells exports (including analysis by regions, cells, regions by cells) |
Latitude/longitude of GPS antenna at time of ping |
Exported region and cell start, middle and end latitude/ longitude are not at the real world coordinates unless the transducer was located at the same point on the platform as the GPS antenna and was pointing straight down |
|
Latitude/longitude of GPS antenna at time of ping |
||
|
Latitude/longitude of GPS antenna at time of ping |
||
|
Latitude/longitude of GPS antenna at time of ping |
||
|
Latitude/longitude are not exported |
||
|
Corrected for transducer geometry |
Geographic positions of fish track exports are at the real world coordinates |
The table below defines whether the data is used to construct 3D objects and place them in scenes is corrected for transducer geometry or is based on the latitude/longitude of the GPS antenna at time of ping.
|
3D Object type |
Latitude/longitude data used in construction and placement of the 3D object |
Implications |
|
Corrected for transducer geometry Note: There is not a dynamic link between the 3D objects and transducer geometry settings, i.e. if you change the transducer geometry settings the 3D objects will not be updated automatically |
3D objects size, shape and position in the scene are based on real world coordinates |
|
|
Latitude/longitude of GPS antenna at time of ping |
Surface properties and position in the scene will not represent real world coordinates unless the transducer was located at the same point on the platform as the GPS antenna and was pointing straight down |
On 3D Single target graphs showing multiple beams, transducer geometry is taken into account when drawing the beams.
Single target manipulation operators calculate distance between single targets using data that have been corrected for transducer geometry when comparing positions of single targets.