Welcome, Guest
Username: Password: Remember me

TOPIC: Help

Help 10 years 9 months ago #6603

  • SRR68
  • SRR68's Avatar
  • Offline
I've spent the last few years mapping my lake which has an area of approximately 900 square kilometers. I currently have one workspace with multiple projects for different portions of the lake. With the amount of data that I have collected and memory limitations my current configuration is quickly becoming unworkable.

My solution is to break this down further into one workspace per lake portion. If anyone has a better idea, I'm all ears.

Many of my tracks have been filtered for bad data and my understanding is that RM does not modify the original track, so to do what I am proposing, I would need to filter all of those tracks once again when I load them into the new workspace. Am I missing something here? Your help and suggestions would be greatly appreciated.
The administrator has disabled public write access.

Help 10 years 9 months ago #6606

  • Matt
  • Matt's Avatar
  • Offline
You could export the track data in CSV format, which will keep your modifications. Then import this into another workspace. The downside of this is that you will lose connection to the sonar file, so you won't be able to use the viewer, sidescan etc - but for mapping it will be fine. Note that you can export multiple tracks at once by multi-selecting in the asset list (or global view).

The other option is to leave everything in the one workspace, but just work on one project at a time - this should be OK, memory wise.
The administrator has disabled public write access.

Help 10 years 9 months ago #6617

  • SRR68
  • SRR68's Avatar
  • Offline
Matt wrote:
You could export the track data in CSV format, which will keep your modifications. Then import this into another workspace. The downside of this is that you will lose connection to the sonar file, so you won't be able to use the viewer, sidescan etc - but for mapping it will be fine. Note that you can export multiple tracks at once by multi-selecting in the asset list (or global view).

The other option is to leave everything in the one workspace, but just work on one project at a time - this should be OK, memory wise.

Thanks for the quick response Matt. I use the viewer on a regular basis to identify key areas so that won't really work for me and I only ever open one project at a time. My issue seems to stem from all of my tracks (600+) being loaded when I open my workspace. This just bogs the program down making it virtually unusable other than to generate charts which takes a long period of time. Is there any way that loading tracks by default could be disabled or done on a per project basis? Failing that, I'll have to start from scratch.
The administrator has disabled public write access.

Help 10 years 9 months ago #6618

  • Matt
  • Matt's Avatar
  • Offline
Just having the tracks loaded bogs RM down? What sort of system specs are you running?
Delayed loading of the tracks is something we have thought about - it could happen in a future version - but apart from some memory usage it shouldn't really slow other things down.
The administrator has disabled public write access.

Help 10 years 9 months ago #6619

  • SRR68
  • SRR68's Avatar
  • Offline
Thanks Matt. I know... its time for me to upgrade my computer but yes it does. No worries. I'll start over.
Last Edit: 10 years 9 months ago by SRR68.
The administrator has disabled public write access.
SCROLL TO TOP