MANUAL TOC
2.2. RESTORE
2.2.1 RESTORE POINTS
2.2.2 STEP BACK
2.4 DATA
2.4.1 LABELS
2.4.2 ICONS
2.4.3. LINES
2.4.4. AREAS
2.4.5. POINTS
2.6 TOOLS
2.6.1. RUN AND CLOSE MAPSEND
2.6.2 POLISH TEXT TO ESRI SHAPE FILE CONVERTER
2.8 KNOWN PROBLEMS
2.8.1 DIRECT ROUTE
2.8.2 S&D AUSTRALIA
2.4 Data
All data must be WGS84, Lat/Long (native format of the MapSend, please use third party converters to reproject your data if they are not WGS84 Lat/Long).
Data are set of objects of line (polyline), area (polygons) or point type. Each object may or may not contain LABEL (shown on the map and used for search). MapSends are very sensitive to the first character of the label, it must be ‘0..9’, or capital ‘A-Z’. AddMagMap will automatically shift 1st character of the label to the capital one (‘a-z’ to ‘A-Z’). If the first character does not belong to the allowed range the label will be skipped (for example, if name has Spanish “Ñ” at the very first position this label will be skipped).
AddMagMap does preliminary detection of the data formats (and also detects delimiters); if some errors are found warning screen will be shown with the first 10 lines of the imported file and brief description of the expected format.
Icons are used to show labels at the line objects in form of special signs, for example show shield-type labels at US freeways, oval or circular labels of major roads, squares of different colors to indicate highways in Europe. The behavior of iconed labels is different in dependence on MapSend version and type of the receiver. Please do you own experiments to find out what is good for your MapSend/Receiver. Below are some clues:
PC (Mapsend)
MapSend Topo3d US and Mapsend DR US: If label contain some name and a digit, only a digit will be shown surrounded with the corresponding icon. For example the following labels "2", "US6", "S-5", "test8", "I-8", "name 3" will be shown as a "2","6","5","8","8","3" surrounded by the corresponding icon (in dependence of line type: Type 18 – blue shield; type 16 – white oval; type 17 – white shield etc. The rule is: for iconed labels there will be no name shown, only the digits.
Mapsend Topo US, icon includes both name and digit, but name is truncated to 4-5 characters.
Receiver
In the receiver there is only one type of data for, for example, highways, to draw different icons there is an additional rules for the name. Below are some examples for Explorist500:
Digits only (1-4 digits): will be shown in a red square;
"USX" (where X is some digits): white shield;
"S-X": white circle;
"I-X": blue shield;
Combination of any character and a digit (i.e. "U8", "M5", "I8") will be shown in blue square;
Combination of any characters and at least 1 digit (total=3) (i.e." UU8", "M55", "I88", "M5A") will be shown in green square;If name contains more than 3 characters and they are not all digits, the name will be shown as is (if all of characters are digits, the digits will be shown in red square).
2.4.3. Lines (polylines)Files of the following types are supported:
2.4.3.1 Row ASCII text (*.csv, *.txt)
This format is similar to Excel *.csv format. Different delimiters (SD-space delimiter) can be used to separate fields (e.g. comma, comma+space, TAB, semicolon etc) and decimal delimiters (DD- decimal delimiter) (dot or comma) can be used. AddMagMap automatically recognize them. Label can be blank, but delimiter is needed, see examples below. All coordinates in the first row must contain decimal delimiter because this row is used for detection of the decimal delimiter (example: coordinate is 42, but it must be written as 42.0). The file may have as many lines as needed. All data in the file must have the same SD and DD.
Label; Y0; X0; Y1; X1; Y2; X2;…. (Y is a Latitude; X is a Longitude)
(semicolon is used as SD only for example, others can also be used, see below)Examples:
Example 1:
(SD is ‘, ‘ (comma+space); DD is ‘.’ (dot))
TestLabel1, -0.04000, 26.00000, -0.04000, 26.05000, -0.04000, 26.10000Example 2:
(SD is TAB (0x09); DD is ‘,’ (comma))
TestLabel2 -0,05000 26,00000 -0,05000 26,05000Example 3:
(SD is ‘;‘ (semicolon); DD is ‘.’ (dot))
TestLabel1;-0.04000;26.00000;-0.04000;26.05000;-0.04000;26.10000Example 4:
Line1, -0.04000, 26.00000, -0.04000, 26.05000, -0.04000, 26.10000
Line2, -0.05000, 26.00000, -0.05000, 26.05000, -0.05000, 26.10000
, -0.04000, 26.00000, -0.04000, 26.05000, -0.04000, 26.10000
Line4, -0.05000, 26.00000, -0.05000, 26.05000, -0.05000, 26.10000In Example 4 the label for line 3 is blank, the line will be shown on the map but without any label.
This format does not have any options to tune while importing (‘Nothing to select” will be shown in the third column of AddMagMap grid).
2.4.3.2 Column ASCII text (*.txt)
This format may be useful when small amount of data are imported, editing the data may be more simple than for the raw format, because there are no long lines. The rules for the space delimiter and the decimal delimiter are the same as for Raw ASCII format (2.3.1.1). File begins with “[LINE]”; label starts with “@” (if there is no label just use “@” alone); pairs are Y,X (Latitude, longitude); data for each objects ends with “end”. DD must be presented in the first raw (i.e. 42 must be written as 42.0).
[LINE]
@line1
0.00000, 26.00000
0.00294, 26.00500
0.00476, 26.01000
0.00476, 26.01500
0.00294, 26.02000
0.00000, 26.02500
-0.00294, 26.03000
-0.00476, 26.03500
-0.00476, 26.04000
-0.00294, 26.04500
0.00000, 26.05000
0.00294, 26.05500
0.00476, 26.06000
0.00476, 26.06500
0.00294, 26.07000
0.00000, 26.07500
-0.00294, 26.08000
-0.00476, 26.08500
-0.00476, 26.09000
-0.00294, 26.09500
0.00000, 26.10000
end
@line2
-0.01000, 26.00000
-0.00706, 26.00500
-0.00524, 26.01000
-0.00524, 26.01500
-0.00706, 26.02000
-0.01000, 26.02500
-0.01294, 26.03000
-0.01476, 26.03500
-0.01476, 26.04000
-0.01294, 26.04500
-0.01000, 26.05000
-0.00706, 26.05500
-0.00524, 26.06000
-0.00524, 26.06500
-0.00706, 26.07000
-0.01000, 26.07500
-0.01294, 26.08000
-0.01476, 26.08500
-0.01476, 26.09000
-0.01294, 26.09500
-0.01000, 26.10000
end
This format does not have any options to tune while importing (‘Nothing to select” will be shown in the third column of the AddMagMap grid).
2.4.3.3 Mapsend routes (*.wpt)
This format is extremely useful when MapSend routes are imported (either converted from tracks or drawn with MapSend). There are several ways to convert track to route either with Magellan/Sportrack/Explorist or with the MapSend software. Please refer the user manual for the procedure. MapSend uses the same format of file for waypoints and routes, so when *.wpt file is used for importing lines or areas (see below) the route part is used, when the *.wpt file is used for importing the points, waypoint part is used instead. AddMagMap program extracts all routes from the files and uses the route names as labels (Note: route names are not the same as the file name).
This format does not have any options to tune while importing (‘Nothing to select” will be shown in the third column of the AddMagMap grid).
2.4.3.4 OZI Explorer routes (*.rte)
OZI Explorer is a very popular program for GPS navigation. It has support for many different types of GPS receivers and, more important, it is based on raster (image) maps rather than on vector graphics. OZI Explorer can be used to draw objects on raster images (aerial photos, Google maps,scanned maps etc). OZI Explorer route file format is a text file, labels can be long, but they are always in capital. AddMagMap has an option to change OZI’s labels to lower case format (with the first capital). When OZI Route is imported you will see “Name conversion: No (click to change)” in the third column of the AddMagMap grid. With “Name conversion:No” labels will be shown as is (i.e. in capital characters), to convert labels to lower case with the first capital double click to the corresponding cell of the grid, “Name conversion: Yes (click to change)” will be shown.
2.4.3.5. ESRI shape files (*.shp)
ESRI shape files is one of the most developed geo-data formats. It may have many data fields with different information. AddMagMap program has advanced support of this data format. This data format is also used for importing Garmin maps (with build in Garmin source to *.shp converter). With AddMagMap data can be filtered using 2 fields (logical AND); any data field can be selected as a label source. AddMagMap has also a statistics screen showing how many objects exist with the selected filters.
When the shape file is imported “Name=No” is shown in the third column, it means all objects will be imported without labels and without any filtering. To enter object selection screen double click to the corresponding cell of the grid. The following screen will appear (example is from the line objects of the Garmin maps (St.Petersburg, Russia):
To make import of Garmin data simple there is a Check Box named “Garmin Types”. If checked hex names for Garmin types will be replaced with the Garmin type names (see example at left).
button (bottom-right side of the main dialog). In the example we see that with the (TYPE=”Arterial Road, thin” AND LEVEL=0) filters in the above file there are 10176 objects, 5742 of them have a label, the other 4434 do not have any labels. The file contain 21096 records (any type, any level).
Nothing wrong to set output of the main dialog window or statistics window dialog to several thousand lines, it will slow down the process, but may be useful if some known name should be selected.
Here we considered one of the most complex examples, if simple *.shp files are imported it is necessary just select the field for the labels and leave Filter1 and Filter2 with “Nothing selected”. It will mean that all objects will be imported.
There is another good stuff about shape files, since their header contain rectangle of the area these coordinates can be shown by double click to the first column of the AddMagMap (file name)); these coordinates can be used for definition of the Map rectangle.
To draw polygons (area) formats similar to line formats are used. The polygon is treated as area inside the perimeter, drawn by the line. The first and the last points of the perimeter are considered to be connected, so not necessary to draw closed perimeter.“Islands”
MapSend format allows drawing polygons with “islands”. If some area is defined by several perimeters MapSend fills the areas and the fills are followed by logical XOR. So if some areas are overlapped, the overlapping area will be transparent. This is correct if several areas are defined with several blocks of data for one object; if the areas are in separate objects, they will be shown as just overlapped areas:
a) 2 overlapped areas are defined in the two blocks of data for one object
b) 2 overlapped areas are defined in different objects, one block of data each
Only Column ASCII data format and ESRI shapes files support definition of multiples blocks of data for one object, so only them can be used for “island” drawing (see below for details).
Sorting
MapSend does not care of the order of points which define the polygon. MapSend is just moving to the first, second etc points trying to fill the area in between (using XOR rule). For example is we define a star with the point order indicated the star will be drawn as shown in A). AddMagMap program has an option to sort points automatically around the gravity center. If sort option is used the same star will look like B):
A)
B)
The sort option is applied not for all formats, see below for details)
2.4.4.1 Row ASCII text (*.csv, *.txt) (Areas)
Format is the same to line format. There is an option to sort points as described above. Double click to the third column and the sort dialog appears. Select “As Is” or “Auto”.
2.3.4.2 Column ASCII text (*.txt) (Areas)
Similar to lines, but one area object can consist of several data blocks. These blocks can be used to draw polygons with “islands”; as discussed in the previous section they will be drawn with XOR rule. If at the block end there is a “+” sign the data in this block will be sorted automatically. Here is some example (the area with 2 islands):
[AREA]
@area2
-0.05000, 26.20500
-0.04412, 26.20023
-0.04049, 26.18773
-0.04049, 26.17227
-0.04412, 26.15977
-0.05000, 26.15500
-0.05588, 26.15977
-0.05951, 26.17227
-0.05951, 26.18773
-0.05588, 26.20023
-0.05000, 26.20500
end + //the above block will be sorted automatically
-0.05000, 26.19200
-0.04706, 26.19105
-0.04524, 26.18855
-0.04524, 26.18545
-0.04706, 26.18295
-0.05000, 26.18200
-0.05294, 26.18295
-0.05476, 26.18545
-0.05476, 26.18855
-0.05294, 26.19105
-0.05000, 26.19200
end
-0.05000, 26.17700
-0.04853, 26.17605
-0.04762, 26.17355
-0.04762, 26.17045
-0.04853, 26.16795
-0.05000, 26.16700
-0.05147, 26.16795
-0.05238, 26.17045
-0.05238, 26.17355
-0.05147, 26.17605
-0.05000, 26.17700
endThis format has no options (because everything can be defined in the text file), “Nothing to select” is displayed in the third column.
2.3.4.3 Mapsend routes (*.wpt) (Area)
Similar to lines (MapSand routes) . No import options.
2.4.3.4 OZI Explorer routes (*.rte) (Area)
Similar to lines (OZI routes) , but in case of area there is an option to sort the data. When third column is double clicked the dialog will be shown, in which Name conversion and Sort options can be selected.
2.4.4.5 ESRI shape files (Area)
Full control similar to lines (ESRI shape). Polygons with the “islands” can be drawn, for that several data blocks can be defined for one object, see description of the SHP file format.
Another possibility to create multiblock area is use Polish text format, and then convert this format to ESRI shape file with the built-in to AddMagMap ptxt2shp converter. See chapter 2.6.2.
Formats are the same to line formats (except of missing Column ASCII text format, because it has no advantages compared to row ASCII text format). For each point the label and pair of Y,X coordinates are defined. Points may have no labels. In case of MapSend *.wpt format, waypoint information is used (in contrast to the route info as it was for lines and areas). Point type of data typically is not used in MapSend detail maps, so most probably point layers will not be allowed.
