I am manually reconstructing the creek and rivers.

I am submitting a Reefmaster Feature suggestion that I will likely need.

This process of build creeks and rivers, will result in 30-50 individual tracks that I can include in a User Map. I write-out this User Map(with 30-50 track-segments) as a Humminbird .HT file.

I would like Reefmaster to be able to import this 000.HT file and have the track-segments remain as individual track-segments and remain unconnected.

I would like to create several User Map in this manner, then be able to merge into a single track and have the track-segments remain as individual track-segments.

I'm just wondering what the reason is for needing to import the split track from an HT file? Tracks within RM do not have segments, so the only way of implementing something like this now would be to create a separate RM track for each segment within the HT file; in your case, 50 tracks or so. This would be similar the situation you have now, where you have created each track separately within RM?
Or am I missing something?

Matt

I was building creek beds. Each creek might have 3-5 branches off a main trunk.
All totaled for Lake Fork I now have 141 individual tracks.

I was assuming that if I combined the 3-5 branches and the main trunk of one creek, then the User Map constructed was of track-segments.

When I Write Out this User Map to a Humminbird .HT, then is it not a track with track-segments? It displays correctly on my HB units.

If I turn-around and Import GPS Assets and import this .HT file, then the track-segment end-points are linked. Shouldn't the .HT file import as a track that is the same as the User Map from which it was built?

Here is the User Map of a creek. The creek has 1 main trunk and 3 branches.
I created 4 individual tracks, then build the User Map for the whole creek.

Then written out to a HB .HT file, and re-imported into ReefMaster and created a User Map of this 1 track:

My problem is the track end-points are now joined on the track for the whole creek.

Hi,
At the moment this is the expected behaviour, as each track in a .HT file is imported as a single track. RM tracks do not have the concept of separate segments, but we can combine multiple tracks into a single, segmented HT track on export. The only way we could fix this in RM with the current track model would be to import segmented HT tracks as multiple tracks. So in your example, there would be 3 or 4 tracks in RM after importing your creek beds. Would this resolve your issue? I am also curious as to why you want to re-import the HT file?

Matt

Since a creek consisted of 3-4 individual tracks, I was attempting to merge into just 1 RM track.

I was just attempting to reduce the total number of individual tracks to maintain.
I can work with and use User Maps to accomplish this.

No RM changes necessary.

In what formats can RM export segmented tracks?
Does Lowrance support track-segments?

RM can export GPX files with segments also - although whether these segments are honoured depends on the application that imports them (e.g. HBPC ignores the GPX <trkseg> tag as far as I am aware).
Having said that, RM also ignore segments, but we could change that by creating a separate track for each segment, which would be easy enough - although it could result in a lot of tracks.

As far as I know, Lowrance does not support segmented tracks. There are however other options for displaying this sort of information on Lowrance units; RM can make "proper" maps in AT5 or LCM formats, which also means you can style tracks within RM and have them appear this way on your unit.

Matt

I'm good.

I guess I had it in my mind that RM supported track-segments.

Guess I was assuming that each contour-line was a track-segment.

Thanks, I'm GTG.

Really nice a fishing those creeks I've been mapping, this is a great help poking up creeks into some shallow waters. Tough turning around in some.