MasterHelp

Rob Norris

Viking Manual {.title}

Guilhem Bonnefille {.author}

Rob Norris {.author}

username: Alexxy {.author}

username: Vikingis {.author}

username: Tallguy {.author}

username: EliotB {.author}

Alex Foobarian {.author}

This manual describes version 1.6 of Viking.

Copyright © 2013 Guilhem Bonnefille, Rob Norris

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License (GFDL), Version
1.1 or any later version published by the Free Software Foundation with
no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
You can find a copy of the GFDL at this link or in the file
COPYING-DOCS distributed with this manual.

This manual is part of a collection of GNOME manuals distributed under
the GFDL. If you want to distribute this manual separately from the
collection, you can do so by adding a copy of the license to the manual,
as described in section 6 of the license.

Many of the names used by companies to distinguish their products and
services are claimed as trademarks. Where those names appear in any
GNOME documentation, and the members of the GNOME Documentation Project
are made aware of those trademarks, then the names are in capital
letters or initial capital letters.

DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE
TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER
UNDERSTANDING THAT:

  1. DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY
    KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
    WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS
    FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
    NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND
    PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS
    WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN
    ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR)
    ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION.
    THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
    LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT
    IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND UNDER NO
    CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING
    NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL
    WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR
    MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH
    PARTIES, BE LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL,
    INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
    WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE,
    COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR
    LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND
    MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE
    BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.

Feedback

To report a bug or make a suggestion regarding the Viking application or
this manual, follow the directions in the Feedback section of the GNOME
User Guide
.

Revision History

Revision Viking Manual V1.6

March 2015

Guilhem Bonnefille <guilhem.bonnefille@gmail.com>{.email}

Rob Norris <rw_norris@hotmail.com>{.email}

GNOME Documentation Project

This document was generated on 2015-04-09.

Abstract

Viking is a free/open source program to manage GPS data.


Table of Contents

1. Introduction

2. General Concepts

2.1. Layers

2.2. Layers Panel

2.3. Viewport

2.4. Statusbar

2.5. Toolbar

2.6. Projections

2.7. Map Cache

2.8. Shortcut Keys

2.9. Keyboard Configuration

2.10. Tracks vs Routes

3. File Types and the Main Window

3.1. New

3.2. Open

3.3. Save

3.4. Save As

3.5. Append

3.6. Acquire

3.7. Print

3.8. Generate Image File

3.9. Generate Directory of Images

4. Layers

5. TrackWaypoint Layer

5.1. Layer Operations

5.2. Track and Route Sublayer Options

5.3. Track and Route Properties

5.4. Track and Route Operations

5.5. Waypoint Sublayer Options

5.6. Waypoint Properties

5.7. Waypoint Operations

5.8. Version1.3+: Geotag Images

6. GPS Layer

6.1. Download

6.2. Upload

6.3. Realtime Tracking

6.4. Empty Item

7. DEM (Digital Elevation Model) Layer

8. Maps Layer

8.1. Map Layer Properties

8.2. Layer Operations

9. Aggregate Layer

9.1. Layer Operations

9.2. New Layer

9.3. Sort

9.4. Track List

9.5. Waypoint List

9.6. Visibility Options

9.7. Search by Date

10. GeoRef Layer

10.1. Layer Properties

10.2. Layer Operations

11. Mapnik Rendering Layer

11.1. Layer Properties

11.2. Layer Operations

11.3. Viewport Tools

12. Coordinate Layer

13. Tools

13.1. Pan

13.2. Zoom

13.3. Ruler

13.4. Version1.1+: Select

13.5. TrackWaypoint Layer Tools

13.6. Georef Map Layer Tools

13.7. Map Download

13.8. DEM Download

13.9. Webtools

14. Preferences

14.1. General

14.2. Export/External

14.3. Advanced

14.4. OpenStreetMap Traces

14.5. Mapnik

14.6. Routing

14.7. Startup

14.8. Toolbar

15. Howto's

15.1. Getting Started

15.2. From 1st startup to GPS track (including offline
maps)

15.3. OpenStreetMap project

15.4. Geotagging

15.5. GPS Real Time Location (Not Windows™)

15.6. What to Do if Viking Does Not Seem to
Work

16. Extending Viking

16.1. Map Source

16.2. Go-to search engines

16.3. External tools

16.4. Routing engine

16.5. Remote File Datasources

16.6. More

16.7. Miscellaneous Settings

16.8. Keyboard Shortcuts (Accelerator)
Settings

17. Recommended Programs

18. Command Line

18.1. Overview

18.2. Details

19. Attributions

19.1. coords.c + coords.h

19.2. strtod.c

19.3. kdtree.c + kdtree.h - 0.5.6

19.4. Data: cities15000.txt

1. Introduction {.title style="clear: both"}

Viking aims to be easy to use, yet powerful in accomplishing a wide
variety of tasks. Some of the things you can use Viking for are:

  • Uploading and downloading waypoints, tracks and routes to/from GPS.

  • Preparing tracks, routes and waypoints for trips using maps from
    services such as OpenStreetMap (OSM). The data is only needed to be
    uploaded to your GPS before you leave. The maps together with your
    tracks, routes and waypoints can also be printed and used during the
    trip.

  • After trips, tracks and waypoints from GPS can be downloaded,
    stored, managed and reused in your (or your friends') later trips.

  • Analyzing Off Highway Vehicle (OHV) and hiking trips, understanding
    where you went and how far you were from something.

  • Making waypoints, tracks and routes to follow to easily get
    someplace you've never been before or don't have GPS data for but
    online maps exist for it.

  • Making maps with coordinate lines.

  • Grouping data from multiple trips using a hierarchical data manager.

  • Analyzing speed at different places (to some degree), adding
    waypoints where you forgot to mark one but did slow down or stop.

  • Downloading and storing OpenStreetMap and/or other map types on your
    hard drive and looking at them later.

  • Editing routes or tracks and their trackpoints, joining and
    splitting up tracks and routes.

  • Show the live GPS position on the map (for use on a mobile device -
    e.g. a laptop). Not Windows™ at the moment.

  • Import track, route and waypoint files of various types via GPSBabel

  • View, create and update Geotagged Images (using EXIF data).

![[Note]](note.png)

Note

Viking is under continual improvement: see the potential areas in the
Roadmap /
Wishlist
:

Figure 1. Screenshot: OSM Cycle Map and Many Tracks

Screenshot: OSM Cycle Map and Many
Tracks

\

2. General Concepts {.title style="clear: both"}

2.1. Layers

2.2. Layers Panel

2.3. Viewport

2.4. Statusbar

2.5. Toolbar

2.6. Projections

2.7. Map Cache

2.8. Shortcut Keys

2.9. Keyboard Configuration

2.10. Tracks vs Routes

2.1. Layers {.title}

Layers is concept one may know from powerful graphics editors such as
Photoshop or GIMP. Instead of putting all the data on the same level, it
is stacked (i.e. layered) with different data over one another. This can
be useful for analysis and general handling of various sets of data.

Unfortunately the downside of this complexity is remembering how
differing layers of data can obscure other data.

The Map layers have Alpha
Compositing
, to create
the appearance of partial transparency. By controlling this value one
can see data below it in the layer heirarchy for interesting effects.

2.2. Layers Panel {.title}

The panel on the left is called the layers panel. It determines
which layers and sublayers (such as tracks and waypoints) are shown, and
the order in which they are drawn. Layers on the top of the layers panel
list are drawn last. You can change the order by drag and drop, or by
selecting a layer and using the up and down buttons at the bottom of the
layers panel.

2.3. Viewport {.title}

The main Viking area where the layer data is drawn, is called the
viewport.

2.4. Statusbar {.title}

This provides a readout of various information:

  • The currently selected (mouse pointer) tool

  • The number of items to process in the background - normally this the
    number in the map tile download queue

  • The zoom factor

  • The location of the mouse pointer (and potentially height
    information if DEM data is available)

When creating a track/route, the statusbar also displays some
information about the track/route.

Figure 2. Statusbar

Statusbar

\

This part of the statusbar displays:

  • The total distance of the track/route (including currently edited
    segment).

  • The bearing of the currently edited segment.

  • The distance of the currently edited segment.

For convenience, a zoom selector can be opened from the status bar.
Simply left-click on the zoom factor.

Figure 3. The zoom selector available from status bar

The zoom selector available from status
bar

\

2.5. Toolbar {.title}

The toolbar is an area for buttons that perform common actions.

Some actions are modal, so the appropriate layer needs selected before
these toolbar buttons are enabled. See
Tools more detail.

The display of the toolbar is influenced by the Toolbar
Preferences

Right clicking on the toolbar and selecting Customize allows jumping to
the Customize
Toolbar

directly.

2.6. Projections {.title}

Viking supports differents projections:

  • UTM

  • LatLon (also called EPSG:4326)

  • Mercator (also called Spherical Mercator)

2.7. Map Cache {.title}

Viking stores downloaded map tiles to disk for a couple of reasons:

  • Enables off line usage

  • Reduces loading on the map tile provider

The Viking automatic caching strategy is two fold:

  • If the age of the tile on disk is less than the specified tile age
    (see Preferences), it will
    not attempt to contact the server to get a new version of the
    tile.

  • When the tile age has expired Viking will attempt a refresh
    update, so that it provides the cached tile generation timestamp so
    the server can determine if a new tile image needs to be returned.
    Not all map types support this refresh method.

You can override the caching scheme by using right-click on the Map on
the layers panel and selecting Redownload All Onscreen Maps, or
Ctrl+F5 for the top most map displayed. This will get the latest
version held by the server.

![[Note]](note.png)

Note

This can be useful if you contribute to OpenStreetMap and wish to see
your modifications (of course give time for the server to have processed
your changes - see I have made edits but they don't show up on the
map
)

The layout of the cache on disk itself can be controlled via a per Map
Layer property.

  • Viking - Legacy default in a private cache layout scheme

  • OSM - Newer available default (1.6+)

    This is to increase the compatibility between Viking and similar
    applications that cache tiles on disk so that the tiles can be
    shared.

2.8. Shortcut Keys {.title}

Viking has several shortcut keys or key combinations for commands as
listed in the main window along side the command.

By default some function keys follow standard GUI behaviour:

  • F1 Help (view this manual)

  • F5 or Ctrl+R Refresh the maps on screen

  • F10 Select the Menubar (in built behaviour)

  • F11 Full Screen

  • Ctrl+F5 or Ctrl+Shift+R Redownload the maps on screen

![[Note]](note.png)

Note

Refresh attempts to get new maps only if the local tile cache time
period has expired for any particular map tile. Redownload gets all on
screen maps from the server, ignoring the local tile cache.

Other function keys control turn on/off visibility of various elements:

  • F3 Toggle visibility of the Toolbar

  • F4 Toggle visibility of the Menubar

  • Shift+F5 Toggle visibility of the Scale indicator on the
    viewport

  • F6 Toggle visibility of the Center Crosshairs on the viewport

  • F7 Toggle showing selected items (e.g. tracks or waypoints) in
    the highlight colour in the viewport

  • F9 Toggle visibility of the Layers Panel

  • F12 Toggle visibility of the Statusbar

Standard shortcuts are provided for normal GUI operations: such as
creating new files, opening, saving and exitting. Then there are
shortcuts specific to Viking to switch projection modes, zoom in/out,
create layers,switch the active tool mode and move the map:

  • Ctrl+Up Pan the viewport North

  • Ctrl+Right Pan the viewport East

  • Ctrl+Down Pan the viewport South

  • Ctrl+Left Pan the viewport West

  • Ctrl+Keypad+ Zoom In

  • Ctrl+Keypad- Zoom Out

![[Important]](important.png)

Important

These work irrespective of the Tools
mode selected

For other combinations see the menu entry themselves.

2.9. Keyboard Configuration {.title}

Keyboard configuration is supported by the standard GTK+ way of changing
shortcuts for menu entries.

Hover over the menu option with the mouse pointer and press the keyboard
shortcut you want to bind it to.

To delete a keyboard assignment, press Backspace whilst over the
menu entry.

![[Note]](note.png)

Note

If the keyboard shortcut is already in use you will not receive any
notification that new action replaces the old action. This is probably
why most distributions have this facility disabled by default. Thus you
will need to enable Editable menu accelerators for your system. Check
the Desktop Menu and Toolbar Control or other User Interface preferences
for this setting.

![[Note]](note.png)

Note

For Windows systems this can be done by adding the line
gtk-can-change-accels=1 to %USERPROFILE%\.gtkrc-2.0{.filename}
(create the file if it does not exist).

From Viking 1.6+ the keyboard configuration is automatically loaded and
saved between sessions in the Keyboard Shortcuts
File

2.10. Tracks vs Routes {.title}

In theory a route is path you are planning to follow and a track of
where you have actually been. The GPX specification splits these into
two separate catergories, although tracks contain everything route may
have.

Q. When planning a route what difference does it make if it's a route
or a track?

A. One difference is in how a GPS device navigates following the route
or track. Or you may want to consider interoperability with other
software. Otherwise it is probably best to use tracks as they are a
superset of the route functionality.

For example on Garmin Etrex:

  • Route following: Uses navigation mode with compass and estimated
    time to next point.

    If following on road it can calculate a route on fly.

    I (RN) always use this mode to follow pre planned routes.

  • Track following: Uses a TracBack™ mode

    I (RN) never use this so I can't comment on how it actually compares
    to the route mode.

![[Note]](note.png)

Note

There are often restrictions on the numbers of route points the GPS
Device can handle - may be 250 or as little as 50. This generally not a
problem for single day routes, but needs managing for multi-day events
or for highly detailed routes.

3. File Types and the Main Window {.title style="clear: both"}

3.1. New

3.2. Open

3.3. Save

3.4. Save As

3.5. Append

3.6. Acquire

3.7. Print

3.8. Generate Image File

3.9. Generate Directory of Images

Viking has it's own file type traditionally marked by the .vik file
extension. This is a plain text file saving all information of the
current window including the view location, zoom level, projection type
and then all the layer information (aggregrates, maps, tracks,
waypoints, etc...).

Besides it's own file type, Viking can open (and save to via export
methods) GPX and KML file types.

![[Note]](note.png)

Note

Viking does not handle GPX 1.1 particularly well - it prefers GPX 1.0

By default Viking opens a default blank window centered on the home
location. This behaviour can be changed by the Startup
Preferences
. Each window
contains menus, a toolbar, a viewport, layers panel and a statusbar.
Each section (apart from the viewport) can be hidden using the Shortcut
Keys
or from the View →
Show choices.

One may consider each Viking window to be a separate project - each with
it's project Viking file. However generally one window is enough for
most purposes!

Several operations apply at the window level as follows next. Also see
Tools for the operational modes that
generally work in conjunction with a selected layer.

3.1. New {.title}

Located on the File → New menu and on the toolbar New.

This creates a new window with the default settings.

3.2. Open {.title}

Located on the File → Open menu and on the toolbar Open.

This opens a file chooser dialog to select one (or more) files of the
supported GPS data file types:

  • Viking

  • GPX

  • KML

  • JPG

GPX, KML and JPG files will be loaded into the existing Viking view. A
Viking file will be given a new window if the current window is
already assigned.

![[Tip]](tip.png)

Tip

Viking handles more file types via the
Acquire methods below.

3.3. Save {.title}

Located on the File → Save menu and on the toolbar Save.

If the current opened file is Viking file, this save will simply
update it. If it is a new file or the file loaded was an external type
(i.e. GPX or KML), then this will ask for a new name to save as a
Viking file.

3.4. Save As {.title}

Located on the File → Save As menu only.

This will ask for a new name to save as a Viking file (even it was
already a Viking file).

3.5. Append {.title}

Located on the File → Append menu only.

Selecting a Viking file from this method will join the file contents
to the current window (instead of creating a new one). GPX and KML files
may also be appended, but this is exactly the same as the normal file
open method.

3.6. Acquire {.title}

Available on the File → Acquire menu and from the
TrackWaypoint layer
menu.

If used from the File menu these methods place the results in a new
TrackWaypoint layer.

If used from the
TrackWaypoint layer
menu these methods place the results in that TrackWaypoint layer.

3.6.1. From GPS {.title}

File → Acquire → From GPS Probably the easiest way of getting
information from a GPS Device.

Select the GPS Device communication settings and then hit OK. See the
Getting Started section for more info about the
settings.

![[Note]](note.png)

Note

Some GPS devices (such as the Garmin Nuvi 255™) support a native file
system and write information to a Current.gpx{.filename} file or
similar. You will have to browse the file system on the device and open
it directly.

3.6.2. Import File With GPSBabel {.title}

File → Acquire → Import File With GPSBabel

Other formats can be imported that are supported by GPSBabel.

You need to select the file and the type of the file that is going to
be opened, since there is no automatic detection of the file kind.

3.6.3. OSM Traces {.title}

File → Acquire → OSM Traces

See OpenStreetMap Traces
Download

section for more information.

3.6.4. My OSM Traces {.title}

File → Acquire → My OSM Traces

See OpenStreetMap My Traces
Download

section for more information.

3.6.5. From Geotagged Images {.title}

File → Acquire → From Geotagged Images Enables automatic creation of
waypoints from geotagged images.

This menu opens a dialog to select such image files. If the image files
have geotag information in them, then a
TrackWaypoint layer
with named waypoints positioned at the location of each image with a
thumbnail of that image is created.

3.6.6. From Wikipedia Waypoints {.title}

File → Acquire → From Wikipedia Waypoints

This gets interesting points from Wikipedia for the specified view:
either within the extent of layer bounds or within the current viewport
boundary.

3.6.7. From Routing {.title}

File → Acquire → From Directions

This gets a route from given directions.

3.6.8. From URL {.title}

File → Acquire → From URL

This gets a file from the entered URL. File formats that can be opened
are those supported by GPSBabel.

![[Note]](note.png)

Note

You need to select the type of the file that is going to be returned,
since there is no automatic detection of the file kind.

3.6.9. Import GeoJSON File {.title}

File → Acquire → Import GeoJSON File

This uses the program togpx to load
.geojson files. If the program is not detected on your system, then this
option will not be available. See
here for the installation method.

The current version (1.4.4) of GPSBabel does not support the
GeoJSON file format.

3.7. Print {.title}

Located on the File → Print menu and on the toolbar Print.

Print uses what is displayed on the current map view for printing: i.e.
what ever map, tracks and waypoints that are in view, including the
cross hairs and the scale.

It uses a standard system print dialog using an image the size of the
current viewport in pixel terms. On the Image Settings you can move
the image around the page and scale the image up / or down.

3.8. Generate Image File {.title}

Located on the File → Generate Image File menu only.

Allows generation of larger (pixel) area images than the standard Print
method above. From the generated image you can use the facilities of the
Operating System to print the image or perform other actions.

You should have previously downloaded the tile images for the chosen
zoom level, otherwise the image produced will have missing sections.

![[Warning]](warning.png)

Warning

Using large areas takes some time to process and due to the method used
it may run out of memory to complete the operation. Unfortunately under
Windows™ systems it can not detect this failure and may crash the
program. So the maximum size is dependent on the capabilities of your
system. For instance the largest successful image generated on my (RN)
Debian system is a pixel area of 20,000 x 20,000.

3.9. Generate Directory of Images {.title}

Located on the File → Generate Directory of Images menu only.

![[Note]](note.png)

Note

This is only available in UTM mode.

4. Layers {.title style="clear: both"}

Layers supported by Viking are:

For each layer there are a few standard options:

  • Properties - Layer setup / configuration settings

  • Cut

  • Copy

  • Paste

  • Delete

  • Visibility - This checkbox on the Layers Panel controls whether the
    layer is shown in the viewport or not

The cut/copy/paste options can be accessed in a variety of ways once the
layer has been selected:

  • Standard keys: Ctrl+x|c|v

  • Main menu Edit

  • From the right click menu

  • Buttons at the bottom of the Layers Panel

Default values used for each layer's properties can be altered via the
Edit → Layer Defaults menu options.

See the individual section for detail about each layer.

5. TrackWaypoint Layer {.title style="clear: both"}

5.1. Layer Operations

5.2. Track and Route Sublayer Options

5.3. Track and Route Properties

5.4. Track and Route Operations

5.5. Waypoint Sublayer Options

5.6. Waypoint Properties

5.7. Waypoint Operations

5.8. Version1.3+: Geotag Images

TrackWaypoint layers display GPS data (tracks, routes and waypoints).

One way to create new waypoints is to copy a latitude/longitude
coordinate pair, such as the one shown on most geocaches, and paste it
into an active TrackWaypoint layer. Viking can automatically recognize
several variations of the lat/lon format.

By right-clicking on tracks, routes or waypoints in the Layers
Panel
, you can access
many commands on them. You can easily find a specific track, route or
waypoint by expanding the appropriate containing Tracks, Routes or
Waypoints sublayer in the layers panel to show all the individual items
and then typing the name of the track, route or waypoint.

The containing Tracks, Routes or Waypoints sublayers are only shown when
items of that type exist. To start creating them enter into a create
mode via either the Create toolbar commands or the New menu commands.

The sublayers also offer right click menu options. These are the same as
those available at the TrackWaypoint level, but only those that relate
to the sublayer type.

By default routes are coloured red. Tracks are automatically assigned a
spread of colours.

Most operations available on tracks are available on routes, except for
functionality that relies on having timestamps - since routes by
definition have no timing information. Thus for example, uploading a
route to OpenStreetMap Traces is not available nor is Geotagging on a
route. It is possible to convert between Tracks and Routes, although
converting from a Track to a Route may involve a loss of information
(hence you are required to confirm this operation before it happens).

5.1. Layer Operations {.title}

The layer has a context menu with several operations.

5.1.1. View Layer {.title}

Version1.1+: This will automatically move the viewport and select the
best zoom level to see the whole layer (i.e. all tracks, routes and
waypoints).

5.1.2. View {.title}

5.1.2.1. View All Tracks {.title}

Version1.1+: This will automatically move the viewport and select the
best zoom level to see the all the tracks in the layer (ignoring
positions of any routes or waypoints).

5.1.2.2. View All Routes {.title}

Version1.4+: This will automatically move the viewport and select the
best zoom level to see the all the routes in the layer (ignoring
positions of any tracks or waypoints).

5.1.2.3. View All Waypoints {.title}

Version1.1+: This will automatically move the viewport and select the
best zoom level to see the all the waypoints in the layer (ignoring
positions of any tracks or routes).

5.1.3. Goto Center of Layer {.title}

This will automatically move the viewport to see the whole layer (i.e.
tracks, routes and waypoints). It does not adjust the zoom level.

5.1.4. Goto Waypoint {.title}

This opens a dialog box to enter a name of waypoint to search for. If it
is found the viewport is centred on it.

![[Note]](note.png)

Note

Note this search is not very clever and only finds exact matches. You
are probably better off expanding the waypoint list and directly start
typing, as mentioned above, which finds a match based on each letter
typed.

5.1.5. Export Layer {.title}

The layer (all tracks, routes and waypoints) can be exported to
following file formats:

  1. GPX

  2. GPSPoint

  3. GPSMapper

  4. Google's KML

  5. Any GPSBabel File
    Formats

  6. GeoJSON. Via the program
    togeojson

    This option will not be available if the program is not detected on
    your system. See here for
    the installation method.

Version1.1+: An individual track can be exported to a GPX file via the
track menu.

5.1.6. Finish Track or Route {.title}

Selecting this option ends the creation of that individual track or
route.

![[Note]](note.png)

Note

This is only available when a track or route is being created by the
Create Track or
Create Route tools.

5.1.7. New {.title}

5.1.7.1. New Waypoint {.title}

This opens a dialog box to create a new waypoint. A default name will be
suggested and the default position is the center of the viewport.

5.1.7.2. New Track {.title}

This turns on the Create
Track
tool.

5.1.7.3. New Route {.title}

This turns on the Create
Route
tool.

5.1.8. Geotag Images {.title}

This starts the Geotagging Images dialog against all tracks in the
layer. See
Geotagging
for further detail.

5.1.9. Acquire {.title}

This offers the same choice from
acquire methods as on the File
menu. However when invoked from here, the results will be stored in this
layer (instead of creating a new one).

5.1.10. Upload {.title}

5.1.10.1. Upload to GPS {.title}

This opens a dialog to select the GPS Device and port to which the layer
information will be transferred.

The types of GPS information (tracks, routes or waypoints) to be
transferred can be selected.

Tracks, Routes or Waypoints that are invisible will not be transferred.

5.1.10.2. Upload To OSM {.title}

This opens a dialog to upload all tracks and waypoints to
OpenStreetMap traces. Useful if you are an
OpenStreetMap contributor (you will need an OpenStreetMap account),
these details can be stored in Viking OpenStreetMap Traces
Preferences

Viking allows you to edit a track, e.g. remove duplicate points, perhaps
remove track points leading to your home and then upload it to
OpenStreetMap.

![[Warning]](warning.png)

Warning

The password is transferred unencrypted in every request sent to the
OpenStreetMap server. This is due to the use of OpenStreetMap's basic
authentication method.

Currently Viking does not support the OAuth
mechanism.

5.1.11. Delete {.title}

Offers deletion of various parts of a TrackWaypoint layer:

5.1.11.1. Delete All Tracks {.title}

Deletes all the tracks in this layer.

5.1.11.2. Delete Tracks from Selection {.title}

Opens a dialog with list of all the tracks from this layer to choose the
ones to delete.

5.1.11.3. Delete All Routes {.title}

Deletes all the routes in this layer.

5.1.11.4. Delete Routes from Selection {.title}

Opens a dialog with list of all the routes from this layer to choose the
ones to delete.

5.1.11.5. Delete All Waypoints {.title}

Deletes all the waypoints in this layer.

5.1.11.6. Delete Waypoints from Selection {.title}

Opens a dialog with list of all the waypoints from this layer to choose
the ones to delete.

5.1.12. Filter {.title}

5.1.12.1. Simplify All Tracks {.title}

This opens dialog to request the number of points each track will be
simplified using GPSBabel. The result is put into a new layer. The
simplification method removes points considered to be in a 'near
straight line', thus reducing the number of points and attempting to
keep the most important turning points.

5.1.12.2. Compress Tracks {.title}

Enables compression of tracks and routes via GPSBabel's Crosstrack
simplify method. It opens a dialog to request the Error factor value
which is the maximum allowable error that may be introduced by removing
a single point. It is expressed a distance in units as specified by the
Preferences distance option. Thus
a higher value will remove more points. The result is put into a new
layer.

5.1.12.3. Remove Duplicate Waypoints {.title}

Remove Duplicate Waypoints - fairly self explainatory, with the results
created in a new layer.

![[Note]](note.png)

Note

However it only considers a precise position (waypoints only 1 metre
away from each other are considered different) and also doesn't consider
if the waypoints have different comments, symbols or images.

5.1.13. Filter With Trackname {.title}

This runs GPSBabel on the layer using information from a previously
selected track (select via the track menu "Use With Filter" option) with
the following command types:

  • Waypoints Inside This

  • Waypoints Outside This

The result is generated in a new Track/Waypoint layer.

5.1.14. Geotag Images {.title}

This starts the Geotagging Images dialog using the specific track. See
Geotagging
for further detail.

5.1.15. List Tracks or Routes {.title}

Opens a new dialog with the list. As described in the Aggregrate layer
Track List

5.1.16. List Waypoints {.title}

Opens a new dialog with the list. As described in the Aggregrate layer
Waypoint List

5.2. Track and Route Sublayer Options {.title}

Repeats options available at the TrackWaypoint level, but only those for
tracks and routes:

Also gives other options for handling multiple items:

  • Sort. Gives the ability to sort the items in the treeview
    alphabetically or by date.

  • Visibility. Offers options to quickly control the visibility of all
    items within the sublayer, as per Visibility
    Options

5.3. Track and Route Properties {.title}

This shows several tabs for properties and useful statistics about a
track or a route, including elevation-distance and speed-time graphs (if
data is available). Moving the mouse pointer over the graph displays
values related to that point along the track. You can click on these
graphs to jump to the point in the track. You can reverse it, delete
duplicates, split at marked position or split a track from its component
segments (discontinuous breaks in a track) into separate tracks.

5.3.1. Track and Route Properties Tab {.title}

Figure 4. Properties Tab: Example

Properties Tab: Example

\

5.3.2. Track and Route Statistics Tab {.title}

Figure 5. Statistics Tab: Example

Statistics Tab: Example

\

5.3.3. Track Elevation Graph {.title}

Figure 6. Elevation Distance Tab: Example

Elevation Distance Tab: Example

\

The following colors are used in the elevation-distance graph:

Main colour - this is dependent on your Desktop theme - often blue by default
: elevation data in graph

Yellow
: no elevation data

Green
: elevation data from DEM

Red
: speed

5.4. Track and Route Operations {.title}

5.4.1. Finish Track {.title}

Selecting this option ends the creation of the individual track.

![[Note]](note.png)

Note

This is only available when a track is being created by the Create
Track
tool.

5.4.2. Goto {.title}

This centers the viewport on the selected position on the track:

  • Startpoint

  • "Center" - the notional center from the bounds of the track

  • Endpoint

  • Version1.1+: Highest Altitude

  • Version1.1+: Lowest Altitude

  • Version1.1+: Maximum Speed (Not Available on Routes)

5.4.3. View {.title}

Version1.1+: This centers the viewport on the track and selects the best
zoom level to see it.

5.4.4. Combine {.title}

5.4.4.1. Merge By Time {.title}

This operation repeatedly tries to merge the right-clicked track with
tracks in the same TrackWaypoint layer. The tracks which are merged are
those which have at least one trackpoint less than some threshold time
away. This way, if you somehow end up with lots of small segments (say,
caused by turning the GPS on and off) you can merge them easily into one
track.

![[Note]](note.png)

Note

This is not available on routes as they have no timestamps.

5.4.4.2. Merge With Other Tracks {.title}

This opens a dialog listing the other tracks in the same TrackWaypoint
layer, from which one can select the other tracks to merge with.

5.4.4.3. Merge Segments {.title}

Combines track segments. Effectively removing track segment markers to
leave one segment for the whole track.

5.4.4.4. Append Track or Route {.title}

Enable joining of a single track to the end of the current track. This
opens a dialog listing the other tracks in the same TrackWaypoint layer
from which one can make the selection.

5.4.5. Split {.title}

5.4.5.1. Split By Time {.title}

This operation will split a single track into segments wherever the time
interval between successive trackpoints is larger than some threshold.
This is useful when processing raw NMEA GPS data, especially taken over
a long time.

![[Note]](note.png)

Note

This is not available on routes as they have no timestamps.

5.4.5.2. Split By Number of Points {.title}

Version1.2+: This operation will split a single track into segments by
the number of points specified. This can be useful with devices which
may have limits on the number of points it supports.

5.4.5.3. Split Segments {.title}

Splits track segments into new tracks.

![[Note]](note.png)

Note

This is not available on routes as they do not have route segments.

5.4.5.4. Split at Trackpoint {.title}

Splits the track at the currently selected trackpoint.

The current track will finish at this trackpoint. A new track will start
from a copy of this trackpoint.

![[Note]](note.png)

Note

This is only enabled when a trackpoint is selected.

5.4.6. Insert Points {.title}

![[Note]](note.png)

Note

These options are only enabled when a trackpoint is selected.

5.4.6.1. Insert Point Before Selected Point {.title}

Inserts a track point halfway between the previous track point and the
current track point. All track point properties are interpolated between
the two points.

5.4.6.2. Insert Point After Selected Point {.title}

Inserts a track point halfway between the current track point and the
next track point. All track point properties are interpolated between
the two points.

5.4.7. Delete Points {.title}

5.4.7.1. Delete Selected Point {.title}

Deletes the currently selected track point.

![[Note]](note.png)

Note

This is only enabled when a trackpoint is selected.

5.4.7.2. Delete Points With the Same Position {.title}

Deletes subsequent points that have the same position (but have
different timestamps).

5.4.7.3. Delete Points With the Same Time {.title}

Deletes subsequent points that have the same time stamp (but may have
different positions).

![[Note]](note.png)

Note

This is not available on routes as they have no timestamps.

5.4.8. Transform {.title}

These options alter the data of trackpoints of a track but not add or
remove trackpoints. And don't seem to fit any other category :)

5.4.8.1. Apply DEM data {.title}

If any DEM data is loaded, this will apply the DEM data to give the
track elevation data. Two ways of applying DEM data are offered:

  1. Keep. Retains the existing elevation data of trackpoints and only
    those missing an elevation value are set.

  2. Overwrite. Elevation data are set on all trackpoints even if they
    already elevation values.

5.4.8.2. Smooth Missing Elevation data {.title}

In various locations across the world, there are missing DEM values (AKA
DEM Holes) from the SRTM data. This is particularly noticeable in
mountainous areas. Two ways of applying elevation data to trackpoints
that do not have elevation values are offered:

  1. Interpolated. Missing elevation data is interpolated between the
    previous and next known values.

  2. Flat. Elevation data is filled in from the last previously known
    value.

5.4.8.3. Convert to Track or Route {.title}

If this is a Route then it will convert it to a Track.

If this is Track then convert it to a Route.

![[Note]](note.png)

Note

Converting from a Track to a Route may involve a loss of information, in
particular timestamp values (hence you are required to confirm this
operation before it happens).

5.4.8.4. Anonymize Times {.title}

Timestamp information of a track can be shifted to be all offset from
1901-01-01.

Thus the timestamps themselves will no longer reveal exactly when a
track was taken. However the relative difference between the timestamps
is kept thus one is still able to calculate some properties such as
speeds along the track.

![[Note]](note.png)

Note

This is not available for routes, as they have no timestamps.

5.4.8.5. Interpolate Times {.title}

Trackpoint timestamps between the first and last points are calculated
such that track is travelled at equal speed. This is mostly useful when
tracks don't have timestamps and you wish to recreate your trip (e.g.
you've forgotten to turn on your GPS or the batteries have run out) Thus
edit the first and last trackpoints to set the approximate times of your
trip and then use this to give approximate times along the track. When
used on tracks with timestamps this will overwrite the existing
timestamps.

![[Note]](note.png)

Note

This is not available for routes, as they have no timestamps.

5.4.9. Export Track as GPX {.title}

Version1.1+: This allows exporting the track as a GPX file by opening a
file save dialog.

5.4.10. Extend Track End {.title}

Changes the current tool to add trackpoints to the end of the track.

5.4.11. Extend Using Route Finder {.title}

Enables the Route Finder tool. Thus on a subsequent left click in the
viewport, a route is calculated from the end of track to that point
using the default route service and applied to the track.

5.4.12. Upload {.title}

5.4.12.1. Upload to GPS {.title}

Same as the layer Upload to
GPS
command, but only
applies to the track.

5.4.12.2. Upload to OSM {.title}

Same as the layer Upload to
OSM
command, but only
applies to the track.

5.4.13. Use With Filter {.title}

This selects the track to be used in the Filter With
Trackname

feature.

![[Note]](note.png)

Note

This is not available on routes.

5.4.14. Edit Trackpoint {.title}

This opens the Trackpoint edit dialog. See Edit Trackpoint
Dialog
.

![[Note]](note.png)

Note

This is only enabled when a trackpoint is selected.

5.4.15. Refine Route... {.title}

This function allows to request a Routing Engine in order to refine a
given route. By "refining" we mean computing all real intermediates
points between some given major points. This could be useful to compute
a trip giving only the wished important steps.

![[Note]](note.png)

Note

This is only available on routes.

5.4.16. View Google Directions {.title}

This option is only available on a track created using the Route Finder
tool.

Launch a web browser to see the Google directions page which yielded the
route.

![[Note]](note.png)

Note

The record of the Google route is stored in the track's comment, so if
the comment is changed (or the route was created by something other than
the Route Finder tool) this will not work correctly.

5.5. Waypoint Sublayer Options {.title}

Repeats options available at the TrackWaypoint level, but only those for
waypoints:

Also gives other options for handling multiple items:

  • Sort. Gives the ability to sort the items in the treeview
    alphabetically or by date.

  • Visibility. Offers options to quickly control the visibility of all
    items within the sublayer, as per Visibility
    Options

5.6. Waypoint Properties {.title}

This shows a dialog with detailed information for the waypoint. Many
properties of the waypoint can changed here, such as the comment, the
symbol used in drawing or the image (normally a photograph taken at this
position) assiocated with it. When a waypoint has an image, a thumbnail
of it is drawn in the viewport for the waypoint (in preference to the
symbol).

If the waypoint has an associated image, then the Geotag information may
be updated, either with updating the file's modification timestamp or
not. This can be useful when the waypoint has been moved.

5.7. Waypoint Operations {.title}

5.7.1. Goto {.title}

This centers the viewport on the selected waypoint.

5.7.2. Geotag Images... {.title}

This opens the Geotag
Dialog
to
allow Geotagging multiple images to the position of this waypoint. In
this circumstance creation of waypoint options are disabled and only the
options related to writing the EXIF information are available.

5.7.3. Transform {.title}

Offers a subset of the track
Transform utilities.
Currently only setting the altitude from DEM data methods are available.

5.7.4. Visit Webpage {.title}

If the waypoint's comment (or description) starts with http:{.literal}
then this option is available and allows launching a web browser to go
to the webpage.

5.7.5. Visit Geocache Webpage {.title}

If the waypoint's name is in Geocache form (GCXXXXX) then this option is
available and allows launching a web browser to go to the Geocache page.

5.7.6. New Waypoint {.title}

Same as the layer New
Waypoint
.

5.8. Version1.3+: Geotag Images {.title}

This dialog allows geotagging images (normally taken with a digital
camera) against a specific waypoint or via interpolation against a
specific track or all tracks in the TrackWaypoint layer - depending on
how it is invoked.

When geotagging against tracks, images need to have an EXIF
DATE_TIME_ORIGINAL (nearly always set by a camera). This timestamp is
then used to find the location when the image(s) was taken by searching
through the track(s) to find the nearest time - interpolating between
points if necessary to set the location.

![[Note]](note.png)

Note

Generally it is good policy to synchronize your camera's clock with your
GPS clock before taking photographs. However the times can be adjusted
afterwards (if necessary) to take into consideration clock differences.

Various options allow control of how the geotagging process is
performed:

  • Images - Add the images used for geotagging

  • Create Waypoints

  • Overwrite Existing Waypoints

  • Write EXIF

  • Overwrite Existing GPS Information

  • Interpolate Between Track Segments

  • Image Time Offset - The number of seconds to ADD to the photos time
    to make it match the GPS data. Calculate this with (GPS - Photo).
    Can be negative or positive. Useful to adjust times when a camera's
    timestamp was incorrect.

  • Image Timezone - The timezone that the used when the images were
    created. For example, if a camera is set to AWST or +8:00 hours.
    Enter +8:00 here so that the correct adjustment to the images' time
    can be made. GPS data is always in UTC.

6. GPS Layer {.title style="clear: both"}

6.1. Download

6.2. Upload

6.3. Realtime Tracking

6.4. Empty Item

The GPS layer is responsible for uploading and downloading GPS data from
a GPS device. It also is responsible for realtime GPS tracking. Expand
the GPS layer in the layers panel to see the two
TrackWaypoint
layers it uses for uploading and downloading. To upload, download, or
use realtime tracking, right-click the GPS layer and click the
appropiate menu item.

6.1. Download {.title}

To download data from the GPS, right-click the GPS layer and click
Download from GPS.

6.2. Upload {.title}

To upload data to the GPS, first populate the GPS Upload child layer of
the GPS layer (either by creating waypoints/tracks/routes in it, or
copying and pasting or dragging waypoints/tracks/routes from another
layer). Then right-click the GPS layer and click Upload to GPS.

6.3. Realtime Tracking {.title}

You must set up gpsd correctly or use a GPSD server and put the correct
information in the GPS layer properties dialog. Then right-click the
layer and select Start Realtime Tracking.

6.4. Empty Item {.title}

There are several options to quickly delete a subsection of data:

  • Empty Realtime

  • Empty Upload

  • Empty Download

  • Empty All

7. DEM (Digital Elevation Model) Layer {.title style="clear: both"}

This layer provides elevation data from the Shuttle Radar Topography
Mission (SRTM)

Elevation data can be useful in planning trips, as you many wish to
avoid/minimise the hills encountered. [OSM Cyclemap is also useful this]
way too

To download the data use the DEM Download tool (shown on the toolbar),
and then click on a area of the viewport. Once files have been
downloaded they can then be loaded from disk via the DEM properties in
future application runs.

The current data server is: NASA STRM
2.1
.

ATM Viking does not auto download DEM data. If you want to get lots of
data blocks, you may wish to use some other program get such as curl or
wget to download them for an area.

![[Note]](note.png)

Note

Using many DEMs is CPU/memory intensive. Depending on your computer's
capability, Viking will be less responsive when about 50+ DEM blocks are
loaded. It is probably unwise to attempt using 200+ blocks, so trying to
use DEMs covering large countries/continents (USA, Australia etc...) is
unlikely to work. In these conditions under Linux, Viking may be
automatically stopped by the
"OOM Killer"

8. Maps Layer {.title style="clear: both"}

8.1. Map Layer Properties

8.2. Layer Operations

This layer provides a single map resource, you may have multiple map
layers but only top one (if enabled) will be visible (subject to the
Alpha compositing property).

Some maps are continually improving over time (e.g. OpenStreetMap) thus
Viking employs a caching mechanism to avoid redownloading data (see Map
Cache
). However a forced refresh
for the current view can be made via the Reload All Onscreen Maps option
or Ctrl+F5.

Online Map Tile Providers.  You will need an open internet
connection when you are downloading maps these following map types, but
once downloaded they are available from the hard disk cache. When map
are avaliable from the disk cache it is much faster and can be used
offline. Inbuilt maps include various OpenStreetMap
(OSM)
ones and more:

  • Bing Bird's Eye (Aerial) Maps (Viking Version1.2+)

  • OpenStreetMap (Mapquest) - This is the default (Viking Version1.3+)

  • OpenStreetMap (Mapnik)

  • OpenStreetMap (Cycle)

  • OpenStreetMap (Transport) (Viking Version1.3+)

  • OpenStreetMap (Humanitarian) (Viking Version1.5+)

  • NASA BlueMarble

Viking can be configured to handle additional online map resources. See
Extending Viking for
further detail.

Offline Map Tilesets.  Some map types supported are for on disk tile
formats:

Of course you need to have acquired or generated these tilesets
yourself.

8.1. Map Layer Properties {.title}

Configurable properties:

  • Map Type. The kind of map this layer displays.

    ![[Note]](note.png)

    Note

    Map types are dependent on the current
    Projection mode.

  • Maps Directory. Not applicable for MBTiles Map type since it is a
    single file.

  • Cache Layout. Viking or OSM. See Map
    Cache
    . Only applies to maps
    from online tile providers.

  • Map File. Ony applicable for MBTiles Map type since it is a single
    file.

  • Alpha. Control the Alpha value for transparency effect using a value
    between 0 and 255 with the default being 255 for a fully solid
    image.

    Zero is fully transparent. A value of around 160 can be useful for
    blending views of multiple map layers (when applied to the upper
    most map layer).

  • Autodownload Maps. This can be useful to turn off when you are not
    online to avoid pointless download requests or may be keep a map in
    a 'historical' state. e.g. perhaps in case a current map rendering
    is broken.

  • Autodownload Only Gets Missing Maps. Using this option avoids
    attempting to update already acquired tiles. This can be useful if
    you want to restrict the network usage, without having to resort to
    manual control. Only applies when Autodownload Maps is on.

  • Zoom Level. Determines the method of displaying map tiles for the
    current zoom level. Viking Zoom Level uses the best matching
    level, otherwise setting a fixed value will always use map tiles of
    the specified value regardless of the actual zoom level.

8.2. Layer Operations {.title}

8.2.1. Download Missing Onscreen Maps {.title}

This requests map tiles for areas of the viewport that do not currently
have one.

8.2.2. Download New Onscreen Maps {.title}

This requests map tiles only if the maps are older than the Tile Age
preference.

8.2.3. Reload All Onscreen Maps {.title}

Force a refresh of all visible map tiles.

8.2.4. Download Maps in Zoom Levels {.title}

This opens a dialog to enable requesting the download of maps for the
region in the viewport over a specified number of zoom levels. The
download method type can be specified to help limit the number of
requests.

![[Warning]](warning.png)

Warning

There are some inbuilt limits to prevent downloading large amounts of
map tiles.

Please respect the usage policy of the tile set provider. Such as OSM
Tile Usage
Policy
.

Figure 7. Maps Download Dialog: Example

Maps Download Dialog:
Example

\

9. Aggregate Layer {.title style="clear: both"}

9.1. Layer Operations

9.2. New Layer

9.3. Sort

9.4. Track List

9.5. Waypoint List

9.6. Visibility Options

9.7. Search by Date

This layer is a container layer to hold other layers. There is always an
initial and controlling Top Layer that can not be removed or renamed.

This layer type is useful for grouping other layers, especially
TrackWaypoint
layers, in whatever categories are relevant to you: such as by activity,
location or date. Here are some suggestions:

  • Hiking

  • Mountain Biking

  • Road Cycling

  • Car Trips

  • Sailing

  • Holidays

  • UK Points of Interest

  • USA Points of Interest

  • etc...

Thus one can have a list of all your tracks, but groups can be shown or
not using the relevant layers visibility checkbox.

9.1. Layer Operations {.title}

The following are available on Aggregate Layers:

9.2. New Layer {.title}

Add a new layer of the selected type.

9.3. Sort {.title}

The list within the treeview can be sorted.

Alphabetical and Date sorts are available.

![[Note]](note.png)

Note

Generally it is not useful to sort the Top most layer. Sort is mainly
intended for Aggregate groups of TrackWaypoint layers.

9.4. Track List {.title}

Selecting this opens a dialog listing all the tracks in a table along
side statistics such as track length and maximum speed. Each column
header is clickable and will reorder the list according to that
particular column. You can also rearrange the columns via dragging the
column header to the new location.

This table may be invoked from a variety of different layer levels and
will then list only the relevant tracks (and/or routes).

  • Aggregate Layer: Lists Tracks and Routes and the TrackWaypoint Layer
    they are in

  • TrackWaypoint Layer: Lists Tracks and Routes

  • TrackWaypoint Track sublayer: Lists Tracks only

  • TrackWaypoint Route sublayer: Lists Routes only

Figure 8. Track List Dialog: Example

This is showing all tracks and routes (although there are no actual
routes here!) in multiple TrackWaypoint layers, that has been sorted
by height. Note that routes will not have timestamps or speeds, but
may have elevations and should have some distance!

Track List Dialog: Example

\

Hovering the mouse over an entry will show a tooltip of the comment or
description if it is available.

Each entry in the track list can be selected and on mouse right click
offers these options:

  • View. Move the viewport to the area of the item and highlight it.

  • Statistics. Opens the Properties dialog on the Track and Route
    Statistics

    tab. Note this will close the track list dialog.

  • Copy Data. Copy the data fields as text.

If multiple entries are selected the only right click option is Copy
Data
. This copies the individual data fields as plain text separated by
tab characters, ideal for pasting into other applications in particular
spreadsheet programs. Note that the order of the fields copied is the
default column ordering (irrespective to how they may have been
rearranged).

9.5. Waypoint List {.title}

Selecting this opens a dialog listing all the waypoints to give a
overview of the waypoint information. Each column header is clickable
and will reorder the list according to that particular column. You can
also rearrange the columns via dragging the column header to the new
location.

This table may be invoked from a variety of different layer levels and
will then list only the relevant waypoints.

  • Aggregate Layer: Lists Waypoints and the TrackWaypoint Layer they
    are in

  • TrackWaypoint Layer: : Lists Waypoints

  • TrackWaypoint Waypoint sublayer: Lists Waypoints

Figure 9. Waypoint List Dialog: Example

This was invoked on a TrackWaypoint layer and shows all waypoints from
that single layer. It has been sorted by the symbols.

Waypoint List Dialog: Example

\

Hovering the mouse over an entry will show a tooltip of the description
if it is available.

Each entry in the list can be selected and on mouse right click offers
these options:

  • View. Move the viewport to the area of the item and highlight it.

  • Properties. This will open the properties dialog. Note this will
    close the waypoint list dialog.

  • Show Picture. If enabled, this will open the associated image in an
    external Image Viewer program.

  • Copy Data. Copy the data fields as text.

If multiple entries are selected the only right click option is Copy
Data
. This copies the individual data fields as plain text separated by
tab characters, ideal for pasting into other applications in particular
spreadsheet programs. Note that the order of the fields copied is the
default column ordering (irrespective to how they may have been
rearranged).

9.6. Visibility Options {.title}

This offers a quick way to set all the visibilities of each item within
the containing layer, rather than having to change each one
individually.

  • Show All. Ensures all items are set to be visible.

  • Hide All. Ensures all items are set to be invisible. This is useful
    for then turning on single items afterwards so the display is not
    cluttered.

  • Toggle. Inverts the visibility status of each item.

9.7. Search by Date {.title}

This opens calendar dialog to select a date to search by within this
Aggregate layer. The first item that is found on that date will be
selected. Tracks are searched first in preference over waypoints.

10. GeoRef Layer {.title style="clear: both"}

10.1. Layer Properties

10.2. Layer Operations

This layer allows one to use any image as a map. You will need to tell
it how to align the map to a position in the world and the scale of map.

When a new image is selected the values from a World
File
will automatically be
tried to be found. (subject to the setting in Export/External
Preferences
)

![[Note]](note.png)

Note

Viking does not currently support skew values and since World Files do
not contain what coordinate system the coordinate values are in - Viking
assumes they are in UTM.

If you do not know the scale of the map but know the coordinates of both
upper left and lower right coordinates, you can enter these coordinates
(Lat/Lon only) and then use the Calculate MPP values from coordinates
button.

The map once loaded can be repositioned via Section 13.6, “Georef Map
Layer Tools”
,
which may be easier than trying to edit the raw property values.

10.1. Layer Properties {.title}

Configurable properties:

  • The map image file.

  • X + Y Scales in metres per pixel.

  • Coordinates of the upper left corner of the map (either UTM or
    Lat/Lon value).

  • Alpha. Control the Alpha value for transparency effects using a
    value between 0 and 255 with the default being 255 for a fully solid
    image, whereas 0 is transparent.

10.2. Layer Operations {.title}

10.2.1. Zoom to Fit Map {.title}

Automatically set a zoom level to see the entire map coverage.

10.2.2. Goto Map Center {.title}

Center the viewport on this map.

10.2.3. Export to World File {.title}

Opens a file save dialog to save the scale and position information as a
World File.

11. Mapnik Rendering Layer {.title style="clear: both"}

11.1. Layer Properties

11.2. Layer Operations

11.3. Viewport Tools

The Mapnik Rendering Layer uses the Mapnik Library
to generate map images according to the Mapnik configuration.

When using the this layer it is useful to review the Mapnik
Preferences
to ensure the
settings are correct for your system.

Mapnik configurations can be created via the CartoCSS Mapnik stylesheet
pre-processor. Viking will automatically invoke the carto program when
a carto project file is specified. Currently Viking can not tell when an
included file of the project has changed, so there is an option to
manually run the carto command.

Viking will only (re)render tiles when it believes it is necessary -
such as when there is no tile in the file cache, when there is a new
Mapnik configuration style or the tile is over a certain age. To force
Viking to (re)render all tiles - create the file
~/.viking/planet-import-complete{.filename} and/or update its
timestamp. (e.g. using the touch command).

Creating a Carto project or an initial Mapnik configuration file and
maintaining the datasource is beyond the scope of this documentation.
There are various existing Carto projects such as OSM
Carto
or OSM
Bright
. These use OSM data and
contain guides on how to setup the datasource. Further detail about
using OSM data can be found on the
Switch2OSM website.

If you use a simple Mapnik configuration then the tile rendering time
can be negligible and you can avoid having a tile cache. However for
most systems using a stylesheet of similar complexity to the OSM Carto
styling, rendering a tile (including reading/acquiring the data) can
take some time and thus several seconds to generate a display screen's
worth of tiles. Hence Viking runs these tasks in the background and uses
the tile cache to save this output.

Generated tiles are stored in the PNG format in the standard OSM Tile
name
layout.

![[Note]](note.png)

Note

Currently due to code build and dependency complexities, Mapnik
Rendering is not available in the Windows™ version of Viking

11.1. Layer Properties {.title}

Configurable properties:

Carto project file. When specified, this is used to generate the
mapnik configuration file.

Mapnik configuration file. Specify the Mapnik configuration file or
leave it blank when using a Carto project file.

Alpha. Control the Alpha value for transparency effects using a
value between 0 and 255 with the default being 255 for a fully solid
image, whereas 0 is transparent.

Use File Cache. The default is to use a file cache.

Tile cache directory. The top level directory of where the generated
tiles are stored.

11.2. Layer Operations {.title}

These extra options are available when right clicking on the Mapnik
Rendering Layer in the Layers Panel.

Refresh. Reload the Mapnik configuration.

Run Carto Command. Force running the carto command and reload the
generated Mapnik configuration.

About. Show some information about the Mapnik version in use.

11.3. Viewport Tools {.title}

When a Mapnik Rendering Layer is selected in the Layers Panel, the
Mapnik Features tool can be selected from the toolbar. This enables
location dependent actions to be invoked by right clicking on the
viewport and selecting an action from the drop down menu.

  • Rerender Tile.

  • Tile Info

12. Coordinate Layer {.title style="clear: both"}

This layer is allows drawing of grid lines on the viewport.

13. Tools {.title style="clear: both"}

13.1. Pan

13.2. Zoom

13.3. Ruler

13.4. Version1.1+: Select

13.5. TrackWaypoint Layer Tools

13.6. Georef Map Layer Tools

13.7. Map Download

13.8. DEM Download

13.9. Webtools

Viking's mouse actions on the viewport are controlled by which tool is
active. Only one tool can be active at a time. The default mode is pan.

You can use the scroll wheel, the middle-click, the middle-click+drag to
zoom, center map at position and pan respectively no matter what tool
you are using.

Scroll: zoom in and out keeping the mouse over same location

Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down)

Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right)

Ctrl-shift-scroll: zoom in and out, without changing the center
(also Ctrl+, Ctrl- [*not* KeyPad +/-])

Middle-click: make the clicked point on the map the center

Middle-click and drag: pan

13.1. Pan {.title}

This is the default mode of operation for Viking.

This mode is entered by clicking on the toolbar icon:

Pan moves the viewpoint. A single click centers the viewport at that
point, whereas click and drag dynamically moves the view around. This is
the default tool.

This mode can also be entered by the keyboard shortcut Ctrl+Shift+P

Double clicking the left mouse button will zoom the map in. Shift +
double clicking the left mouse button will zoom the map out. Double
clicking the right mouse button will also zoom the map out.

13.2. Zoom {.title}

This mode is entered by clicking on the toolbar icon:

Zooms in and out on the clicked part of the map or by the selected area.

This mode can also be entered by the keyboard shortcut Ctrl+Shift+Z

Ctrl + left or right click: Zoom in/out and center the map on the
clicked location

Shift (and hold) + left mouse button: Draws a bounding box area on
which to zoom in. The zoom action is performed when the left mouse
button is released.

Shift + left click button: Jump Zoom In by up to factor of 3
standard zooms.

Shift + right click button: Jump Zoom Out by up to factor of 3
standard zooms.

13.3. Ruler {.title}

This mode is entered by clicking on the toolbar icon:

The ruler is used to measure the bearing and distance between two
points: Click on first point and then move the mouse point around - the
values will be continually updated. A second click will freeze the
ruler at that point.

This mode can also be entered by the keyboard shortcut Ctrl+Shift+U

13.4. Version1.1+: Select {.title}

This mode is entered by clicking on the toolbar icon:

The select tool allows one to choose any waypoint or track by clicking
on it (or reasonably near) in the viewpoint.

ATM to select a track one must actually click on a trackpoint, which is
also selected.

This mode can also be entered by the keyboard shortcut Ctrl+Shift+S

13.5. TrackWaypoint Layer Tools {.title}

You must have a
TrackWaypoint Layer
selected to use these tools.

13.5.1. Create Waypoint {.title}

Enable this tool by clicking on the toolbar icon:

Left click will open the new waypoint dialog using the specified
position.

13.5.2. Create Track {.title}

Enable this tool by clicking on the toolbar icon:

Left click to create a new trackpoint. If it's the initial trackpoint
you will be asked to enter a name for the track. If Ctrl is held at
the same time, it will jump the new trackpoint position to a nearby
existing trackpoint. Right click or Backspace: undo one point.

Double click or Escape: to finish track creation. Finishing the
track is also available via the right click
TrackWaypoint and
track menus.

One must finish the current track to be able to create another track.

13.5.3. Create Route {.title}

Enable this tool by clicking on the toolbar icon:

This operates in exactly the same way as the Create
Track
above.

One must finish the current route to be able to create another route.

One can switch between the Create
Route
and Route
Finder

tools while editing routes.

13.5.4. Create Route Using the Route Finder {.title}

Enable this tool by clicking on the toolbar icon:

Requires an internet connection. Left click to create a new trackpoint.
If it's the initial trackpoint you will be asked to enter a name for the
route, otherwise the default routing engine will be queried to find a
route to the new trackpoint. Right click or Backspace: remove the
last added route.

Escape: to finish route creation. Finishing the track is also
available via the right click
TrackWaypoint and
track menus.

One must finish the current route to be able to create another route.

One can switch between the Create
Route
and Route
Finder

tools while editing routes.

13.5.5. Edit Waypoint {.title}

Enable this tool by clicking on the toolbar icon:

Left Click/drag: select/move a waypoint. If Ctrl is held at the same
time, it will jump the waypoint position to a nearby existing
trackpoint. If Shift is held at the same time, it will jump the
waypoint position to a nearby existing waypoint.

Right-click on waypoint: opens a menu with waypoint actions (the same
menu accessed by right-clicking the waypoint in the layers panel)

13.5.6. Edit Trackpoint {.title}

Enable this tool by clicking on the toolbar icon:

Left click near a trackpoint (in screen pixel terms) to bring up the
Track Point Edit dialog on that trackpoint. Whilst the edit dialog is
already open, left click again and drag enables moving of the
trackpoint. If Ctrl is held at the same time, it will jump the new
trackpoint position to a nearby existing trackpoint.

13.5.6.1. Edit Trackpoint Dialog {.title}

Editing options in the Trackpoint Edit dialog include:

  • Edit the trackpoint name

  • Changing raw lat/long position and altitude

  • Forward (go to the next trackpoint)

  • Back (go to the previous trackpoint)

  • Delete

  • Insert. Inserts a point halfway to next trackpoint

  • Split. Split at
    Trackpoint

Several fields are read only for reference purposes, values are shown if
the trackpoint has such information:

  • Time.

  • Speed and course.

  • 'Between' values: Speed, Time Difference and Distance Difference.
    When moving between trackpoints (via the Back and Forward buttons)
    these values are calculated.

  • GPS precision factors.

Figure 10. Trackpoint Edit Dialog: Example

Trackpoint Edit Dialog: Example

\ One must have been going downhill here to get a reasonable speed by
bicycle!

13.5.7. Show Picture {.title}

Enable this tool by clicking on the toolbar icon:

Opens an image viewer with the picture associated with the waypoint. By
default this uses the default system image viewer. For Linux you can
override this with the setting in the Export/External
Preferences

13.6. Georef Map Layer Tools {.title}

You must have a GeoRef Map Layer
selected to use these tools.

13.6.1. Georef zoom {.title}

Enable this tool by clicking on the toolbar icon:

Changes the zoom level of the georeferenced map and changes the Viking
zoom level accordingly. Useful if you are trying to match GPS data to a
georeferenced map.

13.6.2. Georef move {.title}

Enable this tool by clicking on the toolbar icon:

Drag to move the georeferenced map.

13.7. Map Download {.title}

You must have a Maps Layer selected
to use this.

Enable this tool by clicking on the toolbar icon:

Click to download a single tile. Drag to download tiles in the dragged
rectangle area.

Right-click to redownload tiles via the selected method. Right-click and
drag to redownload tiles in the dragged rectangle area by the selected
method. The possible methods to redownload one or more tiles are:

  • Bad - Only if the tile is corrupt in some way or missing, then this
    will download a new copy

  • New - Refresh the tile according to the local map cache and if
    server has a newer version

  • All - Redownload the tile

Map Tile Information.  By right clicking on viewport and selecting
Show Tile Information you can see the tile properties of this location
for the current map layer and current zoom level. This includes the
remote source URL for the tile and the cached version on the local
filesystem with timestamp details.

Figure 11. Map Tile Info Dialog: Example

Map Tile Info Dialog: Example

\ This is using MapQuest at Viking zoom level 128 over the Isle of Wight,
UK.

13.8. DEM Download {.title}

You must have a
DEM Layer
selected to use this.

Enable this tool by clicking on the toolbar icon:

Click to download and import a DEM file.

DEM File Information.  By right clicking on viewport and selecting
Show DEM File Infomation you can see the file properties of the DEM file
for this location. This includes the remote source URL for the file and
the cached version on the local filesystem with timestamp details.

Figure 12. DEM File Info Dialog: Example

DEM File Info Dialog: Example

\ This is for block 51N, 003W - covering Bristol in the UK.

13.9. Webtools {.title}

Many services are available only via a web browser (Google Maps,
OpenStreetMap Potlach editor, etc.).

Jumping from Viking to such service can become annoying.

Viking allows you to open such service directly at the position
currently viewed in Viking.

This feature is called Webtools. It is also known as External Tools.

14. Preferences {.title style="clear: both"}

14.1. General

14.2. Export/External

14.3. Advanced

14.4. OpenStreetMap Traces

14.5. Mapnik

14.6. Routing

14.7. Startup

14.8. Toolbar

14.1. General {.title}

14.1.1. Localisation {.title}

You can select units displayed by Viking to best fit your usage.

Figure 13. Properties dialog: units part

Properties dialog: units part

\

Concerning degrees, you can select the way to display them:

DDD
: decimal degree

DMM
: partial sexagesimal display: degrees, minutes and decimal part of
minutes

DMS
: sexagesimal display: degrees, minutes and seconds

Figure 14. Properties dialog: degree display options

Properties dialog: degree display
options

\

14.1.2. Waypoint Icon Size {.title}

An option exists to control the icon (symbol) size used for waypoints

14.1.3. Home Default Location: Latitude and Longitude {.title}

You can set the Home location directly by inputting the latitude and
longitude in decimal degrees.

14.1.4. Time Display {.title}

This controls the reference timezone that times are shown in.

Locale is the current user's system preference. This was how all times
were shown up to version 1.5.

World will attempt to determine the timezone at an object's position.

UTC enforces this standard timezone.

14.1.5. Tile's age {.title}

This age is used to decided wether or not a new request to tile server
must be done.

Changing this value, you will increase or decrese the network load.

14.1.6. Default map layer directory {.title}

This property sets the default directory of the tiles cache. This value
is used when you create a new map layer.

You are still able to change this value in each map layer properties.

14.1.7. Map Cache Memory Size {.title}

This controls the amount of maps that are stored in memory, rather than
having to reread from disk. Generally if you have a system with lots of
memory it's recommended to increase this value.

14.2. Export/External {.title}

14.2.1. KML Export Units {.title}

Allows setting the units used when saved as the KML file type, such as
Metric or Statue units

14.2.2. GPX Track Order {.title}

Other software may display tracks in a particular order (often the order
saved into the file). This allows you to control the order they are
saved when exporting to a GPX file.

14.2.3. GPX Waypoint Symbols {.title}

Some GPS devices require waypoint symbols to be in a particular case.

E.g. On a Garmin Oregon 450 they must be in Title Case to be
recognized.

14.2.4. Image Viewer (Not Windows) {.title}

Allows setting the program used to view images associated with
Waypoints.

By default this is set to xdg-open which should open the system's
default image viewer, however this can be overridden with this setting.

Note: for Windows systems, viewing images associated with Waypoints
always uses the system's default image viewer.

14.2.5. External GPX programs {.title}

Allows setting the programs invoked via the
TrackWaypoint Layer
menu Export Layer → Open With 'program'

Two options are given so that it can be configured for various uses such
as:

  • An OSM editor (default)

  • Some other user defined program

14.2.6. GPSBabel {.title}

This allows setting the specific location of GPSBabel.

Viking will need to be restarted for this setting to take effect.

14.2.7. Auto Read World Files {.title}

If this is on, when a new image is selected for the GeoRef layer then
the associated world file will be read to find the scale and positional
properties.

The associated file is based on filename patterns; e.g. if the image is
filename.jpg{.filename} - then the world file may be
filename.jpgw{.filename} or filename.jgw{.filename}

14.3. Advanced {.title}

14.3.1. Save File Reference Mode {.title}

Files referenced within project files can be saved with either absolute
or relative paths. Using relative paths can be useful when copying the
project file and the associated files between different systems.

14.3.2. Ask for Name before Track Creation {.title}

A setting to control whether an automatic name is used when creating a
new track or route, or whether you are asked to enter a name.

14.3.3. Show Tooltip during Track Creation {.title}

A setting to control whether the tooltip with the cumulative track or
route distance is shown when creating tracks and routes.

14.3.4. The number of recent files {.title}

The number of recent files shown in the File → Open Recent File menu. A
value of -1 means all files. The new value applies to New Windows only
(or on application restart).

14.4. OpenStreetMap Traces {.title}

14.4.1. OSM Username + Password {.title}

Store your OSM details here, so that you don't need to enter it in every
time in the Upload To
OSM
procedure.

![[Warning]](warning.png)

Warning

Your OSM password will be stored in plain text.

14.5. Mapnik {.title}

![[Note]](note.png)

Note

If any changes to these settings are made, you will need to restart
Viking to make them be applied.

14.5.1. Plugins Directory {.title}

The location of Mapnik plugins. An attempt is made to automatically
determine the initial value, however if this is wrong or Mapnik is
upgraded then the directory can be set here.

14.5.2. Fonts Directory {.title}

The location of fonts for use with Mapnik. Normally it is best to simply
use the System's font directory.

14.5.3. Recurse Fonts Directory {.title}

Load fonts in any sub-directories of the main font directory.

14.5.4. Rerender Timeout {.title}

The time in hours before any tile is rerendered.

This is useful in case the underlying source data for the tiles changes
(e.g. OSM data is continually evovling). Viking normally has no way of
knowing when the data has changed, so this simple timeout method is
provided to maintain consistency of the tile images.

14.5.5. CartoCSS {.title}

This allows setting the specific location of the carto executable.

14.5.6. Threads {.title}

The number of threads to use for Mapnik rendering tasks. By default the
value is set to the 1 in case of any multi-threading rendering code
chain crashes. Otherwise trying setting the value to the number of the
CPUs of the system minus one (so as not to overload the system), in
order to minimise the overall rendering times.

14.6. Routing {.title}

14.6.1. Routing engine {.title}

You can select the routing engine used by default, ie by features that
do not propose a live selection, like Route
Finder
.

14.7. Startup {.title}

Naturally since these preferences effect the startup, the values will
not be used until Viking is restarted.

14.7.1. Restore Window Setup {.title}

When this is enabled, the main window size and layout (such as whether
the statusbar or layers panel are shown) is restored to the values from
last use.

14.7.2. Default Map Layer {.title}

When this is enabled, a map layer is automatically added whenever Viking
is opened and a Viking file is not to be loaded.

The map layer used is defined by the map layer's default values.

14.7.3. Startup Method {.title}

Enables selection of how the startup position should be determined.

  • Home Location (default) - Position as set by the Set the Default
    Location

  • Last Location - Uses the last position viewed on the viewport

  • Specified File - Load the file as specified below

  • Auto Location - Use the web service
    hostip.info to attempt to determine your
    location via IP lookup

14.7.4. Startup File {.title}

Loads this specified file when the Startup method is set to Specified
File

14.7.5. Check For New Version {.title}

Periodically (no more than once every 14 days), check to see if there is
a new version of Viking available.

14.8. Toolbar {.title}

14.8.1. Append to Menu {.title}

Allows setting the toolbar on the same vertical space as the menu, thus
increasing vertical space for the map.

14.8.2. Icon Size {.title}

Allows configuration of the icon size, including overiding the system's
default preference to the setting desired just for Viking

14.8.3. Icon Style {.title}

Allows configuration of the icon style, including overiding the system's
default preference to the setting desired just for Viking

14.8.4. Customize {.title}

Opens the Customize Toolbar dialog.

From this dialog the items in the toolbar can be added, removed and
reordered. Reordering of items is performed by drag and drop.

Figure 15. Customize Toolbar dialog

Customize Toolbar dialog

\

15. Howto's {.title style="clear: both"}

15.1. Getting Started

15.2. From 1st startup to GPS track (including offline
maps)

15.3. OpenStreetMap project

15.4. Geotagging

15.5. GPS Real Time Location (Not Windows™)

15.6. What to Do if Viking Does Not Seem to
Work

15.1. Getting Started {.title}

Viking from version 1.5 has several features to ease the start up
process. On the very first run, you will be asked if you want to enable
these features which make use of an Internet connection. If you select
no or you have upgraded from an earlier version you can choose to enable
any of the startup options via the Startup
Preferences
.

Some other general use cases for using Viking, are as follows:

15.1.1. Go to an area of interest {.title}

Viking's default location is a Manhatten, New York, USA, so you may need
to pick another place that interests you - such as where you live.

Procedure 1. Method A

  • Use the online location address/place search.

    Use the Go to Location toolbar button or from the menus View → Go to
    Location. You can change the search location provider if desired.
    Enter the name of place you wish to go to (you may need to specify
    the country to refine the search). Also you can enter a post code or
    a ZIP code instead.

    ![[Note]](note.png)

    Note

    You will need an internet connection for this search to work

Procedure 2. Method B

  • If you know the coordinates of where you want to view:

    Use View and select from either Go to Lat/Lon or Go to UTM and then
    enter in the specific coordinates.

Procedure 3. Method C

  • Use the GPS Layer or File → Acquire → From GPS to load data directly
    from your GPS into Viking.

    You can specify the types of data to acquire: Tracks, Routes and/or
    Waypoints.

    ![[Note]](note.png)

    Note

    You must have write permission to the port used. For Unix™ like OS:

    • /dev/ttyS0 is the first serial port

    • /dev/ttyUSB0 is the first USB port

    • usb: is any USB port

    Depending on your distribution only one of the USB port types may
    work

    For Windows™:

    • com1: is the first serial port

    • usb: is any USB port

    ![[Note]](note.png)

    Note

    The GPS devices supported are those supported by GPSBabel.

    Garmin and Magellan GPS devices supported by all versions, later
    versions of GPSBabel support more devices such as DeLorme and
    Navilink.

Procedure 4. Method D

  • Get data from files in GPX or KML format, which can be opened
    directly. Use File → Open

    Other formats can be imported that are supported by GPSBabel. File →
    Acquire → Import File With GPSBabel...

    ![[Note]](note.png)

    Note

    The viewport will be automatically moved and resized to view the
    contents of the file.

15.1.2. Add a Map Layer {.title}

Use Layers → New Map Layer, and choose a suitable cache directory where
you would like to store your tracks and click OK. Zoom to a comfortable
level (I suggest 4 mpp) by clicking the left and right mouse buttons on
the gray area where your tracks are. Now from the menu choose the Map
Download
Tool. Click where
you would like to download a map. Regardless of what tool you are using,
the middle mouse button always pans.

![[Note]](note.png)

Note

You need an open internet connection when you are downloading maps.

If you can no longer see your tracks or waypoints and only the map, it
is because the layer named Map is ABOVE your TrackWaypoint layer
that your GPS data is in. This means that it will be drawn last and on
top of the other Layers. Look at
the Layers Panel to
the left which shows this order. Select the Map layer from the list and
click the down arrow button beneath the list until the Map layer is
below the TrackWaypoint layer. Your tracks will now be drawn over the
map.

15.1.3. Set Your Home Location {.title}

You can save the current center position of the viewport as the default
location AKA the Home Location by Edit → Set the Default Location.

Then at any time you can return to this place by clicking on the Home
icon on the toolbar.

You can also set the default location via specifing the exact latitude
and longitude in the Preferences.

15.2. From 1st startup to GPS track (including offline maps) {.title}

The first you'll see is an empty map, because Viking in its default
configuration will download maps only on demand. Before fetching
unneeded data, one can position to a location of interest, e.g.
Stuttgart: View → Go to Location, enter Stuttgart.

15.2.1. Fetching the maps {.title}

Map

  1. Layers → New Map Layer

  2. in the layer properties dialogue choose e.g. OpenStreetMap (Mapnik).

  3. For the moment, we keep the default Maps Directory (the directory in
    which the maps will be stored and can be used for offline usage).

  4. Check Autodownload maps and keep the zoom level as Use Viking Zoom
    Level.

    ![[Note]](note.png)

    Note

    however, that these settings will play an important role in the
    pre-fetch for offline usage discussed later

You'll see a map of Stuttgart. Using the mouse wheel, you can zoom in
and out. The maps for the choosen resolution will be downloaded
automatically.

DEM Layer (Height Map)

  1. Zoom out to 512.

  2. Layers → New DEM Layer

  3. Keep the download source as is (SRTM Global 90m), hit OK.

In the layer listing on the left, the
DEM layer
should reside above the map layer. If this is not the case, highlight
the DEM layer an shift it one up (using the arrow up button).

  1. highlight the DEM layer in the layer listing on the left

  2. in the toolbar, check DEM layer download/import (the last symbol)

  3. a left-click in the map window should then fetch the DEM data

This might take some time.

Sometimes, a tile does not show up correctly (you might see only a black
frame in the map window) because it got corrupted during transfer. In
order to correct this, you can delete the corresponding datafile in the
cache.

 right-click the DEM layer properties

The DEM Files listing allows you to delete the specific tiles
(alternatively do this from the command line).

You can also alter the Min. and Max. elevation in this dialogue.

15.2.2. GPS Track with Height Profile {.title}

  1. Uncheck the
    DEM layer
    (the map is shown again)

  2. Layers → New TrackWaypoint Layer

    Ensure the new track layer is above the map layer.

  3. Expand the
    TrackWaypoint
    layer, select Tracks

  4. In the tools menu choose Create Track

  5. Leftclick in the map window, enter a name

  6. Click several times to generate a track (a right-click removes the
    last point).

    Height data is set automatically since DEM data is available

  7. Expand tracks in the layer menu, your track should show up, select
    it

  8. Right click your track, select Properties

  9. Click the tab Elevation-distance - enjoy the plot

In order to save this setting for later usage

  1. click OK in the Track Properties dialog

  2. File → Save As, choose a name (you can open this view later via
    file → Open).

15.2.3. Usecase: offline data for holiday {.title}

Suppose you want to have the Maps and
DEM data
offline for your holiday in Italy near Bologna.

  1. Start a new Viking session.

  2. View → Go to Location, enter Bologna

  3. Layers → New Map Layer

  4. Choose e.g. OpenStreetMap (mapnik).

  5. adapt the maps directory e.g. to
    /home/user/.viking-map-holiday/{.filename}. This allows you to
    delete the map stuff after holiday without purging the rest of your
    maps.

  6. check autodownload map

  7. keep viking zoom level

  8. zoom out to 1024

  9. add a DEM
    layer (as discussed above)

  10. download the DEM data

In the Viking version discussed here, the DEM data automatically are
stored in /home/user/.viking-maps/{.filename}. You can move the
corresponding tiles into .viking-map-holiday/{.filename} if you like.

Download map data for all zoom levels

  1. uncheck the DEM layer for the map to show up

  2. navigate the map to be centered at Bologna

  3. choose the zoom such, that all regions of interest are displayed in
    the map window (e.g. 1024)

  4. follow this sequence until you have all tiles for all zoom levels
    you need

    1. right-click the map layer properties

    2. set the zoomlevel explicitely one below the last (in the first
      cycle 512), hit OK

    3. right click the map layer Download Missing Onscreen Maps

    4. wait until all tiles for that resolution have been downloaded

This may take some time and some hard disk capacity.

Do not forget to save your configuration (as discussed above).

15.3. OpenStreetMap project {.title}

OpenStreetMap (OSM) is a collaborative
project to create a free editable map of the world. One of sources of
data for this project is GPS tracks. Viking supports this project via
the GPS Traces methods, both uploading and downloading such data.

Also see http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces for
further detail.

15.3.1. Uploading data to OpenStreetMap {.title}

It is possible to upload data directly from Viking to OpenStreetMap.

Upload a layer.  One solution is to upload whole a
TrackWaypoint
layer. To do this, simply select the layer and right click on it. Then,
select Upload to OSM.

Upload a single track. Another solution is to upload an individual
track. Simply select the track and right click on it. Then select Upload
to OSM.

Fill in the form.  In both cases, Viking will retain some
information. The email field is the email you used to subscribed into
OpenStreetMap. The password field is the password you used with this
account. The filename is the name you want your upload has on the
server. This information is displayed by the osm server. The description
is some descriptive information. The tags field is a white separated
list of tags.

15.3.2. Downloading Traces from OpenStreetMap {.title}

It is possible to download GPS traces directly from OpenStreetMap into
Viking. This feature can be really useful for checking existing data
before uploading new ones.

Download all visible tracks. One solution is to select File →
Acquire → OSM traces.... Each request can get up to 5,000 points. The
dialog box allows setting which group of 5,000 points to get. These
groups are known as Page Numbers which start at 0. Increasing the page
number parameter allows one to request the subsequent sets of point
groups.

15.3.3. Downloading Your Own Traces from OpenStreetMap {.title}

It is possible to download any of your personal GPS traces previously
uploaded to OpenStreetMap into Viking.

You will need to provide your OSM username and password to get the list
of your OSM Traces. From this list you can select which traces to
retrieve. This list can be sorted on each column so that it easier to
find an individual trace or select a group of traces by similar
properties.

15.4. Geotagging {.title}

This assumes you already have a Maps
layer enabled for ease of use (if not see above to get one).

15.4.1. Manual Positioning {.title}

This is useful for instances when you already know exactly where the
image was taken (no need for tracklog). Or maybe you want to adjust an
automatically generated waypoint for the position of the subject of the
image rather than the location that the photograph is taken from. ATM
this process only works on an individual image, so it will be tedious
for handling lots of images.

First create a
TrackWaypoint layer
or use an existing one; and select it in the Layers
Panel
. NB Make sure
this layer is above the map layer in the Layers Panel list. Create a new
waypoint (or move an existing one) to exact location desired:

  • Select the Create
    Waypoint
    tool,
    then left click on the map at the location desired, choosing an
    image to associate with it in the new waypoint dialog

  • Select the Select
    tool, then left click on waypoint to be moved. Left click again and
    drag the waypoint to the location desired

Then using the Select tool left click on waypoint to select it, then
right click to access the Waypoint properties menu, then choose Update
Geotag on Image → Update

The Update Geotag on Image options are only available when a waypoint
has an image associated with it.

15.4.2. Automatic Positioning Against a Tracklog {.title}

First you will need a tracklog with timestamps in it. Either load one
from a previously saved file or freshly acquired from a GPS device - see
Getting Started. It
helps if this is the track that was recorded at the time you took some
photographs!

Select the track either from the layers panel on the left or via the
viewport using the
Select tool. Then right
click on it and chose the Geotag Images... leading you to the
Geotagging
Dialog.

Load some images that where taken around the time the track log was
recorded. Confirm the other options in the dialog - normally the
defaults should be alright and select OK. If things are succesful, new
waypoints with thumbnail images of the photographs will appear. You
should probably check they are really in the right place as often the
timestamp of the camera may not be aligned to the GPS correctly leading
to inferring incorrect locations.

Option: Overwrite Waypoints.  This is particularly useful when one
finds an attempt at geotagging gives wrong locations, often due to time
offset issues. Simply try again with a new time offset (often 1 hour
adjustments due to Daylight Savings or Summer Time times) and the old
waypoints will be updated (instead of creating new ones).

If you have multiple tracks in a TrackWaypoint layer, then invoking the
Geotag Images... action on the layer will search all the tracks to find
location matches.

15.5. GPS Real Time Location (Not Windows™) {.title}

Viking relies on gpsd to provide the
current location from a real time feed from a GPS device. Unfortunately
gpsd is not available on Windows™, so currently this functionality is
disabled in Windows™ builds of Viking

This assumes you already have a Maps
layer enabled for ease of use (if not see above to get one).

Turn on the GPS Device, ensure it has figured out it's location and plug
it in to your computer.

15.5.1. Set Up GPS Layer {.title}

You will need a GPS layer. One can be
added via Layers → Add GPS Layer.

Adjust the Realtime Tracking Mode settings to interface with
gpsd as necessary. Normally the defaults
should suffice.

Current Linux distributions should run gpsd automatically when a GPS
Device is plugged in. Otherwise you may have to run gpsd manually.

Then right-click the layer and select Start Realtime Tracking. Hopefully
the viewport should jump to the GPS location.

Troubleshooting checklist:

  • Confirm gpsd is running.

  • Confirm on the GPS device it has a location.

  • Confirm the Realtime Tracking Mode settings.

15.6. What to Do if Viking Does Not Seem to Work {.title}

In order to get some information about what Viking is doing, start it in
verbose debug mode via the command line:

viking -dV

For instance you can check the correct URLs Viking is using in
requesting remote data for DEMs or map tiles in the verbose debug
output. E.g. Something like this for DEMs:

** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
* About to connect() to dds.cr.usgs.gov port 80 (#0)
* Trying 152.61.128.95... * connected
* Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
 GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
Host: dds.cr.usgs.gov
Accept: */*
 HTTP/1.1 200 OK
 Date: Sun, 26 Jul 2009 18:13:38 GMT
 Server: Apache
 Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
 ETag: eac3f8-1828f5-46f3caa76070a
 Accept-Ranges: bytes
 Content-Length: 1583349
 Content-Type: application/zip

* Connection #0 to host dds.cr.usgs.gov left intact
* Closing connection #0
** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip

Or for OSM Mapnik tile server:

* About to connect() to tile.openstreetmap.org port 80 (#0)
*   Trying 193.63.75.28... * connected
* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
 GET /13/4065/2748.png HTTP/1.1
User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
Host: tile.openstreetmap.org
Accept: */*

* HTTP 1.0, assume close after body
 HTTP/1.0 200 OK
 Date: Thu, 14 Oct 2010 22:18:42 GMT
 Server: Apache/2.2.8 (Ubuntu)
 ETag: "b66ff9d46474bab68262a3483428a232"
** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
 Content-Length: 17194
 Cache-Control: max-age=94805
 Expires: Sat, 16 Oct 2010 00:38:47 GMT
 Content-Type: image/png
 Age: 5153
 X-Cache: HIT from konqi.openstreetmap.org
 X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
 Connection: close

* Closing connection #0
* About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
*   Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
* About to connect() to tile.openstreetmap.org port 80 (#0)
*   Trying 193.63.75.28... * connected
* Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
 GET /tiles/cycle/13/4065/2747.png HTTP/1.1
User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
Host: a.andy.sandbox.cloudmade.com
Accept: */*

* connected
* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
 GET /13/4065/2749.png HTTP/1.1
User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
Host: tile.openstreetmap.org
Accept: */*

* HTTP 1.0, assume close after body
 HTTP/1.0 200 OK
 Date: Thu, 14 Oct 2010 23:44:35 GMT
 Server: Apache/2.2.8 (Ubuntu)
 ETag: "8e520ad47ce9c1b63430554886eb5fab"
** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
 Content-Length: 18094
 Cache-Control: max-age=87742
 Expires: Sat, 16 Oct 2010 00:06:57 GMT
 Content-Type: image/png
 X-Cache: MISS from konqi.openstreetmap.org
 X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
 Connection: close

16. Extending Viking {.title style="clear: both"}

16.1. Map Source

16.2. Go-to search engines

16.3. External tools

16.4. Routing engine

16.5. Remote File Datasources

16.6. More

16.7. Miscellaneous Settings

16.8. Keyboard Shortcuts (Accelerator)
Settings

Currently, Viking has some extention points based on configuration
files. The file format is heavily inspired by the GtkBuilder file
format: you specify the class of the GObject to build and set its
properties. Technically, it is a XML file containing a "objects" root
element. Inside this element, you set a collection of "object".

Here is an example:

<objects>
  <object class="ClassName">
    <property name="property_name1">Property value</property>
    <property name="property_name2">Property value</property>
  </object>
  ...
<objects>

You can find more examples in the documentation part of the
distribution.

16.1. Map Source {.title}

It is possible to add new map's sources. The file is
~/.viking/maps.xml{.filename} for UNIX™ like systems,
C:\Documents and Settings\username{.filename}\.viking\maps.xml on
Windows XP™ or C:\Users\username{.filename}\.viking\maps.xml on
Windows 7™ onwards.

An example of the file is in the distribution
doc/examples/maps.xml{.filename}. Further examples and values are
online in the Maps
Wiki

The VikSlippyMapSource{.classname} allows to declare any map's source
working like OpenStreetMap. It supports the following properties:

id
: this is an integer and should be unique as it used to identify the
map source

name
: a string (should be unique) that is used for the OSM style cache
directory name when the Map Cache directory is the default
(~/.viking-maps{.filename})

label
: the text displayed in the map's source selection dialog

hostname
: the server's hostname (eg. "tile.openstreetmap.org")

url
: the parametrized address of the tile, in the spirit of C printf
format, with 3 "%d" fields for Z, X and Y (in that order) (eg.
"/%d/%d/%d.png")

zoom-min (optional)
: The minimum zoom value supported by the tile server. The Default is
0 if not specified.

zoom-max (optional)
: The maximum zoom value supported by the tile server. The Default is
18 if not specified.

See [Zoom Levels](http://wiki.openstreetmap.org/wiki/Zoom_levels)

lat-min (optional)
: The minimum latitude value in degrees supported by the tile server.
The Default is -90 degrees if not specified.

lat-max (optional)
: The maximum latitude value in degrees supported by the tile server.
The Default is 90 degrees if not specified.

lon-min (optional)
: The minimum longitude value in degrees supported by the tile server.
The Default is -180 degrees if not specified.

lon-max (optional)
: The maximum longitude value in degrees supported by the tile server.
The Default is 180 degrees if not specified.

file-extension (optional)
: The file extension of the files on disk. The default is .png

If the tile source URL ends in something other than .png, then this
parameter will need to match it.

This can also be useful in reading a tileset from other software
which may name tiles in an alternative form, e.g. for Mobile Atlas
creator it names them *.png.tile*

![[Note]](note.png)

Note

The file types actually usable are those supported by GDK Pixbuf
Library, which includes at least PNG and JPEG.

![[Note]](note.png)

Note

Remember to include the beginning *'.'* when specifying this
parameter.

use-direct-file-access (optional)
: Only use files on disk. The default is FALSE

This can also be useful for tilesets already on disk as it will
avoid attempting to download any tiles.

Thus with this type the *hostname* and *url* parameters are not
necessary and are ignored.

switch-xy (optional)
: Swap the X,Y values around in the URL parametrized ordering.

The default is false.

check-file-server-time (optional)
: Sends the timestamp of the tile to the server, so the server can
decide whether it should send a new tile or not.

The default is false.

use-etag (optional)
: Use and compare the ETag
value in determining whether to download a newer tile. The default
is false.

The ETag value is stored in a separate file in the same directory as
the tile to enable checking the value across multiple runs of the
program.

The VikTmsMapSource{.classname} allows to declare any TMS service. It
supports the following properties (as per VikSlippyMapSource above):

id
:

label
:

hostname
:

url
:

check-file-server-time (optional)
:

zoom-min (optional)
:

zoom-max (optional)
:

lat-min (optional)
:

lat-max (optional)
:

lon-min (optional)
:

lon-max (optional)
:

The VikWmscMapSource{.classname} allows to declare any WMS or WMS-C
service. It supports the following properties (as per VikSlippyMapSource
above):

id
:

label
:

hostname
:

url
:

check-file-server-time (optional)
:

zoom-min (optional)
:

zoom-max (optional)
:

lat-min (optional)
:

lat-max (optional)
:

lon-min (optional)
:

lon-max (optional)
:

16.2. Go-to search engines {.title}

It is possible to add new new search engines for the "Go-To" feature.
The file is ~/.viking/goto_tools.xml{.filename}.

An example of the file in the distribution
doc/examples/goto_tools.xml{.filename}.

Currently, there is a single object class available:
VikGotoXmlTool{.classname}. Such feature allows to declare any search
engine using a XML format as result.

The related properties are:

label
: the text displayed in the Go-To dialog

url-format
: the parametrized address of the query, in the spirit of C
printf{.function} format, with a single "%s" field (replaced by
the query string)

lat-path
: XML path of the latitude (eg. /root/parent/elem{.literal})

lat-attr (optional)
: name of the attribute (of previous element) containing the latitude

lon-path
: XML path of the longitude (eg. /root/parent/elem{.literal})

lon-attr (optional)
: name of the attribute (of previous element) containing the longiude

As a facility (or readability) it is possible to set both path and
attribute name in a single property, like an XPath expression. To do so,
simply set both info in lat-path (or lon-path) in the following format:
/root/parent/elem@attribute{.literal}.

16.3. External tools {.title}

It is possible to add new external tools. The file is
~/.viking/external_tools.xml{.filename}.

An example of the file in the distribution
doc/examples/external_tools.xml{.filename}.

The VikWebtoolCenter{.classname} allows to declare any Webtool using a
logic based on center coordinates and zoom level value.

The related properties are:

label
: the text displayed in the menu entry

url
: the parametrized URL to open, in the spirit of C printf format, with
2 "%s" and a "%d" fields for X, Y and Z (zoom level) (eg.
"http://hostname/?lat=%s&lon=%s&zoom=%d")

The VikWebtoolBounds{.classname} allows to declare any Webtool using a
logic based on bounds coordinates.

The related properties are:

label
: the text displayed in the menu entry

url
: the parametrized address of the tile, in the spirit of C printf
format, with 4 "%s" fields for left, right, bottom and top (eg.
"http://hostname:8111/load_and_zoom?left=%s&right=%s&bottom=%s&top=%s")

16.4. Routing engine {.title}

It is possible to declare new routing engines. The file is
~/.viking/routing.xml{.filename}.

An example of the file in the distribution
doc/examples/routing.xml{.filename}.

The VikRoutingWebEngine{.classname} allows to declare a routing engine
available via HTTP.

The related properties are:

id
: a string, should be unique as it used to identify the routing engine

label
: the text displayed in the menu entry

url-base
: the base URL of the web service (eg. "http://hostname/service?")

url-start-ll
: the part of the URL setting the starting point location,
parametrized in the spirit of C printf format, with 2 "%s" for
coordinates (eg. "&start=%s,%s")

url-stop-ll
: the part of the URL setting the end point location, parametrized in
the spirit of C printf format, with 2 "%s" for coordinates (eg.
"&stop=%s,%s")

url-via-ll
: the part of the URL setting via point location, parametrized in the
spirit of C printf format, with 2 "%s" for coordinates (eg.
"&via=%s,%s")

url-start-dir
: the part of the URL setting the starting point location for
direction based routing, parametrized in the spirit of C printf
format, with one "%s" for direction (eg. "&start=%s")

(Optional)

url-stop-dir
: the part of the URL setting the end point location for direction
based routing, parametrized in the spirit of C printf format, with
one "%s" for direction (eg. "&start=%s")

(Optional)

referer
: an URL to serve as referer for the HTTP request (eg.
"http://hostname/")

follow-location
: the max depth of recursive redirections

16.5. Remote File Datasources {.title}

It is possible to add web references expected to return a file which can
then be opened directly or converted via GPSBabel.

The file is ~/.viking/datasources.xml{.filename}.

An example of the file is in the source distribution
doc/examples/datasources.xml{.filename}.

The VikWebtoolDatasource{.classname} allows to declare any URL using
logic based on coordinates.

The related properties are:

label
: the text displayed in the menu entry

url
: the parametrized URL to open in the spirit of C printf format, with
up to 9 "%s" values. e.g.
http://hostname/getfile?lat=%s&lon=%s{.literal}

The order and meaning of these parameters is given by the
url\_format\_code below

url_format_code
: A string describing the parametrized URL substitution parameters,
each character represents how to translate each term.

B = Bottom of the current view i.e. minimum latitude

L = Left of the current view i.e. minimum longitude

T = Top of the current view i.e. maximum latitude

R = Right of the current view i.e. maximum longitude

A = center lAtitude of the current view

O = center lOngitude of the current view

Z = OSM Zoom value of the current view. See [Zoom
Levels](http://wiki.openstreetmap.org/wiki/Zoom_levels)

P = selected Point's latitude

N = selected poiNt's longitude

S = A user specified input string requested from the user via a
dialog box

Thus for the url example above then the format code should be *AO*

file_type
: This value is passed on for the -i parameter in interfacing with
GPSBabel.

If it is not defined then the returned file is interpreted
internally as a GPX file.

Possible values such as 'kml', 'mapsource' etc.. can be used. See
[GPSBabel File Formats](http://www.gpsbabel.org/capabilities.html)
for the full list.

babel_filter_args
: This value is passed on for the filter arguments interfacing with
GPSBabel.

E.g. "-x nuketypes,routes" can be used to filter all routes from the
results.

input_label
: This value is used when requesting input from the user.

It is the label of the text input box.

16.6. More {.title}

Note that, on UNIX™ like systems, the extension files
(maps.xml{.filename}, goto_tools.xml{.filename},
external_tools.xml{.filename}, datasources.xml{.filename}) are also
searched in /etc/viking{.filename} and /usr/share/viking{.filename}
directories (or related in your system).

The XDG_DATA_DIRS{.envar} environment variable can be used to change
these directories.

The XDG_DATA_HOME{.envar} environment variable is also used (if set)
to look for these extension files.

16.7. Miscellaneous Settings {.title}

Various individual values are automatically saved between Viking
sessions in the ~/.viking/viking.ini{.filename} file.

This file is not intended to be manually edited, but since it is a plain
text file it can be changed if desired.

Some values in this file are read only, in the sense that there is no
way to set it other than by manually entering in the keys and values
(the key will not exist in the file otherwise). This allows some fine
tuning of Viking behaviours, without resorting to recompiling the code.
However is it not expected that these values should need to be changed
for a normal user, hence no GUI options for these have been provided.

Here is the list of the read only keys and their default values.

  1. layers_create_trw_auto_default=false

    Create new TrackWaypoint layers without showing the layer properties
    dialog first.

  2. maps_max_tiles=1000

  3. maps_min_shrinkfactor=0.0312499

  4. maps_max_shrinkfactor=8.0000001

  5. maps_real_min_shrinkfactor=0.0039062499

  6. maps_scale_inc_down=4

  7. maps_scale_inc_up=2

  8. maps_scale_smaller_zoom_first=true

  9. mapnik_buffer_size=128 (in pixels)

  10. background_max_threads=10

  11. background_max_threads_local=Number of CPUs

  12. window_menubar=true

  13. window_copy_centre_full_format=false

  14. version_check_period_days=14

  15. trackwaypoint_start_end_distance_diff=100.0

  16. gps_statusbar_format=GSA

    This string is in the Message Format Code

  17. trkpt_selected_statusbar_format=KEATDN

    This string is in the Message Format Code

  18. utils_nearest_tz_factor=1.0

  19. viewport_history_size=20

  20. viewport_history_diff_dist=500

    In metres.

    Go Back or Go Forward requests over this range from the last history
    location will move back to that position. If within this range it
    will skip over this location and move on to the next saved history
    location.

  21. external_diary_program=rednotebook

    Or in Windows it uses
    C:/Progra~1/Rednotebook/rednotebook.exe{.filename} - This string
    value must use Unix separators and not have spaces.

  22. external_astro_program=stellarium

    Or in Windows use C:/Progra~1/Stellarium/stellarium.exe{.filename}
    - This string value must use Unix separators and not have spaces.
    Further note due to this
    Bug in
    Stellarium means this does not actually work. You will need to
    reference a shortcut, rather than the executable directly.

16.7.1. Message Format Code {.title}

Currently for ease of implementation the message format code is a string
of characters.

Each character represents what should be inserted in relation to a
Trackpoint.

One day it might evolve into something more user friendly with a
frontend to control it, perhaps allowing arbitary text too. However for
now at least some control is offered :)

Character Code
: G = Some text to display at the start of the message - GPSD

K = Some text to display at the start of the message - *Trkpt*

A = Altitude of a Trackpoint

S = Speed of a Trackpoint

B = Vertical Speed (Climb)

C = Course of a Trackpoint

L = Location of a Trackpoint

T = Time of a Trackpoint

M = Time diff of a Trackpoint from the previous trackpoint

X = Number of satellites used in the trackpoint fix

D = Distance of the trackpoint from the start of a track (following
along the track)

F = Distance of the trackpoint from the finish (end) of a track
(following along the track)

P = Distance difference of the trackpoint from the previous
trackpoint

N = Name of track to which the trackpoint belongs

E = Name of the trackpoint

Output Notes
: If the output has * after it, then the value has been calculated
via interpolation (such as speed when the Trackpoint does not
contain a speed value).

If the output has *\*\** after it, then difficulties were
encountered in trying to work the value so probably a default of 0
will be shown.

16.8. Keyboard Shortcuts (Accelerator) Settings {.title}

This is held in the file ~/.viking/keys.rc{.filename}

It is in the standard GTK Accelerator map format. Values are
automatically read in and saved between Viking sessions.

This file is not intended to be manually edited, but since it is a plain
text file it can be changed if desired.

gpsbabel. Viking uses GPSBabel for several
important functions, such as:

  • Importing Files from many formats (including KML)

  • Exporting Files to various formats

  • Transfer Data to/from GPS Devices via serial connections

  • Using Google Directions for routes

Thus these will not be available if the program can not be found.

For Unix™ like systems this will search the system path to find the
program, as it is typically installed via the System's package manager.

From Viking 1.6 onwards GPSBabel is not deployed automatically on
Windows™ systems, as it is made an optional install component (using the
official GPSBabel installation program). If GPSBabel is not installed in
a typical Windows™ location that Viking can find, then the GPSBabel
preference can be set to specify the exact location. See
Export/External
Preferences
.

Viking will need to be restarted to use the new GPSBabel location
preference.

unbuffer. Viking uses unbuffer command to optimize conversion calls.

This mainly applies to Unix™ like systems when invoking GPSBabel
commands.

gpsd (not available for Windows™). Viking can use
gpsd to get the current location.

togpx. Viking will use togpx to
open GeoJSON files if the program is available on the system.

togeojson. Viking will use
togeojson to export to GeoJSON
files if the program is available on the system.

18. Command Line {.title style="clear: both"}

18.1. Overview

18.2. Details

18.1. Overview {.title}

Viking being a Graphical User Interface program only has a few command
line options.

18.2. Details {.title}

Note that the ordering of files can be important depending on their file
type. Subsequent non Viking project files are loaded into the previous
Viking project, with the files being processed left to right. Some
examples:

  • viking file1.gpx file2.gpx file3.gpx{.literal}

    Here all GPX files are loaded into a new Viking project in one
    window.

  • viking file1.vik file2.vik{.literal}

    Each Viking project file is opened in a new window.

  • viking file1.vik file2.gpx file3.gpx{.literal}

    The GPX files are loaded into the Viking project in one window.

  • viking file2.gpx file3.gpx file1.vik{.literal}

    The GPX files are loaded into a new Viking project in a one window
    and the Viking project is loaded seperately in a seperate window.

Table 1. Command Line Reference


Short Option
Long Option
Description


-h -V -d
--help --verbose --debug
Show the command line options and then exit. Run in verbose mode. Some information about what Viking is doing is shown in stdout. Run in debug mode. Even more information about what Viking is doing is shown in stdout. This also enables some extra information features in the GUI itself, primarily of interest to developers.


\

: Internal Map Ids:

: OSM Mapnik = 13

: OSM Cycle = 17

: Mapquest OSM = 19

An example to open at a specified location with an OSM Mapnik map layer:

viking --latitude 51.4 --longitude -1.3 --zoom 12 --map 13

If a file is also specified on the command line, the command line
location and zoom parameters will take precendence.

![[Note]](note.png)

Note

As a special combination when both -V and -d are both enabled at the
same time, Viking will not delete some of the temporary files created
during the program run. This is especially useful to monitor results of
download requests (which need to be interpreted) if they suddenly start
failing, as the file will have often more detailed information about the
failure mode.

Viking being a GTK+ program means some options are processed by GTK+
itself such as --display. Use the following to find out what they are
for your system:

viking --help-gtk

19. Attributions {.title style="clear: both"}

19.1. coords.c + coords.h

19.2. strtod.c

19.3. kdtree.c + kdtree.h - 0.5.6

19.4. Data: cities15000.txt

This document contains licenses and notices for open source software
used in this product. The source code used in this product is available
on the project website http://viking.sf.net

19.1. coords.c + coords.h {.title}

Available under license:

** Copyright © 2001 by Jef Poskanzer <jef@acme.com>.
** All rights reserved.
**
** Redistribution and use in source and binary forms, with or without
** modification, are permitted provided that the following conditions
** are met:
** 1. Redistributions of source code must retain the above copyright
**    notice, this list of conditions and the following disclaimer.
** 2. Redistributions in binary form must reproduce the above copyright
**    notice, this list of conditions and the following disclaimer in the
**    documentation and/or other materials provided with the distribution.
**
** THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
** ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
** IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
** ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
** FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
** DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
** OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
** HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
** LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
** OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
** SUCH DAMAGE.

19.2. strtod.c {.title}

Source: http://www.jbox.dk/sanos/

Available under license:

// Copyright (C) 2002 Michael Ringgaard. All rights reserved.
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions
// are met:
// 
// 1. Redistributions of source code must retain the above copyright 
//    notice, this list of conditions and the following disclaimer.  
// 2. Redistributions in binary form must reproduce the above copyright
//    notice, this list of conditions and the following disclaimer in the
//    documentation and/or other materials provided with the distribution.  
// 3. Neither the name of the project nor the names of its contributors
//    may be used to endorse or promote products derived from this software
//    without specific prior written permission. 
// 
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
// ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
// ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
// FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
// DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
// OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
// HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
// LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
// OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 
// SUCH DAMAGE.

19.3. kdtree.c + kdtree.h - 0.5.6 {.title}

Source: https://code.google.com/p/kdtree/

Available under license:

Copyright (C) 2007-2011 John Tsiombikas  <nuclear@member.fsf.org>

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
   derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.

19.4. Data: cities15000.txt {.title}

Source: http://download.geonames.org/export/dump/

This is used in a lookup of positions to timezones.

Unneccesary fields in the dataset (for Viking) have been removed and the
resultant file is data/latlontz.txt{.filename}

Available under license:

This work is licensed under a Creative Commons Attribution 3.0 License,
see http://creativecommons.org/licenses/by/3.0/
The Data is provided "as is" without warranty or any representation of accuracy, timeliness or completeness.


Next  viking



Related

Main Wiki: Main_Page
Main Wiki: Users_Manual

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks