A sonar log is a long list of pings, and each ping carries a time, a position and the unit's
readings. This tool writes them all out as a CSV file that Excel, Numbers, LibreOffice, R or
Python read directly, from .sl2, .sl3 and .slg logs of Lowrance, Simrad and B&G units.
The columns
One row per ping, in the order the pings are in the log:
frame,channelandchannel_name(2D sonar, down scan, side scan…),frequencylog_time_s: seconds since logging started, andtime_utcwhen the log stores the datelatitudeandlongitudein decimal degreesdepth,keel, and therange_topandrange_bottomthe ping coversgps_speed,water_speed,course_deg,heading_degwater_tempandaltitudesamples(echo values in the ping) andfile_offset(where the ping is in the log)
The unit is part of each column name, such as depth_m or depth_ft, gps_speed_km_per_h or
gps_speed_mph, water_temp_c or water_temp_f. Choose metres or feet on the form; the automatic
setting uses feet for logs recorded in or near the United States.
Working with it
- Filter by channel. A unit logging 2D sonar, down scan and side scan writes a row for each, interleaved. For a depth profile, keep the rows of the 2D sonar: side-scan pings often have no depth.
- Empty cells mean the log has no value there: no bottom found, no temperature sensor, or no paddle wheel for water speed.
- Decimal points. Numbers use a point. In a spreadsheet set to a comma as the decimal separator, import the file with the point as separator instead of opening it by double-click.
Also in the result
The same job draws the sonar pictures and writes a GPX track with depths, a KML file for Google Earth and a depth map, so the CSV is there for your own charts and statistics rather than for looking at the sonar.
More about what this tool reads and writes: Sonar Log Viewer.