Hi Hubert,
I don't *think* that depth data is stored at all in USR v3. I agree - it would be nice if we could support v4, but we don't have the access to the format at the moment. That may change in the future, but for now we recommend sonar logs as the data source when using Lowrance - although I appreciate that that doesn't help you if you have v4 tracks that you would like to use!

Matt

Supporting v4 would offer the user to collect much more data on a sd card than storing whole recordings.
For example when you are on holiday for a week or two,
there is no need to move recordings from the sd card to a pc or to use more than one sd card.
It is much less data to handle.

Usr-files for depth logging should be ever an exception. The detriments prevail, e. g. identification of logg errors etc. and for SS and BT is usr not useable

In times of 16 ... 32GB and more SD-cards (sufficient for minimum one day or more) would be a usr-file for depth logging a step backward.
This is my opinion!


Best wishes
fjordfisher

User data V 3 should be with depth data. The user manual for HDS Gen2 Touch says:

User Data file version 3 (with depth) --> Can be used when transferring user data fram an HDS system or Mark/Elite to a legacy Lowrance (LMS, LCX, etc)


User Data V2 do not contain depth data.

---
The difference between using *.usr data / exported track data unlike to use logfiles _for me_ is:

Logfiles contain a lot of information and my storage cards have enough space, but a lot of inexperienced users do not store sl2 data. But almost everybody is running a track and it is simple, to get these tracks and also it is easy to send and share these files by mail.

The second purpose is, that most units only have a single sd slot. If someone is using a navionics card, there should be stored no log data to prevent the card and maps from damage. In that case ist would be a great alternative to get depth data by exporting stored tracks and use them for mapping.

Luke wrote:
True Luke - but these days you can buy a 16gb SD card for around 10 Euros, I think the problem is much less than it was. As Fjordfisher says, sonar logs are a much better solution. Sonar viewer, depth correction, bottom hardness etc. Still - I will look into the USR v3 depths. If they are there, then we should support them.

But also as Hubert says:
Users with Units that have only one Slot and using a Commercial Card in that Slot,
cant record anything on the card.
But they can store the Track in the internal Memory.

I dont say that this has to get the highest Priority, but has to be taken in mind.

I think the depth stored in version 3 is for waypoints, not tracks. I might be wrong though...

/Martin

Martin wrote:
Martin - you are right. I've taken a look, and we do get depths for waypoints, but not track-points - and there is no space within the file for depths to be associated with track-points.

Matt

That could be an explanation.

USR V3 is for exporting / importing data from one unit to another (Elite units only can write this version)
USR V4 is only for exporting / importing data for (all) HDS units
USR V5 is only for exporting / importing data for HDS Touch units.

If I open a USR V3 with Insight Planer, there is an empty column for depth values.

Never the less, V4 created with a HDS / HDS Touch contain depth values and would be a choice to transfer data by email, share over the internet or create data, when you use a Navionics map with the unit.

I`m not recommending it, but I have saved sonarlogs and screenshots to Navionicscards (I have two, one 4-5 years old and one that is brand new) on numerous occations with no issues.

On the one I got hired, only 400 mb memory was free. It is a bit cumbersome, to use this one for logging and I do not want to take the risk of damaging it.

Does any Lowrance USR version 2-5 support track-segment(TRKSEG) format.

So far I've only been successful importing tracks with segments using GPX.
And hope I'm not hijacking thread, subjects seem close.