Hi TJ. First thing - Switched everything over to Vector. It works fine, looks fine on the Lowrance and there is a much, much faster "user map" generation time compared with Raster. (Thanks to Matt for convincing me to switch)
Second, I'm still experimenting with "multiple sections" for one big lake. (BTW No problem putting multiple maps of separate/Different lake maps on one SD card whether they're Raster or Vector)
Anyways, for the big lake project, I put one of those "multiple sections" together tonight and with a few more "adjustments and some fine tuning" (Which I'm going to finish in the morning) I think it will look good.
I tested a version I got done and it looked good on the Lowrance, well, except for a small gap between the two sections where they're supposed to join up. It looks like my "fine tuning" will be concentrating on where and how I place the borders of the "Defined Area" for each map. To much overlap of those borders, and I get a screwy looking merge between the two when I look at them on the Lowrance, but playing with the borders, constantly switching between the maps while using ReefMaster and finding a spot on the shoreline to use as a reference point for where one map ends and another begins might make the merge look better. (And hopefully there will be no gaps!) I'll know tomorrow and will report back.
As for Raster or Vector and putting it all on one map, Though I good do it, at least with what I've recorded so far, I faced a few problems. I'd get "Insufficient Memory" warnings when ever I tried to make a change or add more tracks, which I found ways to get around, but that's a pain. After finally getting everything generated, the map would run great on the Lowrance, but I came to the conclusion that the best thing to do for the big lakes, like others have said, is multiple sections with smaller "defined Area's". (Which will take care of the "Insufficient Memory" messages!) I just have to work on the map section "merge" points a bit more to get the finished product to look good.