I would think it would be easy to implement. Make a copy/move to option for a workspace.

I've had to break my first workspace up into multiple lakes now that I've logged so much data. It would be nice instead of having to reimport and manually edit the depths of each track to just move the data from one workspace to the next.

Chris

Further to reelnmn's request, a global filter on that data would be of huge benefit. I've logged so much data that my project is taking a good half hour to load. I am sure that much of my data is superfluous and having to manually filter all of this data would be tedious to say the least. My chart has the level of detail that I need so essentially I'd like to see my chart, as displayed, converted back into filtered track files(???) to load into a new project or something along those lines. Is this a possibility?

Moving assets between workspaces is something we've had on the list for a while - it'll come quite soon hopefully, and shouldn't be too hard to implement.
If you do have tracks with a lot of edited points that you want to use in another WS, the best course of action now is to just export those tracks in GPX or CSV, and re-import. You'll lose sonar and bottom composition, so it's not a perfect solution, but you would get your edited points which could then be used in a project. Note that if you export with the tide adjusted option, then you shouldn't adjust the track in the new WS.

Half an hour load time for a project? Have you updated to 1.7? Load times are massively reduced (x50 or more). If you have already updated - how big is the WS file on disk, and how many tracks do you have?

Matt

Yes I have upgraded to version 1.7. I live on a huge body of water and my current chart covers about 235 square kilometers. The workspace is about 110mb with about 95 tracks containing 35GB of data. A lot of this data is redundant for the level of detail that I need so like I said a global filter would be nice. For example to be able to set my map resolution to say 25m and discard all but the shallowest point.

S.

And that workspace takes half an hour to open, or to generate the map? If it's the former - that is unexpected after the 1.7 upgrade - we have tested workspaces with several hundred tracks that load in under 30 seconds. What are your system specs?

We are working on a simplify feature, that will reduce a set of track-points to remove anything that doesn't contribute to the map. It will be a little while though, and probably something that makes it into 1.8.

It takes 30+ minutes to open the project (generate the map). I am using a laptop that is about 5 yrs old, running windows7, 4GB memory, with 2 AMD M300 processors. Its not the quickest car on the lot. I guess I need to do some track filtering and/or break my chart down into segments.

S.