If you look at the pics below, you'll see my finished (Or nearly finished) lake map. Note that there is another lake to the north connected to the finished lake by a canal.

In pic two, you see the expandable 'box' my finished lake is in. Can I expand this work space box and begin working on the second lake... depth readings, shoreline etc.. (just like I've already done) so when all is converted to a user map, all is on one SD card, or must I begin a new work space just for the new map and when complete, put it on a separate SD card?





Sorry for the constant questions. Its the way I learn, and hopefully, it will help some future new guy searching for answers!

Thanks.

You can only have one shoreline in each project. So the other lake should be in another project. The two can be combined in one User Map.

Just to expand on Team Colibri's answer; adding all components to a single user map and keeping the source projects separate is one way to go, and will mean that you spend less time regenerating the map when you make changes. One thing to be aware of in this case is that the default depth colouring system just spreads all of the available palette colours out over the depth range of the project. This means that if your two projects have different min/max depths (likely that min depth always equals zero, but max will probably be different), then your depth colours will be different for the isobaths. You can fix this by using a fixed depth range for depth colours using the settings circled below:



Specifying the min/max depth to be used for colouring the contours to the same values for both projects will give you the exact same colour scheme for both. You'll likely leave the min depth at 0 for both, and then use the deeper of the two project maximum depths as the maximum value for both.

Another option is to extend your shoreline in Google Earth, remove and replace your existing one and just make the whole lot in a single map. I generally reckon on about 20km (12 miles) being the maximum usable height/width for a map - memory usage and generate times can get a little painful after that.

Note also that it is possible to have more than one AT5 map on an SD card - in this case, the unit will load and show them all. The issue you will have is a name clash because RM exported files all have the default "large.at5" name. You can simply change the name to something else, so long as you keep the .at5 extension. If you are displaying transparent areas over images then things get a little more complicated but if you are not then that is all there is to it.

Because I worked with a similar projekt ...

Your lakes are joined with a channel? So they are physically one lake. You could expand your shoreline / create one shoreline, that goes around your two lakes and the channel. This solution I would prefer, if the area is not to big. you could simply replace your old shoreline with the new one. If everything is fine, keep it. If your hardware will get lazy, return to the old shoreline und use another for the second lake.

Thanks fella's.