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.3">
7 <!ENTITY manrevision "0.2">
8 <!ENTITY date "September 2012">
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 to/from GPS.
115 <para>Preparing tracks and waypoints for trips using maps from services
116 such as OpenStreetMap (OSM) and/or Terrasever. The data is only needed to be uploaded to
117 your GPS before you leave. The maps together with your tracks and
118 waypoints can also be printed and used during the trip.
123 After trips, tracks and waypoints from GPS can be downloaded, stored, managed and reused in your (or your friends') later trips.
128 Analyzing Off Highway Vehicle (OHV) and hiking trips, understanding where you went and how far you were from something.
132 <para>Making waypoints and tracks to follow to easily get someplace
133 you've never been before or don't have GPS data for but online
139 Making maps with coordinate lines.
144 Grouping data from multiple trips using a hierarchical data manager.
149 Analyzing speed at different places (to some degree), adding waypoints where you forgot to mark one but did slow down or stop.
154 Downloading and storing OpenStreetMap and/or Terraserver maps on your hard drive and looking at them later.
159 Editing tracks and trackpoints, joining and splitting up tracks
164 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.
169 Import track+waypoint files of various types via <application>GPSBabel</application>
174 View, create and update Geotagged Images (using EXIF data).
180 &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>:
185 <section><title>General Concepts</title>
186 <section><title>Layers</title>
188 'Layers' is concept one may know from powerful graphics editors such as <application>Photoshop</application> or <application>GIMP</application>.
189 Instead of putting all the data on the same level, it is stacked (i.e. layered) with different data over one another.
190 This can be useful for analysis and general handling of various sets of data.
193 Unfortunately the downside of this complexity is remembering how differing layers of data can obscure other data.
196 The Map layers have <ulink url="http://en.wikipedia.org/wiki/Alpha_compositing"><citetitle>Alpha Compositing</citetitle></ulink>,
197 to create the appearance of partial transparency.
198 By controlling this value one can see data below it in the layer heirarchy for interesting effects.
201 <section><title>Layers Panel</title>
203 The panel on the left is called the <emphasis role="bold">layers panel</emphasis>.
204 It determines which layers and sublayers (such as tracks and waypoints)
205 are shown, and the order in which they are drawn. Layers list on the
206 top of the layers panel are drawn last. You can change the order by
207 drag and drop, or by selecting a layer and using the up and down
208 buttons at the bottom of the layers panel.
211 <section><title>Viewport</title>
213 The main &appname; area where the layer data is drawn, is called the <emphasis role="bold">viewport</emphasis>.
216 <section><title>Statusbar</title>
217 <para>This provides a readout of various information:</para>
219 <listitem><para>The currently selected (mouse pointer) tool</para></listitem>
220 <listitem><para>The number of items to process in the background - normally this the number in the map tile download queue</para></listitem>
221 <listitem><para>The zoom factor</para></listitem>
222 <listitem><para>The location of the mouse pointer (and potentially height information if DEM data is available)</para></listitem>
226 <section><title>Projections</title>
228 &appname; supports differents projections:
234 <para>LatLon (also called EPSG:4326)</para>
237 <para>Mercator (also called Spherical Mercator)</para>
243 <section><title>Shortcut Keys</title>
245 &appname; has several shortcut keys or key combinations for commands as listed in the main window along side the command.
248 Some function keys follow standard GUI behaviour:
251 <listitem><para><keycap>F1</keycap> Help (view this manual)</para></listitem>
252 <listitem><para><keycap>F5</keycap> or <keycap>Ctrl+R</keycap> Refresh the maps on screen</para></listitem>
253 <listitem><para><keycap>F10</keycap> Select the Menubar (in built behaviour)</para></listitem>
254 <listitem><para><keycap>F11</keycap> Full Screen</para></listitem>
255 <listitem><para><keycap>Ctrl+F5</keycap> or <keycap>Ctrl+Shift+R</keycap> Redownload the maps on screen</para></listitem>
259 Refresh attempts to get new maps only if the local tile cache time period has expired for any particular map tile.
260 Redownload gets all on screen maps from the server, ignoring the local tile cache.
264 Other function keys control turn on/off visibility of various elements:
267 <listitem><para><keycap>F3</keycap> Toggle visibility of the Toolbar</para></listitem>
268 <listitem><para><keycap>F4</keycap> Toggle visibility of the Menubar</para></listitem>
269 <listitem><para><keycap>Shift+F5</keycap> Toggle visibility of the Scale indicator on the viewport</para></listitem>
270 <listitem><para><keycap>F6</keycap> Toggle visibility of the Center Crosshairs on the viewport</para></listitem>
271 <listitem><para><keycap>F7</keycap> Toggle showing selected items (e.g. tracks or waypoints) in the highlight colour in the viewport</para></listitem>
272 <listitem><para><keycap>F9</keycap> Toggle visibility of the Layers Panel</para></listitem>
273 <listitem><para><keycap>F12</keycap> Toggle visibility of the Statusbar</para></listitem>
276 Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exitting.
277 Then there are shortcuts specific to &appname; to switch projection modes, zoom in/out, create layers and switch the active tool mode.
278 For these combinations see the menu entry themselves.
282 </section><!--General Concepts End-->
284 <section><title>Layers</title>
287 Layers supported by &appname; are:
290 <listitem><para>Aggregate</para></listitem>
291 <listitem><para>TrackWaypoint</para></listitem>
292 <listitem><para>GPS</para></listitem>
293 <listitem><para>DEM</para></listitem>
294 <listitem><para>Coord</para></listitem>
295 <listitem><para>Map</para></listitem>
296 <listitem><para>GeoRef</para></listitem>
299 For each layer there are a few standard options:
302 <listitem><para>Properties - Layer setup / configuration settings</para></listitem>
303 <listitem><para>Cut</para></listitem>
304 <listitem><para>Copy</para></listitem>
305 <listitem><para>Paste</para></listitem>
306 <listitem><para>Delete</para></listitem>
307 <listitem><para>Visibility - This checkbox on the Layers Panel controls whether the layer is shown in the viewport or not</para></listitem>
310 The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected:
313 <listitem><para>Standard keys: <keycap>Ctrl+x|c|v</keycap></para></listitem>
314 <listitem><para>Main menu <guimenuitem>Edit</guimenuitem></para></listitem>
315 <listitem><para>From the right click menu</para></listitem>
316 <listitem><para>Buttons at the bottom of the Layers Panel</para></listitem>
319 See the individual section for detail about each layer.
322 <section><title>TrackWaypoint Layer</title>
324 TrackWaypoint layers display GPS data (tracks and waypoints).
326 <para>One way to create new waypoints is to copy a
327 latitude/longitude coordinate pair, such as the one shown on most
328 geocaches, and paste it into an active TrackWaypoint layer. &appname; can
329 automatically recognize several variations of the lat/lon format.
332 By right-clicking tracks and waypoints in the layers panel, you can do
333 many things with tracks and waypoints. You can easily find a specific
334 track or waypoint by expanding the Tracks or Waypoints sublayers in the
335 layers panel to show all tracks or waypoints, and typing the name of
339 <section><title>Layer Operations</title>
341 The layer has a context menu with several operations.
344 <section><title>View Layer</title>
346 Version1.1+: This will automatically move the viewport and select the best zoom level to see the whole layer (i.e. tracks and waypoints).
350 <section><title>View All Tracks</title>
352 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 waypoints).
356 <section><title>View All Waypoints</title>
358 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).
362 <section><title>Goto Center of Layer</title>
364 This will automatically move the viewport to see the whole layer (i.e. tracks and waypoints). It does not adjust the zoom level.
368 <section><title>Goto Waypoint</title>
370 This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it.
374 Note this search is not very clever and only finds exact matches.
375 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.
380 <section><title>Export Layer</title>
382 The layer (all tracks and waypoints) can be exported to a file GPX, GPSPoint, GPSMapper or Google's KML format.
385 Version1.1+: An individual track can be exported to a GPX file via the track menu.
389 <section id="new_wp"><title>New Waypoint</title>
391 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.
395 <section><title>Add Wikipedia Waypoints</title>
397 This gets 'interesting' points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary.
401 <section><title>Geotag Images</title>
403 This starts the Geotagging Images dialog against all tracks in the layer.
404 See <link linkend="geotagging">Geotagging</link> for further detail.
408 <section id="osm_upload"><title>Upload To OSM</title>
410 This opens a dialog to upload all tracks and waypoints to <ulink url="http://openstreetmap.org/">OpenStreetMap</ulink> traces.
411 Useful if you are an OpenStreetMap contributor (you will need an OpenStreetMap account), these details can be stored in &appname; <link linkend="prefs_osm">preferences.</link>
414 &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.
418 <emphasis role="bold">Warning!</emphasis>
419 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.
421 <para>Currently &appname; does not support the <ulink url="http://oauth.net/">OAuth</ulink> mechanism.</para>
425 <section><title>Filter</title>
426 <section><title>Simplify All Tracks</title>
428 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.
431 <section><title>Remove Duplicate Waypoints</title>
433 Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer.
437 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.
443 <section id="filter_with_track"><title>Filter With <emphasis>Trackname</emphasis></title>
445 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:
448 <listitem><para>Waypoints Inside This</para></listitem>
449 <listitem><para>Waypoints Outside This</para></listitem>
452 The result is generated in a new Track/Waypoint layer.
456 <section><title>Geotag Images</title>
458 This starts the Geotagging Images dialog using the specific track.
459 See <link linkend="geotagging">Geotagging</link> for further detail.
463 </section><!-- End TRW Layer Options -->
465 <section><title>Track Properties</title>
467 Show many useful statistics about a track, including a
468 elevation-distance graph and a speed-time graph (if data is available).
469 You can click these graphs to jump to the point in the track. You can
470 also reverse a track, delete duplicates, and split a track from its
471 component segments (discontinuous breaks in a track) into separate
475 The following colors are used in the elevation-distance graph:
479 <term>'Main' colour - this is dependent on your Desktop theme - often blue by default</term>
480 <listitem><para>elevation data in graph</para></listitem>
485 <para>no elevation data</para>
491 <para>elevation data from DEM</para>
504 <section><title>Track Operations</title>
506 <section><title>Goto</title>
508 This centers the viewport on the selected position on the track:
511 <listitem><para>Startpoint</para></listitem>
512 <listitem><para>"Center" - the notional center from the bounds of the track</para></listitem>
513 <listitem><para>Endpoint</para></listitem>
514 <listitem><para>Version1.1+: Highest Altitude</para></listitem>
515 <listitem><para>Version1.1+: Lowest Altitude</para></listitem>
516 <listitem><para>Version1.1+: Maximum Speed</para></listitem>
520 <section><title>View</title>
522 Version1.1+: This centers the viewport on the track and selects the best zoom level to see it.
526 <section><title>Combine</title>
527 <section><title>Merge By Time</title>
529 This operation repeatedly tries to merge the right-clicked track
530 with tracks in the same TrackWaypoint layer. The tracks which are
531 merged are those which have at least one trackpoint less than some
532 threshold time away. This way, if you somehow end up with lots of small
533 segments (say, caused by turning the GPS on and off) you can merge them
534 easily into one track.
538 <section><title>Merge With Other Tracks</title>
540 This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with.
544 <section><title>Merge Segments</title>
546 Combines track segments. Effectively removing track segment markers to leave one segment for the whole track.
550 <section><title>Append Track</title>
552 Enable joining of a single track to the end of the current track.
553 This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection.
558 <section><title>Split</title>
559 <section><title>Split By Time</title>
561 This operation will split a single track into segments wherever the
562 time interval between successive trackpoints is larger than some
563 threshold. This is useful when processing raw NMEA GPS data, especially
564 taken over a long time.
568 <section><title>Split By Number of Points</title>
570 Version1.2+: This operation will split a single track into segments by the number of points specified.
571 This can be useful with devices which may have limits on the number of points it supports.
575 <section><title>Split Segments</title>
577 Splits track segments into new tracks.
581 <section><title>Split at Trackpoint</title>
583 Splits the track at the currently selected trackpoint. This is only enabled when a trackpoint is selected.
588 <section><title>Delete Points</title>
589 <section><title>Delete Points With the Same Position</title>
591 Deletes subsequent points that have the same position (but have different timestamps).
594 <section><title>Delete Points With the Same Time</title>
596 Deletes subsequent points that have the same time stamp (but may have different positions).
602 <section><title>Apply DEM data</title>
604 If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
608 <section><title>Export Track as GPX</title>
610 Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog.
614 <section><title>Extend Track End</title>
616 Changes the current tool to add trackpoints to the end of the track.
621 <section><title>Extend Using Route Finder</title>
623 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 Google's route service and applied to the track.
628 <section><title>Upload to OSM</title>
630 Same as the layer <link linkend="osm_upload">Upload to OSM</link> command, but only applies to the track.
634 <section><title>Use With Filter</title>
636 This selects the track to be used in the <link linkend="filter_with_track">Filter With <emphasis>Trackname</emphasis></link> feature.
641 <section><title>View Google Directions</title>
643 This option is only available on a track created using the Route Finder tool.
646 Launch a web browser to see the Google directions page which yielded the route.
650 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.
655 </section><!-- End Track Options -->
657 <section><title>Waypoint Properties</title>
660 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).
663 If the waypoint has an associated image, then the Geotag information may be updated, either with updating the file's modification timestamp or not.
664 This can be useful when the waypoint has been moved.
667 </section><!-- WP Prop END -->
669 <section><title>Waypoint Operations</title>
671 <section><title>Goto</title>
673 This centers the viewport on the selected waypoint.
677 <section><title>Visit Geocache Webpage</title>
679 If the waypoint's name is in Geocache form (GCXXXXX) you can launch a web browser to go to the Geocache page.
683 <section><title>New Waypoint</title>
685 Same as the layer <link linkend="new_wp">New Waypoint</link>.
689 </section><!-- WP END -->
691 <section id="geotagging"><title>Version1.3+: Geotag Images</title>
693 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.
696 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.
700 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.
704 Various options allow control of how the geotagging process is performed:
707 <listitem><para>Images - Add the images used for geotagging</para></listitem>
708 <listitem><para>Create Waypoints</para></listitem>
709 <listitem><para>Overwrite Existing Waypoints</para></listitem>
710 <listitem><para>Write EXIF</para></listitem>
711 <listitem><para>Overwrite Existing GPS Information</para></listitem>
712 <listitem><para>Interpolate Between Track Segments</para></listitem>
713 <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>
714 <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>
718 </section><!-- TRW Layer END -->
720 <section id="gps_layer"><title>GPS Layer</title>
722 The GPS layer is responsible for uploading and downloading GPS data
723 from a GPS device. It also is responsible for realtime GPS tracking.
724 Expand the GPS layer in the layers panel to see the two TrackWaypoint layers it
725 uses for uploading and downloading. To upload, download, or use
726 realtime tracking, right-click the GPS layer and click the appropiate
730 <section><title>Download</title>
732 To download data from the GPS, right-click the GPS layer and click <guimenuitem>Download from GPS</guimenuitem>.
736 <section><title>Upload</title>
738 To upload data to the GPS, first populate the GPS Upload child
739 layer of the GPS layer (either by creating waypoints/tracks in it, or
740 copying and pasting or dragging waypoints/tracks from another layer).
741 Then right-click the GPS layer and click <guimenuitem>Upload to GPS</guimenuitem>.
745 <section><title>Realtime Tracking</title>
747 You must set up gpsd correctly or use a GPSD server and put the
748 correct information in the GPS layer properties dialog. Then right-click
749 the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
753 <section><title>Empty <emphasis>Item</emphasis></title>
755 There are several options to quickly delete a subsection of data:
758 <listitem><para>Empty Realtime</para></listitem>
759 <listitem><para>Empty Upload</para></listitem>
760 <listitem><para>Empty Download</para></listitem>
761 <listitem><para>Empty All</para></listitem>
765 </section><!-- End GPS -->
767 <section><title>DEM (Digital Elevation Model) Layer</title>
769 This layer provides elevation data from the <ulink url="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission (SRTM)</ulink>
772 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]
775 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.
778 The current data server is: <ulink url="http://dds.cr.usgs.gov/srtm/version2_1/">NASA STRM 2.1</ulink>.
781 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.
785 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"
789 </section><!-- End DEM -->
792 <section><title>Maps Layer</title>
794 This layer provides a single map resource, you may have multiple map layers but only top one (if enabled) will be visible.
795 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.
798 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 - 'Tile Age' 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.
801 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:
804 <listitem><para>Bing Bird's Eye (Aerial) Maps (&appname; Version1.2+)</para></listitem>
805 <listitem><para>Terraserver Topos</para></listitem>
806 <listitem><para>Terraserver Aerials</para></listitem>
807 <listitem><para>Terraserver Urban Areas</para></listitem>
808 <listitem><para>OpenStreetMap (Mapquest) - This is the default (&appname; Version1.3+)</para></listitem>
809 <listitem><para>OpenStreetMap (Mapnik)</para></listitem>
810 <listitem><para>OpenStreetMap (Cycle)</para></listitem>
811 <listitem><para>OpenStreetMap (Transport) (&appname; Version1.3+)</para></listitem>
812 <listitem><para>NASA BlueMarble</para></listitem>
813 <listitem><para>SpotMap (&appname; Version1.1+)</para></listitem>
817 &appname; can be configured to handle additional maps. See <link linkend="extend_viking">Extending &appname;</link> for further detail.
820 <section><title>Layer Operations</title>
821 <section><title>Download Missing Onscreen Maps</title>
823 This requests map tiles for areas of the viewport that do not currently have one.
827 <section><title>Download New Onscreen Maps</title>
829 This requests map tiles only if the maps are older than the Tile Age preference.
833 <section><title>Reload All Onscreen Maps</title>
835 Force a refresh of all visible map tiles.
841 </section><!-- End Maps -->
843 <section><title>Aggregrate Layer</title>
845 This layer is a container layer to hold other layers. There is always an initial and controlling 'Top Layer' that can not be removed, although it can be renamed.
848 This layer type is useful for grouping other layers, especially TrackWaypoint layers, in whatever categories are relevant to you: such as by activity, location or date.
849 Here are some suggestions:
851 <listitem><para>Hiking</para></listitem>
852 <listitem><para>Mountain Biking</para></listitem>
853 <listitem><para>Road Cycling</para></listitem>
854 <listitem><para>Car Trips</para></listitem>
855 <listitem><para>Sailing</para></listitem>
856 <listitem><para>Holidays</para></listitem>
857 <listitem><para>UK Points of Interest</para></listitem>
858 <listitem><para>USA Points of Interest</para></listitem>
859 <listitem><para>etc...</para></listitem>
863 Thus one can have a list of all your tracks, but groups can be shown or not using the relevant layers visibility checkbox.
867 This layer only has one operation: <guilabel>New Layer</guilabel>
870 <section><title>New Layer</title>
872 Add a new layer of the selected type.
876 </section><!-- End Agg -->
878 <section><title>GeoRef Layer</title>
880 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.
882 <section><title>Layer Operations</title>
883 <section><title>Zoom to Fit Map</title>
885 Automatically set a zoom level to see the entire map coverage.
889 <section><title>Goto Map Center</title>
891 Center the viewport on this map.
895 <section><title>Export to World File</title>
897 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>.
902 </section><!-- End GeoRef -->
904 <section><title>Coord Layer</title>
906 This layer is allows drawing of grid lines on the viewport.
908 </section><!-- End Coord -->
912 <section><title>Tools</title>
914 You can use the scroll wheel and the right-click to zoom and pan no matter what tool you are using.
917 Scroll: zoom in and out keeping the mouse over same location
920 Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down)
923 Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right)
926 Ctrl-shift-scroll: zoom in and out, without changing the center (also Ctrl+, Ctrl- [*not* KeyPad +/-])
929 Left or Middle-click: make the clicked point on the map the center
932 Middle-click and drag: pan
935 <section><title>Pan</title>
937 Pan moves the viewpoint. A single click centers the viewport at that point, whereas click and drag dynamically moves the view around.
938 This is the default tool.
941 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+P</keycap>
945 <section><title>Zoom</title>
947 Zooms in and out on the clicked part of the map or by the selected area.
950 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+Z</keycap>
953 Ctrl + left or right click: Zoom in/out and center the map on the clicked location
956 Shift (and hold) + left mouse button: Draws a bounding box area on which to zoom in. The zoom action is performed when the left mouse button is released.
960 <section><title>Ruler</title>
962 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.
963 A second click will 'freeze' the ruler at that point.
966 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+U</keycap>
970 <section id="select"><title>Version1.1+: Select</title>
972 The select tool allows one to choose any waypoint or track by clicking on it (or reasonably near) in the viewpoint.
975 ATM to select a track one must actually click on a trackpoint, which is also selected.
978 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+S</keycap>
982 <section><title>TrackWaypoint Layer Tools</title>
984 You must have a TrackWaypoint Layer selected to use these tools.
986 <section><title>Create Waypoint</title>
988 Left click will open the new waypoint dialog using the specified position.
992 <section><title>Create/Begin Track</title>
994 Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track.
995 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
996 Right click or <keycap>Backspace</keycap>: undo one point.
999 Double click or <keycap>Escape</keycap>: finish track creation.
1003 <section><title>Edit Waypoint</title>
1005 Left Click/drag: select/move a waypoint.
1006 If <keycap>Ctrl</keycap> is held at the same time, it will jump the waypoint position to a nearby existing trackpoint.
1007 If <keycap>Shift</keycap> is held at the same time, it will jump the waypoint position to a nearby existing waypoint.
1009 <para>Right-click on waypoint: opens a menu with waypoint actions (the
1010 same menu accessed by right-clicking the waypoint in the layers panel)
1014 <section><title>Edit Trackpoint</title>
1016 Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint.
1017 Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint.
1018 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1021 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.
1025 <section><title>Show Picture</title>
1027 Opens an image viewer with the picture associated with the waypoint.
1028 By default this uses the default system image viewer.
1029 For Linux you can override this with the setting in the <link linkend="prefs_external">preferences.</link>
1034 <section><title>Route Finder</title>
1035 <para>Creates a track using Google maps routing between two points.
1036 Requires an internet connection. Click one point, then click another to
1040 Right-click: undo last routing (only track removed - not any waypoints)
1043 <keycap>Ctrl</keycap>: continue previous track
1049 <section><title>Georef Map Layer Tools</title>
1051 You must have a Georef Map Layer selected to use these tools.
1053 <section><title>Georef zoom</title>
1054 <para>Changes the zoom level of the georeferenced map and changes the
1055 &appname; zoom level accordingly. Useful if you are trying to match GPS
1056 data to a georeferenced map.
1060 <section><title>Georef move</title>
1062 Drag to move the georeferenced map.
1067 <section><title>Map Download</title>
1069 You must have a Map Layer selected to use this.
1072 Click to download a single tile. Drag to download tiles in the dragged rectangle area.
1075 Right-click to redownload bad/all tiles. Right-click and drag to redownload bad/all tiles in the dragged rectangle area.
1079 <section><title>DEM Download</title>
1081 You must have a DEM Layer selected to use this.
1084 Click to download and import a DEM file.
1088 <section><title>Webtools</title>
1090 Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
1093 Jumping from &app; to such service can become annoying.
1096 &appname; allows you to open such service directly at the position currently viewed in &app;.
1099 This feature is called <guilabel>Webtools</guilabel>. It is also known as External Tools.
1105 <!-- Preferences -->
1106 <section id="prefs"><title>Preferences</title>
1107 <section><title>General</title>
1108 <section><title>Localisation</title>
1109 <para>You can select units displayed by &appname; to best fit your usage.</para>
1111 <title>Properties dialog: units part</title>
1113 <graphic format="PNG" fileref="figures/properties_units.png"/>
1116 <para>Concerning degrees, you can select the way to display them:
1119 <term>DDD</term><listitem><para>decimal degree</para></listitem>
1122 <term>DMM</term><listitem><para>partial sexagesimal display: degrees, minutes and decimal part of minutes</para></listitem>
1125 <term>DMS</term><listitem><para>sexagesimal display: degrees, minutes and seconds</para></listitem>
1130 <title>Properties dialog: degree display options</title>
1132 <graphic format="PNG" fileref="figures/properties_degree.png"/>
1136 <section><title>Waypoint Icon Size</title>
1137 <para>An option exists to control the icon (symbol) size used for waypoints
1140 <section><title>'Home' Default Location: Latitude and Longitude</title>
1141 <para>You can set the 'Home' location directly by inputting the latitude and longitude in decimal degrees.
1144 <section><title>Tile's age</title>
1145 <para>This age is used to decided wether or not a new request to tile server must be done.
1147 <para>Changing this value, you will increase or decrese the network load.</para>
1149 <section><title>Default maplayer directory</title>
1150 <para>This property sets the default directory of the tiles cache.
1151 This value is used when you create a new map layer.
1153 <para>You are still able to change this value in each map layer properties.</para>
1155 <section><title>Map Cache Memory Size</title>
1156 <para>This controls the amount of maps that are stored in memory, rather than having to reread from disk.
1157 Generally if you have a system with lots of memory it's recommended to increase this value.
1162 <section id="prefs_external"><title>Export/External</title>
1163 <section><title>KML Export Units</title>
1164 <para>Allows setting the units used when saved as the KML file type, such as Metric or Statue units</para>
1166 <section><title>Image Viewer (Not Windows)</title>
1167 <para>Allows setting the program used to view images associated with Waypoints.</para>
1168 <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>
1169 <para>Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.</para>
1171 <section><title>External GPX programs</title>
1172 <para>Allows setting the programs invoked via the TrackWaypoint Layer -> Export Layer -> Open With 'program'</para>
1173 <para>Two options are given so that it can be configured for various uses such as:</para>
1175 <listitem><para>An OSM editor (default)</para></listitem>
1176 <listitem><para>Some other user defined program</para></listitem>
1181 <section id="prefs_osm"><title>OpenStreetMap Traces</title>
1182 <section><title>OSM Username + Password</title>
1183 <para>Store your OSM details here, so that you don't need to enter it in every time in the <link linkend="osm_upload">Upload to OSM</link> procedure.</para>
1186 Your OSM password will be stored in plain text.
1195 <section><title>Howto's</title>
1196 <section id="howto_start"><title>Getting Started</title>
1198 To quickly get started using &appname;, follow these instructions.
1200 <section><title>Go to an area of interest</title>
1202 &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.
1205 <title>Method A</title>
1208 Use the online location address/place search.
1211 Use the <guibutton>Go to Location</guibutton> toolbar button or from the menus
1212 <menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>.
1213 You can change the search location provider if desired.
1214 Enter the name of place you wish to go to (you may need to specify the country to refine the search).
1215 Also you can enter a post code or a ZIP code instead.
1218 <para>You will need an internet connection for this search to work</para>
1223 <title>Method B</title>
1226 If you know the coordinates of where you want to view:
1229 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.
1234 <title>Method C</title>
1236 <para>Use the GPS Layer or <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
1237 to load data directly from your GPS into &appname;.
1239 <para>You can specify the types of data to acquire: Tracks and/or Waypoints.
1242 <para>You must have write permission to the port used. For <trademark>Unix</trademark> like OS:</para>
1244 <listitem><para>/dev/ttyS0 is the first serial port</para></listitem>
1245 <listitem><para>/dev/ttyUSB0 is the first USB port</para></listitem>
1246 <listitem><para>usb: is any USB port</para></listitem>
1248 <para>Depending on your distribution only one of the USB port types may work</para>
1249 <para>For <trademark>Windows</trademark>:</para>
1251 <listitem><para>com1: is the first serial port</para></listitem>
1252 <listitem><para>usb: is any USB port</para></listitem>
1256 <para>The GPS devices supported are those supported by <application>GPSBabel</application>.</para>
1257 <para>Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.</para>
1262 <title>Method D</title>
1265 Get data from files in GPX or KML format, which can be opened directly.
1266 Use <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice>
1269 Other formats can be imported that are supported by GPSBabel.
1270 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel...</guimenuitem></menuchoice>
1275 Expand Tracks or Waypoints. Right-click on the
1276 track or waypoint of interest and select <guimenuitem>Goto "Center"</guimenuitem>.
1281 <section><title>Add a map layer</title>
1283 1. Use Layers - New Map Layer, and choose a suitable cache directory
1284 where you would like to store your tracks and click <guilabel>OK</guilabel>. Zoom to a
1285 comfortable level (I suggest 4 mpp) by clicking the left and right
1286 mouse buttons on the gray area where your tracks are. Now from the menu
1287 choose Tools - Map Download, Click where you would like to download a
1288 map. Regardless of what tool you are using, the middle mouse button
1289 always pans. </para>
1292 You need an open internet connection when you are downloading maps.
1296 1. You will notice the maps are being drawn on top of the tracks, which
1297 is probably not what you want. Look at the Layers Panel to the left.
1298 Notice how the layer named Map is ABOVE your TrackWaypoint layer that
1299 your GPS data is in. This means that it will be drawn last, or on top
1300 of the other layers. Select the Map layer from the list and click the
1301 down arrow button beneath the list. Your tracks will now be drawn over
1305 <section><title>Set Your Home Location</title>
1307 You can save the current center position of the viewport as the default location AKA the Home Location by
1308 <menuchoice><guimenu>Edit</guimenu><guimenuitem>Set the Default Location</guimenuitem></menuchoice>.
1311 Then at any time you can return to this place by clicking on the <guibutton>Home</guibutton> icon on the toolbar.
1314 You can also set the default location via specifing the exact latitude and longitude in the <link linkend="prefs">Preferences</link>.
1319 <section><title>From 1st startup to GPS track (including offline maps)</title>
1321 The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
1322 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 'Stuttgart'.
1324 <section><title>Fetching the maps</title>
1326 <emphasis role="bold">Map</emphasis>
1329 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
1330 <step><para>in the layer properties dialogue choose e.g. <guilabel>OpenStreetMap (Mapnik)</guilabel>.</para></step>
1332 <para>For the moment, we keep the default <guilabel>Maps Directory</guilabel> (the directory in
1333 which the maps will be stored and can be used for offline usage).</para>
1336 <para>Check <guilabel>Autodownload maps</guilabel> and keep the zoom level as <guilabel>Use Viking
1337 Zoom Level</guilabel>.</para>
1340 however, that these settings will play an important
1341 role in the pre-fetch for offline usage discussed later
1346 <para>You'll see a map of Stuttgart. Using the mouse wheel, you can
1347 zoom in and out. The maps for the choosen resolution will be downloaded
1351 <emphasis role="bold">DEM Layer (Height Map)</emphasis>
1354 <step><para>Zoom out to 512.</para></step>
1355 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New DEM Layer</guimenuitem></menuchoice></para></step>
1356 <step><para>Keep the download source as is (SRTM Global 90m), hit <guilabel>OK</guilabel>.</para></step>
1359 <para>In the layer listing on the left, the DEM layer should reside
1360 above the map layer. If this is not the case, highlight the DEM layer
1361 an shift it one up (using the arrow up button).
1364 <step><para>highlight the DEM layer in the layer listing on the left</para></step>
1365 <step><para>in the toolbar, check DEM layer download/import (the last symbol)</para></step>
1366 <step><para>a left-click in the map window should then fetch the DEM data</para></step>
1369 This might take some time.
1372 Sometimes, a tile does not show up correctly (you might see only a
1373 black frame in the map window) because it got corrupted during
1374 transfer. In order to correct this, you can delete the corresponding
1375 datafile in the cache. <programlisting> right-click the DEM layer properties</programlisting>
1378 The <guilabel>DEM Files</guilabel> listing allows you to delete the specific tiles (alternatively do this from the command line).
1381 You can also alter the Min. and Max. elevation in this dialogue.
1385 <section><title>GPS Track with Height Profile</title>
1387 <step><para>Uncheck the DEM layer (the map is shown again)</para></step>
1389 <para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New TrackWaypoint Layer</guimenuitem></menuchoice></para>
1390 <para>Ensure the new track layer is above the map layer.</para>
1392 <step><para>Expand the TrackWaypoint layer, select <guimenuitem>Tracks</guimenuitem></para></step>
1393 <step><para>In the tools menu choose <guiicon><inlinegraphic fileref="figures/begintr_18.png"/></guiicon> <guibutton>Begin Track</guibutton>
1395 <step><para>Leftclick in the map window, enter a name</para></step>
1397 <para>Click several times to generate a track (a right-click removes the last point).</para>
1398 <para>Height data is set automatically since DEM data is available</para>
1400 <step><para>Expand tracks in the layer menu, your track should show up, select it</para></step>
1401 <step><para>Right click your track, select <guimenuitem>Properties</guimenuitem></para></step>
1402 <step><para>Click the tab <guilabel>Elevation-distance</guilabel> - enjoy the plot</para></step>
1405 In order to save this setting for later usage
1408 <step><para>click <guilabel>OK</guilabel> in the <guilabel>Track Properties</guilabel> dialog</para></step>
1409 <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>
1413 <section><title>Usecase: offline data for holiday</title>
1415 Suppose you want to have the map and DEM data offline for your holiday in Italy near Bologna.
1418 <step><para>Start a new &appname; session.</para></step>
1419 <step><para><menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter Bologna</para></step>
1420 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
1421 <step><para>Choose e.g. <guilabel>OpenStreetMap (mapnik)</guilabel>.</para></step>
1422 <step><para>adapt the <guilabel>maps directory</guilabel> e.g. to <filename>/home/user/.viking-map-holiday/</filename>.
1423 This allows you to delete the map stuff after holiday without purging the rest of your maps.
1425 <step><para>check <guilabel>autodownload map</guilabel></para></step>
1426 <step><para>keep <guilabel>viking zoom level</guilabel></para></step>
1427 <step><para>zoom out to 1024</para></step>
1428 <step><para>add a DEM layer (as discussed above)</para></step>
1429 <step><para>download the DEM data</para></step>
1431 <para>In the &app; version discussed here, the DEM data automatically
1432 are stored in <filename>/home/user/.viking-maps/</filename>. You can move the corresponding
1433 tiles into <filename>.viking-map-holiday/</filename> if you like.
1436 <emphasis role="bold">Download map data for all zoom levels</emphasis>
1439 <step><para>uncheck the DEM layer for the map to show up</para></step>
1440 <step><para>navigate the map to be centered at Bologna</para></step>
1441 <step><para>choose the zoom such, that all regions of interest are displayed in the map window (e.g. 1024)</para></step>
1443 <para>follow this sequence until you have all tiles for all zoom levels you need</para>
1445 <step><para>right-click the map layer properties</para></step>
1446 <step><para>set the zoomlevel explicitely one below the last (in the first cycle 512), hit OK</para></step>
1447 <step><para>right click the map layer <guimenuitem>Download Missing Onscreen Maps</guimenuitem></para></step>
1448 <step><para>wait until all tiles for that resolution have been downloaded</para></step>
1452 <para>This may take some time and some hard disk capacity.</para>
1454 Do not forget to save your configuration (as discussed above).
1460 <section><title>OpenStreetMap project</title>
1462 <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> is a collaborative project to create a free editable map of the world.
1463 One of sources of data for this project is GPS tracks.
1464 &appname; supports this project via the GPS Traces methods, both uploading and downloading such data.
1466 <section><title>Uploading data to OpenStreetMap</title>
1468 It is possible to upload data directly from &appname; to OpenStreetMap.
1471 <title>Upload a layer</title>
1473 One solution is to upload whole a TrackWaypoint layer. To do this,
1474 simply select the layer and right click on it. Then, select <guimenuitem>Upload to
1479 <title>Upload a single track</title>
1480 <para>One solution is to upload whole a TrackWaypoint layer. To do
1481 this, simply select the layer and right click on it. Then, select
1482 <guimenuitem>Upload to OSM</guimenuitem>.
1486 <title>Fill in the form</title>
1488 In both cases, &appname; will retain some information.
1489 The email field is the email you used to subscribed into OpenStreetMap.
1490 The password field is the password you used with this account.
1491 The filename is the name you want your upload has on the server. This information is displayed by the osm server.
1492 The description is some descriptive information.
1493 The tags field is a white separated list of tag.
1497 <section><title>Downloading traces from OpenStreetMap</title>
1499 It is possible to download GPS traces directly from OpenStreetMap into &appname;.
1500 This feature can be really useful for checking existing data before uploading new ones.
1503 <title>Download all visible tracks</title>
1504 <para>One solution is to select
1506 <guimenu>File</guimenu>
1507 <guisubmenu>Acquire</guisubmenu>
1508 <guimenuitem>OSM traces...</guimenuitem>
1510 Each request can get up to 5,000 points.
1511 The dialog box allows setting which group of 5,000 points to get. These groups are known as 'Page Numbers' which start at 0.
1512 Increasing the page number parameter allows one to request the subsequent sets of point groups.
1513 See <ulink url="http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces"/> for further detail.
1519 <section><title>Geotagging</title>
1521 This assumes you already have a map layer enabled for ease of use (if not see above to get one).
1523 <section><title>Manual Positioning</title>
1525 This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
1526 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.
1527 ATM this process only works on an individual image, so it will be tedious for handling lots of images.
1530 First create a Track Waypoint layer or use an existing one; and select it in the Layers Panel.
1531 NB Make sure this layer is above the map layer in the Layers Panel list.
1532 Create a new waypoint (or move an existing one) to exact location desired:
1534 <listitem><para>Select the New Waypoint 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>
1535 <listitem><para>Select the <link linkend="select">Select Tool</link>, then left click on waypoint to be moved. Left click again and drag the waypoint to the location desired</para></listitem>
1537 Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
1538 <menuchoice><guimenu>Update Geotag on Image</guimenu><guisubmenu>Update</guisubmenu></menuchoice>
1541 The <guilabel>Update Geotag on Image</guilabel> options are only available when a waypoint has an image associated with it.
1545 <section><title>Automatic Positioning Against a Tracklog</title>
1547 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 -
1548 see <link linkend="howto_start">Getting Started</link>.
1549 It helps if this is the track that was recorded at the time you took some photographs!
1552 Select the track either from the layers panel on the left or via the viewport using the <link linkend="select">Select Tool</link>.
1553 Then right click on it and chose the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> leading you to the <link linkend="geotagging">Geotagging Dialog</link>.
1556 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.
1557 If things are succesful, new waypoints with thumbnail images of the photographs will appear.
1558 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.
1560 <formalpara><title>Option: Overwrite Waypoints</title>
1562 This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
1563 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).
1567 If you have multiple tracks in a TrackWaypoint layer, then invoking the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> action on the layer
1568 will search all the tracks to find location matches.
1573 <section><title>GPS Real Time Location (Not <trademark>Windows</trademark>)</title>
1575 &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.
1576 Unfortunately <application>gpsd</application> is not available on <trademark>Windows</trademark>,
1577 so currently this functionality is disabled in <trademark>Windows</trademark> builds of &appname;
1580 This assumes you already have a map layer enabled for ease of use (if not see above to get one).
1583 Turn on the GPS Device, ensure it has figured out it's location and plug it in to your computer.
1585 <section><title>Set Up GPS Layer</title>
1587 You will need a <link linkend="gps_layer">GPS Layer</link>. One can be added via <menuchoice><guimenu>Layers</guimenu><guisubmenu>Add GPS Layer</guisubmenu></menuchoice>.
1590 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.
1593 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.
1596 Then right-click the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
1597 Hopefully the viewport should jump to the GPS location.
1600 Troubleshooting checklist:
1602 <procedure><step><para>Confirm <application>gpsd</application> is running.</para></step></procedure>
1603 <procedure><step><para>Confirm on the GPS device it has a location.</para></step></procedure>
1604 <procedure><step><para>Confirm the <emphasis>Realtime Tracking Mode</emphasis> settings.</para></step></procedure>
1608 <section id="extend_viking">
1609 <title>Extending Viking</title>
1611 <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>
1612 <para>Here is an example:
1613 <programlisting><![CDATA[
1615 <object class="ClassName">
1616 <property name="property_name1">Property value</property>
1617 <property name="property_name2">Property value</property>
1624 <para>You can find more examples in the documentation part of the distribution.</para>
1626 <title>Map Source</title>
1627 <para>It is possible to add new map's sources. The file is <filename>~/.viking/maps.xml</filename> for <trademark>UNIX</trademark> like systems and <filename>C:\Documents and Settings\<replaceable>username</replaceable>\.viking\maps.xml</filename> on <trademark>Windows XP</trademark>.</para>
1628 <para>An example of the file is in the distribution <filename>doc/examples/maps.xml</filename>. Further examples and values are online in the <ulink url="http://sourceforge.net/apps/mediawiki/viking/index.php?title=Maps">Maps Wiki</ulink></para>
1630 <para>The VikSlippyMapSource allows to declare any map's source working like OpenStreetMap. It supports the following properties:
1634 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
1638 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
1641 <term>hostname</term>
1642 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
1646 <listitem><para>the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for X, Y and Z (zoom level) (eg. "/%d/%d/%d.png")</para></listitem>
1650 <para>The VikTmsMapSource allows to declare any TMS service. It supports the following properties:
1654 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
1658 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
1661 <term>hostname</term>
1662 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
1666 <listitem><para>the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for X, Y and Z (zoom level) (eg. "/%d/%d/%d.png")</para></listitem>
1670 <para>The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties:
1674 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
1678 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
1681 <term>hostname</term>
1682 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
1686 <listitem><para>the parametrized address of the tile, in the spirit of C printf format, with 4 "%s" fields for bounding box coordinates (eg. "/coord=%s,%s,%s,%s")</para></listitem>
1693 <title>Go-to search engines</title>
1694 <para>It is possible to add new new search engines for the "Go-To" feature. The file is <filename>~/.viking/goto_tools.xml</filename>.</para>
1695 <para>An example of the file in the distribution <filename>doc/examples/goto_tools.xml</filename>.</para>
1696 <para>Currently, there is a single object class available: VikGotoXmlTool. Such feature allows to declare any search engine using a XML format as result.</para>
1697 <para>The related properties are:
1701 <listitem><para>the text displayed in the <guilabel>Go-To</guilabel> dialog</para></listitem>
1704 <term>url-format</term>
1705 <listitem><para>the parametrized address of the query, in the spirit of C <function>printf</function> format, with a single "%s" field (replaced by the query string)</para></listitem>
1708 <term>lat-path</term>
1709 <listitem><para>XML path of the latitude (eg. <literal>/root/parent/elem</literal>)</para></listitem>
1712 <term>lat-attr (optional)</term>
1713 <listitem><para>name of the attribute (of previous element) containing the latitude</para></listitem>
1716 <term>lon-path</term>
1717 <listitem><para>XML path of the longitude (eg. <literal>/root/parent/elem</literal>)</para></listitem>
1720 <term>lon-attr (optional)</term>
1721 <listitem><para>name of the attribute (of previous element) containing the longiude</para></listitem>
1725 <para>As a facility (or readability) it is possible to set both path and attribute name in a single property, like an XPath expression. To do so, simply set both info in lat-path (or lon-path) in the following format: <literal>/root/parent/elem@attribute</literal>.</para>
1729 <title>External tools</title>
1730 <para>It is possible to add new external tools. The file is <filename>~/.viking/external_tools.xml</filename>.</para>
1731 <para>An example of the file in the distribution <filename>doc/examples/external_tools.xml</filename>.</para>
1732 <para>The VikWebtoolCenter allows to declare any Webtool using a logic based on center coordinates and zoom level value.</para>
1733 <para>The related properties are:
1737 <listitem><para>this is an integer and should be unique as it used to identify the tool</para></listitem>
1741 <listitem><para>the text displayed in the menu entry</para></listitem>
1745 <listitem><para>the parametrized URL to open, in the spirit of C printf format, with 2 "%s" and a "%d" fields for X, Y and Z (zoom level) (eg. "http://hostname/?lat=%s&lon=%s&zoom=%d")</para></listitem>
1749 <para>The VikWebtoolBounds allows to declare any Webtool using a logic based on bounds coordinates.</para>
1750 <para>The related properties are:
1754 <listitem><para>this is an integer and should be unique as it used to identify the tool</para></listitem>
1758 <listitem><para>the text displayed in the menu entry</para></listitem>
1762 <listitem><para>the parametrized address of the tile, in the spirit of C printf format, with 4 "%s" fields for left, right, bottom and top (eg. "http://hostname:8111/load_and_zoom?left=%s&right=%s&bottom=%s&top=%s")</para></listitem>
1770 <para>Note that, on <trademark>UNIX</trademark> like systems, the extension files (<filename>maps.xml</filename>, <filename>goto_tools.xml</filename>, <filename>external_tools.xml</filename>) are also searched in <filename>/etc/viking</filename> and <filename>/usr/share/viking</filename> directories (or related in your system).</para>
1771 <para>The <envar>XDG_DATA_DIRS</envar> environment variable can be used to change these directories.</para>
1772 <para>The <envar>XDG_DATA_HOME</envar> environment variable s also used (if set) to look for these extension files.</para>
1777 <section><title>What to Do if &appname; Does Not Seem to Work</title>
1779 In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
1780 <programlisting>viking -dV</programlisting>
1783 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.
1784 E.g. Something like this for DEMs:
1786 ** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
1787 * About to connect() to dds.cr.usgs.gov port 80 (#0)
1788 * Trying 152.61.128.95... * connected
1789 * Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
1790 GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
1791 User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
1792 Host: dds.cr.usgs.gov
1795 Date: Sun, 26 Jul 2009 18:13:38 GMT
1797 Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
1798 ETag: eac3f8-1828f5-46f3caa76070a
1799 Accept-Ranges: bytes
1800 Content-Length: 1583349
1801 Content-Type: application/zip
1803 * Connection #0 to host dds.cr.usgs.gov left intact
1804 * Closing connection #0
1805 ** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
1807 Or for OSM Mapnik tile server:
1809 * About to connect() to tile.openstreetmap.org port 80 (#0)
1810 * Trying 193.63.75.28... * connected
1811 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
1812 GET /13/4065/2748.png HTTP/1.1
1813 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
1814 Host: tile.openstreetmap.org
1817 * HTTP 1.0, assume close after body
1819 Date: Thu, 14 Oct 2010 22:18:42 GMT
1820 Server: Apache/2.2.8 (Ubuntu)
1821 ETag: "b66ff9d46474bab68262a3483428a232"
1822 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
1823 Content-Length: 17194
1824 Cache-Control: max-age=94805
1825 Expires: Sat, 16 Oct 2010 00:38:47 GMT
1826 Content-Type: image/png
1828 X-Cache: HIT from konqi.openstreetmap.org
1829 X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
1830 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
1833 * Closing connection #0
1834 * About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
1835 * Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
1836 * About to connect() to tile.openstreetmap.org port 80 (#0)
1837 * Trying 193.63.75.28... * connected
1838 * Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
1839 GET /tiles/cycle/13/4065/2747.png HTTP/1.1
1840 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
1841 Host: a.andy.sandbox.cloudmade.com
1845 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
1846 GET /13/4065/2749.png HTTP/1.1
1847 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
1848 Host: tile.openstreetmap.org
1851 * HTTP 1.0, assume close after body
1853 Date: Thu, 14 Oct 2010 23:44:35 GMT
1854 Server: Apache/2.2.8 (Ubuntu)
1855 ETag: "8e520ad47ce9c1b63430554886eb5fab"
1856 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
1857 Content-Length: 18094
1858 Cache-Control: max-age=87742
1859 Expires: Sat, 16 Oct 2010 00:06:57 GMT
1860 Content-Type: image/png
1861 X-Cache: MISS from konqi.openstreetmap.org
1862 X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
1863 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
1871 <section><title>Dependencies</title>
1872 <formalpara><title>gpsbabel</title>
1873 <para>&appname; uses <ulink url="http://gpsbabel.org/">GPSBabel</ulink> to convert data.</para>
1875 <formalpara><title>unbuffer (optional)</title>
1876 <para>&appname; uses unbuffer command to optimize conversion calls.</para>
1878 <formalpara><title>gpsd (optional - but not <trademark>Windows</trademark>)</title>
1879 <para>&appname; can use <ulink url="http://www.catb.org/gpsd/">gpsd</ulink> to get the current location.</para>