Hi Matt,
With the latest update I am reimporting all my Sonar Log files so I can use the new Sonar viewer. It is easier to manage any anomolies using the visual method.

However the initial edit window (before you open either Edit or Sonar) does not fill the screen with the track like it used to do. Here is an example of the screen I get when I first import an sl2 file. In previous versions the edit page would be filled with the zoomed in track. Any ideas???

Hi Meggs,
It looks to me like there must be some track-points at the top-left of the screen (obscured by the toolbar).
Is this a log file that you have imported before without issues?
If so, we need to take a look at it - is there any chance you could upload the original sl2 file (eg www.sendspace.com/) and send the link to the uploaded file to This email address is being protected from spambots. You need JavaScript enabled to view it. . I will take a look and get back to you.

cheers,
Matt

Hi Matt,

I'll see if it behaves the same with a smaller file. The example was an all day recording (nearly 2GB) and uploading it will kill my wireless internet allowance. Here's another image from Global View when you close the track file.

Thanks,
Meggs

Hi Meggs,
You've got some rogue track-points in there for sure. Not sure what the cause is, it could just be some sort of corruption/bad values in the file, or it could be an issue with RM 1.5. If you go to the track view, zoom out a bit and then zoom into the top-left of your track, you'll probably see a group of points (or maybe just one). Select it - draw a region around - and delete them. That will fix your track up in the short-term.
If you do this this issue again in a smaller file, please do upload it and send me the link. You'll get some size reduction if you compress the file first in winzip or similar.

cheers,
Matt

Hi Matt,
You are correct. There are rogue trackpoints in most of the recent imports I have done (strangely not all). These files had all been previously imported and edited in the non Sonar view version. I'll get a file to you to have a look at.

Thanks,
Meggs

Thanks Meggs, I appreciate it. We've run a lot of sl2's through test but not seen this issue - we'll get to the bottom of it and I'll get back to you.

cheers,
Matt

Hi Matt,

I have seen the same behaviour a few days ago when reimporting some tracks.
I will try to find them.

Danny - I have found the issue with this. It is an occasional error that occurs when correcting transducer location during import. The good(ish) news is that the affected track-points are *very* wrong (several thousand km's), and a very small number are affected - so they are easily removed post-import. The rest of the import is OK. We have a fix, but are waiting on the other sl2 import issue before we make an update.

cheers,
Matt