2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY appname "Viking">
5 <!ENTITY app "<application>Viking</application>">
6 <!ENTITY appversion "1.5">
7 <!ENTITY manrevision "1.5">
8 <!ENTITY date "October 2013">
11 (Do not remove this comment block.)
12 Maintained by the GNOME Documentation Project
13 http://live.gnome.org/DocumentationProject
14 Template version: 3.0 beta
15 Template last modified 2006-11-21
18 <!-- =============Document Header ============================= -->
19 <article id="index" lang="en">
21 <title>&app; Manual</title>
22 <abstract role="description">
23 <para>&app; is a free/open source program to manage GPS data.</para>
28 <holder>Guilhem Bonnefille</holder>
29 <holder>Rob Norris</holder>
32 <!-- An address can be added to the publisher information. -->
33 <publisher role="maintainer">
34 <publishername>GNOME Documentation Project</publishername>
37 <xi:include href="legal.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
38 <!-- The file legal.xml contains link to license for the documentation,
39 and other legal stuff such as "NO WARRANTY" statement.
40 Please do not change any of this. -->
44 <firstname>Guilhem</firstname>
45 <surname>Bonnefille</surname>
48 <firstname>Rob</firstname>
49 <surname>Norris</surname>
51 <!-- Contributors from the Wiki history -->
53 <firstname>username:</firstname>
54 <surname>Alexxy</surname>
57 <firstname>username:</firstname>
58 <surname>Vikingis</surname>
61 <firstname>username:</firstname>
62 <surname>Tallguy</surname>
65 <firstname>username:</firstname>
66 <surname>EliotB</surname>
69 <firstname>Alex</firstname>
70 <surname>Foobarian</surname>
77 <revnumber>&appname; Manual V&manrevision;</revnumber>
80 <para role="author">Guilhem Bonnefille <email>guilhem.bonnefille@gmail.com</email></para>
81 <para role="author">Rob Norris <email>rw_norris@hotmail.com</email></para>
82 <para role="publisher">GNOME Documentation Project</para>
83 <para>This document was generated on <?dbtimestamp format="Y-m-d"?>.</para>
88 <releaseinfo>This manual describes version &appversion; of &appname;.</releaseinfo>
91 <title>Feedback</title>
92 <para>To report a bug or make a suggestion regarding the &app; application or
93 this manual, follow the directions in the
94 <ulink url="ghelp:user-guide?feedback-bugs" type="help">Feedback section of the GNOME User Guide</ulink>.
99 <indexterm zone="index">
100 <primary>&app;</primary>
102 <!-- ============= Document Body ============================= -->
103 <section id="introduction">
104 <title>Introduction</title>
106 &appname; aims to be easy to use, yet powerful in accomplishing a wide
107 variety of tasks. Some of the things you can use &appname; for are:
109 <itemizedlist mark="opencircle"><listitem>
111 Uploading and downloading waypoints, tracks and routes to/from GPS.
115 <para>Preparing tracks, routes and waypoints for trips using maps from services such as OpenStreetMap (OSM).
116 The data is only needed to be uploaded to your GPS before you leave.
117 The maps together with your tracks, routes and waypoints can also be printed and used during the trip.
122 After trips, tracks and waypoints from GPS can be downloaded, stored, managed and reused in your (or your friends') later trips.
127 Analyzing Off Highway Vehicle (OHV) and hiking trips, understanding where you went and how far you were from something.
131 <para>Making waypoints, tracks and routes to follow to easily get someplace
132 you've never been before or don't have GPS data for but online
138 Making maps with coordinate lines.
143 Grouping data from multiple trips using a hierarchical data manager.
148 Analyzing speed at different places (to some degree), adding waypoints where you forgot to mark one but did slow down or stop.
153 Downloading and storing OpenStreetMap and/or other map types on your hard drive and looking at them later.
158 Editing routes or tracks and their trackpoints, joining and splitting up tracks and routes.
163 Show the live GPS position on the map (for use on a mobile device - e.g. a laptop). Not <trademark>Windows</trademark> at the moment.
168 Import track, route and waypoint files of various types via <application>GPSBabel</application>
173 View, create and update Geotagged Images (using EXIF data).
179 &appname; is under continual improvement: see the potential areas in the <ulink url="http://sourceforge.net/apps/mediawiki/viking/index.php?title=Main_Page#TODO_.2F_Ideas"><citetitle>Roadmap / Wishlist</citetitle></ulink>:
183 <title>Screenshot: OSM Cycle Map and Many Tracks</title>
185 <graphic format="JPG" fileref="figures/Viking-OSM-CycleMap-ManyTracks.jpg"/>
190 <section><title>General Concepts</title>
191 <section id="gc_layers" xreflabel="Layers"><title>Layers</title>
193 <emphasis>Layers</emphasis> is concept one may know from powerful graphics editors such as <application>Photoshop</application> or <application>GIMP</application>.
194 Instead of putting all the data on the same level, it is stacked (i.e. layered) with different data over one another.
195 This can be useful for analysis and general handling of various sets of data.
198 Unfortunately the downside of this complexity is remembering how differing layers of data can obscure other data.
201 The Map layers have <ulink url="http://en.wikipedia.org/wiki/Alpha_compositing"><citetitle>Alpha Compositing</citetitle></ulink>,
202 to create the appearance of partial transparency.
203 By controlling this value one can see data below it in the layer heirarchy for interesting effects.
206 <section id="gc_layers_panel" xreflabel="Layers Panel"><title>Layers Panel</title>
208 The panel on the left is called the <emphasis role="bold">layers panel</emphasis>.
209 It determines which layers and sublayers (such as tracks and waypoints)
210 are shown, and the order in which they are drawn. Layers on the
211 top of the layers panel list are drawn last. You can change the order by
212 drag and drop, or by selecting a layer and using the up and down
213 buttons at the bottom of the layers panel.
216 <section><title>Viewport</title>
218 The main &appname; area where the layer data is drawn, is called the <emphasis role="bold">viewport</emphasis>.
221 <section><title>Statusbar</title>
222 <para>This provides a readout of various information:</para>
224 <listitem><para>The currently selected (mouse pointer) tool</para></listitem>
225 <listitem><para>The number of items to process in the background - normally this the number in the map tile download queue</para></listitem>
226 <listitem><para>The zoom factor</para></listitem>
227 <listitem><para>The location of the mouse pointer (and potentially height information if DEM data is available)</para></listitem>
229 <para>When creating a track/route, the statusbar also displays some information about the track/route.</para>
231 <title>Statusbar</title>
233 <graphic format="PNG" fileref="figures/trw_statusbar.png"/>
236 <para>This part of the statusbar displays:
238 <listitem><para>The total distance of the track/route (including currently edited segment).</para></listitem>
239 <listitem><para>The bearing of the currently edited segment.</para></listitem>
240 <listitem><para>The distance of the currently edited segment.</para></listitem>
243 <para>For convenience, a zoom selector can be opened from the status bar. Simply left-click on the zoom factor.</para>
245 <title>The zoom selector available from status bar</title>
247 <graphic format="PNG" fileref="figures/zoom_status_popup.png"/>
252 <section id="toolbar" xreflabel="Toolbar"><title>Toolbar</title>
253 <para>The toolbar is an area for buttons that perform common actions.</para>
254 <para>Some actions are modal, so the appropriate layer needs selected before these toolbar buttons are enabled. See <xref linkend="tools"/> more detail.</para>
255 <para>The display of the toolbar is influenced by the <xref linkend="prefs_toolbar"/></para>
256 <para>Right clicking on the toolbar and selecting <menuchoice><guimenu>Customize</guimenu></menuchoice> allows jumping to the <xref linkend="prefs_toolbar_customize"/> directly.</para>
259 <section id="projection" xreflabel="Projection"><title>Projections</title>
261 &appname; supports differents projections:
267 <para>LatLon (also called EPSG:4326)</para>
270 <para>Mercator (also called Spherical Mercator)</para>
276 <section id="mapcache" xreflabel="Map Cache"><title>Map Cache</title>
278 &appname; stores downloaded map tiles to disk for a couple of reasons:
281 <listitem><para>Enables off line usage</para></listitem>
282 <listitem><para>Reduces loading on the map tile provider</para></listitem>
285 The &appname; automatic caching strategy is two fold:
290 If the age of the tile on disk is less than the specified tile age (see <xref linkend="prefs"/>),
291 it will <emphasis>not</emphasis> attempt to contact the server to get a new version of the tile.
296 When the tile age has expired &appname; will attempt a <emphasis>refresh</emphasis> 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.
301 You can override the caching scheme by using right-click on the Map on the layers panel and selecting <guimenuitem>Redownload All Onscreen Maps</guimenuitem>, or <keycap>Ctrl+F5</keycap> for the top most map displayed. This will get the latest version held by the server.
305 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 <ulink url="http://help.openstreetmap.org/questions/102/i-have-made-edits-but-they-dont-show-up-on-the-map">I have made edits but they don't show up on the map</ulink>)
310 The layout of the cache on disk itself can be controlled via a per Map Layer property.
312 <listitem><para>Viking - Legacy default in a private cache layout scheme</para></listitem>
313 <listitem><para>OSM - Newer available default (1.6+)</para>
315 This is to increase the compatibility between &appname; and similar applications that cache tiles on disk so that the tiles can be shared.
323 <section id="shortcut_keys" xreflabel="Shortcut Keys"><title>Shortcut Keys</title>
325 &appname; has several shortcut keys or key combinations for commands as listed in the main window along side the command.
328 By default some function keys follow standard GUI behaviour:
331 <listitem><para><keycap>F1</keycap> Help (view this manual)</para></listitem>
332 <listitem><para><keycap>F5</keycap> or <keycap>Ctrl+R</keycap> Refresh the maps on screen</para></listitem>
333 <listitem><para><keycap>F10</keycap> Select the Menubar (in built behaviour)</para></listitem>
334 <listitem><para><keycap>F11</keycap> Full Screen</para></listitem>
335 <listitem><para><keycap>Ctrl+F5</keycap> or <keycap>Ctrl+Shift+R</keycap> Redownload the maps on screen</para></listitem>
339 Refresh attempts to get new maps only if the local tile cache time period has expired for any particular map tile.
340 Redownload gets all on screen maps from the server, ignoring the local tile cache.
344 Other function keys control turn on/off visibility of various elements:
347 <listitem><para><keycap>F3</keycap> Toggle visibility of the Toolbar</para></listitem>
348 <listitem><para><keycap>F4</keycap> Toggle visibility of the Menubar</para></listitem>
349 <listitem><para><keycap>Shift+F5</keycap> Toggle visibility of the Scale indicator on the viewport</para></listitem>
350 <listitem><para><keycap>F6</keycap> Toggle visibility of the Center Crosshairs on the viewport</para></listitem>
351 <listitem><para><keycap>F7</keycap> Toggle showing selected items (e.g. tracks or waypoints) in the highlight colour in the viewport</para></listitem>
352 <listitem><para><keycap>F9</keycap> Toggle visibility of the Layers Panel</para></listitem>
353 <listitem><para><keycap>F12</keycap> Toggle visibility of the Statusbar</para></listitem>
356 Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exitting.
357 Then there are shortcuts specific to &appname; to switch projection modes, zoom in/out, create layers,switch the active tool mode and move the map:
359 <listitem><para><keycap>Ctrl+Up</keycap> Pan the viewport North</para></listitem>
360 <listitem><para><keycap>Ctrl+Right</keycap> Pan the viewport East</para></listitem>
361 <listitem><para><keycap>Ctrl+Down</keycap> Pan the viewport South</para></listitem>
362 <listitem><para><keycap>Ctrl+Left</keycap> Pan the viewport West</para></listitem>
363 <listitem><para><keycap>Ctrl+Keypad+</keycap> Zoom In</para></listitem>
364 <listitem><para><keycap>Ctrl+Keypad-</keycap> Zoom Out</para></listitem>
366 <important><para>These work irrespective of the <xref linkend="tools"/> mode selected</para></important>
367 For other combinations see the menu entry themselves.
372 <title>Keyboard Configuration</title>
373 <para>Keyboard configuration is supported by the standard GTK+ way of changing shortcuts for menu entries.</para>
374 <para>Hover over the menu option with the mouse pointer and press the keyboard shortcut you want to bind it to.</para>
375 <para>To delete a keyboard assignment, press <keycap>Backspace</keycap> whilst over the menu entry.</para>
378 If the keyboard shortcut is already in use you will not receive any notification that new action replaces the old action.
379 This is probably why most distributions have this facility disabled by default.
380 Thus you will need to enable <emphasis>Editable menu accelerators</emphasis> for your system.
381 Check the Desktop Menu and Toolbar Control or other User Interface preferences for this setting.
386 For Windows systems this can be done by adding the line <emphasis>gtk-can-change-accels=1</emphasis> to <filename>%USERPROFILE%\.gtkrc-2.0</filename> (create the file if it does not exist).
389 <para>From &app; 1.6+ the keyboard configuration is automatically loaded and saved between sessions in the <xref linkend="config_keys"/></para>
392 <section><title>Tracks vs Routes</title>
394 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.
397 Q. When planning a <emphasis>route</emphasis> what difference does it make if it's a route or a track?
400 A. One difference is in how a GPS device navigates following the route or track.
401 Or you may want to consider interoperability with other software.
402 Otherwise it is probably best to use tracks as they are a superset of the route functionality.
405 For example on Garmin Etrex:
409 <para>Route following: Uses navigation mode with compass and estimated time to next point.</para>
410 <para>If following on road it can calculate a route on fly.</para>
411 <para>I (RN) always use this mode to follow pre planned routes.</para>
414 <para>Track following: Uses a <trademark>TracBack</trademark> mode</para>
415 <para>I (RN) never use this so I can't comment on how it actually compares to the route mode.</para>
419 There are often restrictions on the numbers of route points the GPS Device can handle - may be 250 or as little as 50.
420 This generally not a problem for single day routes, but needs managing for multi-day events or for highly detailed routes.
424 </section><!--General Concepts End-->
426 <section><title>File Types and the Main Window</title>
429 &appname; has it's own file type traditionally marked by the <emphasis>.vik</emphasis> file extension.
430 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...).
433 Besides it's own file type, &appname; can open (and save to via export methods) GPX and KML file types.
437 &appname; does not handle GPX 1.1 particularly well - it prefers GPX 1.0
441 By default &appname; opens a default blank window centered on the home location. This behaviour can be changed by the <xref linkend="prefs_startup"/>.
442 Each window contains menus, a toolbar, a viewport, layers panel and a statusbar.
443 Each section (apart from the viewport) can be hidden using the <xref linkend="shortcut_keys"/> or from the
444 <menuchoice><guimenu>View</guimenu><guisubmenu>Show</guisubmenu></menuchoice> choices.
447 One may consider each &appname; window to be a separate project - each with it's project <emphasis>Viking</emphasis> file.
448 However generally one window is enough for most purposes!
451 Several operations apply at the window level as follows next.
452 Also see <xref linkend="tools"/> for the operational modes that generally work in conjunction with a selected layer.
455 <section><title>New</title>
457 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu></menuchoice> menu and on the toolbar <guibutton>New</guibutton>.
460 This creates a new window with the default settings.
464 <section><title>Open</title>
466 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Open</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Open</guibutton>.
469 This opens a file chooser dialog to select one (or more) files of the supported GPS data file types:
471 <listitem><para>Viking</para></listitem>
472 <listitem><para>GPX</para></listitem>
473 <listitem><para>KML</para></listitem>
474 <listitem><para>JPG</para></listitem>
478 GPX, KML and JPG files will be loaded into the existing &appname; view. A <emphasis>Viking</emphasis> file will be given a new window if the current window is already assigned.
482 &appname; handles more file types via the <link linkend="acquire">Acquire</link> methods below.
487 <section><title>Save</title>
489 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Save</guibutton>.
492 If the current opened file is <emphasis>Viking</emphasis> file, this save will simply update it.
493 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 <emphasis>new name</emphasis> to save as a <emphasis>Viking</emphasis> file.
497 <section><title>Save As</title>
499 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save As</guisubmenu></menuchoice> menu only.
502 This will ask for a <emphasis>new name</emphasis> to save as a <emphasis>Viking</emphasis> file (even it was already a <emphasis>Viking</emphasis> file).
506 <section><title>Append</title>
508 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Append</guisubmenu></menuchoice> menu only.
511 Selecting a <emphasis>Viking</emphasis> file from this method will join the file contents to the current window (instead of creating a new one).
512 GPX and KML files may also be appended, but this is exactly the same as the normal file open method.
516 <section id="acquire" xreflabel="acquire"><title>Acquire</title>
519 Available on the <menuchoice><guimenu>File</guimenu><guisubmenu>Acquire</guisubmenu></menuchoice> menu and from the <xref linkend="TrackWaypoint"/> layer menu.
522 If used from the <guimenu>File</guimenu> menu these methods place the results in a new TrackWaypoint layer.
525 If used from the <xref linkend="TrackWaypoint"/> layer menu these methods place the results in that TrackWaypoint layer.
529 <title>From GPS</title>
531 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
532 Probably the easiest way of getting information from a GPS Device.
535 Select the GPS Device communication settings and then hit <guibutton>OK</guibutton>.
536 See the <link linkend="method_c">Getting Started</link> section for more info about the settings.
540 Some GPS devices (such as the <trademark>Garmin Nuvi 255</trademark>) support a native file system and write information to a <filename>Current.gpx</filename> file or similar. You will have to browse the file system on the device and open it directly.
546 <title>Import File With GPSBabel</title>
548 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel</guimenuitem></menuchoice>
551 Other formats can be imported that are supported by GPSBabel.
554 You need to select the file <emphasis>and</emphasis> the type of the file that is going to be opened,
555 since there is no automatic detection of the file kind.
560 <title>OSM Traces</title>
562 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>OSM Traces</guimenuitem></menuchoice>
565 See <xref linkend="osm_dl"/> section for more information.
570 <title>My OSM Traces</title>
572 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>My OSM Traces</guimenuitem></menuchoice>
575 See <xref linkend="osm_my_dl"/> section for more information.
580 <title>From Geotagged Images</title>
582 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Geotagged Images</guimenuitem></menuchoice>
583 Enables automatic creation of waypoints from geotagged images.
586 This menu opens a dialog to select such image files.
587 If the image files have geotag information in them, then a <xref linkend="TrackWaypoint"/> layer with named waypoints positioned at the location of each image with a thumbnail of that image is created.
592 <title>From Wikipedia Waypoints</title>
594 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Wikipedia Waypoints</guimenuitem></menuchoice>
597 This gets <emphasis>interesting</emphasis> points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary.
602 <title>From Routing</title>
604 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Directions</guimenuitem></menuchoice>
607 This gets a route from given directions.
612 <title>From URL</title>
614 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From URL</guimenuitem></menuchoice>
617 This gets a file from the entered URL.
618 File formats that can be opened are those supported by GPSBabel.
622 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.
628 <title>Import GeoJSON File</title>
630 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import GeoJSON File</guimenuitem></menuchoice>
633 This uses the program <ulink url="https://github.com/tyrasd/togpx">togpx</ulink> to load .geojson files.
634 If the program is not detected on your system, then this option will not be available.
635 See <ulink url="https://www.npmjs.org/package/togpx">here</ulink> for the installation method.
638 The current version (1.4.4) of GPSBabel does not support the <ulink url="http://geojson.org/">GeoJSON</ulink> file format.
642 </section> <!-- End Acquire -->
644 <section><title>Print</title>
646 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Print</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Print</guibutton>.
649 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
650 cross hairs and the scale.
653 It uses a standard system print dialog using an image the size of the current viewport in pixel terms.
654 On the <emphasis>Image Settings</emphasis> you can move the image around the page and scale the image up / or down.
658 <section><title>Generate Image File</title>
660 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Image File</guisubmenu></menuchoice> menu only.
663 Allows generation of larger (pixel) area images than the standard Print method above.
664 From the generated image you can use the facilities of the <application>Operating System</application> to print the image
665 or perform other actions.
668 You should have previously downloaded the tile images for the chosen zoom level,
669 otherwise the image produced will have missing sections.
673 Using large areas takes some time to process and due to the method used it may run out of memory to complete the operation.
674 Unfortunately under <trademark>Windows</trademark> systems it can not detect this failure and may crash the program.
675 So the maximum size is dependent on the capabilities of your system.
676 For instance the largest successful image generated on my (RN) Debian system is a pixel area of 20,000 x 20,000.
681 <section><title>Generate Directory of Images</title>
683 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Directory of Images</guisubmenu></menuchoice> menu only.
687 This is only available in UTM mode.
692 </section> <!-- End File Types -->
694 <section><title>Layers</title>
697 Layers supported by &appname; are:
700 <listitem><para><xref linkend="Aggregate"/></para></listitem>
701 <listitem><para><xref linkend="TrackWaypoint"/></para></listitem>
702 <listitem><para><xref linkend="GPS"/></para></listitem>
703 <listitem><para><xref linkend="DEM"/></para></listitem>
704 <listitem><para><xref linkend="Coordinate"/></para></listitem>
705 <listitem><para><xref linkend="Maps"/></para></listitem>
706 <listitem><para><xref linkend="GeoRef"/></para></listitem>
709 For each layer there are a few standard options:
712 <listitem><para>Properties - Layer setup / configuration settings</para></listitem>
713 <listitem><para>Cut</para></listitem>
714 <listitem><para>Copy</para></listitem>
715 <listitem><para>Paste</para></listitem>
716 <listitem><para>Delete</para></listitem>
717 <listitem><para>Visibility - This checkbox on the Layers Panel controls whether the layer is shown in the viewport or not</para></listitem>
720 The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected:
723 <listitem><para>Standard keys: <keycap>Ctrl+x|c|v</keycap></para></listitem>
724 <listitem><para>Main menu <guimenuitem>Edit</guimenuitem></para></listitem>
725 <listitem><para>From the right click menu</para></listitem>
726 <listitem><para>Buttons at the bottom of the Layers Panel</para></listitem>
729 Default values used for each layer's properties can be altered via the <menuchoice><guimenu>Edit</guimenu><guisubmenu>Layer Defaults</guisubmenu></menuchoice> menu options.
732 See the individual section for detail about each layer.
736 <section id="TrackWaypoint" xreflabel="TrackWaypoint"><title>TrackWaypoint Layer</title>
738 TrackWaypoint layers display GPS data (tracks, routes and waypoints).
740 <para>One way to create new waypoints is to copy a
741 latitude/longitude coordinate pair, such as the one shown on most
742 geocaches, and paste it into an active TrackWaypoint layer. &appname; can
743 automatically recognize several variations of the lat/lon format.
746 By right-clicking on tracks, routes or waypoints in the <xref linkend="gc_layers_panel"/>, you can access many commands on them.
747 You can easily find a specific track, route or waypoint by expanding the appropriate containing Tracks, Routes or Waypoints sublayer in the
748 layers panel to show all the individual items and then typing the name of the track, route or waypoint.
752 The containing Tracks, Routes or Waypoints sublayers are only shown when items of that type exist.
753 To start creating them enter into a create mode via either the <guibutton>Create</guibutton> toolbar commands or the <guimenuitem>New</guimenuitem> menu commands.
757 The sublayers also offer right click menu options.
758 These are the same as those available at the TrackWaypoint level, but only those that relate to the sublayer type.
762 By default routes are coloured red. Tracks are automatically assigned a spread of colours.
766 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.
767 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).
770 <section><title>Layer Operations</title>
772 The layer has a context menu with several operations.
775 <section><title>View Layer</title>
777 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).
781 <section><title>View</title>
783 <section id="track_view_all"><title>View All Tracks</title>
785 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).
789 <section id="route_view_all"><title>View All Routes</title>
791 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).
795 <section id="wp_view_all"><title>View All Waypoints</title>
797 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).
803 <section><title>Goto Center of Layer</title>
805 This will automatically move the viewport to see the whole layer (i.e. tracks, routes and waypoints). It does not adjust the zoom level.
809 <section id="wp_goto"><title>Goto Waypoint</title>
811 This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it.
815 Note this search is not very clever and only finds exact matches.
816 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.
821 <section><title>Export Layer</title>
823 The layer (all tracks, routes and waypoints) can be exported to following file formats:
830 <para>GPSPoint</para>
833 <para>GPSMapper</para>
836 <para>Google's KML</para>
839 <para>Any GPSBabel <ulink url="http://www.gpsbabel.org/capabilities.html">File Formats</ulink></para>
842 <para>GeoJSON. Via the program <ulink url="https://github.com/mapbox/togeojson">togeojson</ulink></para>
843 <para>This option will not be available if the program is not detected on your system.
844 See <ulink url="https://www.npmjs.org/package/togeojson">here</ulink> for the installation method.</para>
848 Version1.1+: An individual track can be exported to a GPX file via the track menu.
852 <section id="finish_track"><title>Finish Track or Route</title>
854 Selecting this option ends the creation of that individual track or route.
858 This is only available when a track or route is being created by the <xref linkend="track_create"/> or <xref linkend="route_create"/> tools.
863 <section><title>New</title>
864 <section id="new_wp"><title>New Waypoint</title>
866 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.
869 <section id="new_track"><title>New Track</title>
871 This turns on the <xref linkend="track_create"/> tool.
874 <section id="new_route"><title>New Route</title>
876 This turns on the <xref linkend="route_create"/> tool.
881 <section><title>Geotag Images</title>
883 This starts the Geotagging Images dialog against all tracks in the layer.
884 See <link linkend="geotagging">Geotagging</link> for further detail.
888 <section><title>Acquire</title>
890 This offers the same choice from <xref linkend="acquire"/> methods as on the <guimenu>File</guimenu> menu.
891 However when invoked from here, the results will be stored in this layer (instead of creating a new one).
895 <section><title>Upload</title>
897 <section id="gps_upload"><title>Upload to GPS</title>
899 This opens a dialog to select the GPS Device and port to which the layer information will be transferred.
902 The types of GPS information (tracks, routes or waypoints) to be transferred can be selected.
905 Tracks, Routes or Waypoints that are invisible will not be transferred.
909 <section id="osm_upload" xreflabel="Upload To OSM" ><title>Upload To OSM</title>
911 This opens a dialog to upload all tracks and waypoints to <ulink url="http://openstreetmap.org/">OpenStreetMap</ulink> traces.
912 Useful if you are an OpenStreetMap contributor (you will need an OpenStreetMap account), these details can be stored in &appname; <xref linkend="prefs_osm"/>
915 &appname; 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.
919 The password is transferred <emphasis role="bold">unencrypted</emphasis> in every request sent to the OpenStreetMap server. This is due to the use of OpenStreetMap's basic authentication method.
921 <para>Currently &appname; does not support the <ulink url="http://oauth.net/">OAuth</ulink> mechanism.</para>
927 <section><title>Delete</title>
928 <para>Offers deletion of various parts of a TrackWaypoint layer:</para>
929 <section id="delete_all_tracks"><title>Delete All Tracks</title>
930 <para>Deletes all the tracks in this layer.</para>
932 <section id="delete_selection_tracks"><title>Delete Tracks from Selection</title>
933 <para>Opens a dialog with list of all the tracks from this layer to choose the ones to delete.</para>
935 <section id="delete_all_routes"><title>Delete All Routes</title>
936 <para>Deletes all the routes in this layer.</para>
938 <section id="delete_selection_routes"><title>Delete Routes from Selection</title>
939 <para>Opens a dialog with list of all the routes from this layer to choose the ones to delete.</para>
941 <section id="delete_all_waypoints"><title>Delete All Waypoints</title>
942 <para>Deletes all the waypoints in this layer.</para>
944 <section id="delete_selection_waypoints"><title>Delete Waypoints from Selection</title>
945 <para>Opens a dialog with list of all the waypoints from this layer to choose the ones to delete.</para>
949 <section><title>Filter</title>
950 <section><title>Simplify All Tracks</title>
952 This opens dialog to request the number of points each track will be simplified using <application>GPSBabel</application>. 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.
955 <section><title>Compress Tracks</title>
957 Enables compression of tracks and routes via <application>GPSBabel</application>'s <emphasis>Crosstrack</emphasis> simplify method.
958 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.
959 It is expressed a distance in units as specified by the <xref linkend="prefs"/> distance option.
960 Thus a higher value will remove more points.
961 The result is put into a new layer.
964 <section><title>Remove Duplicate Waypoints</title>
966 Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer.
970 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.
976 <section id="filter_with_track"><title>Filter With <emphasis>Trackname</emphasis></title>
978 This runs <application>GPSBabel</application> on the layer using information from a previously selected track (select via the track menu "Use With Filter" option) with the following command types:
981 <listitem><para>Waypoints Inside This</para></listitem>
982 <listitem><para>Waypoints Outside This</para></listitem>
985 The result is generated in a new Track/Waypoint layer.
989 <section><title>Geotag Images</title>
991 This starts the Geotagging Images dialog using the specific track.
992 See <link linkend="geotagging">Geotagging</link> for further detail.
996 <section><title>List Tracks or Routes</title>
998 Opens a new dialog with the list. As described in the Aggregrate layer <xref linkend="track_list"/>
1002 <section><title>List Waypoints</title>
1004 Opens a new dialog with the list. As described in the Aggregrate layer <xref linkend="waypoint_list"/>
1008 </section><!-- End TRW Layer Options -->
1010 <section><title>Track and Route Sublayer Options</title>
1011 <para>Repeats options available at the TrackWaypoint level, but only those for tracks and routes:</para>
1013 <listitem><para>Finish Track or Route. Same as the layer <link linkend="finish_track">Finish Track or Route</link></para></listitem>
1014 <listitem><para>New Track or Route. Same as the layer <link linkend="new_track">New Track</link> or <link linkend="new_route">New Route</link></para></listitem>
1015 <listitem><para>View All Tracks or Routes. Same as the layer <link linkend="track_view_all">View All Tracks</link> or <link linkend="route_view_all">View All Routes</link></para></listitem>
1016 <listitem><para>Delete All Tracks or Routes. Same as the layer <link linkend="delete_all_tracks">Delete All Tracks</link> or <link linkend="delete_all_routes">Delete All Routes</link></para></listitem>
1017 <listitem><para>Delete Tracks or Routes from Selection. Same as the layer <link linkend="delete_selection_tracks">Delete Tracks from Selection</link> or <link linkend="delete_selection_routes">Delete Routes from Selection</link></para></listitem>
1018 <listitem><para>List Tracks or Routes. Opens a new dialog with the list. As described in the Aggregrate layer <xref linkend="track_list"/></para></listitem>
1020 <para>Also gives other options for handling multiple items:</para>
1022 <listitem><para>Sort. Gives the ability to sort the items in the treeview alphabetically</para></listitem>
1023 <listitem><para>Visibility. Offers options to quickly control the visibility of all items within the sublayer, as per <xref linkend="vis_options"/></para></listitem>
1027 <section xreflabel="Track and Route Properties"><title>Track and Route Properties</title>
1029 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).
1030 Moving the mouse pointer over the graph displays values related to that point along the track.
1031 You can click on these graphs to jump to the point in the track.
1032 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.
1034 <section id='track_properties' xreflabel="Track and Route Properties"><title>Track and Route Properties Tab</title>
1037 <title>Properties Tab: Example</title>
1039 <graphic format="PNG" fileref="figures/Track_properties.png"/>
1044 <section id='track_statistics' xreflabel="Track and Route Statistics"><title>Track and Route Statistics Tab</title>
1047 <title>Statistics Tab: Example</title>
1049 <graphic format="PNG" fileref="figures/Track_statistics.png"/>
1054 <section id='track_elev_graphs' xreflabel="Track Elevation Graph"><title>Track Elevation Graph</title>
1057 <title>Elevation Distance Tab: Example</title>
1059 <graphic format="PNG" fileref="figures/Track_elevation_graph.png"/>
1064 The following colors are used in the elevation-distance graph:
1068 <term><emphasis>Main</emphasis> colour - this is dependent on your Desktop theme - often blue by default</term>
1069 <listitem><para>elevation data in graph</para></listitem>
1074 <para>no elevation data</para>
1080 <para>elevation data from DEM</para>
1093 <section><title>Track and Route Operations</title>
1095 <section><title>Finish Track</title>
1097 Selecting this option ends the creation of the individual track.
1101 This is only available when a track is being created by the <xref linkend="track_create"/> tool.
1106 <section><title>Goto</title>
1108 This centers the viewport on the selected position on the track:
1111 <listitem><para>Startpoint</para></listitem>
1112 <listitem><para>"Center" - the notional center from the bounds of the track</para></listitem>
1113 <listitem><para>Endpoint</para></listitem>
1114 <listitem><para>Version1.1+: Highest Altitude</para></listitem>
1115 <listitem><para>Version1.1+: Lowest Altitude</para></listitem>
1116 <listitem><para>Version1.1+: Maximum Speed (Not Available on Routes)</para></listitem>
1120 <section><title>View</title>
1122 Version1.1+: This centers the viewport on the track and selects the best zoom level to see it.
1126 <section><title>Combine</title>
1127 <section><title>Merge By Time</title>
1129 This operation repeatedly tries to merge the right-clicked track
1130 with tracks in the same TrackWaypoint layer. The tracks which are
1131 merged are those which have at least one trackpoint less than some
1132 threshold time away. This way, if you somehow end up with lots of small
1133 segments (say, caused by turning the GPS on and off) you can merge them
1134 easily into one track.
1138 This is not available on routes as they have no timestamps.
1143 <section><title>Merge With Other Tracks</title>
1145 This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with.
1149 <section><title>Merge Segments</title>
1151 Combines track segments. Effectively removing track segment markers to leave one segment for the whole track.
1155 <section><title>Append Track or Route</title>
1157 Enable joining of a single track to the end of the current track.
1158 This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection.
1163 <section><title>Split</title>
1164 <section><title>Split By Time</title>
1166 This operation will split a single track into segments wherever the
1167 time interval between successive trackpoints is larger than some
1168 threshold. This is useful when processing raw NMEA GPS data, especially
1169 taken over a long time.
1173 This is not available on routes as they have no timestamps.
1178 <section><title>Split By Number of Points</title>
1180 Version1.2+: This operation will split a single track into segments by the number of points specified.
1181 This can be useful with devices which may have limits on the number of points it supports.
1185 <section><title>Split Segments</title>
1187 Splits track segments into new tracks.
1191 This is not available on routes as they do not have route segments.
1196 <section id='trkpt_split' xreflabel="Split at Trackpoint"><title>Split at Trackpoint</title>
1198 Splits the track at the currently selected trackpoint.
1201 The current track will finish at this trackpoint.
1202 A new track will start from a copy of this trackpoint.
1206 This is only enabled when a trackpoint is selected.
1212 <section><title>Insert Points</title>
1215 These options are only enabled when a trackpoint is selected.
1218 <section><title>Insert Point Before Selected Point</title>
1220 Inserts a track point halfway between the previous track point and the current track point.
1221 All track point properties are interpolated between the two points.
1224 <section><title>Insert Point After Selected Point</title>
1226 Inserts a track point halfway between the current track point and the next track point.
1227 All track point properties are interpolated between the two points.
1232 <section><title>Delete Points</title>
1233 <section><title>Delete Selected Point</title>
1235 Deletes the currently selected track point.
1239 This is only enabled when a trackpoint is selected.
1243 <section><title>Delete Points With the Same Position</title>
1245 Deletes subsequent points that have the same position (but have different timestamps).
1248 <section><title>Delete Points With the Same Time</title>
1250 Deletes subsequent points that have the same time stamp (but may have different positions).
1254 This is not available on routes as they have no timestamps.
1261 <section id="transform" xreflabel="Transform"><title>Transform</title>
1263 These options alter the data of trackpoints of a track but not add or remove trackpoints.
1264 And don't seem to fit any other category :)
1266 <section><title>Apply DEM data</title>
1268 If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
1269 Two ways of applying DEM data are offered:
1271 <listitem><para>Keep. Retains the existing elevation data of trackpoints and only those missing an elevation value are set.</para></listitem>
1272 <listitem><para>Overwrite. Elevation data are set on all trackpoints even if they already elevation values.</para></listitem>
1276 <section><title>Smooth Missing Elevation data</title>
1278 In various locations across the world, there are missing DEM values (AKA DEM Holes) from the SRTM data.
1279 This is particularly noticeable in mountainous areas.
1280 Two ways of applying elevation data to trackpoints that do not have elevation values are offered:
1282 <listitem><para>Interpolated. Missing elevation data is interpolated between the previous and next known values.</para></listitem>
1283 <listitem><para>Flat. Elevation data is filled in from the last previously known value.</para></listitem>
1288 <title>Convert to Track or Route</title>
1290 If this is a Route then it will convert it to a Track.
1293 If this is Track then convert it to a Route.
1297 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).
1302 <title>Anonymize Times</title>
1304 Timestamp information of a track can be shifted to be all offset from 1901-01-01.
1307 Thus the timestamps themselves will no longer reveal exactly when a track was taken.
1308 However the relative difference between the timestamps is kept thus one is still able to calculate some properties such as speeds along the track.
1312 This is not available for routes, as they have no timestamps.
1318 <section><title>Export Track as GPX</title>
1320 Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog.
1324 <section><title>Extend Track End</title>
1326 Changes the current tool to add trackpoints to the end of the track.
1330 <section><title>Extend Using Route Finder</title>
1332 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.
1336 <section><title>Upload</title>
1338 <section><title>Upload to GPS</title>
1340 Same as the layer <link linkend="gps_upload">Upload to GPS</link> command, but only applies to the track.
1344 <section><title>Upload to OSM</title>
1346 Same as the layer <link linkend="osm_upload">Upload to OSM</link> command, but only applies to the track.
1352 <section><title>Use With Filter</title>
1354 This selects the track to be used in the <link linkend="filter_with_track">Filter With <emphasis>Trackname</emphasis></link> feature.
1358 This is not available on routes.
1363 <section><title>Edit Trackpoint</title>
1365 This opens the Trackpoint edit dialog. See <xref linkend="Trackpoint_edit"/>.
1369 This is only enabled when a trackpoint is selected.
1374 <section><title>Refine Route...</title>
1376 This function allows to request a Routing Engine in order to refine a given route.
1377 By "refining" we mean computing all real intermediates points between some given major points.
1378 This could be useful to compute a trip giving only the wished important steps.
1382 This is only available on routes.
1387 <section><title>View Google Directions</title>
1389 This option is only available on a track created using the Route Finder tool.
1392 Launch a web browser to see the Google directions page which yielded the route.
1396 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.
1401 </section><!-- End Track Options -->
1403 <section><title>Waypoint Sublayer Options</title>
1404 <para>Repeats options available at the TrackWaypoint level, but only those for waypoints:</para>
1406 <listitem><para>New Waypoint. Same as the layer <link linkend="new_wp">New Waypoint</link></para></listitem>
1407 <listitem><para>View All Waypoints. Same as the layer <link linkend="wp_view_all">View All Waypoints</link></para></listitem>
1408 <listitem><para>Goto Waypoint. Same as the layer <link linkend="wp_goto">Goto Waypoint</link></para></listitem>
1409 <listitem><para>Delete All Waypoints. Same as the layer <link linkend="delete_all_waypoints">Delete All Waypoints</link></para></listitem>
1410 <listitem><para>Delete Waypoints from Selection. Same as the layer <link linkend="delete_selection_waypoints">Delete Waypoints from Selection</link></para></listitem>
1411 <listitem><para>List Waypoints. Opens a new dialog with the list. As described in the Aggregrate layer <xref linkend="waypoint_list"/></para></listitem>
1415 <section><title>Waypoint Properties</title>
1418 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).
1421 If the waypoint has an associated image, then the Geotag information may be updated, either with updating the file's modification timestamp or not.
1422 This can be useful when the waypoint has been moved.
1425 </section><!-- WP Prop END -->
1427 <section><title>Waypoint Operations</title>
1429 <section><title>Goto</title>
1431 This centers the viewport on the selected waypoint.
1435 <section><title>Geotag Images...</title>
1437 This opens the <link linkend="geotagging">Geotag Dialog</link> to allow Geotagging multiple images to the position of this waypoint.
1438 In this circumstance creation of waypoint options are disabled and only the options related to writing the EXIF information are available.
1442 <section><title>Transform</title>
1444 Offers a subset of the track <xref linkend="transform"/> utilities.
1445 Currently only setting the altitude from DEM data methods are available.
1449 <section><title>Visit Webpage</title>
1451 If the waypoint's comment (or description) starts with <literal>http:</literal> then this option is available and allows launching a web browser to go to the webpage.
1455 <section><title>Visit Geocache Webpage</title>
1457 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.
1461 <section><title>New Waypoint</title>
1463 Same as the layer <link linkend="new_wp">New Waypoint</link>.
1467 </section><!-- WP END -->
1469 <section id="geotagging" xreflabel="Geotagging"><title>Version1.3+: Geotag Images</title>
1471 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.
1474 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.
1478 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.
1482 Various options allow control of how the geotagging process is performed:
1485 <listitem><para>Images - Add the images used for geotagging</para></listitem>
1486 <listitem><para>Create Waypoints</para></listitem>
1487 <listitem><para>Overwrite Existing Waypoints</para></listitem>
1488 <listitem><para>Write EXIF</para></listitem>
1489 <listitem><para>Overwrite Existing GPS Information</para></listitem>
1490 <listitem><para>Interpolate Between Track Segments</para></listitem>
1491 <listitem><para>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.</para></listitem>
1492 <listitem><para>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.</para></listitem>
1496 </section><!-- TRW Layer END -->
1498 <section id="GPS" xreflabel="GPS"><title>GPS Layer</title>
1500 The GPS layer is responsible for uploading and downloading GPS data
1501 from a GPS device. It also is responsible for realtime GPS tracking.
1502 Expand the GPS layer in the layers panel to see the two <xref linkend="TrackWaypoint"/> layers it
1503 uses for uploading and downloading. To upload, download, or use
1504 realtime tracking, right-click the GPS layer and click the appropiate
1508 <section><title>Download</title>
1510 To download data from the GPS, right-click the GPS layer and click <guimenuitem>Download from GPS</guimenuitem>.
1514 <section><title>Upload</title>
1516 To upload data to the GPS, first populate the GPS Upload child
1517 layer of the GPS layer (either by creating waypoints/tracks/routes in it, or
1518 copying and pasting or dragging waypoints/tracks/routes from another layer).
1519 Then right-click the GPS layer and click <guimenuitem>Upload to GPS</guimenuitem>.
1523 <section><title>Realtime Tracking</title>
1525 You must set up gpsd correctly or use a GPSD server and put the
1526 correct information in the GPS layer properties dialog. Then right-click
1527 the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
1531 <section><title>Empty <emphasis>Item</emphasis></title>
1533 There are several options to quickly delete a subsection of data:
1536 <listitem><para>Empty Realtime</para></listitem>
1537 <listitem><para>Empty Upload</para></listitem>
1538 <listitem><para>Empty Download</para></listitem>
1539 <listitem><para>Empty All</para></listitem>
1543 </section><!-- End GPS -->
1545 <section id="DEM" xreflabel="DEM"><title>DEM (Digital Elevation Model) Layer</title>
1547 This layer provides elevation data from the <ulink url="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission (SRTM)</ulink>
1550 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]
1553 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.
1556 The current data server is: <ulink url="http://dds.cr.usgs.gov/srtm/version2_1/">NASA STRM 2.1</ulink>.
1559 ATM &appname; 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 <application>curl</application> or <application>wget</application> to download them for an area.
1563 Using many DEMs is CPU/memory intensive. Depending on your computer's capability, &appname; 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, &appname; may be automatically stopped by the "<ulink url="http://en.wikipedia.org/wiki/Out_of_memory/">OOM</ulink> Killer"
1567 </section><!-- End DEM -->
1570 <section id="Maps" xreflabel="Maps"><title>Maps Layer</title>
1572 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).
1575 Some maps are continually improving over time (e.g. OpenStreetMap) thus &appname; employs a caching mechanism to avoid redownloading data (see <xref linkend="mapcache"/>).
1576 However a forced refresh for the current view can be made via the <guilabel>Reload All Onscreen Maps</guilabel> option or <keycap>Ctrl+F5</keycap>.
1578 <formalpara><title>Online Map Tile Providers</title>
1580 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.
1581 Inbuilt maps include various <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> ones and more:
1585 <listitem><para>Bing Bird's Eye (Aerial) Maps (&appname; Version1.2+)</para></listitem>
1586 <listitem><para>OpenStreetMap (Mapquest) - This is the default (&appname; Version1.3+)</para></listitem>
1587 <listitem><para>OpenStreetMap (Mapnik)</para></listitem>
1588 <listitem><para>OpenStreetMap (Cycle)</para></listitem>
1589 <listitem><para>OpenStreetMap (Transport) (&appname; Version1.3+)</para></listitem>
1590 <listitem><para>OpenStreetMap (Humanitarian) (&appname; Version1.5+)</para></listitem>
1591 <listitem><para>NASA BlueMarble</para></listitem>
1595 &appname; can be configured to handle additional online map resources. See <xref linkend="extend_viking"/> for further detail.
1598 <formalpara><title>Offline Map Tilesets</title>
1600 Some map types supported are for on disk tile formats:
1605 <para>On Disk OSM Tile Format</para>
1606 <para>This is equivalent to any map set with <emphasis>OSM</emphasis> Cache Layput.</para>
1608 <listitem><para><ulink url="https://github.com/mapbox/mbtiles-spec">MBTiles File</ulink></para></listitem>
1609 <listitem><para><ulink url="http://wiki.openstreetmap.org/wiki/Meta_tiles">OSM Metatiles</ulink></para></listitem>
1612 Of course you need to have acquired or generated these tilesets yourself.
1615 <section><title>Map Layer Properties</title>
1617 Configurable properties:
1621 <para>Map Type. The kind of map this layer displays.</para>
1622 <note><para>Map types are dependent on the current <xref linkend="projection"/> mode.</para></note>
1624 <listitem><para>Maps Directory. Not applicable for MBTiles Map type since it is a single file.</para></listitem>
1625 <listitem><para>Cache Layout. Viking or OSM. See <xref linkend="mapcache"/>. Only applies to maps from online tile providers.</para></listitem>
1626 <listitem><para>Map File. Ony applicable for MBTiles Map type since it is a single file.</para></listitem>
1628 <para>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.</para>
1629 <para>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).</para>
1631 <listitem><para>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.
1632 e.g. perhaps in case a current map rendering is broken.</para></listitem>
1633 <listitem><para>Autodownload Only Gets Missing Maps. Using this option avoids attempting to update already acquired tiles.
1634 This can be useful if you want to restrict the network usage, without having to resort to manual control. Only applies when <emphasis>Autodownload Maps</emphasis> is on.</para></listitem>
1635 <listitem><para>Zoom Level. Determines the method of displaying map tiles for the current zoom level.
1636 <emphasis>Viking Zoom Level</emphasis> 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.</para></listitem>
1638 </section><!-- Map Prop END -->
1641 <section><title>Layer Operations</title>
1642 <section><title>Download Missing Onscreen Maps</title>
1644 This requests map tiles for areas of the viewport that do not currently have one.
1648 <section><title>Download New Onscreen Maps</title>
1650 This requests map tiles only if the maps are older than the Tile Age preference.
1654 <section><title>Reload All Onscreen Maps</title>
1656 Force a refresh of all visible map tiles.
1660 <section><title>Download Maps in Zoom Levels</title>
1662 This opens a dialog to enable requesting the download of maps for the region in the viewport over a specified number of zoom levels.
1663 The download method type can be specified to help limit the number of requests.
1667 There are some inbuilt limits to prevent downloading large amounts of map tiles.
1670 Please respect the usage policy of the tile set provider.
1671 Such as <ulink url="http://wiki.openstreetmap.org/wiki/Tile_usage_policy"><citetitle>OSM Tile Usage Policy</citetitle></ulink>.
1676 <title>Maps Download Dialog: Example</title>
1678 <graphic format="PNG" fileref="figures/Maps_download_region_dialog.png"/>
1686 </section><!-- End Maps -->
1688 <section id="Aggregate" xreflabel="Aggregate"><title>Aggregate Layer</title>
1690 This layer is a container layer to hold other layers. There is always an initial and controlling <emphasis>Top Layer</emphasis> that can not be removed or renamed.
1693 This layer type is useful for grouping other layers, especially <xref linkend="TrackWaypoint"/> layers, in whatever categories are relevant to you: such as by activity, location or date.
1694 Here are some suggestions:
1696 <listitem><para>Hiking</para></listitem>
1697 <listitem><para>Mountain Biking</para></listitem>
1698 <listitem><para>Road Cycling</para></listitem>
1699 <listitem><para>Car Trips</para></listitem>
1700 <listitem><para>Sailing</para></listitem>
1701 <listitem><para>Holidays</para></listitem>
1702 <listitem><para>UK Points of Interest</para></listitem>
1703 <listitem><para>USA Points of Interest</para></listitem>
1704 <listitem><para>etc...</para></listitem>
1708 Thus one can have a list of all your tracks, but groups can be shown or not using the relevant layers visibility checkbox.
1711 <section><title>Layer Operations</title>
1713 The following are available on Aggregate Layers:
1717 <section><title>New Layer</title>
1719 Add a new layer of the selected type.
1723 <section id="sort_items" xreflabel="Sort"><title>Sort</title>
1725 The list within the treeview can be sorted.
1728 Currently alphabetical (A to Z or Z to A) sorts are available, since only the name can be seen in the treeview.
1732 <section id="track_list" xreflabel="Track List"><title>Track List</title>
1734 Selecting this opens a dialog listing all the tracks in a table along side statistics such as track length and maximum speed.
1735 Each column header is clickable and will reorder the list according to that particular column.
1738 This table may be invoked from a variety of different layer levels and will then list only the relevant tracks (and/or routes).
1740 <listitem><para>Aggregate Layer: Lists Tracks and Routes and the TrackWaypoint Layer they are in</para></listitem>
1741 <listitem><para>TrackWaypoint Layer: Lists Tracks and Routes</para></listitem>
1742 <listitem><para>TrackWaypoint Track sublayer: Lists Tracks only</para></listitem>
1743 <listitem><para>TrackWaypoint Route sublayer: Lists Routes only</para></listitem>
1748 <title>Track List Dialog: Example</title>
1751 This is showing all tracks and routes (although there are no actual routes here!) in multiple TrackWaypoint layers, that has been sorted by height.
1752 Note that routes will not have timestamps or speeds, but may have elevations and should have some distance!
1756 <graphic format="PNG" fileref="figures/LayersTracksList.png"/>
1761 Hovering the mouse over an entry will show a tooltip of the comment or description if it is available.
1764 Each entry in the track list can be selected and on mouse right click offers these options:
1766 <listitem><para>View. Move the viewport to the area of the item and highlight it.</para></listitem>
1767 <listitem><para>Statistics. Opens the Properties dialog on the <xref linkend="track_statistics"/> tab. Note this will close the track list dialog.</para></listitem>
1772 <section id="waypoint_list" xreflabel="Waypoint List"><title>Waypoint List</title>
1774 Selecting this opens a dialog listing all the waypoints to give a overview of the waypoint information.
1775 Each column header is clickable and will reorder the list according to that particular column.
1778 This table may be invoked from a variety of different layer levels and will then list only the relevant waypoints.
1780 <listitem><para>Aggregate Layer: Lists Waypoints and the TrackWaypoint Layer they are in</para></listitem>
1781 <listitem><para>TrackWaypoint Layer: : Lists Waypoints</para></listitem>
1782 <listitem><para>TrackWaypoint Waypoint sublayer: Lists Waypoints</para></listitem>
1787 <title>Waypoint List Dialog: Example</title>
1790 This was invoked on a TrackWaypoint layer and shows all waypoints from that single layer. It has been sorted by the symbols.
1794 <graphic format="PNG" fileref="figures/WaypointsList.png"/>
1799 Hovering the mouse over an entry will show a tooltip of the description if it is available.
1802 Each entry in the list can be selected and on mouse right click offers these options:
1804 <listitem><para>View. Move the viewport to the area of the item and highlight it.</para></listitem>
1805 <listitem><para>Properties. This will open the properties dialog. Note this will close the waypoint list dialog.</para></listitem>
1806 <listitem><para>Show Picture. If enabled, this will open the associated image in an external Image Viewer program.</para></listitem>
1811 <section id="vis_options" xreflabel="Visibility Options"><title>Visibility Options</title>
1813 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.
1815 <listitem><para>Show All. Ensures all items are set to be visible.</para></listitem>
1816 <listitem><para>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.</para></listitem>
1817 <listitem><para>Toggle. Inverts the visibility status of each item.</para></listitem>
1822 <section id="search_date" xreflabel="Search by Date"><title>Search by Date</title>
1824 This opens calendar dialog to select a date to search by within this Aggregate layer.
1825 The first item that is found on that date will be selected.
1826 Tracks are searched first in preference over waypoints.
1830 </section><!-- End Agg -->
1832 <xi:include href="georef_layer.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
1834 <section id="Coordinate" xreflabel="Coordinate"><title>Coordinate Layer</title>
1836 This layer is allows drawing of grid lines on the viewport.
1838 </section><!-- End Coord -->
1841 <section id="tools" xreflabel="Tools"><title>Tools</title>
1843 &appname;'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.
1846 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.
1849 <keycap>Scroll</keycap>: zoom in and out keeping the mouse over same location
1852 <keycap>Ctrl-scroll</keycap>: pan north-south (also <keycap>Ctrl-up</keycap>, <keycap>Ctrl-down</keycap>)
1855 <keycap>Shift-scroll</keycap>: pan east-west (also <keycap>Ctrl-left</keycap>, <keycap>Ctrl-right</keycap>)
1858 <keycap>Ctrl-shift-scroll</keycap>: zoom in and out, without changing the center (also <keycap>Ctrl+</keycap>, <keycap>Ctrl-</keycap> [*not* KeyPad +/-])
1861 <keycap>Middle-click</keycap>: make the clicked point on the map the center
1864 <keycap>Middle-click</keycap> and drag: pan
1867 <section><title>Pan</title>
1869 This is the default mode of operation for &appname;.
1872 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mover_22.png"/></guiicon>
1875 Pan moves the viewpoint. A single click centers the viewport at that point, whereas click and drag dynamically moves the view around.
1876 This is the default tool.
1879 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+P</keycap>
1882 Double clicking the left mouse button will zoom the map in.
1883 <keycap>Shift</keycap> + double clicking the left mouse button will zoom the map out.
1884 Double clicking the right mouse button will also zoom the map out.
1888 <section><title>Zoom</title>
1890 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/zoom_18.png"/></guiicon>
1893 Zooms in and out on the clicked part of the map or by the selected area.
1896 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+Z</keycap>
1899 <keycap>Ctrl</keycap> + left or right click: Zoom in/out and center the map on the clicked location
1902 <keycap>Shift</keycap> (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.
1905 <keycap>Shift</keycap> + left click button: Jump Zoom In by up to factor of 3 standard zooms.
1908 <keycap>Shift</keycap> + right click button: Jump Zoom Out by up to factor of 3 standard zooms.
1912 <section><title>Ruler</title>
1914 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/ruler_18.png"/></guiicon>
1917 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.
1918 A second click will <emphasis>freeze</emphasis> the ruler at that point.
1921 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+U</keycap>
1925 <section id="select" xreflabel="Select"><title>Version1.1+: Select</title>
1927 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/select_18.png"/></guiicon>
1930 The select tool allows one to choose any waypoint or track by clicking on it (or reasonably near) in the viewpoint.
1933 ATM to select a track one must actually click on a trackpoint, which is also selected.
1936 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+S</keycap>
1940 <section><title>TrackWaypoint Layer Tools</title>
1942 You must have a <xref linkend="TrackWaypoint"/> Layer selected to use these tools.
1944 <section id="createwptool" xreflabel="Create Waypoint"><title>Create Waypoint</title>
1946 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addwp_18.png"/></guiicon>
1949 Left click will open the new waypoint dialog using the specified position.
1953 <section id="track_create" xreflabel="Create Track"><title>Create Track</title>
1955 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon>
1958 Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track.
1959 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1960 Right click or <keycap>Backspace</keycap>: undo one point.
1963 Double click or <keycap>Escape</keycap>: to finish track creation.
1964 Finishing the track is also available via the right click <xref linkend="TrackWaypoint"/> and track menus.
1967 One must finish the current track to be able to create another track.
1971 <section id="route_create" xreflabel="Create Route"><title>Create Route</title>
1973 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/vik_new_route_18.png"/></guiicon>
1976 This operates in exactly the same way as the <link linkend="track_create">Create Track</link> above.
1979 One must finish the current route to be able to create another route.
1982 One can switch between the <link linkend="route_create">Create Route</link> and <link linkend="route_finder">Route Finder</link> tools while editing routes.
1986 <section id="route_finder" xreflabel="Route Finder"><title>Create Route Using the Route Finder</title>
1988 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/route_finder_18.png"/></guiicon>
1991 Requires an internet connection.
1992 Left click to create a new trackpoint.
1993 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.
1994 Right click or <keycap>Backspace</keycap>: remove the last added route.
1997 <keycap>Escape</keycap>: to finish route creation.
1998 Finishing the track is also available via the right click <xref linkend="TrackWaypoint"/> and track menus.
2001 One must finish the current route to be able to create another route.
2004 One can switch between the <link linkend="route_create">Create Route</link> and <link linkend="route_finder">Route Finder</link> tools while editing routes.
2008 <section><title>Edit Waypoint</title>
2010 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edwp_18.png"/></guiicon>
2013 Left Click/drag: select/move a waypoint.
2014 If <keycap>Ctrl</keycap> is held at the same time, it will jump the waypoint position to a nearby existing trackpoint.
2015 If <keycap>Shift</keycap> is held at the same time, it will jump the waypoint position to a nearby existing waypoint.
2017 <para>Right-click on waypoint: opens a menu with waypoint actions (the
2018 same menu accessed by right-clicking the waypoint in the layers panel)
2022 <section><title>Edit Trackpoint</title>
2024 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edtr_18.png"/></guiicon>
2027 Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint.
2028 Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint.
2029 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
2031 <section id="Trackpoint_edit" xreflabel="Edit Trackpoint Dialog"><title>Edit Trackpoint Dialog</title>
2033 Editing options in the Trackpoint Edit dialog include:
2035 <listitem><para>Edit the trackpoint name</para></listitem>
2036 <listitem><para>Changing raw lat/long position and altitude</para></listitem>
2037 <listitem><para>Forward (go to the next trackpoint)</para></listitem>
2038 <listitem><para>Back (go to the previous trackpoint)</para></listitem>
2039 <listitem><para>Delete</para></listitem>
2040 <listitem><para>Insert. Inserts a point halfway to next trackpoint</para></listitem>
2041 <listitem><para>Split. <xref linkend="trkpt_split"/></para></listitem>
2045 Several fields are read only for reference purposes, values are shown if the trackpoint has such information:
2047 <listitem><para>Time.</para></listitem>
2048 <listitem><para>Speed and course.</para></listitem>
2049 <listitem><para>'Between' values: Speed, Time Difference and Distance Difference. When moving between trackpoints (via the Back and Forward buttons) these values are calculated.</para></listitem>
2050 <listitem><para>GPS precision factors.</para></listitem>
2055 <title>Trackpoint Edit Dialog: Example</title>
2057 <graphic format="PNG" fileref="figures/Trackpoint_edit_dialog.png"/>
2060 One must have been going downhill here to get a reasonable speed by bicycle!
2065 <section><title>Show Picture</title>
2067 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/showpic_18.png"/></guiicon>
2070 Opens an image viewer with the picture associated with the waypoint.
2071 By default this uses the default system image viewer.
2072 For Linux you can override this with the setting in the <xref linkend="prefs_external"/>
2078 <section id="georef_tools"><title>Georef Map Layer Tools</title>
2080 You must have a <xref linkend="GeoRef"/> Map Layer selected to use these tools.
2082 <section><title>Georef zoom</title>
2084 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geozoom_18.png"/></guiicon>
2086 <para>Changes the zoom level of the georeferenced map and changes the
2087 &appname; zoom level accordingly. Useful if you are trying to match GPS
2088 data to a georeferenced map.
2092 <section><title>Georef move</title>
2094 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geomove_18.png"/></guiicon>
2097 Drag to move the georeferenced map.
2102 <section id="map_tool_dl" xreflabel="Map Download"><title>Map Download</title>
2104 You must have a <xref linkend="Maps"/> Layer selected to use this.
2107 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mapdl_18.png"/></guiicon>
2110 Click to download a single tile. Drag to download tiles in the dragged rectangle area.
2113 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.
2114 The possible methods to redownload one or more tiles are:
2118 <listitem><para>Bad - Only if the tile is corrupt in some way or missing, then this will download a new copy</para></listitem>
2119 <listitem><para>New - Refresh the tile according to the local map cache and if server has a newer version</para></listitem>
2120 <listitem><para>All - Redownload the tile</para></listitem>
2123 <formalpara><title>Map Tile Information</title>
2125 By right clicking on viewport and selecting <guimenu>Show Tile Information</guimenu> you can see the tile properties of this location for the current map layer and current zoom level.
2126 This includes the remote source URL for the tile and the cached version on the local filesystem with timestamp details.
2131 <title>Map Tile Info Dialog: Example</title>
2133 <graphic format="PNG" fileref="figures/map_tile_info_dialog.png"/>
2136 This is using MapQuest at &appname; zoom level 128 over the Isle of Wight, UK.
2140 <section><title>DEM Download</title>
2142 You must have a <xref linkend="DEM"/> Layer selected to use this.
2145 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/demdl_18.png"/></guiicon>
2148 Click to download and import a DEM file.
2150 <formalpara><title>DEM File Information</title>
2152 By right clicking on viewport and selecting <guimenu>Show DEM File Infomation</guimenu> you can see the file properties of the DEM file for this location.
2153 This includes the remote source URL for the file and the cached version on the local filesystem with timestamp details.
2158 <title>DEM File Info Dialog: Example</title>
2160 <graphic format="PNG" fileref="figures/DEM_file_info_dialog.png"/>
2163 This is for block 51N, 003W - covering Bristol in the UK.
2167 <section><title>Webtools</title>
2169 Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
2172 Jumping from &app; to such service can become annoying.
2175 &appname; allows you to open such service directly at the position currently viewed in &app;.
2178 This feature is called <guilabel>Webtools</guilabel>. It is also known as External Tools.
2184 <!-- Preferences -->
2185 <section id="prefs" xreflabel="Preferences"><title>Preferences</title>
2186 <section><title>General</title>
2187 <section><title>Localisation</title>
2188 <para>You can select units displayed by &appname; to best fit your usage.</para>
2190 <title>Properties dialog: units part</title>
2192 <graphic format="PNG" fileref="figures/properties_units.png"/>
2195 <para>Concerning degrees, you can select the way to display them:
2198 <term>DDD</term><listitem><para>decimal degree</para></listitem>
2201 <term>DMM</term><listitem><para>partial sexagesimal display: degrees, minutes and decimal part of minutes</para></listitem>
2204 <term>DMS</term><listitem><para>sexagesimal display: degrees, minutes and seconds</para></listitem>
2209 <title>Properties dialog: degree display options</title>
2211 <graphic format="PNG" fileref="figures/properties_degree.png"/>
2215 <section><title>Waypoint Icon Size</title>
2216 <para>An option exists to control the icon (symbol) size used for waypoints
2219 <section><title><emphasis>Home</emphasis> Default Location: Latitude and Longitude</title>
2220 <para>You can set the <emphasis>Home</emphasis> location directly by inputting the latitude and longitude in decimal degrees.
2223 <section><title>Time Display</title>
2224 <para>This controls the reference timezone that times are shown in.</para>
2225 <para><emphasis>Locale</emphasis> is the current user's system preference. This was how all times were shown up to version 1.5.</para>
2226 <para><emphasis>World</emphasis> will attempt to determine the timezone at an object's position.</para>
2227 <para><emphasis>UTC</emphasis> enforces this standard timezone.</para>
2229 <section><title>Tile's age</title>
2230 <para>This age is used to decided wether or not a new request to tile server must be done.
2232 <para>Changing this value, you will increase or decrese the network load.</para>
2234 <section><title>Default map layer directory</title>
2235 <para>This property sets the default directory of the tiles cache.
2236 This value is used when you create a new map layer.
2238 <para>You are still able to change this value in each map layer properties.</para>
2240 <section><title>Map Cache Memory Size</title>
2241 <para>This controls the amount of maps that are stored in memory, rather than having to reread from disk.
2242 Generally if you have a system with lots of memory it's recommended to increase this value.
2247 <section id="prefs_external" xreflabel="Export/External Preferences"><title>Export/External</title>
2248 <section><title>KML Export Units</title>
2249 <para>Allows setting the units used when saved as the KML file type, such as Metric or Statue units</para>
2251 <section><title>GPX Track Order</title>
2253 Other software may display tracks in a particular order (often the order saved into the file).
2254 This allows you to control the order they are saved when exporting to a GPX file.
2257 <section><title>GPX Waypoint Symbols</title>
2258 <para>Some GPS devices require waypoint symbols to be in a particular case.</para>
2259 <para>E.g. On a Garmin Oregon 450 they must be in <emphasis>Title Case</emphasis> to be recognized.</para>
2261 <section><title>Image Viewer (Not Windows)</title>
2262 <para>Allows setting the program used to view images associated with Waypoints.</para>
2263 <para>By default this is set to <application>xdg-open</application> which should open the system's default image viewer, however this can be overridden with this setting.</para>
2264 <para>Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.</para>
2266 <section><title>External GPX programs</title>
2267 <para>Allows setting the programs invoked via the <xref linkend="TrackWaypoint"/> Layer menu <menuchoice><guimenu>Export Layer</guimenu><guisubmenu>Open With 'program'</guisubmenu></menuchoice></para>
2268 <para>Two options are given so that it can be configured for various uses such as:</para>
2270 <listitem><para>An OSM editor (default)</para></listitem>
2271 <listitem><para>Some other user defined program</para></listitem>
2274 <section><title>GPSBabel</title>
2275 <para>This allows setting the specific location of GPSBabel.</para>
2276 <para>&appname; will need to be restarted for this setting to take effect.</para>
2278 <section><title>Auto Read World Files</title>
2279 <para>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.</para>
2280 <para>The associated file is based on filename patterns; e.g. if the image is <filename>filename.jpg</filename> - then the world file may be <filename>filename.jpgw</filename> or <filename>filename.jgw</filename></para>
2284 <section id="prefs_osm" xreflabel="OpenStreetMap Traces Preferences"><title>OpenStreetMap Traces</title>
2285 <section><title>OSM Username + Password</title>
2286 <para>Store your OSM details here, so that you don't need to enter it in every time in the <xref linkend="osm_upload"/> procedure.</para>
2289 Your OSM password will be stored in plain text.
2295 <section id="prefs_routing" xreflabel="Routing Preferences"><title>Routing</title>
2296 <section><title>Routing engine</title>
2297 <para>You can select the routing engine used by default, ie by features that do not propose a live selection, like <xref linkend="route_finder"/>.</para>
2301 <section id="prefs_startup" xreflabel="Startup Preferences"><title>Startup</title>
2302 <para>Naturally since these preferences effect the startup, the values will not be used until &appname; is restarted.</para>
2303 <section><title>Restore Window Setup</title>
2304 <para>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.</para>
2306 <section><title>Default Map Layer</title>
2307 <para>When this is enabled, a map layer is automatically added whenever &appname; is opened and a &appname; file is not to be loaded.</para>
2308 <para>The map layer used is defined by the map layer's default values.</para>
2310 <section><title>Startup Method</title>
2311 <para>Enables selection of how the startup position should be determined.</para>
2313 <listitem><para>Home Location (default) - Position as set by the <guilabel>Set the Default Location</guilabel></para></listitem>
2314 <listitem><para>Last Location - Uses the last position viewed on the viewport</para></listitem>
2315 <listitem><para>Specified File - Load the file as specified below</para></listitem>
2316 <listitem><para>Auto Location - Use the web service <ulink url="http://www.hostip.info">hostip.info</ulink> to attempt to determine your location via IP lookup</para></listitem>
2319 <section><title>Startup File</title>
2320 <para>Loads this specified file when the Startup method is set to <guilabel>Specified File</guilabel></para>
2322 <section><title>Check For New Version</title>
2323 <para>Periodically (no more than once every 14 days), check to see if there is a new version of &appname; available.</para>
2327 <section id="prefs_toolbar" xreflabel="Toolbar Preferences"><title>Toolbar</title>
2328 <section><title>Append to Menu</title>
2329 <para>Allows setting the toolbar on the same vertical space as the menu, thus increasing vertical space for the map.</para>
2331 <section><title>Icon Size</title>
2332 <para>Allows configuration of the icon size, including overiding the system's default preference to the setting desired just for &appname;</para>
2334 <section><title>Icon Style</title>
2335 <para>Allows configuration of the icon style, including overiding the system's default preference to the setting desired just for &appname;</para>
2337 <section id="prefs_toolbar_customize" xreflabel="Customize Toolbar"><title>Customize</title>
2338 <para>Opens the Customize Toolbar dialog.</para>
2339 <para>From this dialog the items in the toolbar can be added, removed and reordered. Reordering of items is performed by drag and drop.</para>
2341 <title>Customize Toolbar dialog</title>
2343 <graphic format="PNG" fileref="figures/customize_toolbar_dialog.png"/>
2352 <section><title>Howto's</title>
2353 <section id="howto_start"><title>Getting Started</title>
2355 &appname; from version 1.5 has several features to ease the start up process.
2356 On the very first run, you will be asked if you want to enable these features which make use of an Internet connection.
2357 If you select no or you have upgraded from an earlier version you can choose to enable any of the startup options via the <xref linkend="prefs_startup"/>.
2360 Some other general use cases for using &appname;, are as follows:
2362 <section><title>Go to an area of interest</title>
2364 &appname;'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.
2367 <title>Method A</title>
2370 Use the online location address/place search.
2373 Use the <guibutton>Go to Location</guibutton> toolbar button or from the menus
2374 <menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>.
2375 You can change the search location provider if desired.
2376 Enter the name of place you wish to go to (you may need to specify the country to refine the search).
2377 Also you can enter a post code or a ZIP code instead.
2380 <para>You will need an internet connection for this search to work</para>
2385 <title>Method B</title>
2388 If you know the coordinates of where you want to view:
2391 Use <menuchoice><guimenu>View</guimenu></menuchoice> and select from either <menuchoice><guimenu>Go to Lat/Lon</guimenu></menuchoice> or <menuchoice><guimenu>Go to UTM</guimenu></menuchoice> and then enter in the specific coordinates.
2396 <title id="method_c">Method C</title>
2398 <para>Use the GPS Layer or <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
2399 to load data directly from your GPS into &appname;.
2401 <para>You can specify the types of data to acquire: Tracks, Routes and/or Waypoints.
2404 <para>You must have write permission to the port used. For <trademark>Unix</trademark> like OS:</para>
2406 <listitem><para>/dev/ttyS0 is the first serial port</para></listitem>
2407 <listitem><para>/dev/ttyUSB0 is the first USB port</para></listitem>
2408 <listitem><para>usb: is any USB port</para></listitem>
2410 <para>Depending on your distribution only one of the USB port types may work</para>
2411 <para>For <trademark>Windows</trademark>:</para>
2413 <listitem><para>com1: is the first serial port</para></listitem>
2414 <listitem><para>usb: is any USB port</para></listitem>
2418 <para>The GPS devices supported are those supported by <application>GPSBabel</application>.</para>
2419 <para>Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.</para>
2424 <title>Method D</title>
2427 Get data from files in GPX or KML format, which can be opened directly.
2428 Use <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice>
2431 Other formats can be imported that are supported by GPSBabel.
2432 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel...</guimenuitem></menuchoice>
2436 The viewport will be automatically moved and resized to view the contents of the file.
2442 <section><title>Add a Map Layer</title>
2444 Use <menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice>, and choose a suitable cache directory
2445 where you would like to store your tracks and click <guilabel>OK</guilabel>. Zoom to a
2446 comfortable level (I suggest 4 mpp) by clicking the left and right
2447 mouse buttons on the gray area where your tracks are. Now from the menu
2448 choose the <xref linkend="map_tool_dl"/> Tool. Click where you would like to download a
2449 map. Regardless of what tool you are using, the middle mouse button
2450 always pans. </para>
2453 You need an open internet connection when you are downloading maps.
2457 If you can no longer see your tracks or waypoints and only the map,
2458 it is because the layer named <emphasis>Map</emphasis> is <emphasis>ABOVE</emphasis> your TrackWaypoint layer that your GPS data is in.
2459 This means that it will be drawn last and on top of the other <xref linkend="gc_layers"/>.
2460 Look at the <xref linkend="gc_layers_panel"/> to the left which shows this order.
2461 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.
2462 Your tracks will now be drawn over the map.
2466 <section><title>Set Your Home Location</title>
2468 You can save the current center position of the viewport as the default location AKA the Home Location by
2469 <menuchoice><guimenu>Edit</guimenu><guimenuitem>Set the Default Location</guimenuitem></menuchoice>.
2472 Then at any time you can return to this place by clicking on the <guibutton>Home</guibutton> icon on the toolbar.
2475 You can also set the default location via specifing the exact latitude and longitude in the <xref linkend="prefs"/>.
2480 <section><title>From 1st startup to GPS track (including offline maps)</title>
2482 The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
2483 Before fetching unneeded data, one can position to a location of interest, e.g. Stuttgart: <menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter <userinput>Stuttgart</userinput>.
2485 <section><title>Fetching the maps</title>
2487 <emphasis role="bold">Map</emphasis>
2490 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
2491 <step><para>in the layer properties dialogue choose e.g. <guilabel>OpenStreetMap (Mapnik)</guilabel>.</para></step>
2493 <para>For the moment, we keep the default <guilabel>Maps Directory</guilabel> (the directory in
2494 which the maps will be stored and can be used for offline usage).</para>
2497 <para>Check <guilabel>Autodownload maps</guilabel> and keep the zoom level as <guilabel>Use Viking
2498 Zoom Level</guilabel>.</para>
2501 however, that these settings will play an important
2502 role in the pre-fetch for offline usage discussed later
2507 <para>You'll see a map of Stuttgart. Using the mouse wheel, you can
2508 zoom in and out. The maps for the choosen resolution will be downloaded
2512 <emphasis role="bold">DEM Layer (Height Map)</emphasis>
2515 <step><para>Zoom out to 512.</para></step>
2516 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New DEM Layer</guimenuitem></menuchoice></para></step>
2517 <step><para>Keep the download source as is (SRTM Global 90m), hit <guilabel>OK</guilabel>.</para></step>
2520 <para>In the layer listing on the left, the <xref linkend="DEM"/> layer should reside
2521 above the map layer. If this is not the case, highlight the DEM layer
2522 an shift it one up (using the arrow up button).
2525 <step><para>highlight the DEM layer in the layer listing on the left</para></step>
2526 <step><para>in the toolbar, check DEM layer download/import (the last symbol)</para></step>
2527 <step><para>a left-click in the map window should then fetch the DEM data</para></step>
2530 This might take some time.
2533 Sometimes, a tile does not show up correctly (you might see only a
2534 black frame in the map window) because it got corrupted during
2535 transfer. In order to correct this, you can delete the corresponding
2536 datafile in the cache. <programlisting> right-click the DEM layer properties</programlisting>
2539 The <guilabel>DEM Files</guilabel> listing allows you to delete the specific tiles (alternatively do this from the command line).
2542 You can also alter the Min. and Max. elevation in this dialogue.
2546 <section><title>GPS Track with Height Profile</title>
2548 <step><para>Uncheck the <xref linkend="DEM"/> layer (the map is shown again)</para></step>
2550 <para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New TrackWaypoint Layer</guimenuitem></menuchoice></para>
2551 <para>Ensure the new track layer is above the map layer.</para>
2553 <step><para>Expand the <xref linkend="TrackWaypoint"/> layer, select <guimenuitem>Tracks</guimenuitem></para></step>
2554 <step><para>In the tools menu choose <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon> <guibutton>Create Track</guibutton>
2556 <step><para>Leftclick in the map window, enter a name</para></step>
2558 <para>Click several times to generate a track (a right-click removes the last point).</para>
2559 <para>Height data is set automatically since DEM data is available</para>
2561 <step><para>Expand tracks in the layer menu, your track should show up, select it</para></step>
2562 <step><para>Right click your track, select <guimenuitem>Properties</guimenuitem></para></step>
2563 <step><para>Click the tab <guilabel>Elevation-distance</guilabel> - enjoy the plot</para></step>
2566 In order to save this setting for later usage
2569 <step><para>click <guilabel>OK</guilabel> in the <guilabel>Track Properties</guilabel> dialog</para></step>
2570 <step><para><menuchoice><guimenu>File</guimenu><guimenuitem>Save As</guimenuitem></menuchoice>, choose a name (you can open this <emphasis>view</emphasis> later via <menuchoice><guimenu>file</guimenu><guimenuitem>Open</guimenuitem></menuchoice>).</para></step>
2574 <section><title>Usecase: offline data for holiday</title>
2576 Suppose you want to have the <xref linkend="Maps"/> and <xref linkend="DEM"/> data offline for your holiday in Italy near Bologna.
2579 <step><para>Start a new &appname; session.</para></step>
2580 <step><para><menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter Bologna</para></step>
2581 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
2582 <step><para>Choose e.g. <guilabel>OpenStreetMap (mapnik)</guilabel>.</para></step>
2583 <step><para>adapt the <guilabel>maps directory</guilabel> e.g. to <filename>/home/user/.viking-map-holiday/</filename>.
2584 This allows you to delete the map stuff after holiday without purging the rest of your maps.
2586 <step><para>check <guilabel>autodownload map</guilabel></para></step>
2587 <step><para>keep <guilabel>viking zoom level</guilabel></para></step>
2588 <step><para>zoom out to 1024</para></step>
2589 <step><para>add a <xref linkend="DEM"/> layer (as discussed above)</para></step>
2590 <step><para>download the DEM data</para></step>
2592 <para>In the &app; version discussed here, the DEM data automatically
2593 are stored in <filename>/home/user/.viking-maps/</filename>. You can move the corresponding
2594 tiles into <filename>.viking-map-holiday/</filename> if you like.
2597 <emphasis role="bold">Download map data for all zoom levels</emphasis>
2600 <step><para>uncheck the DEM layer for the map to show up</para></step>
2601 <step><para>navigate the map to be centered at Bologna</para></step>
2602 <step><para>choose the zoom such, that all regions of interest are displayed in the map window (e.g. 1024)</para></step>
2604 <para>follow this sequence until you have all tiles for all zoom levels you need</para>
2606 <step><para>right-click the map layer properties</para></step>
2607 <step><para>set the zoomlevel explicitely one below the last (in the first cycle 512), hit OK</para></step>
2608 <step><para>right click the map layer <guimenuitem>Download Missing Onscreen Maps</guimenuitem></para></step>
2609 <step><para>wait until all tiles for that resolution have been downloaded</para></step>
2613 <para>This may take some time and some hard disk capacity.</para>
2615 Do not forget to save your configuration (as discussed above).
2621 <section><title>OpenStreetMap project</title>
2623 <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> is a collaborative project to create a free editable map of the world.
2624 One of sources of data for this project is GPS tracks.
2625 &appname; supports this project via the GPS Traces methods, both uploading and downloading such data.
2628 Also see <ulink url="http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces"/> for further detail.
2630 <section><title>Uploading data to OpenStreetMap</title>
2632 It is possible to upload data directly from &appname; to OpenStreetMap.
2635 <title>Upload a layer</title>
2637 One solution is to upload whole a <xref linkend="TrackWaypoint"/> layer. To do this,
2638 simply select the layer and right click on it. Then, select <guimenuitem>Upload to
2643 <title>Upload a single track</title>
2644 <para>Another solution is to upload an individual track. Simply select the track and right click on it.
2645 Then select <guimenuitem>Upload to OSM</guimenuitem>.
2649 <title>Fill in the form</title>
2651 In both cases, &appname; will retain some information.
2652 The email field is the email you used to subscribed into OpenStreetMap.
2653 The password field is the password you used with this account.
2654 The filename is the name you want your upload has on the server. This information is displayed by the osm server.
2655 The description is some descriptive information.
2656 The tags field is a white separated list of tags.
2661 <section id="osm_dl" xreflabel="OpenStreetMap Traces Download"><title>Downloading Traces from OpenStreetMap</title>
2663 It is possible to download GPS traces directly from OpenStreetMap into &appname;.
2664 This feature can be really useful for checking existing data before uploading new ones.
2667 <title>Download all visible tracks</title>
2668 <para>One solution is to select
2670 <guimenu>File</guimenu>
2671 <guisubmenu>Acquire</guisubmenu>
2672 <guimenuitem>OSM traces...</guimenuitem>
2674 Each request can get up to 5,000 points.
2675 The dialog box allows setting which group of 5,000 points to get. These groups are known as <emphasis>Page Numbers</emphasis> which start at 0.
2676 Increasing the page number parameter allows one to request the subsequent sets of point groups.
2680 <section id="osm_my_dl" xreflabel="OpenStreetMap My Traces Download"><title>Downloading Your Own Traces from OpenStreetMap</title>
2682 It is possible to download any of <emphasis>your personal</emphasis> GPS traces previously uploaded to OpenStreetMap into &appname;.
2685 You will need to provide your OSM username and password to get the list of your OSM Traces.
2686 From this list you can select which traces to retrieve.
2687 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.
2693 <section><title>Geotagging</title>
2695 This assumes you already have a <xref linkend="Maps"/> layer enabled for ease of use (if not see above to get one).
2697 <section><title>Manual Positioning</title>
2699 This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
2700 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.
2701 ATM this process only works on an individual image, so it will be tedious for handling lots of images.
2704 First create a <xref linkend="TrackWaypoint"/> layer or use an existing one; and select it in the <xref linkend="gc_layers_panel"/>.
2705 NB Make sure this layer is above the map layer in the Layers Panel list.
2706 Create a new waypoint (or move an existing one) to exact location desired:
2708 <listitem><para>Select the <xref linkend="createwptool"/> tool, then left click on the map at the location desired, choosing an image to associate with it in the new waypoint dialog</para></listitem>
2709 <listitem><para>Select the <xref linkend="select"/> tool, then left click on waypoint to be moved. Left click again and drag the waypoint to the location desired</para></listitem>
2711 Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
2712 <menuchoice><guimenu>Update Geotag on Image</guimenu><guisubmenu>Update</guisubmenu></menuchoice>
2715 The <guilabel>Update Geotag on Image</guilabel> options are only available when a waypoint has an image associated with it.
2719 <section><title>Automatic Positioning Against a Tracklog</title>
2721 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 -
2722 see <link linkend="howto_start">Getting Started</link>.
2723 It helps if this is the track that was recorded at the time you took some photographs!
2726 Select the track either from the layers panel on the left or via the viewport using the <xref linkend="select"/> tool.
2727 Then right click on it and chose the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> leading you to the <xref linkend="geotagging"/> Dialog.
2730 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.
2731 If things are succesful, new waypoints with thumbnail images of the photographs will appear.
2732 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.
2734 <formalpara><title>Option: Overwrite Waypoints</title>
2736 This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
2737 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).
2741 If you have multiple tracks in a TrackWaypoint layer, then invoking the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> action on the layer
2742 will search all the tracks to find location matches.
2747 <section><title>GPS Real Time Location (Not <trademark>Windows</trademark>)</title>
2749 &appname; relies on <ulink url="http://www.catb.org/gpsd/">gpsd</ulink> to provide the current location from a real time feed from a GPS device.
2750 Unfortunately <application>gpsd</application> is not available on <trademark>Windows</trademark>,
2751 so currently this functionality is disabled in <trademark>Windows</trademark> builds of &appname;
2754 This assumes you already have a <xref linkend="Maps"/> layer enabled for ease of use (if not see above to get one).
2757 Turn on the GPS Device, ensure it has figured out it's location and plug it in to your computer.
2759 <section><title>Set Up GPS Layer</title>
2761 You will need a <xref linkend="GPS"/> layer. One can be added via <menuchoice><guimenu>Layers</guimenu><guisubmenu>Add GPS Layer</guisubmenu></menuchoice>.
2764 Adjust the <emphasis>Realtime Tracking Mode</emphasis> settings to interface with <ulink url="http://www.catb.org/gpsd/">gpsd</ulink> as necessary. Normally the defaults should suffice.
2767 Current Linux distributions should run <application>gpsd</application> automatically when a GPS Device is plugged in. Otherwise you may have to run <application>gpsd</application> manually.
2770 Then right-click the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
2771 Hopefully the viewport should jump to the GPS location.
2774 Troubleshooting checklist:
2776 <procedure><step><para>Confirm <application>gpsd</application> is running.</para></step></procedure>
2777 <procedure><step><para>Confirm on the GPS device it has a location.</para></step></procedure>
2778 <procedure><step><para>Confirm the <emphasis>Realtime Tracking Mode</emphasis> settings.</para></step></procedure>
2782 <section><title>What to Do if &appname; Does Not Seem to Work</title>
2784 In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
2785 <programlisting>viking -dV</programlisting>
2788 For instance you can check the correct URLs &appname; is using in requesting remote data for DEMs or map tiles in the verbose debug output.
2789 E.g. Something like this for DEMs:
2791 ** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
2792 * About to connect() to dds.cr.usgs.gov port 80 (#0)
2793 * Trying 152.61.128.95... * connected
2794 * Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
2795 GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
2796 User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
2797 Host: dds.cr.usgs.gov
2800 Date: Sun, 26 Jul 2009 18:13:38 GMT
2802 Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
2803 ETag: eac3f8-1828f5-46f3caa76070a
2804 Accept-Ranges: bytes
2805 Content-Length: 1583349
2806 Content-Type: application/zip
2808 * Connection #0 to host dds.cr.usgs.gov left intact
2809 * Closing connection #0
2810 ** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
2812 Or for OSM Mapnik tile server:
2814 * About to connect() to tile.openstreetmap.org port 80 (#0)
2815 * Trying 193.63.75.28... * connected
2816 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2817 GET /13/4065/2748.png HTTP/1.1
2818 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2819 Host: tile.openstreetmap.org
2822 * HTTP 1.0, assume close after body
2824 Date: Thu, 14 Oct 2010 22:18:42 GMT
2825 Server: Apache/2.2.8 (Ubuntu)
2826 ETag: "b66ff9d46474bab68262a3483428a232"
2827 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
2828 Content-Length: 17194
2829 Cache-Control: max-age=94805
2830 Expires: Sat, 16 Oct 2010 00:38:47 GMT
2831 Content-Type: image/png
2833 X-Cache: HIT from konqi.openstreetmap.org
2834 X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
2835 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2838 * Closing connection #0
2839 * About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
2840 * Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
2841 * About to connect() to tile.openstreetmap.org port 80 (#0)
2842 * Trying 193.63.75.28... * connected
2843 * Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
2844 GET /tiles/cycle/13/4065/2747.png HTTP/1.1
2845 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2846 Host: a.andy.sandbox.cloudmade.com
2850 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2851 GET /13/4065/2749.png HTTP/1.1
2852 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2853 Host: tile.openstreetmap.org
2856 * HTTP 1.0, assume close after body
2858 Date: Thu, 14 Oct 2010 23:44:35 GMT
2859 Server: Apache/2.2.8 (Ubuntu)
2860 ETag: "8e520ad47ce9c1b63430554886eb5fab"
2861 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
2862 Content-Length: 18094
2863 Cache-Control: max-age=87742
2864 Expires: Sat, 16 Oct 2010 00:06:57 GMT
2865 Content-Type: image/png
2866 X-Cache: MISS from konqi.openstreetmap.org
2867 X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
2868 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2875 <!-- End of Howtos -->
2877 <section id="extend_viking" xreflabel="Extending Viking">
2878 <title>Extending Viking</title>
2880 <para>Currently, &app; 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".</para>
2881 <para>Here is an example:
2882 <programlisting><
projects / andy / viking.git / blob