I am a new user to ReefMaster, and while importing my old DrDepth data (a lot of it), it strikes me that I am missing a function for adding the water level offset while importing data.

So in other words, I would love an option in the "Import GPS assets" window, where I could set a manual offset value for the entire batch chosen.
This would reduce the cumbersome need to edit every single track afterwards.

Thanks
//Mats

Follow the pictures.










Best wishes
fjordfisher

Thanks Fjordfisher - that is one simple way to do it.

Another way, which can take into account varying water levels, is to create a tide station with known water levels specified at particular times. This does not have to be for tides - it can be used for lake levels as well.

Here's an example:

First, create a new tide station.

Create a text file holding the depth offsets for known times. Bear in mind that depths between two specified points are interpolated so, if you know a lake level is 3 feet up on a certain range of dates, you should enter this level at the beginning and end of these dates so that the same value is used throughout the range (if you are only using a single depth, then you do not need to do this). Also note that tide depth values are subtracted from track-point depths. This is the opposite of the way the keel offset value is applied. Negative values are OK if you wish to add a depth offset.





Once you have a tide station, you can set your import to use this tide station for all imported tracks. If your tide station covers a range of dates/depths, then the appropriate offset will be applied to each track.




Matt

Mats wrote:
You probably know this already, but if you are importing exported csv files from DrDepth there is no need to offset water level once again, it was done already in the DrDepth import. All other edits are also passed along if you use the csv-option to transfer to ReefMaster. If you, like me, had done lots of bad data editing in DrDepth that is a better option than to reimport the slg/sl2-files or whatever. But for upcoming ReefMaster-hardness it might be better to go the sl2/slg-route.

Regards,

/Martin

Thank you Fjordfisher, and thank you Matt.

Fjordfisher's idéa with changing sensor profile is a bit radical, but will work. It generates some extra work though, because the waterlevel tend to never be at the same level as before. So then I would have to created a new profile every time.

Matt,
I actually tried making a Tide Station, but failed. So I did not think it was possible with single values.
Now I tried it again, per your instructions, with dual values, but still fails. Reefmaster reads the date/time but not the level. Please see below:

However, I still beleive it would be best to implement the same 'manual' function to the "Import GPS assets" window as this functionality already exists in the Track=>Edit=>Tide dialog. Then it would be consistant.


Thanks
//Mats

The import settings best for keel offsst, Bu You can also use it for tide correction with many profiles. Better for tide correction is Matt's tip.
I can say, that was the usual setting from DD and i never had problems. But each user can set, what he want.

Elite-user - don't Forget to mark with a cross the Elite unit.

Best wishes
fjordfisher

Hi Mats,
I've had a closer look at this for lake-level use, and there is a problem (a bug, I guess..) where the track is only looking for tide points that are present within the track time period. This is fine for tides, but not so good for lake levels - it means that unless you have a point specified within the track period, it will not be applied.
I will fix this behaviour so that points from either side of the track time are used for the interpolation.
In the meantime I suggest you follow fjordfisher's advice.

Your suggestion for a single water offset value in the import screen is a good one and I will look at that also.

Matt

Thanks for looking into this Matt, on a Saturday... That's what I call customer focus :-)

Ok, so that explains why I didn't get the tidal station to work. I though it was me!


I think I will stick to the manual Track=>Edit=>Tide function for now. Then I feel I have better control over the data, and can edit it easily, if needed.

Cheers
//Mats

This issue is fixed in v1.5.0.12.