## How can I download my tracks and waypoints and view them with Viking?

There are multiple solutions, all described in the Users Manual.

In few words:

• extract data from your GPS as a file and load file in Viking;
• or directly load data from Viking (if GPS device is supported).

## How can I export a TrackWaypoint layer as a GPSMapper file so I can make Garmin maps?

(NOTE: You should always save your data as a gpspoint or Viking file also because Viking cannot open gpsmapper files) The comment field for each track/waypoint you want to export to GPSMapper should be in the following format:

Name RGN## 0x####


- or -

Name RGN## 0x##


Where the first '##' is 10, 20, 40, or 80, and the second group of '#'s is the type of region. See the GPSmapperdocs for more details.

### Note on Garmin Maps

Generally it's far easier to use pre-made Garmin Maps, e.g. use the freely available OSM binary images.

## What are the meanings of GeoRef Map parameters?

X (easting) scale mpp: the scale of the map in the X direction. "mpp" stands for meters per pixel, but this is only in units of meters per pixel in UTM mode, otherwise it is Viking's "zoom factor" units, which are related to the size of Google Maps / OpenStreetMap tiles.

Y (northing) scale mpp: the scale of the map in the Y direction.

The map image will be scaled to the current zoom level according to these formulas:

\begin{align} scaled\_width &= width \cdot \frac{xmpp}{zoom\_xmpp} \\ scaled\_height &= height \cdot \frac{ympp}{zoom\_ympp} \\ \end{align}

Corner pixel easting: the UTM "easting" value of the upper-left corner pixel of the map. (try going to View->Go to UTM... to see your current location in UTM). Note that the map is drawn in any UTM zone.

Corner pixel northing: the UTM "northing" value of the upper-left corner pixel of the map.

These parameters can be loaded from a world file. Briefly, the format of this file is:

   x mpp
y rotation (ignored)
x rotation (ignored)
y mpp
corner pixel easting
corner pixel northing


The first and fourth through last are the same as above. As noted, Viking ignores the rotation values.

## Does Viking Support GPX Routes?

Version 1.4+ supports routes.

Here are some old notes for usage with earlier versions:

Up to Viking 1.3 will import routes from GPX files, but automatically convert them into tracks. Similarly routes requested from Google Directions are converted into tracks.

Tracks can be uploaded to a GPS device via the use of a suitable script (such as Bash or Batch script) to convert tracks into routes.

Create a script such as listed here:

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 #!/bin/sh # Quick script to convert the given file and upload it to an attached GPS device # As this modifies the given file, it is ideally designed for temporary files. # # Some basic checks # if [ -z "$1" ]; then echo "Need a file to process" exit 1 fi if [ ! -e "$1" ]; then echo "Specified file >$1< does not exist" exit 1 fi # Delete lines with track segments - there is no equivalent in routes # Then simply replace track and trackpoints with route types sed -i \ -e '/trkseg/d' \ -e 's:::g' \ -e 's:::g' \ -e 's:::g' \ "$1" # Ths is obviously setup for a USB Garmin device gpsbabel -r -i gpx,gpxver=1.1 -f "\$1" -o garmin -F /dev/ttyUSB0 # One may need to change this for your configuration 

Change the gpsbabel line as necessary for your system, device and usage. e.g. maybe add '-w' if you want waypoints transferred as well.

Next in Viking's Preferences -> Export/External, set one of the External GPX Programs to be your script file.

Then any track can be uploaded to the GPS device by right clicking on it in the Layer's Panel -> Export Layer -> Open with External Program: script_file to run the script on a temporary GPX file of the Layer.