I'm working on mapping out a reservoir that has wide swings in water levels, typical range is 1665 to 1677 feet (AMSL), with extremes going as far as 1645 to 1680 ft. The USGS has an onsite depth/height gauge with 15 minute interval water height values available for export on line. I was able to successfully export this data and create a tidal file for the entire summer for 2015 and 2016 to cover all the data collection days so far. However in order to get an appropriate difference value, I had to choose a "normalized" water height value of 1675 ft and subtract the provided height values in excel. I chose 1675 ft because it's the most common summer water height. The normalized adjustment values were exported to the appropriately (tidal) formatted CSV file. I then imported all my tracks utilizing the normalized tidal values. This all worked beautifully!

But now I want to export maps for every 2.5 foot interval (maybe even 1 ft interval) of change from 1660 to 1680 feet. That's nine (or even 20+) different maps! Is there a way to easily do this other than importing the same set of tracks 9+ times, each with a different normalized tidal value? Is there an easy setting to manually adjust the water height before export? Am I missing something obvious?

Kudos on the tidal adjustment feature! That was a huge feature in this particular case. Thanks!

An easy way of doing this is coming in the next major release - just a simple water level offset that can be applied to the entire map project.
For now the best way we have found is to group export all of your project tracks to a single CSV file (multi-select in either global view or asset list). You can then re-import this CSV file and apply a water level offset to the single resulting track and then use this track to create a new project. You can copy projects using the duplicate function, so you can keep boundaries etc (just swap the component tracks out). Not a totally ideal solution but it does work and isn't actually that much effort. Just make sure when you export the tracks that you check "export tide adjusted depths" - this will apply any tide/water level offsets to the exported depths.

Awesome news, and thanks for tip. Can I ask if any kind of max value limitation was going to be used for this offset function? Just wanted to make sure it was going to be more than say, 50 ft for my purposes.

As a follow-up to this. Will the final offset drop boundary layer depths as well?

I know with the reservoir I'm mapping with 20ft water level changes, I create the first map at top water level with boundary depth of 0, then when I work down, I have to assign negative numbers to the boundary depths to make it look correct.

Maybe a checkbox option for yes/no on adjust boundary depths too?

The current (pre-release) implementation is that it changes everything by the set amount, including shorelines, islands and all data points. This seems to work pretty well, and to be honest I can't really think of a situation where you wouldn't want to also adjust boundaries, because if you don't you are going to end up changing the topography.

Awesome! I agree, thanks a lot.