2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
4 <!ENTITY appname "Viking">
5 <!ENTITY app "<application>Viking</application>">
6 <!ENTITY appversion "1.4">
7 <!ENTITY manrevision "1.4">
8 <!ENTITY date "February 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) and/or Terrasever.
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 Terraserver maps 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><title>Projections</title>
254 &appname; supports differents projections:
260 <para>LatLon (also called EPSG:4326)</para>
263 <para>Mercator (also called Spherical Mercator)</para>
269 <section><title>Map Cache</title>
271 &appname; stores downloaded map tiles to disk for a couple of reasons:
274 <listitem><para>Enables off line usage</para></listitem>
275 <listitem><para>Reduces loading on the map tile provider</para></listitem>
278 The &appname; automatic caching strategy is two fold:
283 If the age of the tile on disk is less than the specified tile age (see <xref linkend="prefs"/>),
284 it will <emphasis>not</emphasis> attempt to contact the server to get a new version of the tile.
289 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.
294 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.
298 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>)
303 <section id="shortcut_keys" xreflabel="Shortcut Keys"><title>Shortcut Keys</title>
305 &appname; has several shortcut keys or key combinations for commands as listed in the main window along side the command.
308 Some function keys follow standard GUI behaviour:
311 <listitem><para><keycap>F1</keycap> Help (view this manual)</para></listitem>
312 <listitem><para><keycap>F5</keycap> or <keycap>Ctrl+R</keycap> Refresh the maps on screen</para></listitem>
313 <listitem><para><keycap>F10</keycap> Select the Menubar (in built behaviour)</para></listitem>
314 <listitem><para><keycap>F11</keycap> Full Screen</para></listitem>
315 <listitem><para><keycap>Ctrl+F5</keycap> or <keycap>Ctrl+Shift+R</keycap> Redownload the maps on screen</para></listitem>
319 Refresh attempts to get new maps only if the local tile cache time period has expired for any particular map tile.
320 Redownload gets all on screen maps from the server, ignoring the local tile cache.
324 Other function keys control turn on/off visibility of various elements:
327 <listitem><para><keycap>F3</keycap> Toggle visibility of the Toolbar</para></listitem>
328 <listitem><para><keycap>F4</keycap> Toggle visibility of the Menubar</para></listitem>
329 <listitem><para><keycap>Shift+F5</keycap> Toggle visibility of the Scale indicator on the viewport</para></listitem>
330 <listitem><para><keycap>F6</keycap> Toggle visibility of the Center Crosshairs on the viewport</para></listitem>
331 <listitem><para><keycap>F7</keycap> Toggle showing selected items (e.g. tracks or waypoints) in the highlight colour in the viewport</para></listitem>
332 <listitem><para><keycap>F9</keycap> Toggle visibility of the Layers Panel</para></listitem>
333 <listitem><para><keycap>F12</keycap> Toggle visibility of the Statusbar</para></listitem>
336 Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exitting.
337 Then there are shortcuts specific to &appname; to switch projection modes, zoom in/out, create layers and switch the active tool mode.
338 For these combinations see the menu entry themselves.
342 <section><title>Tracks vs Routes</title>
344 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.
347 Q. When planning a <emphasis>route</emphasis> what difference does it make if it's a route or a track?
350 A. One difference is in how a GPS device navigates following the route or track.
351 Or you may want to consider interoperability with other software.
352 Otherwise it is probably best to use tracks as they are a superset of the route functionality.
355 For example on Garmin Etrex:
359 <para>Route following: Uses navigation mode with compass and estimated time to next point.</para>
360 <para>If following on road it can calculate a route on fly.</para>
361 <para>I (RN) always use this mode to follow pre planned routes.</para>
364 <para>Track following: Uses a <trademark>TracBack</trademark> mode</para>
365 <para>I (RN) never use this so I can't comment on how it actually compares to the route mode.</para>
369 There are often restrictions on the numbers of route points the GPS Device can handle - may be 250 or as little as 50.
370 This generally not a problem for single day routes, but needs managing for multi-day events or for highly detailed routes.
374 </section><!--General Concepts End-->
376 <section><title>File Types and the Main Window</title>
379 &appname; has it's own file type traditionally marked by the <emphasis>.vik</emphasis> file extension.
380 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...).
383 Besides it's own file type, &appname; can open (and save to via export methods) GPX and KML file types.
387 &appname; does not handle GPX 1.1 particularly well - it prefers GPX 1.0
391 By default &appname; opens a default blank window centered on the home location. This behaviour can be changed by the <xref linkend="prefs_startup"/>.
392 Each window contains menus, a toolbar, a viewport, layers panel and a statusbar.
393 Each section (apart from the viewport) can be hidden using the <xref linkend="shortcut_keys"/> or from the
394 <menuchoice><guimenu>View</guimenu><guisubmenu>Show</guisubmenu></menuchoice> choices.
397 One may consider each &appname; window to be a separate project - each with it's project <emphasis>Viking</emphasis> file.
398 However generally one window is enough for most purposes!
401 Several operations apply at the window level as follows next.
402 Also see <xref linkend="tools"/> for the operational modes that generally work in conjunction with a selected layer.
405 <section><title>New</title>
407 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu></menuchoice> menu and on the toolbar <guibutton>New</guibutton>.
410 This creates a new window with the default settings.
414 <section><title>Open</title>
416 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Open</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Open</guibutton>.
419 This opens a file chooser dialog to select one (or more) files of the supported GPS data file types:
421 <listitem><para>Viking</para></listitem>
422 <listitem><para>GPX</para></listitem>
423 <listitem><para>KML</para></listitem>
427 GPX and KML 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.
431 &appname; handles more file types via the <link linkend="acquire">Acquire</link> methods below.
436 <section><title>Save</title>
438 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Save</guibutton>.
441 If the current opened file is <emphasis>Viking</emphasis> file, this save will simply update it.
442 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.
446 <section><title>Save As</title>
448 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save As</guisubmenu></menuchoice> menu only.
451 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).
455 <section><title>Append</title>
457 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Append</guisubmenu></menuchoice> menu only.
460 Selecting a <emphasis>Viking</emphasis> file from this method will join the file contents to the current window (instead of creating a new one).
461 GPX and KML files may also be appended, but this is exactly the same as the normal file open method.
465 <section id="acquire" xreflabel="acquire"><title>Acquire</title>
468 Available on the <menuchoice><guimenu>File</guimenu><guisubmenu>Acquire</guisubmenu></menuchoice> menu and from the <xref linkend="TrackWaypoint"/> layer menu.
471 If used from the <guimenu>File</guimenu> menu and a TrackWaypoint layer is not currently selected, these methods place the results in a new TrackWaypoint layer. When a TrackWaypoint layer is selected, then using the <menuchoice><guimenu>File</guimenu><guisubmenu>Acquire</guisubmenu></menuchoice> will put the results into the selected TrackWaypoint layer.
474 If used from the <xref linkend="TrackWaypoint"/> layer menu these methods place the results in that TrackWaypoint layer.
478 <title>From GPS</title>
480 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
481 Probably the easiest way of getting information from a GPS Device.
484 Select the GPS Device communication settings and then hit <guibutton>OK</guibutton>.
485 See the <link linkend="method_c">Getting Started</link> section for more info about the settings.
489 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.
495 <title>Import File With GPSBabel</title>
497 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel</guimenuitem></menuchoice>
500 Other formats can be imported that are supported by GPSBabel.
503 You need to select the file <emphasis>and</emphasis> the type of the file that is going to be opened,
504 since there is no automatic detection of the file kind.
509 <title>OSM Traces</title>
511 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>OSM Traces</guimenuitem></menuchoice>
514 See <xref linkend="osm_dl"/> section for more information.
519 <title>My OSM Traces</title>
521 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>My OSM Traces</guimenuitem></menuchoice>
524 See <xref linkend="osm_my_dl"/> section for more information.
529 <title>From Geotagged Images</title>
531 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Geotagged Images</guimenuitem></menuchoice>
532 Enables automatic creation of waypoints from geotagged images.
535 This menu opens a dialog to select such image files.
536 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.
541 <title>From Wikipedia Waypoints</title>
543 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Wikipedia Waypoints</guimenuitem></menuchoice>
546 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.
551 <title>From Routing</title>
553 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Directions</guimenuitem></menuchoice>
556 This gets a route from given directions.
560 </section> <!-- End Acquire -->
562 <section><title>Print</title>
564 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Print</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Print</guibutton>.
567 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
568 cross hairs and the scale.
571 It uses a standard system print dialog using an image the size of the current viewport in pixel terms.
572 On the <emphasis>Image Settings</emphasis> you can move the image around the page and scale the image up / or down.
576 <section><title>Generate Image File</title>
578 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Image File</guisubmenu></menuchoice> menu only.
581 Allows generation of larger (pixel) area images than the standard Print method above.
582 From the generated image you can use the facilities of the <application>Operating System</application> to print the image
583 or perform other actions.
586 You should have previously downloaded the tile images for the chosen zoom level,
587 otherwise the image produced will have missing sections.
591 Using large areas takes some time to process and due to the method used it may run out of memory to complete the operation.
592 Unfortunately under <trademark>Windows</trademark> systems it can not detect this failure and may crash the program.
593 So the maximum size is dependent on the capabilities of your system.
594 For instance the largest successful image generated on my (RN) Debian system is a pixel area of 20,000 x 20,000.
599 <section><title>Generate Directory of Images</title>
601 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Directory of Images</guisubmenu></menuchoice> menu only.
604 This is only available in UTM mode.
608 </section> <!-- End File Types -->
610 <section><title>Layers</title>
613 Layers supported by &appname; are:
616 <listitem><para><xref linkend="Aggregate"/></para></listitem>
617 <listitem><para><xref linkend="TrackWaypoint"/></para></listitem>
618 <listitem><para><xref linkend="GPS"/></para></listitem>
619 <listitem><para><xref linkend="DEM"/></para></listitem>
620 <listitem><para><xref linkend="Coordinate"/></para></listitem>
621 <listitem><para><xref linkend="Maps"/></para></listitem>
622 <listitem><para><xref linkend="GeoRef"/></para></listitem>
625 For each layer there are a few standard options:
628 <listitem><para>Properties - Layer setup / configuration settings</para></listitem>
629 <listitem><para>Cut</para></listitem>
630 <listitem><para>Copy</para></listitem>
631 <listitem><para>Paste</para></listitem>
632 <listitem><para>Delete</para></listitem>
633 <listitem><para>Visibility - This checkbox on the Layers Panel controls whether the layer is shown in the viewport or not</para></listitem>
636 The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected:
639 <listitem><para>Standard keys: <keycap>Ctrl+x|c|v</keycap></para></listitem>
640 <listitem><para>Main menu <guimenuitem>Edit</guimenuitem></para></listitem>
641 <listitem><para>From the right click menu</para></listitem>
642 <listitem><para>Buttons at the bottom of the Layers Panel</para></listitem>
645 Default values used for each layer's properties can be altered via the <menuchoice><guimenu>Edit</guimenu><guisubmenu>Layer Defaults</guisubmenu></menuchoice> menu options.
648 See the individual section for detail about each layer.
652 <section id="TrackWaypoint" xreflabel="TrackWaypoint"><title>TrackWaypoint Layer</title>
654 TrackWaypoint layers display GPS data (tracks, routes and waypoints).
656 <para>One way to create new waypoints is to copy a
657 latitude/longitude coordinate pair, such as the one shown on most
658 geocaches, and paste it into an active TrackWaypoint layer. &appname; can
659 automatically recognize several variations of the lat/lon format.
662 By right-clicking on tracks, routes or waypoints in the <xref linkend="gc_layers_panel"/>, you can access many commands on them.
663 You can easily find a specific track, route or waypoint by expanding the appropriate containing Tracks, Routes or Waypoints sublayer in the
664 layers panel to show all the individual items and then typing the name of the track, route or waypoint.
668 The containing Tracks, Routes or Waypoints sublayers are only shown when items of that type exist.
669 To start creating them enter into a create mode via either the <guibutton>Create</guibutton> toolbar commands or the <guimenuitem>New</guimenuitem> menu commands.
673 The sublayers also offer right click menu options.
674 These are the same as those available at the TrackWaypoint level, but only those that relate to the sublayer type.
678 By default routes are coloured red. Tracks are automatically assigned a spread of colours.
682 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.
683 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).
686 <section><title>Layer Operations</title>
688 The layer has a context menu with several operations.
691 <section><title>View Layer</title>
693 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).
697 <section><title>View</title>
699 <section id="track_view_all"><title>View All Tracks</title>
701 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).
705 <section id="route_view_all"><title>View All Routes</title>
707 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).
711 <section id="wp_view_all"><title>View All Waypoints</title>
713 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).
719 <section><title>Goto Center of Layer</title>
721 This will automatically move the viewport to see the whole layer (i.e. tracks, routes and waypoints). It does not adjust the zoom level.
725 <section id="wp_goto"><title>Goto Waypoint</title>
727 This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it.
731 Note this search is not very clever and only finds exact matches.
732 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.
737 <section><title>Export Layer</title>
739 The layer (all tracks, routes and waypoints) can be exported to a file GPX, GPSPoint, GPSMapper or Google's KML format.
742 Version1.1+: An individual track can be exported to a GPX file via the track menu.
746 <section id="finish_track"><title>Finish Track or Route</title>
748 This is only available when a track or route is being created by the <xref linkend="track_create"/> or <xref linkend="route_create"/> tools.
749 Selecting this option ends the creation of that individual track or route.
753 <section><title>New</title>
754 <section id="new_wp"><title>New Waypoint</title>
756 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.
759 <section id="new_track"><title>New Track</title>
761 This turns on the <xref linkend="track_create"/> tool.
764 <section id="new_route"><title>New Route</title>
766 This turns on the <xref linkend="route_create"/> tool.
771 <section><title>Geotag Images</title>
773 This starts the Geotagging Images dialog against all tracks in the layer.
774 See <link linkend="geotagging">Geotagging</link> for further detail.
778 <section><title>Acquire</title>
780 This offers the same choice from <xref linkend="acquire"/> methods as on the <guimenu>File</guimenu> menu.
781 However when invoked from here, the results will be stored in this layer (instead of creating a new one).
785 <section><title>Upload</title>
787 <section id="gps_upload"><title>Upload to GPS</title>
789 This opens a dialog to select the GPS Device and port to which the layer information will be transferred.
792 The types of GPS information (tracks, routes or waypoints) to be transferred can be selected.
795 Tracks, Routes or Waypoints that are invisible will not be transferred.
799 <section id="osm_upload" xreflabel="Upload To OSM" ><title>Upload To OSM</title>
801 This opens a dialog to upload all tracks and waypoints to <ulink url="http://openstreetmap.org/">OpenStreetMap</ulink> traces.
802 Useful if you are an OpenStreetMap contributor (you will need an OpenStreetMap account), these details can be stored in &appname; <xref linkend="prefs_osm"/>
805 &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.
809 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.
811 <para>Currently &appname; does not support the <ulink url="http://oauth.net/">OAuth</ulink> mechanism.</para>
817 <section><title>Delete</title>
818 <para>Offers deletion of various parts of a TrackWaypoint layer:</para>
819 <section id="delete_all_tracks"><title>Delete All Tracks</title>
820 <para>Deletes all the tracks in this layer.</para>
822 <section id="delete_selection_tracks"><title>Delete Tracks from Selection</title>
823 <para>Opens a dialog with list of all the tracks from this layer to choose the ones to delete.</para>
825 <section id="delete_all_routes"><title>Delete All Routes</title>
826 <para>Deletes all the routes in this layer.</para>
828 <section id="delete_selection_routes"><title>Delete Routes from Selection</title>
829 <para>Opens a dialog with list of all the routes from this layer to choose the ones to delete.</para>
831 <section id="delete_all_waypoints"><title>Delete All Waypoints</title>
832 <para>Deletes all the waypoints in this layer.</para>
834 <section id="delete_selection_waypoints"><title>Delete Waypoints from Selection</title>
835 <para>Opens a dialog with list of all the waypoints from this layer to choose the ones to delete.</para>
839 <section><title>Filter</title>
840 <section><title>Simplify All Tracks</title>
842 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.
845 <section><title>Remove Duplicate Waypoints</title>
847 Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer.
851 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.
857 <section id="filter_with_track"><title>Filter With <emphasis>Trackname</emphasis></title>
859 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:
862 <listitem><para>Waypoints Inside This</para></listitem>
863 <listitem><para>Waypoints Outside This</para></listitem>
866 The result is generated in a new Track/Waypoint layer.
870 <section><title>Geotag Images</title>
872 This starts the Geotagging Images dialog using the specific track.
873 See <link linkend="geotagging">Geotagging</link> for further detail.
877 </section><!-- End TRW Layer Options -->
879 <section><title>Track and Route Sublayer Options</title>
880 <para>Repeats options available at the TrackWaypoint level, but only those for tracks and routes:</para>
882 <listitem><para>Finish Track or Route. Same as the layer <link linkend="finish_track">Finish Track or Route</link></para></listitem>
883 <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>
884 <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>
885 <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>
886 <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>
890 <section><title>Track and Route Properties</title>
892 Show many useful statistics about a track or a route, including a
893 elevation-distance graph and a speed-time graph (if data is available).
894 You can click these graphs to jump to the point in the track. You can
895 also reverse it, delete duplicates, and split a track from its
896 component segments (discontinuous breaks in a track) into separate
900 The following colors are used in the elevation-distance graph:
904 <term><emphasis>Main</emphasis> colour - this is dependent on your Desktop theme - often blue by default</term>
905 <listitem><para>elevation data in graph</para></listitem>
910 <para>no elevation data</para>
916 <para>elevation data from DEM</para>
929 <section><title>Track and Route Operations</title>
931 <section><title>Finish Track</title>
933 This is only available when a track is being created by the <xref linkend="track_create"/> tool.
934 Selecting this option ends the creation of the individual track.
938 <section><title>Goto</title>
940 This centers the viewport on the selected position on the track:
943 <listitem><para>Startpoint</para></listitem>
944 <listitem><para>"Center" - the notional center from the bounds of the track</para></listitem>
945 <listitem><para>Endpoint</para></listitem>
946 <listitem><para>Version1.1+: Highest Altitude</para></listitem>
947 <listitem><para>Version1.1+: Lowest Altitude</para></listitem>
948 <listitem><para>Version1.1+: Maximum Speed (Not Available on Routes)</para></listitem>
952 <section><title>View</title>
954 Version1.1+: This centers the viewport on the track and selects the best zoom level to see it.
958 <section><title>Combine</title>
959 <section><title>Merge By Time</title>
961 This operation repeatedly tries to merge the right-clicked track
962 with tracks in the same TrackWaypoint layer. The tracks which are
963 merged are those which have at least one trackpoint less than some
964 threshold time away. This way, if you somehow end up with lots of small
965 segments (say, caused by turning the GPS on and off) you can merge them
966 easily into one track.
969 This is not available on routes as they have no timestamps.
973 <section><title>Merge With Other Tracks</title>
975 This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with.
979 <section><title>Merge Segments</title>
981 Combines track segments. Effectively removing track segment markers to leave one segment for the whole track.
985 <section><title>Append Track or Route</title>
987 Enable joining of a single track to the end of the current track.
988 This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection.
993 <section><title>Split</title>
994 <section><title>Split By Time</title>
996 This operation will split a single track into segments wherever the
997 time interval between successive trackpoints is larger than some
998 threshold. This is useful when processing raw NMEA GPS data, especially
999 taken over a long time.
1002 This is not available on routes as they have no timestamps.
1006 <section><title>Split By Number of Points</title>
1008 Version1.2+: This operation will split a single track into segments by the number of points specified.
1009 This can be useful with devices which may have limits on the number of points it supports.
1013 <section><title>Split Segments</title>
1015 Splits track segments into new tracks.
1018 This is not available on routes as they do not have route segments.
1022 <section><title>Split at Trackpoint</title>
1024 Splits the track at the currently selected trackpoint. This is only enabled when a trackpoint is selected.
1029 <section><title>Delete Points</title>
1030 <section><title>Delete Points With the Same Position</title>
1032 Deletes subsequent points that have the same position (but have different timestamps).
1035 <section><title>Delete Points With the Same Time</title>
1037 Deletes subsequent points that have the same time stamp (but may have different positions).
1040 This is not available on routes as they have no timestamps.
1046 <section><title>Apply DEM data</title>
1048 If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
1052 <section><title>Export Track as GPX</title>
1054 Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog.
1058 <section><title>Extend Track End</title>
1060 Changes the current tool to add trackpoints to the end of the track.
1064 <section><title>Extend Using Route Finder</title>
1066 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.
1070 <section><title>Upload</title>
1072 <section><title>Upload to GPS</title>
1074 Same as the layer <link linkend="gps_upload">Upload to GPS</link> command, but only applies to the track.
1078 <section><title>Upload to OSM</title>
1080 Same as the layer <link linkend="osm_upload">Upload to OSM</link> command, but only applies to the track.
1086 <section><title>Use With Filter</title>
1088 This selects the track to be used in the <link linkend="filter_with_track">Filter With <emphasis>Trackname</emphasis></link> feature.
1091 This is not available on routes.
1095 <section><title>View Google Directions</title>
1097 This option is only available on a track created using the Route Finder tool.
1100 Launch a web browser to see the Google directions page which yielded the route.
1104 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.
1109 </section><!-- End Track Options -->
1111 <section><title>Waypoint Sublayer Options</title>
1112 <para>Repeats options available at the TrackWaypoint level, but only those for waypoints:</para>
1114 <listitem><para>New Waypoint. Same as the layer <link linkend="new_wp">New Waypoint</link></para></listitem>
1115 <listitem><para>View All Waypoints. Same as the layer <link linkend="wp_view_all">View All Waypoints</link></para></listitem>
1116 <listitem><para>Goto Waypoint. Same as the layer <link linkend="wp_goto">Goto Waypoint</link></para></listitem>
1117 <listitem><para>Delete All Waypoints. Same as the layer <link linkend="delete_all_waypoints">Delete All Waypoints</link></para></listitem>
1118 <listitem><para>Delete Waypoints from Selection. Same as the layer <link linkend="delete_selection_waypoints">Delete Waypoints from Selection</link></para></listitem>
1122 <section><title>Waypoint Properties</title>
1125 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).
1128 If the waypoint has an associated image, then the Geotag information may be updated, either with updating the file's modification timestamp or not.
1129 This can be useful when the waypoint has been moved.
1132 </section><!-- WP Prop END -->
1134 <section><title>Waypoint Operations</title>
1136 <section><title>Goto</title>
1138 This centers the viewport on the selected waypoint.
1142 <section><title>Visit Webpage</title>
1144 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.
1148 <section><title>Visit Geocache Webpage</title>
1150 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.
1154 <section><title>New Waypoint</title>
1156 Same as the layer <link linkend="new_wp">New Waypoint</link>.
1160 </section><!-- WP END -->
1162 <section id="geotagging" xreflabel="Geotagging"><title>Version1.3+: Geotag Images</title>
1164 This dialog allows geotagging images (normally taken with a digital camera) via interpolation against a specific track or all tracks in the TrackWaypoint layer - depending on how it is invoked.
1167 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.
1171 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.
1175 Various options allow control of how the geotagging process is performed:
1178 <listitem><para>Images - Add the images used for geotagging</para></listitem>
1179 <listitem><para>Create Waypoints</para></listitem>
1180 <listitem><para>Overwrite Existing Waypoints</para></listitem>
1181 <listitem><para>Write EXIF</para></listitem>
1182 <listitem><para>Overwrite Existing GPS Information</para></listitem>
1183 <listitem><para>Interpolate Between Track Segments</para></listitem>
1184 <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>
1185 <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>
1189 </section><!-- TRW Layer END -->
1191 <section id="GPS" xreflabel="GPS"><title>GPS Layer</title>
1193 The GPS layer is responsible for uploading and downloading GPS data
1194 from a GPS device. It also is responsible for realtime GPS tracking.
1195 Expand the GPS layer in the layers panel to see the two <xref linkend="TrackWaypoint"/> layers it
1196 uses for uploading and downloading. To upload, download, or use
1197 realtime tracking, right-click the GPS layer and click the appropiate
1201 <section><title>Download</title>
1203 To download data from the GPS, right-click the GPS layer and click <guimenuitem>Download from GPS</guimenuitem>.
1207 <section><title>Upload</title>
1209 To upload data to the GPS, first populate the GPS Upload child
1210 layer of the GPS layer (either by creating waypoints/tracks/routes in it, or
1211 copying and pasting or dragging waypoints/tracks/routes from another layer).
1212 Then right-click the GPS layer and click <guimenuitem>Upload to GPS</guimenuitem>.
1216 <section><title>Realtime Tracking</title>
1218 You must set up gpsd correctly or use a GPSD server and put the
1219 correct information in the GPS layer properties dialog. Then right-click
1220 the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
1224 <section><title>Empty <emphasis>Item</emphasis></title>
1226 There are several options to quickly delete a subsection of data:
1229 <listitem><para>Empty Realtime</para></listitem>
1230 <listitem><para>Empty Upload</para></listitem>
1231 <listitem><para>Empty Download</para></listitem>
1232 <listitem><para>Empty All</para></listitem>
1236 </section><!-- End GPS -->
1238 <section id="DEM" xreflabel="DEM"><title>DEM (Digital Elevation Model) Layer</title>
1240 This layer provides elevation data from the <ulink url="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission (SRTM)</ulink>
1243 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]
1246 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.
1249 The current data server is: <ulink url="http://dds.cr.usgs.gov/srtm/version2_1/">NASA STRM 2.1</ulink>.
1252 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.
1256 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"
1260 </section><!-- End DEM -->
1263 <section id="Maps" xreflabel="Maps"><title>Maps Layer</title>
1265 This layer provides a single map resource, you may have multiple map layers but only top one (if enabled) will be visible.
1266 You will need an open internet connection when you are downloading maps, 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.
1269 Some maps are continually improving over time (e.g. OpenStreetMap) and so in order to not to have to (re)download the data all the time &appname; employs a timeout method - <emphasis>Tile Age</emphasis> to determine whether to access the server. However a forced refresh for the current view can be made via the <guilabel>Reload All Onscreen Maps</guilabel> option.
1272 Inbuilt maps include various <ulink url="http://en.wikipedia.org/wiki/TerraServer-USA">Terraserver</ulink> (Primarily USA coverage) and <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> ones and more:
1275 <listitem><para>Bing Bird's Eye (Aerial) Maps (&appname; Version1.2+)</para></listitem>
1276 <listitem><para>Terraserver Topos</para></listitem>
1277 <listitem><para>Terraserver Aerials</para></listitem>
1278 <listitem><para>Terraserver Urban Areas</para></listitem>
1279 <listitem><para>OpenStreetMap (Mapquest) - This is the default (&appname; Version1.3+)</para></listitem>
1280 <listitem><para>OpenStreetMap (Mapnik)</para></listitem>
1281 <listitem><para>OpenStreetMap (Cycle)</para></listitem>
1282 <listitem><para>OpenStreetMap (Transport) (&appname; Version1.3+)</para></listitem>
1283 <listitem><para>NASA BlueMarble</para></listitem>
1284 <listitem><para>SpotMap (&appname; Version1.1+)</para></listitem>
1288 &appname; can be configured to handle additional maps. See <xref linkend="extend_viking"/> for further detail.
1291 <section><title>Layer Operations</title>
1292 <section><title>Download Missing Onscreen Maps</title>
1294 This requests map tiles for areas of the viewport that do not currently have one.
1298 <section><title>Download New Onscreen Maps</title>
1300 This requests map tiles only if the maps are older than the Tile Age preference.
1304 <section><title>Reload All Onscreen Maps</title>
1306 Force a refresh of all visible map tiles.
1312 </section><!-- End Maps -->
1314 <section id="Aggregate" xreflabel="Aggregate"><title>Aggregate Layer</title>
1316 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.
1319 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.
1320 Here are some suggestions:
1322 <listitem><para>Hiking</para></listitem>
1323 <listitem><para>Mountain Biking</para></listitem>
1324 <listitem><para>Road Cycling</para></listitem>
1325 <listitem><para>Car Trips</para></listitem>
1326 <listitem><para>Sailing</para></listitem>
1327 <listitem><para>Holidays</para></listitem>
1328 <listitem><para>UK Points of Interest</para></listitem>
1329 <listitem><para>USA Points of Interest</para></listitem>
1330 <listitem><para>etc...</para></listitem>
1334 Thus one can have a list of all your tracks, but groups can be shown or not using the relevant layers visibility checkbox.
1338 This layer only has one operation: <guilabel>New Layer</guilabel>
1341 <section><title>New Layer</title>
1343 Add a new layer of the selected type.
1347 </section><!-- End Agg -->
1349 <section id="GeoRef" xreflabel="GeoRef"><title>GeoRef Layer</title>
1351 This layer allows one to use any image as a map. You will need to tell it how to align the map to a position in the world and the scale of map.
1353 <section><title>Layer Operations</title>
1354 <section><title>Zoom to Fit Map</title>
1356 Automatically set a zoom level to see the entire map coverage.
1360 <section><title>Goto Map Center</title>
1362 Center the viewport on this map.
1366 <section><title>Export to World File</title>
1368 Opens a file save dialog to save the scale and position information as a <ulink url="http://en.wikipedia.org/wiki/World_file">World File</ulink>.
1373 </section><!-- End GeoRef -->
1375 <section id="Coordinate" xreflabel="Coordinate"><title>Coordinate Layer</title>
1377 This layer is allows drawing of grid lines on the viewport.
1379 </section><!-- End Coord -->
1382 <section id="tools" xreflabel="Tools"><title>Tools</title>
1384 &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.
1387 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.
1390 <keycap>Scroll</keycap>: zoom in and out keeping the mouse over same location
1393 <keycap>Ctrl-scroll</keycap>: pan north-south (also <keycap>Ctrl-up</keycap>, <keycap>Ctrl-down</keycap>)
1396 <keycap>Shift-scroll</keycap>: pan east-west (also <keycap>Ctrl-left</keycap>, <keycap>Ctrl-right</keycap>)
1399 <keycap>Ctrl-shift-scroll</keycap>: zoom in and out, without changing the center (also <keycap>Ctrl+</keycap>, <keycap>Ctrl-</keycap> [*not* KeyPad +/-])
1402 <keycap>Middle-click</keycap>: make the clicked point on the map the center
1405 <keycap>Middle-click</keycap> and drag: pan
1408 <section><title>Pan</title>
1410 This is the default mode of operation for &appname;.
1413 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mover_22.png"/></guiicon>
1416 Pan moves the viewpoint. A single click centers the viewport at that point, whereas click and drag dynamically moves the view around.
1417 This is the default tool.
1420 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+P</keycap>
1424 <section><title>Zoom</title>
1426 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/zoom_18.png"/></guiicon>
1429 Zooms in and out on the clicked part of the map or by the selected area.
1432 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+Z</keycap>
1435 <keycap>Ctrl</keycap> + left or right click: Zoom in/out and center the map on the clicked location
1438 <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.
1442 <section><title>Ruler</title>
1444 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/ruler_18.png"/></guiicon>
1447 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.
1448 A second click will <emphasis>freeze</emphasis> the ruler at that point.
1451 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+U</keycap>
1455 <section id="select" xreflabel="Select"><title>Version1.1+: Select</title>
1457 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/select_18.png"/></guiicon>
1460 The select tool allows one to choose any waypoint or track by clicking on it (or reasonably near) in the viewpoint.
1463 ATM to select a track one must actually click on a trackpoint, which is also selected.
1466 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+S</keycap>
1470 <section><title>TrackWaypoint Layer Tools</title>
1472 You must have a <xref linkend="TrackWaypoint"/> Layer selected to use these tools.
1474 <section id="createwptool" xreflabel="Create Waypoint"><title>Create Waypoint</title>
1476 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addwp_18.png"/></guiicon>
1479 Left click will open the new waypoint dialog using the specified position.
1483 <section id="track_create" xreflabel="Create Track"><title>Create Track</title>
1485 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon>
1488 Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track.
1489 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1490 Right click or <keycap>Backspace</keycap>: undo one point.
1493 Double click or <keycap>Escape</keycap>: to finish track creation.
1494 Finishing the track is also available via the right click <xref linkend="TrackWaypoint"/> and track menus.
1497 One must finish the current track to be able to create another track.
1501 <section id="route_create" xreflabel="Create Route"><title>Create Route</title>
1503 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/vik_new_route_18.png"/></guiicon>
1506 This operates in exactly the same way as the <link linkend="track_create">Create Track</link> above.
1509 One must finish the current route to be able to create another route.
1513 <section><title>Edit Waypoint</title>
1515 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edwp_18.png"/></guiicon>
1518 Left Click/drag: select/move a waypoint.
1519 If <keycap>Ctrl</keycap> is held at the same time, it will jump the waypoint position to a nearby existing trackpoint.
1520 If <keycap>Shift</keycap> is held at the same time, it will jump the waypoint position to a nearby existing waypoint.
1522 <para>Right-click on waypoint: opens a menu with waypoint actions (the
1523 same menu accessed by right-clicking the waypoint in the layers panel)
1527 <section><title>Edit Trackpoint</title>
1529 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edtr_18.png"/></guiicon>
1532 Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint.
1533 Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint.
1534 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1537 Options in the Track Point Edit dialog include: change position, go to next, go to previous, delete, insert (halfway to next trackpoint) and splitting the track.
1541 <section><title>Show Picture</title>
1543 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/showpic_18.png"/></guiicon>
1546 Opens an image viewer with the picture associated with the waypoint.
1547 By default this uses the default system image viewer.
1548 For Linux you can override this with the setting in the <xref linkend="prefs_external"/>
1552 <section id="route_finder" xreflabel="Route Finder"><title>Route Finder</title>
1554 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/route_finder_18.png"/></guiicon>
1556 <para>Creates a track using default routing engine between two points.
1557 Requires an internet connection. Click one point, then click another to
1561 Right-click: undo last routing (only track removed - not any waypoints)
1564 <keycap>Ctrl</keycap>: continue previous track
1570 <section><title>Georef Map Layer Tools</title>
1572 You must have a <xref linkend="GeoRef"/> Map Layer selected to use these tools.
1574 <section><title>Georef zoom</title>
1576 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geozoom_18.png"/></guiicon>
1578 <para>Changes the zoom level of the georeferenced map and changes the
1579 &appname; zoom level accordingly. Useful if you are trying to match GPS
1580 data to a georeferenced map.
1584 <section><title>Georef move</title>
1586 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geomove_18.png"/></guiicon>
1589 Drag to move the georeferenced map.
1594 <section id="map_tool_dl" xreflabel="Map Download"><title>Map Download</title>
1596 You must have a <xref linkend="Maps"/> Layer selected to use this.
1599 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mapdl_18.png"/></guiicon>
1602 Click to download a single tile. Drag to download tiles in the dragged rectangle area.
1605 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.
1606 The possible methods to redownload one or more tiles are:
1610 <listitem><para>Bad - Only if the tile is corrupt in some way or missing, then this will download a new copy</para></listitem>
1611 <listitem><para>New - Refresh the tile according to the local map cache and if server has a newer version</para></listitem>
1612 <listitem><para>All - Redownload the tile</para></listitem>
1615 <formalpara><title>Map Tile Information</title>
1617 By right clicking on viewport you can see the tile properties of the that location for the current map layer and current zoom level.
1618 This includes the remote source URL for the tile and the cached version on the local filesystem with timestamp details.
1623 <title>Map Tile Info Dialog: Example</title>
1625 <graphic format="PNG" fileref="figures/map_tile_info_dialog.png"/>
1628 This is using MapQuest at &appname; zoom level 128 over the Isle of Wight, UK.
1632 <section><title>DEM Download</title>
1634 You must have a <xref linkend="DEM"/> Layer selected to use this.
1637 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/demdl_18.png"/></guiicon>
1640 Click to download and import a DEM file.
1644 <section><title>Webtools</title>
1646 Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
1649 Jumping from &app; to such service can become annoying.
1652 &appname; allows you to open such service directly at the position currently viewed in &app;.
1655 This feature is called <guilabel>Webtools</guilabel>. It is also known as External Tools.
1661 <!-- Preferences -->
1662 <section id="prefs" xreflabel="Preferences"><title>Preferences</title>
1663 <section><title>General</title>
1664 <section><title>Localisation</title>
1665 <para>You can select units displayed by &appname; to best fit your usage.</para>
1667 <title>Properties dialog: units part</title>
1669 <graphic format="PNG" fileref="figures/properties_units.png"/>
1672 <para>Concerning degrees, you can select the way to display them:
1675 <term>DDD</term><listitem><para>decimal degree</para></listitem>
1678 <term>DMM</term><listitem><para>partial sexagesimal display: degrees, minutes and decimal part of minutes</para></listitem>
1681 <term>DMS</term><listitem><para>sexagesimal display: degrees, minutes and seconds</para></listitem>
1686 <title>Properties dialog: degree display options</title>
1688 <graphic format="PNG" fileref="figures/properties_degree.png"/>
1692 <section><title>Waypoint Icon Size</title>
1693 <para>An option exists to control the icon (symbol) size used for waypoints
1696 <section><title><emphasis>Home</emphasis> Default Location: Latitude and Longitude</title>
1697 <para>You can set the <emphasis>Home</emphasis> location directly by inputting the latitude and longitude in decimal degrees.
1700 <section><title>Tile's age</title>
1701 <para>This age is used to decided wether or not a new request to tile server must be done.
1703 <para>Changing this value, you will increase or decrese the network load.</para>
1705 <section><title>Default maplayer directory</title>
1706 <para>This property sets the default directory of the tiles cache.
1707 This value is used when you create a new map layer.
1709 <para>You are still able to change this value in each map layer properties.</para>
1711 <section><title>Map Cache Memory Size</title>
1712 <para>This controls the amount of maps that are stored in memory, rather than having to reread from disk.
1713 Generally if you have a system with lots of memory it's recommended to increase this value.
1718 <section id="prefs_external" xreflabel="Export/External Preferences"><title>Export/External</title>
1719 <section><title>KML Export Units</title>
1720 <para>Allows setting the units used when saved as the KML file type, such as Metric or Statue units</para>
1722 <section><title>Image Viewer (Not Windows)</title>
1723 <para>Allows setting the program used to view images associated with Waypoints.</para>
1724 <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>
1725 <para>Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.</para>
1727 <section><title>External GPX programs</title>
1728 <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>
1729 <para>Two options are given so that it can be configured for various uses such as:</para>
1731 <listitem><para>An OSM editor (default)</para></listitem>
1732 <listitem><para>Some other user defined program</para></listitem>
1737 <section id="prefs_osm" xreflabel="OpenStreetMap Traces Preferences"><title>OpenStreetMap Traces</title>
1738 <section><title>OSM Username + Password</title>
1739 <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>
1742 Your OSM password will be stored in plain text.
1748 <section id="prefs_routing" xreflabel="Routing Preferences"><title>Routing</title>
1749 <section><title>Routing engine</title>
1750 <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>
1754 <section id="prefs_startup" xreflabel="Startup Preferences"><title>Startup</title>
1755 <para>Naturally since these preferences effect the startup, the values will not be used until &appname; is restarted.</para>
1756 <section><title>Restore Window Setup</title>
1757 <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>
1759 <section><title>Default Map Layer</title>
1760 <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>
1761 <para>The map layer used is defined by the map layer's default values.</para>
1763 <section><title>Startup Method</title>
1764 <para>Enables selection of how the startup position should be determined.</para>
1766 <listitem><para>Home Location (default) - Position as set by the <guilabel>Set the Default Location</guilabel></para></listitem>
1767 <listitem><para>Last Location - Uses the last position viewed on the viewport</para></listitem>
1768 <listitem><para>Specified File - Load the file as specified below</para></listitem>
1769 <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>
1772 <section><title>Startup File</title>
1773 <para>Loads this specified file when the Startup method is set to <guilabel>Specified File</guilabel></para>
1775 <section><title>Check For New Version</title>
1776 <para>Periodically (no more than once every 14 days), check to see if there is a new version of &appname; available.</para>
1783 <section><title>Howto's</title>
1784 <section id="howto_start"><title>Getting Started</title>
1786 &appname; from version 1.5 has several features to ease the start up process.
1787 On the very first run, you will be asked if you want to enable these features which make use of an Internet connection.
1788 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"/>.
1791 Some other general use cases for using &appname;, are as follows:
1793 <section><title>Go to an area of interest</title>
1795 &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.
1798 <title>Method A</title>
1801 Use the online location address/place search.
1804 Use the <guibutton>Go to Location</guibutton> toolbar button or from the menus
1805 <menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>.
1806 You can change the search location provider if desired.
1807 Enter the name of place you wish to go to (you may need to specify the country to refine the search).
1808 Also you can enter a post code or a ZIP code instead.
1811 <para>You will need an internet connection for this search to work</para>
1816 <title>Method B</title>
1819 If you know the coordinates of where you want to view:
1822 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.
1827 <title id="method_c">Method C</title>
1829 <para>Use the GPS Layer or <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
1830 to load data directly from your GPS into &appname;.
1832 <para>You can specify the types of data to acquire: Tracks, Routes and/or Waypoints.
1835 <para>You must have write permission to the port used. For <trademark>Unix</trademark> like OS:</para>
1837 <listitem><para>/dev/ttyS0 is the first serial port</para></listitem>
1838 <listitem><para>/dev/ttyUSB0 is the first USB port</para></listitem>
1839 <listitem><para>usb: is any USB port</para></listitem>
1841 <para>Depending on your distribution only one of the USB port types may work</para>
1842 <para>For <trademark>Windows</trademark>:</para>
1844 <listitem><para>com1: is the first serial port</para></listitem>
1845 <listitem><para>usb: is any USB port</para></listitem>
1849 <para>The GPS devices supported are those supported by <application>GPSBabel</application>.</para>
1850 <para>Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.</para>
1855 <title>Method D</title>
1858 Get data from files in GPX or KML format, which can be opened directly.
1859 Use <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice>
1862 Other formats can be imported that are supported by GPSBabel.
1863 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel...</guimenuitem></menuchoice>
1867 The viewport will be automatically moved and resized to view the contents of the file.
1873 <section><title>Add a Map Layer</title>
1875 Use <menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice>, and choose a suitable cache directory
1876 where you would like to store your tracks and click <guilabel>OK</guilabel>. Zoom to a
1877 comfortable level (I suggest 4 mpp) by clicking the left and right
1878 mouse buttons on the gray area where your tracks are. Now from the menu
1879 choose the <xref linkend="map_tool_dl"/> Tool. Click where you would like to download a
1880 map. Regardless of what tool you are using, the middle mouse button
1881 always pans. </para>
1884 You need an open internet connection when you are downloading maps.
1888 If you can no longer see your tracks or waypoints and only the map,
1889 it is because the layer named <emphasis>Map</emphasis> is <emphasis>ABOVE</emphasis> your TrackWaypoint layer that your GPS data is in.
1890 This means that it will be drawn last and on top of the other <xref linkend="gc_layers"/>.
1891 Look at the <xref linkend="gc_layers_panel"/> to the left which shows this order.
1892 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.
1893 Your tracks will now be drawn over the map.
1897 <section><title>Set Your Home Location</title>
1899 You can save the current center position of the viewport as the default location AKA the Home Location by
1900 <menuchoice><guimenu>Edit</guimenu><guimenuitem>Set the Default Location</guimenuitem></menuchoice>.
1903 Then at any time you can return to this place by clicking on the <guibutton>Home</guibutton> icon on the toolbar.
1906 You can also set the default location via specifing the exact latitude and longitude in the <xref linkend="prefs"/>.
1911 <section><title>From 1st startup to GPS track (including offline maps)</title>
1913 The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
1914 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>.
1916 <section><title>Fetching the maps</title>
1918 <emphasis role="bold">Map</emphasis>
1921 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
1922 <step><para>in the layer properties dialogue choose e.g. <guilabel>OpenStreetMap (Mapnik)</guilabel>.</para></step>
1924 <para>For the moment, we keep the default <guilabel>Maps Directory</guilabel> (the directory in
1925 which the maps will be stored and can be used for offline usage).</para>
1928 <para>Check <guilabel>Autodownload maps</guilabel> and keep the zoom level as <guilabel>Use Viking
1929 Zoom Level</guilabel>.</para>
1932 however, that these settings will play an important
1933 role in the pre-fetch for offline usage discussed later
1938 <para>You'll see a map of Stuttgart. Using the mouse wheel, you can
1939 zoom in and out. The maps for the choosen resolution will be downloaded
1943 <emphasis role="bold">DEM Layer (Height Map)</emphasis>
1946 <step><para>Zoom out to 512.</para></step>
1947 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New DEM Layer</guimenuitem></menuchoice></para></step>
1948 <step><para>Keep the download source as is (SRTM Global 90m), hit <guilabel>OK</guilabel>.</para></step>
1951 <para>In the layer listing on the left, the <xref linkend="DEM"/> layer should reside
1952 above the map layer. If this is not the case, highlight the DEM layer
1953 an shift it one up (using the arrow up button).
1956 <step><para>highlight the DEM layer in the layer listing on the left</para></step>
1957 <step><para>in the toolbar, check DEM layer download/import (the last symbol)</para></step>
1958 <step><para>a left-click in the map window should then fetch the DEM data</para></step>
1961 This might take some time.
1964 Sometimes, a tile does not show up correctly (you might see only a
1965 black frame in the map window) because it got corrupted during
1966 transfer. In order to correct this, you can delete the corresponding
1967 datafile in the cache. <programlisting> right-click the DEM layer properties</programlisting>
1970 The <guilabel>DEM Files</guilabel> listing allows you to delete the specific tiles (alternatively do this from the command line).
1973 You can also alter the Min. and Max. elevation in this dialogue.
1977 <section><title>GPS Track with Height Profile</title>
1979 <step><para>Uncheck the <xref linkend="DEM"/> layer (the map is shown again)</para></step>
1981 <para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New TrackWaypoint Layer</guimenuitem></menuchoice></para>
1982 <para>Ensure the new track layer is above the map layer.</para>
1984 <step><para>Expand the <xref linkend="TrackWaypoint"/> layer, select <guimenuitem>Tracks</guimenuitem></para></step>
1985 <step><para>In the tools menu choose <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon> <guibutton>Create Track</guibutton>
1987 <step><para>Leftclick in the map window, enter a name</para></step>
1989 <para>Click several times to generate a track (a right-click removes the last point).</para>
1990 <para>Height data is set automatically since DEM data is available</para>
1992 <step><para>Expand tracks in the layer menu, your track should show up, select it</para></step>
1993 <step><para>Right click your track, select <guimenuitem>Properties</guimenuitem></para></step>
1994 <step><para>Click the tab <guilabel>Elevation-distance</guilabel> - enjoy the plot</para></step>
1997 In order to save this setting for later usage
2000 <step><para>click <guilabel>OK</guilabel> in the <guilabel>Track Properties</guilabel> dialog</para></step>
2001 <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>
2005 <section><title>Usecase: offline data for holiday</title>
2007 Suppose you want to have the <xref linkend="Maps"/> and <xref linkend="DEM"/> data offline for your holiday in Italy near Bologna.
2010 <step><para>Start a new &appname; session.</para></step>
2011 <step><para><menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter Bologna</para></step>
2012 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
2013 <step><para>Choose e.g. <guilabel>OpenStreetMap (mapnik)</guilabel>.</para></step>
2014 <step><para>adapt the <guilabel>maps directory</guilabel> e.g. to <filename>/home/user/.viking-map-holiday/</filename>.
2015 This allows you to delete the map stuff after holiday without purging the rest of your maps.
2017 <step><para>check <guilabel>autodownload map</guilabel></para></step>
2018 <step><para>keep <guilabel>viking zoom level</guilabel></para></step>
2019 <step><para>zoom out to 1024</para></step>
2020 <step><para>add a <xref linkend="DEM"/> layer (as discussed above)</para></step>
2021 <step><para>download the DEM data</para></step>
2023 <para>In the &app; version discussed here, the DEM data automatically
2024 are stored in <filename>/home/user/.viking-maps/</filename>. You can move the corresponding
2025 tiles into <filename>.viking-map-holiday/</filename> if you like.
2028 <emphasis role="bold">Download map data for all zoom levels</emphasis>
2031 <step><para>uncheck the DEM layer for the map to show up</para></step>
2032 <step><para>navigate the map to be centered at Bologna</para></step>
2033 <step><para>choose the zoom such, that all regions of interest are displayed in the map window (e.g. 1024)</para></step>
2035 <para>follow this sequence until you have all tiles for all zoom levels you need</para>
2037 <step><para>right-click the map layer properties</para></step>
2038 <step><para>set the zoomlevel explicitely one below the last (in the first cycle 512), hit OK</para></step>
2039 <step><para>right click the map layer <guimenuitem>Download Missing Onscreen Maps</guimenuitem></para></step>
2040 <step><para>wait until all tiles for that resolution have been downloaded</para></step>
2044 <para>This may take some time and some hard disk capacity.</para>
2046 Do not forget to save your configuration (as discussed above).
2052 <section><title>OpenStreetMap project</title>
2054 <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> is a collaborative project to create a free editable map of the world.
2055 One of sources of data for this project is GPS tracks.
2056 &appname; supports this project via the GPS Traces methods, both uploading and downloading such data.
2059 Also see <ulink url="http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces"/> for further detail.
2061 <section><title>Uploading data to OpenStreetMap</title>
2063 It is possible to upload data directly from &appname; to OpenStreetMap.
2066 <title>Upload a layer</title>
2068 One solution is to upload whole a <xref linkend="TrackWaypoint"/> layer. To do this,
2069 simply select the layer and right click on it. Then, select <guimenuitem>Upload to
2074 <title>Upload a single track</title>
2075 <para>Another solution is to upload an individual track. Simply select the track and right click on it.
2076 Then select <guimenuitem>Upload to OSM</guimenuitem>.
2080 <title>Fill in the form</title>
2082 In both cases, &appname; will retain some information.
2083 The email field is the email you used to subscribed into OpenStreetMap.
2084 The password field is the password you used with this account.
2085 The filename is the name you want your upload has on the server. This information is displayed by the osm server.
2086 The description is some descriptive information.
2087 The tags field is a white separated list of tags.
2092 <section id="osm_dl" xreflabel="OpenStreetMap Traces Download"><title>Downloading Traces from OpenStreetMap</title>
2094 It is possible to download GPS traces directly from OpenStreetMap into &appname;.
2095 This feature can be really useful for checking existing data before uploading new ones.
2098 <title>Download all visible tracks</title>
2099 <para>One solution is to select
2101 <guimenu>File</guimenu>
2102 <guisubmenu>Acquire</guisubmenu>
2103 <guimenuitem>OSM traces...</guimenuitem>
2105 Each request can get up to 5,000 points.
2106 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.
2107 Increasing the page number parameter allows one to request the subsequent sets of point groups.
2111 <section id="osm_my_dl" xreflabel="OpenStreetMap My Traces Download"><title>Downloading Your Own Traces from OpenStreetMap</title>
2113 It is possible to download any of <emphasis>your personal</emphasis> GPS traces previously uploaded to OpenStreetMap into &appname;.
2116 You will need to provide your OSM username and password to get the list of your OSM Traces.
2117 From this list you can select which traces to retrieve.
2118 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.
2124 <section><title>Geotagging</title>
2126 This assumes you already have a <xref linkend="Maps"/> layer enabled for ease of use (if not see above to get one).
2128 <section><title>Manual Positioning</title>
2130 This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
2131 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.
2132 ATM this process only works on an individual image, so it will be tedious for handling lots of images.
2135 First create a <xref linkend="TrackWaypoint"/> layer or use an existing one; and select it in the <xref linkend="gc_layers_panel"/>.
2136 NB Make sure this layer is above the map layer in the Layers Panel list.
2137 Create a new waypoint (or move an existing one) to exact location desired:
2139 <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>
2140 <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>
2142 Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
2143 <menuchoice><guimenu>Update Geotag on Image</guimenu><guisubmenu>Update</guisubmenu></menuchoice>
2146 The <guilabel>Update Geotag on Image</guilabel> options are only available when a waypoint has an image associated with it.
2150 <section><title>Automatic Positioning Against a Tracklog</title>
2152 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 -
2153 see <link linkend="howto_start">Getting Started</link>.
2154 It helps if this is the track that was recorded at the time you took some photographs!
2157 Select the track either from the layers panel on the left or via the viewport using the <xref linkend="select"/> tool.
2158 Then right click on it and chose the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> leading you to the <xref linkend="geotagging"/> Dialog.
2161 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.
2162 If things are succesful, new waypoints with thumbnail images of the photographs will appear.
2163 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.
2165 <formalpara><title>Option: Overwrite Waypoints</title>
2167 This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
2168 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).
2172 If you have multiple tracks in a TrackWaypoint layer, then invoking the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> action on the layer
2173 will search all the tracks to find location matches.
2178 <section><title>GPS Real Time Location (Not <trademark>Windows</trademark>)</title>
2180 &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.
2181 Unfortunately <application>gpsd</application> is not available on <trademark>Windows</trademark>,
2182 so currently this functionality is disabled in <trademark>Windows</trademark> builds of &appname;
2185 This assumes you already have a <xref linkend="Maps"/> layer enabled for ease of use (if not see above to get one).
2188 Turn on the GPS Device, ensure it has figured out it's location and plug it in to your computer.
2190 <section><title>Set Up GPS Layer</title>
2192 You will need a <xref linkend="GPS"/> layer. One can be added via <menuchoice><guimenu>Layers</guimenu><guisubmenu>Add GPS Layer</guisubmenu></menuchoice>.
2195 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.
2198 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.
2201 Then right-click the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
2202 Hopefully the viewport should jump to the GPS location.
2205 Troubleshooting checklist:
2207 <procedure><step><para>Confirm <application>gpsd</application> is running.</para></step></procedure>
2208 <procedure><step><para>Confirm on the GPS device it has a location.</para></step></procedure>
2209 <procedure><step><para>Confirm the <emphasis>Realtime Tracking Mode</emphasis> settings.</para></step></procedure>
2213 <section><title>What to Do if &appname; Does Not Seem to Work</title>
2215 In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
2216 <programlisting>viking -dV</programlisting>
2219 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.
2220 E.g. Something like this for DEMs:
2222 ** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
2223 * About to connect() to dds.cr.usgs.gov port 80 (#0)
2224 * Trying 152.61.128.95... * connected
2225 * Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
2226 GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
2227 User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
2228 Host: dds.cr.usgs.gov
2231 Date: Sun, 26 Jul 2009 18:13:38 GMT
2233 Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
2234 ETag: eac3f8-1828f5-46f3caa76070a
2235 Accept-Ranges: bytes
2236 Content-Length: 1583349
2237 Content-Type: application/zip
2239 * Connection #0 to host dds.cr.usgs.gov left intact
2240 * Closing connection #0
2241 ** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
2243 Or for OSM Mapnik tile server:
2245 * About to connect() to tile.openstreetmap.org port 80 (#0)
2246 * Trying 193.63.75.28... * connected
2247 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2248 GET /13/4065/2748.png HTTP/1.1
2249 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2250 Host: tile.openstreetmap.org
2253 * HTTP 1.0, assume close after body
2255 Date: Thu, 14 Oct 2010 22:18:42 GMT
2256 Server: Apache/2.2.8 (Ubuntu)
2257 ETag: "b66ff9d46474bab68262a3483428a232"
2258 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
2259 Content-Length: 17194
2260 Cache-Control: max-age=94805
2261 Expires: Sat, 16 Oct 2010 00:38:47 GMT
2262 Content-Type: image/png
2264 X-Cache: HIT from konqi.openstreetmap.org
2265 X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
2266 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2269 * Closing connection #0
2270 * About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
2271 * Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
2272 * About to connect() to tile.openstreetmap.org port 80 (#0)
2273 * Trying 193.63.75.28... * connected
2274 * Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
2275 GET /tiles/cycle/13/4065/2747.png HTTP/1.1
2276 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2277 Host: a.andy.sandbox.cloudmade.com
2281 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2282 GET /13/4065/2749.png HTTP/1.1
2283 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2284 Host: tile.openstreetmap.org
2287 * HTTP 1.0, assume close after body
2289 Date: Thu, 14 Oct 2010 23:44:35 GMT
2290 Server: Apache/2.2.8 (Ubuntu)
2291 ETag: "8e520ad47ce9c1b63430554886eb5fab"
2292 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
2293 Content-Length: 18094
2294 Cache-Control: max-age=87742
2295 Expires: Sat, 16 Oct 2010 00:06:57 GMT
2296 Content-Type: image/png
2297 X-Cache: MISS from konqi.openstreetmap.org
2298 X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
2299 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2306 <!-- End of Howtos -->
2308 <section id="extend_viking" xreflabel="Extending Viking">
2309 <title>Extending Viking</title>
2311 <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>
2312 <para>Here is an example:
2313 <programlisting><
projects / andy / viking.git / blob