As user maps removed, I see the only way to combine set of projects into one map: create one more project and add other projects as layers. Is it correct or I miss something?
If yes, why I need to export each project as shape and only then import it to another? Why it can't be done without these operstions? For example, I have workspace with 10 projects (to speed up calculations and set different approximation parameters).
And I need to export 10 times, then import at least 30 files (area, min maj contours), select depth field 40 times. A lot of manual work.
And, if I add new track which will be included in for example 3 projects, I need to delete 9 layers, export and import again.
And export dusabled in trial, so I can't test it in details.

Map projects now have all of the functionality of user maps, plus a lot more.
You can copy and paste layers between map projects to achieve what you are trying to do, and you can do this in a number of ways - either group select the layers you want in the layers tab, use the copy menu command (or ctrl+C) then paste into another project, or just drag the group of layers from the layers list onto a project within the asset list.
It is also possible now to simply export a set of projects at once; just group select in the asset list, right click and export. Depending on what you are trying to achieve, this might be the easiest option.

Thanks Matt. I missed ability to group select and drag-n-drop layers from one project to another. It's exactly what I need, and is really better than user maps.

One more question about layers and user map replacement - after drag-n-drop from set of projects I got a lot of layers with names isobaths, major contours, minor contours. It would be nice to know from what project I added layer - maybe add prefix with name of original project to layer name?

Yeah - something to think about. You can rename your layers, but I agree this would be a hassle when copying a lot of them.
Remember that, depending on your final export format, you might not need to combine layers in a single map anyway. Just group-export the projects instead. This way you can carry on generating each separate project without having to keep copying layers over afterwards.

I've been group-exporting smaller projects, and this works wonderfully. I just create the projects using the same layers, contours, and map settings. I use a code for the names of my projects that reflect the settings. Like, "North -15 135 V5 B5" North end of the lake, -15 water level offset, 135 degree sun angle, vertical scale 5, Brightness 5). I make them all with 3 foot contours, no minors, smoothing on one, and 50 interpolation.

Matt wrote: It works, but why I get number of shapefiles sets instead of one merged?
Matt wrote: It doesn't work as expected - if I select 2 projects output file contains shapes only from first of selected projects.
How I worked in Rm1: create set of projects, add all to usermap, export usermap to shapefile, import shape into GPSMapEdit, combining in this program with another sources and editing if nesessary.
So overhead in Rm2 comparing to Rm1:

• Need to add TYPE column in isobaths shapes using external tool (my unanswered question here: reefmaster.com.au/index.php/forum/suppor...-rm2-export-to-shape)
• Need to import in GME not 3 files (isobats, min maj contours) but a lot of, as Rm2 can't combine similar layers in one shapefile.

Can it be fixed?

Yes - we can restore the TYPE attribute.

Multiple project should work, but the Shapefile will take the base name of whatever you select when exporting. The rest of the name comes from the layer name, and in the case where you have multiple layers with the same name (e.g. Isobaths), then numbers will be appended in the exported files (e.g. <save_name>_Isobaths1/2 etc).

It is possible to copy components from one layer to another, so you could put all components into single layers in another map project. This could be a little tedious at the moment though, so I will look at adding an option "Merge to..<project/layer> which could be used instead of copy to project. This would just copy all components from one layer into another layer, which should give you the results you are after (single layer/shapefile per component type) with very little overhead compared to RM1 (or none, if we automatically select layers of the same type to merge to).

Thanks, "Merge to.." would be fine.

Make merge sense?
I think only as merging from different project parts - e. g. 3 Projects = merging 3 x isobaths, 3 x major contours etc.

But with big project datas this will failed - my own experiences!!!

But, you cannot merge area-shapes with line-shapes!

If you want to merge, use a free GIS application such as QGIS. Merging is a standard geoprocessing operation in all GIS application and really simple and fast.

Maybe. And after merge we lost ability to replace only one part of combined project. Maybe it would be better to add ability to merge on shape export, to avoid usage of one more external utility.

Not necessarily. Merging not change the source files, because a new shape file will be created. GME is not so good suitable for shape processing. If you not mean charts for Garmin, better use QGIS.