Thursday, January 7, 2016

Helpful Lowrance Hints: Depth Tracking

We promote BioBase as an automated "easy-button" solution for creating aquatic maps, but unfortunately, mobile acoustic data collection is not something you can push a button and forget about and expect perfect results.  Like using most other sophisticated instrumentation, users need to monitor that the instruments are performing as expected and sometimes make adjustments if they aren't.

As such, we often stress the importance of monitoring your sonar and GPS display while logging sonar making sure you get a clear view of bottom with a continuous digital depth reading (Figure 1).  If you can't see a digital depth reading on your screen, add it (here's how). If you're a first timer not familiar with sonar of "fish finders" you should spend some time familiarizing yourself visually interpreting a sonar display prior to mapping "for real."

Figure 1. Example of a clear 200 kHz ("Sonar;" left) and 455 kHz Downscan ("Structure;" right) signal. Depth (white line) should track pretty well through moderately dense plant canopies.  Smooth and accurate depth tracking through plant canopies occurs during times of the year when plants are elongating vertically.  As the growing season progresses, horizontal and "matting" growth proliferates and high levels of plant biomass can obscure bottom readings (see Fig. 2). 
Figure 2. Example of periodic losses of depth in the vegetation canopy.  Extreme changes and periodic losses of depth are automatically smoothed or removed from BioBase.  Users can verify and edit their output in the main trip viewer in BioBase EcoSound, loading the data and using Trip Replay.

Figure 3.  We’ve frequently get calls from users wondering why parts of mapped water bodies were missing from their BioBase map after upload.  Often in these circumstances, depth was lost as some point in the trip and the user did not notice and continued driving their path recording null data.  This stresses the critical need to monitor your sonar display and ensure continual depth tracking.
Mapping Extremely Shallow Water: Tricks for a Tricky Environment
Areas of waterbodies less than 2 ft (< 0.75 m), are difficult to characterize with acoustics.  Target separation between the bottom and the face of the transducer is extremely small and these environments are very acoustically noisy due to wind mixing.  Accordingly, by default BioBase requires a minimum depth of 2.4 ft (0.76 m) to create vegetation and bottom hardness outputs. Reading depth alone is not as difficult and you may find your Lowrance unit providing reliable depths as shallow as 1 ft (0.3 m).  But, as stated earlier, this is a tricky environment and the acoustic signal can easily be lost and difficult to recover, especially in Auto Range.

Alternative 1: Fix the Range (Shallow Water Only)
Fixing the Sonar Range to 5 ft in very shallow waters can be a tool to establish a known zone where the sonar should search for a bottom signal (Figure 3).  This may ensure a more consistent bottom lock.  But, Range should be reset to Auto if mapping in variable or deep waters to ensure the 3200 bytes of data are in the optimal range for bottom typing.  Never change range during logging or it could corrupt the .sl2/.sl3 file.

Alternative 2: Use a Kayak

Figure 4. Sit-on-top kayak mounts of HDS.  Kayak's are light and will not draw as much water.  You may be able to bring your transducer.
Alternative 3: Use a Jet-ski pulling a Catamaran
Figure 5. See how EnvirolinkSouth Ltd in New Zealand maps shallow waters with a Jet-ski pulling a Catamaran with a transducer and Point-1 GPS tethered by long cables to the Jet Ski with HDS Display.  Ensure cavitation behind the jets do not create noise under the transducer.

Alternative 4: Use a Robotic Boat (especially if you have to map rivers with Hippos)!

Figure 6. Autonomous Platypus Lutra boats equipped with Lowrance can help you stay alive if Hippos are in your way or if you want to map waters difficult to access with a boat. Ask a Platypus rep about Boat Rental/BioBase EcoSound Bundles.


  1. Interesting post. I like the idea of the robotic boat method when mapping water habitats of potentially dangerous animals.

  2. To give a little more depth on the Platypus solution, we have an extremely low cost platform that integrates seamlessly with Lowrance and BioBase. The boats are about 40' and 20 lbs, and can be out of the car collecting data in five minutes or less. We have been working with Ray to make the experience as user friendly as possible, and now we have a much more efficient alternative to all the manual options listed above! Please take a look at our website,, for more information

  3. IG charts a great thing.
    But we in europe ask: Why can't give Biobase results in integer meter values? A simple feet converting only give broken meter values - this is not optimal, Biobase could do more in this case.

  4. We hope that metric contouring in BioBase will be an available feature sometime in 2016.

  5. Thanks for answer. Okay, this are a good news. But i know from other Forums, that i and other user ask for more, e. g.:

    - Is there a possiblity to abtain a shapefile additional to an AT5 file? Background: The user can self change a lot of things, e. g. font size, chart categories etc., he can could combine IG charts with other datas in shape file format (e. g. from the government) and he can use the result not only in the unit or in the Insight Planner.

    - Why i only must accept the IG chart name? Better was a choice of IG name or the standard name "Lowrance". Background: Charts with IG name i can't combine with other AT5-files together in the unit. This is only possible, if i forgive to my own charts the IG-chart name. This is not optimal, e. g. also for own topo- or aerial photo overlays.

  6. To answer your first question: Insight Map Creator and Planner are tools to take content you create in GIS and create maps in Lowrance/Simrad chartplotter format. ESRI Shapefiles go in, AT5's come out and is not designed to be the other way around.

    To answer the second question: each Insight Genesis map must have a unique name in order to load more than one at a time on a single chip.

    Hope this helps.


Please share your thoughts about this topic with us