Viking is now available for use in Linux as a Flatpak, however since Viking is running in a sandbox some system integration features no longer work properly in the Flatpak runtime.

See the file FLATPAK.md in the top level of the source distribution for more detail.

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 and various other image features have Alpha Compositing, to create the appearance of partial transparency. This is a value between 0 and 255 with the default being 255 for a fully solid image, whereas 0 is fully transparent. By controlling this value one can see data below it in the layer hierarchy for interesting effects. A value of around 160 can be useful for blending views.

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.

The panel also contains tabs for Section 3.17, “Calendar”, Section 3.18, “Goto” and Section 3.19, “Track/Route Statistics” features.

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

This will typically include a Map layer with a default map created as standard.

Using the mouse (and keyboard) you can move and zoom the viewport or select items on view. See the Tools section for further details about different modes and the various control options supported.

Below the viewport can be shown track (and route) elevation/distance and time/speed (tracks only) graphs of the selected item. These are the same graphs as shown in Track and Route Properties. The graphs will automatically hide itself when nothing or no suitable item is selected.

Moving the mouse pointer over the graphs will show a tooltip readout of the nearest trackpoint. Similarly to the track properties graphs, left clicking will center the viewport on the trackpoint. A right click menu offers controls of the drawing options, a subset of track operations and access to further information dialogs.

This provides a readout of various information:

E.g. when creating a track/route, the general feedback area displays some information about the track/route.

Figure 2. Statusbar

This part of the statusbar displays:

Left clicking on the number of background processes opens a dialog from which the processes can be inspected and cancelled.

Left clicking on the number of log messages opens a dialog from which the messages can be viewed, filtered, copied and cleared. Newest messages are put at the top of the list.

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

Figure 3. The zoom selector available from status bar

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.

Viking supports different projections:

Viking uses a zoom level measured as a pixel factor in Metres Per Pixel (MPP), hence this may also be referred to as a zoom factor. By default in this document the zoom level refers to Viking's MPP definition unless otherwise stated.

This is in contrast to Tiled Web Map systems such as OpenStreetMap which use the Zoom Level as a measure of how much of the world is visible on the map.

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

The Viking automatic caching strategy is two fold:

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
	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 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:

	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:

Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exiting. 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:

	Important
	These work irrespective of the Tools mode selected

Up,Left,Right and Down also pan the viewport in the respective direction when any of the primary window tools is active (Select (when nothing is selected), Pan, Zoom or Ruler)

For other combinations see the menu entry themselves.

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
	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
	For Windows systems this can be done by adding the line gtk-can-change-accels=1 to %USERPROFILE%\.gtkrc-3.0 (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

In theory a route is path you are planning to follow and a track is of where you have actually been. The GPX specification splits these into two separate categories, although tracks contain everything a 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. The capability, the options and data on a particular device also effect how the navigation is performed. Often the how a device actually works doesn't seem to be formally documented by the manufacturer (and can be firmware dependent too). Web searches can reveal people's experiences with specific devices on blogs and various forums. For some devices it will attempt to navigate between route points, which may then suggest various roads and tracks between the points using an internal routing algorithm with some kind of transport profile. However this is limited to the quality of data available and how well the profile matches ones actual need. If the points are close enough then the 'best' route for any form of transport will typically be the straight line between the points.

Note

There are often restrictions on the numbers of route (or track) points the GPS Device can handle - may be 250 or as little as 50. This generally not a problem for shorter routes, but needs managing for longer or detailed routes. The number of track points is normally alot higher (e.g. 500 or typically with latest devices 10,000 or more) and less of a problem. See Auto GPX Simplify for help to manage this.

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

This creates a new window with the default settings.

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:

GPX, TCX, 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
	Viking handles more file types via the Acquire methods below.

Located on the File → Open Recent File menu only.

The most recently opened files are available for opening again. The number of files remembered is controlled by a value in the Advanced Preferences.

Note that files imported via the Acquire mechanism are not available in this list.

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.

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).

Located on the File → Append File... 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, whereby the file contents are added to the currently selected TrackWaypoint or Aggregate layer. Otherwise they are loaded in the normal file open method when no layer is selected.

Located on the File → Open GPX as External Layer... menu only.

Selecting a GPX file from this method will create an external TrackWaypoint Layer that loads from the specified file. The layer is marked as a "no write" external layer, which means any changes made will not be written back to the GPX file. To enable changes to be written, you can change the layer to a standard external layer in the layer properties dialog. This is in contrast to importing the data and storing it in the Viking file.

Located on the File → Properties menu only.

Displays some simple properties about the loaded Viking project file (if any), such as full filename including the path, the filesize and the date/time of the file.

Located on the File → Export All menu only.

Note that some data properties are not supported by the target export file type. Such as item visibility or track colours.

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.10.1. From GPS

File → Acquire → From GPS A way of getting information from GPS Devices using GPSBabel to perform the transfer, typically via serial link connections.

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

Note

Only a limited number of devices are supported this way (e.g. Garmin Etrex Legend devices first available ~2003). For the majority of current (circa 2010-2020) Garmin handheld devices and many other consumer handheld GPS devices (including SatNav style devices such as the Garmin Nuvi 255™) only support a native file system and write information to a Current.gpx file or similar. You will have to browse the file system on the device, opening it directly via File → Open. For modern (circa 2015 onwards) wearable devices such as Garmin Forerunner, Fitbit, Suuntu etc..., often have their own propriety binary (often wireless) protocols - not compatibile with GPSBabel and thus not Viking directly either. You would need to use their programs / apps to export to an open standard (such as GPX) for use with Viking.

3.10.8. From URL

File → Acquire → From URL

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

	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.

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

Print uses what is displayed on the current Section 2.3, “Viewport” 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.

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

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.

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

	Note
	This is only available in UTM mode.

A KMZ file is a compressed version of a KML file and associated supporting files.

A KMZ Map file is a KMZ file with an image overlay often for use as a Custom Map on Garmin GPSr devices.

Viking only supports basic properties in KMZ Map files, primarily intended for use with Garmin GPSr devices although KMZ exports are known to work with Google Earth.

Located on the File menu only.

Enables loading of a selected KMZ map file. This generates a new GeoRef map layer using the overlay image contained within the KMZ file.

Located on the File menu only.

Enables exporting the current Section 2.3, “Viewport” as a KMZ map file. The area and zoom level covered by the KMZ map can be adjusted before saving.

Note that Garmin GPSr devices have limits in using images if they are too large (e.g. over 3Mb big) in KMZ files. Viking does not enforce any limits on the KMZ files it generates.

The calendar marks days when any activity in Tracks occurred. Hovering the mouse pointer over a marked day shows the name of the corresponding TrackWaypoint Layer. Double clicking on a marked day moves the Section 2.3, “Viewport” to view the first track of that day.

Right clicking on the calendar offers further options to navigate in time, including moving the calendar to the next or previous track by date or to move to todays date.

This offers to search locations using the selected online providers, by default either OSM Nominatim or Geonames. One may click on the an entry in the list of returned results to move the Section 2.3, “Viewport” to that location.

See the section Section 18.2, “Go-to Search Engines” to configure additional search providers.

Figure 4. Screenshot: Goto Tab

This offers a compact view of statistics of the selected Track or Route. Currently this does not refresh if the Track/Route changes but there is a right click menu on the tab, which offers a way to manually refresh the values.

Figure 5. Screenshot: Stats Tab

Also available is a tab to shows Track Time Splits. Since this is a more detailed display that is of interest only to a subset of users and takes up more space, the tab is hidden by default. Use View → Show → Show Side Panel Splits to enable it.

Besides the standard edit entries (Cut, Copy, Paste, Delete) that operate on the currently selected item, there is also the Delete All which removes ALL layers (including the automatically created Default Map).

Allows access to Viking Preferences.

Allows access to the Section 5, “Layers” defaults. When creating a new layer it will start with the default values as specified here.

Access to show the messages that are being suppressed and the ability to reset back to the default of no messages being suppressed. Some warning style messages can be selected to be ignored, since if they repeatedly come up in your work flow they could otherwise become tiresome.

Allows selection of the Projection mode.

Offers a selection of methods to jump to a position in the world.

The Go to Lat/Lon dialog method allows manually specifying the coordinates to move to.

	Note
	The latitude entry (although a spin button) can accept any text and will be attempted to be used as a Lat/Lon Pair.

Additionally there is method to move the calendar view to todays date.

These entries allow setting the default background colour (i.e. when there are no maps) and the highlight colour for selected tracks and waypoints.

Offers a selection of methods to zoom the viewport, including not only In and Out but also to any specific level.

Offers a selection of methods to control visibility of various screen elements. Most of these can also be accessed via Shortcut Keys.

Offers alternative access to additional informational dialogs. Otherwise these can be accessed from the Section 2.5, “Statusbar”.

This layer has many configurable properties split into several parts:

The layer has a context menu with several operations.

6.2.4. Goto Waypoint

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 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.

6.2.6. Finish Track or Route

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

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

6.2.11. Delete

Offers deletion of various parts of a TrackWaypoint layer:

6.2.11.1. Delete All Tracks

Deletes all the tracks in this layer.

6.2.11.2. Delete Tracks from Selection

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

6.2.11.3. Delete All Routes

Deletes all the routes in this layer.

6.2.11.4. Delete Routes from Selection

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

6.2.11.5. Delete All Waypoints

Deletes all the waypoints in this layer.

6.2.11.6. Delete Waypoints from Selection

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

6.2.11.7. Delete Duplicate Waypoints

Deletes duplicate waypoints in this layer. Waypoints are considered duplicate if they have the same location and symbol.

	Note
	If other properties are different such as name, comment, altitude, etc... they will still be considered a duplicate.

6.2.12. Filter

6.2.12.1. Simplify All Tracks

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.

6.2.12.2. Compress Tracks

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.

6.2.12.3. Remove Duplicate Waypoints

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

	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.

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

Also gives other options for handling multiple items:

This shows several tabs for properties and useful statistics about a track or a route, including elevation, speed, heart rate, cadence, temperature and power graphs (if the data is available and the graph has not been disabled via Track Properties Dialog Preferences).

The tabs can be reordered via drag 'n' drop of the tab label. The ordering is retained between new invocations of the properties dialog.

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.

For the elevation related graphs the Show DEM check button is only enabled if a suitable DEM is available that overlaps the track.

Graphs either have a Show GPS Speed or Show Speed button. Each of these overlays relative speed markers along the graph. The difference between Speed vs GPS Speed is that GPS Speed is taken directly from a field reporting the speed value in the source data. Typically speeds used in Viking are calculated between the points time and position differences. This is due to the reporting of speed values in source data is not mandatory and often not present.

6.4.1. Track and Route Properties Tab

Figure 6. Properties Tab: Example (Tabs at side option and reordered)

6.4.2. Track and Route Statistics Tab

Figure 7. Statistics Tab: Example

6.4.3. Track Elevation Graph

Figure 8. 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

6.4.4. Track Time Splits

Figure 9. Splits Tab: Example

This tab displays timing splits on tracks with timing information. A few different values of split lengths are available, each having it's own tab display.

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

Also gives other options for handling multiple items:

This shows a dialog with detailed information for the (possibly new) waypoint. Many properties of the waypoint can set or changed here, such as the comment, the symbol used in drawing or the image (normally a photograph taken at this position) associated 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.

Clicking on the time opens the time edit dialog from which the time can be adjusted (or added if the waypoint did not have a time). When the waypoint has a time, right clicking on the button opens a menu from which there are options to copy the time value as text or remove the time value.

Note

The latitude entry can accept any text and will attempt to decode the text as a lat/lon pair. If successfully decoded then this will take precedence over the longitude value. In the case entering e.g. "54.32 -1.098", the latitude will become 54.32 and the longitude -1.098 (when the dialog is accepted). This takes a few various lat/lon format strings, including: "12, 34": Commas are ignored "S12 W34": With cardinal indicators at begining "12 S 34 W": With cardinal indicators after (must have space between the number and letter) "12.34 56.67": DDD format "S034° 12.3456 W003° 45.6789": DMM format. Equals DDD "-34.20576 -3.76131" "S034° 12 34 W003° 45 54": DMS format. Equals DDD "-34.20944 -3.76500"

Figure 10. Waypoint Properties: Example

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
	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:

Typically timestamps in images are either in local time or UTC but there is no way of automatically knowing which; so you need to specify which is the case. Image Time Offset is best used for accounting for camera's clock drift, so normally of the order of a few seconds or minutes. Whereas Image Timezone is more for adjusting for a camera's timezone difference, or perhaps differences in your current timezone and the timezone the images where taken.

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

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.

You must put the correct information to connect to an instance of GPSD in the GPS Layer properties - Realtime Tracking Mode tab.

By default Viking will automatically continually attempt to connect to GPSD using the specified host and port values, otherwise if necessary use right-click on the layer and select Start Realtime Tracking.

See Section 17.5, “GPS Real Time Location” for more detail.

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

Configurable properties:

Tracks Area Coverage (TAC) is a feature to highlight areas with track coverage. It is based on OpenStreetMap style tiles - as an approximation to a grid square system. The size of the area can be changed, which is linked to the OSM Zoom level, such that a higher Zoom level gives a smaller physical area and so more tiles. This can be used for general curiousity or perhaps to plan routes to visit areas previously unexplored.

The calculations are performed in the background when deemed necessary (e.g. loading in a new file) and can also be manually requested.

Note that Viking can be slow in drawing hundreds or more tracks but this analysis is relatively quick and the resulting drawing is much faster. Thus ATM is it recommended to turn off the visibility of the tracks themselves for this type of usage.

Figure 12. Tracks Area Coverage: Example

A concept of ignoring unreachable tiles is supported. This allows marking individual tiles as inaccessible (e.g typically military use only, so no public access) so that the tile is still included for maximum square and clustering count purposes. These tiles are drawn in red on the viewport.

On startup Viking attempts to load the file unreachable_tiles.txt in your User Configuration File Location.

The file should contain a list of tiles in the format of 3 numbers, with each line being "OSM_ZOOM TILE_X_ID TILE_Y_ID". e.g.

14 8116 5474
14 8117 5474

Any lines starting with a '#', '!' or ';' are ignored as intended for comments. A fuller example covering the UK is in /usr/share/viking/unreachable_tiles.txt or C:\Program Files\Viking\data\unreachable_tiles.txt according to the operating system and typical install locations. You may wish to copy this file into your Viking home directory so that it is used.

The heatmap is another feature to analyse areas with track coverage. It must be manually requested via right click on the Aggregate layer and choosing from the menu Tracks Heatmap → Calculate. The heatmap covers the current area displayed on the viewport.

The calculations are performed in the background as depending on the number of tracks, the heatmap options and the speed of the computer the calculation may take a little time. If the viewport size is changed then the heatmap is automatically invalidated and removed. Panning the display leaves the heatmap image only covering the area already calculated. Zooming in and out scales the heatmap image appropriately, but the image may get removed if the scaling operation is likely to be too slow.

Figure 13. Heatmap: Example

Offers basic controls whether it is enabled or not and includes the size of the tile.

Controls subsets of TAC drawing are calculated and shown with their colour and opacity.

Note for Max square coverage, ATM it will only draw the first square encountered, although there may be more than one such area.

Note for Cluster coverage, ATM it will only draw the first cluster encountered, although there may be more than one such area.

Offers controls over the heatmap image.

If there is an existing heatmap on display then changing these values and selecting Apply will cause the heatmap to be recalculated with the new settings.

The following are available on Aggregate Layers:

9.6.4. Sort

The list within the treeview can be sorted.

Alphabetical and Date sorts are available.

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

9.6.5. Track List

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 14. 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!

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.6.6. Waypoint List

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 15. 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.

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.9. Statistics

This opens a dialog to display various statistics about all tracks contained within this Aggregate layer.

Figure 16. Statistics Dialog: Totals

	Note
	This currently generates a simplified Eddington number. In that a per track length value is used, rather than trying to work out a length per day. (i.e. doesn't combine multiple tracks for a single day or split very long tracks into days). The Eddington number is in the current Unit distance Preferences.

Figure 17. Statistics Dialog: Years

Each column can be sorted by clicking on the relevant column header.

The right click menu offers an option to copy all the data as text in a CSV style format (using a tabbed separator).

Selecting a year will update the information in the Months tab.

Figure 18. Statistics Dialog: Months

Each column can be sorted by clicking on the relevant column header.

The right click menu offers an option to copy all the data as text in a CSV style format (using a tabbed separator).

The right click menu offers an option to show the Track List for the relevant month.

Configurable properties are split into several sections:

Other than the standard operations (Cut, Paste etc...), there are no further specific operations available.

Configurable properties:

Configurable properties:

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.

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.

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.

This is the default mode of operation for Viking.

This mode can be entered by clicking on the toolbar icon:

The select tool allows one to choose an item, discard the selection of an existing item or to move the viewport. To select an item (waypoint, track or route) left click on it (or reasonably near) in the viewpoint. ATM to select a track one must actually click on a trackpoint, which is also selected. To deselect an item simply left click away from any item.

To move the viewport hold the left mouse button down whilst moving the mouse pointer around (as per the specific Pan mode). Also if Right Alt (or Windows™ Left Alt) is held down then the item selection/deselection is skipped and goes straight into pan mode; this may be useful if the item selection process is noticeably slow (and hence can be bypassed) or avoiding accidental deselection of the item of interest.

Once an item (waypoint or trackpoint) is selected it can be moved. The item must be clicked on again in order to start moving the it, this is to prevent accidental movement of item in the initial selection. If Ctrl or Shift is held down at the same time, it will jump the item position to a nearby existing trackpoint or waypoint respectively. Note that whole tracks cannot be moved.

When a trackpoint is selected pressing Left or Right moves to the previous or next trackpoint respectively.

[ or Keypad- inserts a point before the selected trackpoint, whereas ] or Keypad+ inserts a point after the selected trackpoint.

Ctrl+d will delete the selected trackpoint or waypoint without any additional confirmation of the action. Since there is no undo system - this shortcut is delibrately a two key operation.

Currently these keyboard shortcuts are not configurable.

By default double click zooming is disabled - see Advanced Preferences to enable it. 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.

This mode can also be entered by the keyboard shortcut Ctrl+Shift+C or now more simply just s.

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 mode can also be entered by the keyboard shortcut Ctrl+Shift+P or now more simply just p.

The double click behaviour is the same as in the Select mode described above (i.e. zooms in or out), however it is always enabled.

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 or now more simply just 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.

This mode is entered by clicking on the toolbar icon:

The ruler is used to measure either:

This mode can also be entered by the keyboard shortcut Ctrl+Shift+U or now more simply just r.

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

15.5.7. Edit Trackpoint

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.

15.5.7.1. Edit Trackpoint Dialog

Editing options in the Trackpoint Edit dialog include:

• Edit the trackpoint name

• Changing raw lat/long position, altitude and time

• 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:

• 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 20. Trackpoint Edit Dialog: Example

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

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

You must have a Map 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:

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 21. Map Tile Info Dialog: Example

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

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 22. DEM File Info Dialog: Example

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

	Note
	The Source URL is generated from the current configuration settings; it is not necessarily the URL that was used to acquire the DEM file, as that information is not saved.

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.

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

Store your NASA Earth login details which uses HTTP Basic Authentication.

	Warning
	Your password will be stored in plain text.

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:

17.1.3. Add a Map Layer

By default Viking will add a map layer for you that will automatically download map tile images, but you can of course change it or add additional map layers.

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
	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.

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.

 right-click the DEM layer properties

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

Authentication/authorization is required to use these services. See OpenStreetMap Traces Preferences.

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

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

Viking relies on GPSD (via the GPSD service library client) to provide the current location from a real time feed from a GPS device.

Note

At the time of writing the GPSD service itself is supported on the following platforms: "Presently Linux, OpenBSD and NetBSD are directly supported... Apple's OS X is supported in a limited fashion.". i.e. Explicitly not on Windows. On Windows Viking provides a GPSD client to connect with the server (service daemon) instance of the GPSD which would be running on different (supported platform) machine. For instance notionally one could run a virtual machine instance of a BSD variant on the Windows host, run GPSD on this BSD instance and then make Viking connect to that GPSD instance. Running the GPSD service is outside the scope of Viking.

This assumes you already have a Map 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.

	Important
	The latest versions of Viking now captures logging messages, which can be accessed via a button in the middle of the statusbar, or via View → Log. The statusbar shows the number of log messages. The debug status itself can also be controlled from the GUI itself, use Help → Debug to toggle the setting in order to capture more messages. The log window displays the newest messages at the top.

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

viking -dV

NB For Windows™ the process is slightly more involved as the output is typically not shown in the command prompt, so you have to redirect the output to a file, e.g. open the command prompt and then:

cd "C:\Program Files\Viking"
viking -dV 2>1 > %TMP%\viking.log

Then close Viking before viewing the output file, such as:

notepad %TMP%\viking.log

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

It is possible to add new map sources. The file is maps.xml placed in your User Configuration File Location

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

The VikSlippyMapSource allows declaration of any map source working like OpenStreetMap. It supports the following properties:

The VikTmsMapSource allows declaration of any TMS service. A TMS (Tile Map Service) is defined in Tile Map Service Specification. The configuration supports the following properties (as per VikSlippyMapSource above):

The VikWmscMapSource allows declaration of any WMS or WMS-C service. A WMS (Web Map Service) is defined in WMS Tile Caching. The configuration supports the following properties (as per VikSlippyMapSource above):

It is possible to add new new search engines for the "Go-To" feature. The file is goto_tools.xml placed in your User Configuration File Location.

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

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

The related properties are:

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.

It is possible to add new external tools. The file is external_tools.xml placed in your User Configuration File Location.

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

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

The related properties are:

The VikWebtoolBounds allows one to declare any Webtool using a logic based on bounds coordinates.

The related properties are:

It is possible to declare new routing engines. The file is routing.xml placed in your User Configuration File Location.

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

The VikRoutingWebEngine allows one to declare a routing engine available via HTTP.

The related properties are:

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 datasources.xml placed in your User Configuration File Location.

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

The VikWebtoolDatasource allows one to declare any URL using logic based on coordinates.

The related properties are:

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

The $XDG_DATA_DIRS environment variable can be used to change these directories.

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

Viking looks for its configuration files (viking.prefs, viking.ini, viking.ini and keys.rc) in a specific directory, searching legacy locations first before trying new locations. Thus if you upgrade Viking it will continue to use your existing setup.

For UNIX™ like systems:

For Windows™ systems:

For Mac™:

/Library/Application Support/Viking

	Note
	If you've upgraded Viking to v1.9 and want it to use the new location, you will have to manually move the existing directory (when Viking is not running). e.g. in the command line: mv ~/.viking ~/.config/viking

Various individual values are automatically saved between Viking sessions in the viking.ini file placed in your User Configuration File Location.

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.

This is held in the file keys.rc in your User Configuration File Location.

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.

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

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:

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.

Viking supports RFC5870, the 'geo' URI scheme. Every 'file' on the command line is checked to see if in fact it is a geo URI. Thus the above example in geo URI format is:

viking geo:51.4,-1.3?z=12 --map 13

	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

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.

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

Version: Sanos 1.3.2

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.

A simple C library for working with KD-Trees.

Source: https://github.com/jtsiomb/kdtree

Files used: kdtree.c + kdtree.h

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.

Converts floating point numbers to an optimal decimal string representation without loss of precision.

Source: https://github.com/night-shift/fpconv

Available under MIT license

Files used: fpconv.c + fpconv.h

Version SHA:dfeb7e938fb85fb5eca130b84f856705ced75012 (August 2013)

An extract from GtkHTML for URI functions.

Source: https://git.gnome.org/browse/gtkhtml

Available under GPL2 or later.

Files used: gtkhtml.c + gtkhtml-private.h

A heatmap generation library.

Source: https://github.com/lucasb-eyer/libheatmap

Available under MIT license

Files used: heatmap.c + heatmap.h

Version SHA:0e22cbdaf4b4790beca2313c329db2332f2609eb (Nov 2017)

Source: https://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

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.

Use of geoPlugin services making use of geolocation data is under condition of acceptance of the Creative Commons Attribution-ShareAlike 3.0 Unported License.

This product includes GeoLite data created by MaxMind, available from http://www.maxmind.com.

Some icons have been used courtesy of https://uxwing.com

Available under MIT license