How To join custom map with MapSend WorldWide BaseMap

Since Nygma (Varga Csongor) has suggested to use MobileMapper Office for Magellan receivers (Sept. 30, 2003), many successful attempts were done to create custom maps and join several maps in one. Joinmaps program was created by Tim Ford (see File section of the mobilemapper group) to simplify the joining process. But if the whole MapSend application is joining with a custom map, there are some tricks specific to the type of MapSend.

If you are not familiar with MMO, please visit mobilemapper yahoo group to find instruction how to create custom maps from either GIS data or scanned maps. Several perfect documents written by members of the group are available at the File section.

Here you will find step-by-step instruction how to join MapSend WorldWide Basemap (WWBM) with custom map created with MMO. The joined map can be exported from WWBM to GPSR as a secondary (and primary) basemap or detailed map (see below). The procedure described is for MMO1.00, if the later versions (1.10, 2.00) are used, the layers *.lay (in a custom map) must be converted with MMOconverter or convertMMOoutput prior to joining.

1. Create custom map with MMO (say in NewMap folder)
2. Copy this NewMap folder to the MAP folder of WWBM
3. Open NewMap\export.cfg; copy to clipboard layers lines under the [LAYERS] section
4. Append these lines to the [LAYERS] section of the WWBM's MAP\export.cfg and change NUMBER= to the total number of exported layers
5. Change digits and description of the appended entries to adjust zoom properties and line/points style as it described in documentation in the File section of mobilemapper group (thanks to Bruno and Alberto). Also joinmaps.exe program by Tim Ford can be used (File section of the same group). This determines how the layers will look on the Magellan Receiver (GPSR) screen.
6. Copy to clipboard [GROUPS] line: 'BackgroundMap 0', insert this line to the [GROUPS] section of the WWBM's MAP\export.cfg; change NUMBER= to the total number of exported groups. (NewMap\export.cfg is not needed longer and can be deleted (or not, does not matter) the same for basemap.ini; WWBM does not use these files.
7. Define look of custom layers on the PC screen in the NewMap\map.ini file [GROUPS] section (see PCmapView and How to MapSend Topo): here:       0=NewMap_BackgroundMap . . ...............
8. Copy NewMap\map.ini to NewMap\export.ini (yes, that's correct)
9. Add reference to NewMap\export.ini in the MAP\export.ini
10. Add reference to NewMap\map.ini in the MAP\map.ini [ADD_MAPS_REF] section.

Example: I add Appalachian trail as a trail line, and shelters as a points with numbers (corresponding SHP files are available at Appalachian trail conference web site).

part of MAP\export.cfg







1. if in the [GROUPS] section of export.cfg some entry goes with 0 or 1 (exampe: 7=BackgroundMap 0) labels will not be visible in the MapInfo field at the bottom of the GPSR screen; if 1 U 2 follows (example:7=BackgroundMap 1 U 2) the labels are visible in the MapInfo field when pointed with marker

2. wwbasemap can also be exported as a detailed map from MapSend WWbasemap (+custom maps if needed). Change to
Export_Basemap=0 in the Magellan\MapSend WorldWide\mapsend.ini

Export_Basemap=2 <<<<change here to Export_Basemap=0

I did not find what means "Export_Basemap=1" (in this case map is exporting as a basemap, similar to =2). if wwbasemap is exported as a detailed map, GPSR authorization is not an issue: map can be used with any GPSR serial number.

3. Basemap created with WWBM can be used as a primary basemap, I'm using uploadGPSserial to upload primary basemaps. This was found by Jesse (csit95217)(Msg# 189 mobilemapper group) for SporTrack Color, I just confirm with my Merigreen.