How to get GPS, depth and a track out of Humminbird sonar recordings
Short answer: every ping in a Humminbird recording already carries the boat’s GPS position, the depth, the time, the speed and the heading. They sit in a small header in front of each ping inside the .SON files. Read those headers and you have a table with one row per ping, and from that table a track (GPX or KML) and a point file for depth maps (XYZ). You can do it with SonarCSV in the browser, or with PING-Mapper if you also want sonar images.
Recording on the unit
Humminbird units with an SD or microSD card slot can record the sonar while you fish or run a survey. Put a card in, start a sonar recording from the unit’s recording menu, and stop it when you are done. The exact menu depends on the model, so check your manual for “sonar recording”. Two things are worth knowing before you go out:
- You need a GPS fix. The position of each ping comes from the unit’s GPS. With no fix, the pings are saved with no position.
- Stop the recording before you switch off. If the power goes while recording, the index files may be incomplete. The pings are usually still readable (see below).
Where the files are on the SD card
Put the card in your computer. The recordings are in a folder called RECORD. Each recording is one small file and one folder with the same name:
RECORD/
R00012.DAT
R00012/
B000.SON B000.IDX
B001.SON B001.IDX
B002.SON B002.IDX
B003.SON B003.IDX
R00013.DAT
R00013/
…Copy the whole RECORD folder to your computer if you want to keep the card free. Keep each .DAT next to its folder: the names are how they are matched.
What each file holds
Rxxxxx.DAT: a few dozen bytes about the whole recording: the date and time it started, where it started, how many pings it has and how long it lasted.B00n.SON: one file per sonar channel. It is a long row of pings. Each ping is a short header followed by the sonar returns (the image). These files are the big ones: hundreds of MB, or several GB for a long day.B00n.IDX: an index for the.SONwith the same number. For each ping: the time and where the ping starts in the.SON.
The channels, as the PING-Mapper documentation lists them:
| File | Channel |
|---|---|
| B000.SON | Down beam, low frequency (50/83 kHz) |
| B001.SON | Down beam, high frequency (200 kHz) |
| B002.SON | Side scan, port |
| B003.SON | Side scan, starboard |
| B004.SON | Down beam, MEGA frequency |
The header of each ping holds: the ping number, the milliseconds since the recording started, the position (as Mercator meters, which convert to latitude and longitude), the heading, the speed, the depth the unit worked out, the channel and its frequency, and how many sonar samples follow. The length of the header changes with the model (67 bytes on the 9xx series, 72 on 11xx, Helix and Onix, 152 on Solix), but each field has a tag in front of it, so one reader can handle all of them. Humminbird does not publish this format. It was worked out by the open-source projects PyHum and PING-Mapper.
Steps with SonarCSV
- Open SonarCSV and press Choose a folder. Pick the
RECORDfolder (every recording) or drag one.DATand its folder onto the page. You can also pick the.DAT,.SONand.IDXfiles by hand. - Your browser may ask you to confirm that the page can read the folder. Nothing is uploaded: the page reads the files on your computer.
- Wait for the progress bar. Only the header of each ping is read, so even a file of several GB takes a short time and is never loaded whole.
- Check the result: number of pings, duration, distance, minimum, maximum and mean depth, and the drawing of your track coloured by depth. If the track is where you were, the conversion is right.
- Download the CSV, the GPX, the KML and the XYZ. With more than one recording there is also a ZIP with everything.
Rows, repeated positions and units
- Repeated positions. The sonar pings faster than the GPS updates, so several pings in a row carry exactly the same position. In the recording we tested, 1,727 pings held 436 different positions. By default SonarCSV keeps the first ping at each new position. Untick the option to keep every ping.
- Depth is the unit’s own digital depth reading, in meters (
depth_m) and feet (depth_ft). A depth of 0 means the unit had no reading at that moment. Those rows stay in the CSV and are left out of the XYZ. - Time.
time_sis seconds since the recording started.time_utcadds the start time from the.DAT. Without the.DATthere is no date, only seconds. - Speed and heading are the values the unit stored with each ping: speed in m/s and mph, heading in degrees.
- Water temperature is not in the files as far as the documented format goes, so it is not exported.
The track: GPX and KML
Open the .kml in Google Earth to see where you went. The .gpx works in GPX viewers and in mapping apps that import tracks. It keeps the time of each point and, as an extension field, the depth.
Making a depth map from the XYZ
The .xyz file is plain text: longitude, latitude and depth in meters on each line, separated by spaces, with no header line. Depth is positive downward. It is the raw material for a depth map, not the map itself. The general recipe is the same in any tool:
- Load the file as a layer of points (in QGIS it is a delimited text layer with X = first column, Y = second column, in WGS 84).
- Interpolate the points into a surface (a grid), with whichever method the tool offers.
- Draw contours or colours from that surface.
The same works in Surfer or other gridding programs. Two honest warnings. A single pass gives you a line of depths, not a map: the interpolation between far-apart tracks is a guess. And the depths are as recorded: they are not corrected for the water level of that day.
Do it in your browser
Add your recording folder. SonarCSV reads the .DAT, .SON and .IDX files as they are, shows the counts, depths and your track, and gives you a CSV, a GPX, a KML and an XYZ. Nothing is uploaded and nothing is installed. The preview and the first 500 rows per recording are free, $9 once for everything.
Convert my recordingOther tools
- PING-Mapper (free, open source). The tool to use if you want the sonar images themselves: side-scan mosaics, georeferenced imagery, substrate maps. It also exports the ping attributes as CSV. It runs in a Python environment that you install first, and GPX or KML are made afterwards in a GIS program.
- Humminbird AutoChart PC (official, paid, Windows). Builds depth maps from your recordings to use on the Humminbird itself. It is a map-making program, not a way to get a table of pings.
- ReefMaster and SonarTRX (paid, Windows). Desktop programs for depth maps and side-scan mosaics that read Humminbird recordings among other formats.
FAQ
Do I need all the channels?
No. One .SON is enough, because every channel carries the same position and depth. Adding the whole folder is simply easier.
Which models were tested?
One real recording, from a unit that writes the 9xx-series layout (67-byte ping headers), made by the USGS on the Colorado River in Arizona. The Helix, Solix and Onix layouts are read from the documented format and have not been tested with real files. The preview is free, so you can check yours.
The recording was cut off. Is it lost?
Usually not. If the .IDX is missing or does not match, SonarCSV reads the .SON ping by ping and keeps everything up to the damaged part.
Is anything uploaded?
No. The recording is read in your browser and the files are built there.