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 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>:
184 <section><title>General Concepts</title>
185 <section><title>Layers</title>
187 'Layers' is concept one may know from powerful graphics editors such as <application>Photoshop</application> or <application>GIMP</application>.
188 Instead of putting all the data on the same level, it is stacked (i.e. layered) with different data over one another.
189 This can be useful for analysis and general handling of various sets of data.
192 Unfortunately the downside of this complexity is remembering how differing layers of data can obscure other data.
195 The Map layers have <ulink url="http://en.wikipedia.org/wiki/Alpha_compositing"><citetitle>Alpha Compositing</citetitle></ulink>,
196 to create the appearance of partial transparency.
197 By controlling this value one can see data below it in the layer heirarchy for interesting effects.
200 <section><title>Layers Panel</title>
202 The panel on the left is called the <emphasis role="bold">layers panel</emphasis>.
203 It determines which layers and sublayers (such as tracks and waypoints)
204 are shown, and the order in which they are drawn. Layers list on the
205 top of the layers panel are drawn last. You can change the order by
206 drag and drop, or by selecting a layer and using the up and down
207 buttons at the bottom of the layers panel.
210 <section><title>Viewport</title>
212 The main &appname; area where the layer data is drawn, is called the <emphasis role="bold">viewport</emphasis>.
215 <section><title>Statusbar</title>
216 <para>This provides a readout of various information:</para>
218 <listitem><para>The currently selected (mouse pointer) tool</para></listitem>
219 <listitem><para>The number of items to process in the background - normally this the number in the map tile download queue</para></listitem>
220 <listitem><para>The zoom factor</para></listitem>
221 <listitem><para>The location of the mouse pointer (and potentially height information if DEM data is available)</para></listitem>
225 <section><title>Projections</title>
227 &appname; supports differents projections:
233 <para>LatLon (also called EPSG:4326)</para>
236 <para>Mercator (also called Spherical Mercator)</para>
242 <section><title>Map Cache</title>
244 &appname; stores downloaded map tiles to disk for a couple of reasons:
247 <listitem><para>Enables off line usage</para></listitem>
248 <listitem><para>Reduces loading on the map tile provider</para></listitem>
251 The &appname; automatic caching strategy is two fold:
256 If the age of the tile on disk is less than the specified tile age in the <link linkend="prefs_osm">preferences</link>,
257 it will <emphasis>not</emphasis> attempt to contact the server to get a new version of the tile.
262 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.
267 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.
271 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>)
276 <section id="shortcut_keys"><title>Shortcut Keys</title>
278 &appname; has several shortcut keys or key combinations for commands as listed in the main window along side the command.
281 Some function keys follow standard GUI behaviour:
284 <listitem><para><keycap>F1</keycap> Help (view this manual)</para></listitem>
285 <listitem><para><keycap>F5</keycap> or <keycap>Ctrl+R</keycap> Refresh the maps on screen</para></listitem>
286 <listitem><para><keycap>F10</keycap> Select the Menubar (in built behaviour)</para></listitem>
287 <listitem><para><keycap>F11</keycap> Full Screen</para></listitem>
288 <listitem><para><keycap>Ctrl+F5</keycap> or <keycap>Ctrl+Shift+R</keycap> Redownload the maps on screen</para></listitem>
292 Refresh attempts to get new maps only if the local tile cache time period has expired for any particular map tile.
293 Redownload gets all on screen maps from the server, ignoring the local tile cache.
297 Other function keys control turn on/off visibility of various elements:
300 <listitem><para><keycap>F3</keycap> Toggle visibility of the Toolbar</para></listitem>
301 <listitem><para><keycap>F4</keycap> Toggle visibility of the Menubar</para></listitem>
302 <listitem><para><keycap>Shift+F5</keycap> Toggle visibility of the Scale indicator on the viewport</para></listitem>
303 <listitem><para><keycap>F6</keycap> Toggle visibility of the Center Crosshairs on the viewport</para></listitem>
304 <listitem><para><keycap>F7</keycap> Toggle showing selected items (e.g. tracks or waypoints) in the highlight colour in the viewport</para></listitem>
305 <listitem><para><keycap>F9</keycap> Toggle visibility of the Layers Panel</para></listitem>
306 <listitem><para><keycap>F12</keycap> Toggle visibility of the Statusbar</para></listitem>
309 Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exitting.
310 Then there are shortcuts specific to &appname; to switch projection modes, zoom in/out, create layers and switch the active tool mode.
311 For these combinations see the menu entry themselves.
315 <section><title>Tracks vs Routes</title>
317 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.
320 Q. When planning a 'route' what difference does it make if it's a route or a track?
323 A. One difference is in how a GPS device navigates following the route or track.
324 Or you may want to consider interoperability with other software.
325 Otherwise it is probably best to use tracks as they are a superset of the route functionality.
328 For example on Garmin Etrex:
332 <para>Route following: Uses navigation mode with compass and estimated time to next point.</para>
333 <para>If following on road it can calculate a route on fly.</para>
334 <para>I (RN) always use this mode to follow pre planned routes.</para>
337 <para>Track following: Uses a <trademark>TracBack</trademark> mode</para>
338 <para>I (RN) never use this so I can't comment on how it actually compares to the route mode.</para>
342 There are often restrictions on the numbers of route points the GPS Device can handle - may be 250 or as little as 50.
343 This generally not a problem for single day routes, but needs managing for multi-day events or for highly detailed routes.
347 </section><!--General Concepts End-->
349 <section><title>File Types and the Main Window</title>
352 &appname; has it's own file type traditionally marked by the <emphasis>.vik</emphasis> file extension.
353 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...).
356 Besides it's own file type, &appname; can open (and save to via export methods) GPX and KML file types.
360 &appname; does not handle GPX 1.1 particularly well - it prefers GPX 1.0
364 By default &appname; opens a default blank window centered on the home location.
365 Each window contains menus, a toolbar, a viewport, layers panel and a statusbar.
366 Each section (apart from the viewport) can be hidden via the <link linkend="shortcut_keys">keyboard shortcuts</link> or from the
367 <menuchoice><guimenu>View</guimenu><guisubmenu>Show</guisubmenu></menuchoice> choices.
370 One may consider each &appname; window to be a separate project - each with it's project <emphasis>Viking</emphasis> file.
371 However generally one window is enough for most purposes!
374 Several operations apply at the window level as follows next.
375 Also see the <link linkend="tools">Tools</link> section for the operational modes that generally work in conjunction with a selected layer.
378 <section><title>New</title>
380 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu></menuchoice> menu and on the toolbar <guibutton>New</guibutton>.
383 This creates a new window with the default settings.
387 <section><title>Open</title>
389 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Open</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Open</guibutton>.
392 This opens a file chooser dialog to select one (or more) files of the supported GPS data file types:
394 <listitem><para>Viking</para></listitem>
395 <listitem><para>GPX</para></listitem>
396 <listitem><para>KML</para></listitem>
400 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.
404 &appname; handles more file types via the <link linkend="acquire">Acquire</link> methods below.
409 <section><title>Save</title>
411 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Save</guibutton>.
414 If the current opened file is <emphasis>Viking</emphasis> file, this save will simply update it.
415 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.
419 <section><title>Save As</title>
421 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Save As</guisubmenu></menuchoice> menu only.
424 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).
428 <section><title>Append</title>
430 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Append</guisubmenu></menuchoice> menu only.
433 Selecting a <emphasis>Viking</emphasis> file from this method will join the file contents to the current window (instead of creating a new one).
434 GPX and KML files may also be appended, but this is exactly the same as the normal file open method.
438 <section id="acquire"><title>Acquire</title>
441 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Acquire</guisubmenu></menuchoice> menu only.
444 If successful, these methods place the results in a new TrackWaypoint layer.
448 <title>From GPS</title>
450 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
451 Probably the easiest way of getting information from a GPS Device.
454 Select the GPS Device communication settings and then hit <guibutton>OK</guibutton>.
455 See the <link linkend="method_c">Getting Started</link> section for more info about the settings.
459 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.
465 <title>Import File With GPSBabel</title>
467 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel</guimenuitem></menuchoice>
470 Other formats can be imported that are supported by GPSBabel.
473 You need to select the file <emphasis>and</emphasis> the type of the file that is going to be opened,
474 since there is no automatic detection of the file kind.
479 <title>OSM Traces</title>
481 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>OSM Traces</guimenuitem></menuchoice>
482 See <link linkend="osm_dl">OpenStreetMap Download</link> section for more information.
487 <title>From Geotagged Images</title>
489 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From Geotagged Images</guimenuitem></menuchoice>
490 Enables automatic creation of waypoints from geotagged images.
493 This menu opens a dialog to select such image files.
494 If the image files have geotag information in them, then a TrackWaypoint layer with named waypoints positioned at the location of each image with a thumbnail of that image is created.
498 </section> <!-- End Acquire -->
500 <section><title>Print</title>
502 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Print</guisubmenu></menuchoice> menu and on the toolbar <guibutton>Print</guibutton>.
505 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
506 cross hairs and the scale.
509 It uses a standard system print dialog using an image the size of the current viewport in pixel terms.
510 On the <emphasis>Image Settings</emphasis> you can move the image around the page and scale the image up / or down.
514 <section><title>Generate Image File</title>
516 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Image File</guisubmenu></menuchoice> menu only.
519 Allows generation of larger (pixel) area images than the standard Print method above.
520 From the generated image you can use the facilities of the <application>Operating System</application> to print the image
521 or perform other actions.
524 You should have previously downloaded the tile images for the chosen zoom level,
525 otherwise the image produced will have missing sections.
529 Using large areas takes some time to process and due to the method used it may run out of memory to complete the operation.
530 Unfortunately under <trademark>Windows</trademark> systems it can not detect this failure and may crash the program.
531 So the maximum size is dependent on the capabilities of your system.
532 For instance the largest successful image generated on my (RN) Debian system is a pixel area of 20,000 x 20,000.
537 <section><title>Generate Directory of Images</title>
539 Located on the <menuchoice><guimenu>File</guimenu><guisubmenu>Generate Directory of Images</guisubmenu></menuchoice> menu only.
542 This is only available in UTM mode.
546 </section> <!-- End File Types -->
548 <section><title>Layers</title>
551 Layers supported by &appname; are:
554 <listitem><para>Aggregate</para></listitem>
555 <listitem><para>TrackWaypoint</para></listitem>
556 <listitem><para>GPS</para></listitem>
557 <listitem><para>DEM</para></listitem>
558 <listitem><para>Coord</para></listitem>
559 <listitem><para>Map</para></listitem>
560 <listitem><para>GeoRef</para></listitem>
563 For each layer there are a few standard options:
566 <listitem><para>Properties - Layer setup / configuration settings</para></listitem>
567 <listitem><para>Cut</para></listitem>
568 <listitem><para>Copy</para></listitem>
569 <listitem><para>Paste</para></listitem>
570 <listitem><para>Delete</para></listitem>
571 <listitem><para>Visibility - This checkbox on the Layers Panel controls whether the layer is shown in the viewport or not</para></listitem>
574 The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected:
577 <listitem><para>Standard keys: <keycap>Ctrl+x|c|v</keycap></para></listitem>
578 <listitem><para>Main menu <guimenuitem>Edit</guimenuitem></para></listitem>
579 <listitem><para>From the right click menu</para></listitem>
580 <listitem><para>Buttons at the bottom of the Layers Panel</para></listitem>
583 See the individual section for detail about each layer.
586 <section><title>TrackWaypoint Layer</title>
588 TrackWaypoint layers display GPS data (tracks, routes and waypoints).
590 <para>One way to create new waypoints is to copy a
591 latitude/longitude coordinate pair, such as the one shown on most
592 geocaches, and paste it into an active TrackWaypoint layer. &appname; can
593 automatically recognize several variations of the lat/lon format.
596 By right-clicking on tracks, routes or waypoints in the layers panel, you can access many commands on them.
597 You can easily find a specific track, route or waypoint by expanding the appropriate containing Tracks, Routes or Waypoints sublayer in the
598 layers panel to show all the individual items and then typing the name of the track, route or waypoint.
602 The containing Tracks, Routes or Waypoints sublayers are only shown when items of that type exist.
603 To start creating them enter into a create mode via either the <guibutton>Create</guibutton> toolbar commands or the <guimenuitem>New</guimenuitem> menu commands.
607 By default routes are coloured red. Tracks are automatically assigned a spread of colours.
611 Most operations are 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.
612 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).
615 <section><title>Layer Operations</title>
617 The layer has a context menu with several operations.
620 <section><title>View Layer</title>
622 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).
626 <section><title>View</title>
628 <section><title>View All Tracks</title>
630 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).
634 <section><title>View All Routes</title>
636 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).
640 <section><title>View All Waypoints</title>
642 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).
648 <section><title>Goto Center of Layer</title>
650 This will automatically move the viewport to see the whole layer (i.e. tracks, routes and waypoints). It does not adjust the zoom level.
654 <section><title>Goto Waypoint</title>
656 This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it.
660 Note this search is not very clever and only finds exact matches.
661 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.
666 <section><title>Export Layer</title>
668 The layer (all tracks, routes and waypoints) can be exported to a file GPX, GPSPoint, GPSMapper or Google's KML format.
671 Version1.1+: An individual track can be exported to a GPX file via the track menu.
675 <section id="new_wp"><title>New Waypoint</title>
677 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.
681 <section><title>Add Wikipedia Waypoints</title>
683 This gets 'interesting' points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary.
687 <section><title>Geotag Images</title>
689 This starts the Geotagging Images dialog against all tracks in the layer.
690 See <link linkend="geotagging">Geotagging</link> for further detail.
694 <section><title>Acquire</title>
696 This offers the same choice of <link linkend="acquire">Acquire</link> methods as on the <guimenu>File</guimenu> menu.
697 However when invoked from here, the results will be stored in this layer (instead of creating a new one).
701 <section><title>Upload</title>
703 <section id="gps_upload"><title>Upload to GPS</title>
705 This opens a dialog to select the GPS Device and port to which the layer information will be transferred.
708 The types of GPS information (tracks, routes or waypoints) to be transferred can be selected.
711 Tracks, Routes or Waypoints that are invisible will not be transferred.
715 <section id="osm_upload"><title>Upload To OSM</title>
717 This opens a dialog to upload all tracks and waypoints to <ulink url="http://openstreetmap.org/">OpenStreetMap</ulink> traces.
718 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>
721 &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.
725 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.
727 <para>Currently &appname; does not support the <ulink url="http://oauth.net/">OAuth</ulink> mechanism.</para>
733 <section><title>Filter</title>
734 <section><title>Simplify All Tracks</title>
736 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.
739 <section><title>Remove Duplicate Waypoints</title>
741 Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer.
745 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.
751 <section id="filter_with_track"><title>Filter With <emphasis>Trackname</emphasis></title>
753 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:
756 <listitem><para>Waypoints Inside This</para></listitem>
757 <listitem><para>Waypoints Outside This</para></listitem>
760 The result is generated in a new Track/Waypoint layer.
764 <section><title>Geotag Images</title>
766 This starts the Geotagging Images dialog using the specific track.
767 See <link linkend="geotagging">Geotagging</link> for further detail.
771 </section><!-- End TRW Layer Options -->
773 <section><title>Track and Route Properties</title>
775 Show many useful statistics about a track or a route, including a
776 elevation-distance graph and a speed-time graph (if data is available).
777 You can click these graphs to jump to the point in the track. You can
778 also reverse it, delete duplicates, and split a track from its
779 component segments (discontinuous breaks in a track) into separate
783 The following colors are used in the elevation-distance graph:
787 <term>'Main' colour - this is dependent on your Desktop theme - often blue by default</term>
788 <listitem><para>elevation data in graph</para></listitem>
793 <para>no elevation data</para>
799 <para>elevation data from DEM</para>
812 <section><title>Track and Route Operations</title>
814 <section><title>Goto</title>
816 This centers the viewport on the selected position on the track:
819 <listitem><para>Startpoint</para></listitem>
820 <listitem><para>"Center" - the notional center from the bounds of the track</para></listitem>
821 <listitem><para>Endpoint</para></listitem>
822 <listitem><para>Version1.1+: Highest Altitude</para></listitem>
823 <listitem><para>Version1.1+: Lowest Altitude</para></listitem>
824 <listitem><para>Version1.1+: Maximum Speed (Not Available on Routes)</para></listitem>
828 <section><title>View</title>
830 Version1.1+: This centers the viewport on the track and selects the best zoom level to see it.
834 <section><title>Combine</title>
835 <section><title>Merge By Time</title>
837 This operation repeatedly tries to merge the right-clicked track
838 with tracks in the same TrackWaypoint layer. The tracks which are
839 merged are those which have at least one trackpoint less than some
840 threshold time away. This way, if you somehow end up with lots of small
841 segments (say, caused by turning the GPS on and off) you can merge them
842 easily into one track.
845 This is not available on routes as they have no timestamps.
849 <section><title>Merge With Other Tracks</title>
851 This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with.
855 <section><title>Merge Segments</title>
857 Combines track segments. Effectively removing track segment markers to leave one segment for the whole track.
861 <section><title>Append Track or Route</title>
863 Enable joining of a single track to the end of the current track.
864 This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection.
869 <section><title>Split</title>
870 <section><title>Split By Time</title>
872 This operation will split a single track into segments wherever the
873 time interval between successive trackpoints is larger than some
874 threshold. This is useful when processing raw NMEA GPS data, especially
875 taken over a long time.
878 This is not available on routes as they have no timestamps.
882 <section><title>Split By Number of Points</title>
884 Version1.2+: This operation will split a single track into segments by the number of points specified.
885 This can be useful with devices which may have limits on the number of points it supports.
889 <section><title>Split Segments</title>
891 Splits track segments into new tracks.
894 This is not available on routes as they do not have route segments.
898 <section><title>Split at Trackpoint</title>
900 Splits the track at the currently selected trackpoint. This is only enabled when a trackpoint is selected.
905 <section><title>Delete Points</title>
906 <section><title>Delete Points With the Same Position</title>
908 Deletes subsequent points that have the same position (but have different timestamps).
911 <section><title>Delete Points With the Same Time</title>
913 Deletes subsequent points that have the same time stamp (but may have different positions).
916 This is not available on routes as they have no timestamps.
922 <section><title>Apply DEM data</title>
924 If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
928 <section><title>Export Track as GPX</title>
930 Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog.
934 <section><title>Extend Track End</title>
936 Changes the current tool to add trackpoints to the end of the track.
940 <section><title>Extend Using Route Finder</title>
942 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.
946 <section><title>Upload</title>
948 <section><title>Upload to GPS</title>
950 Same as the layer <link linkend="gps_upload">Upload to GPS</link> command, but only applies to the track.
954 <section><title>Upload to OSM</title>
956 Same as the layer <link linkend="osm_upload">Upload to OSM</link> command, but only applies to the track.
962 <section><title>Use With Filter</title>
964 This selects the track to be used in the <link linkend="filter_with_track">Filter With <emphasis>Trackname</emphasis></link> feature.
967 This is not available on routes.
971 <section><title>View Google Directions</title>
973 This option is only available on a track created using the Route Finder tool.
976 Launch a web browser to see the Google directions page which yielded the route.
980 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.
985 </section><!-- End Track Options -->
987 <section><title>Waypoint Properties</title>
990 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).
993 If the waypoint has an associated image, then the Geotag information may be updated, either with updating the file's modification timestamp or not.
994 This can be useful when the waypoint has been moved.
997 </section><!-- WP Prop END -->
999 <section><title>Waypoint Operations</title>
1001 <section><title>Goto</title>
1003 This centers the viewport on the selected waypoint.
1007 <section><title>Visit Geocache Webpage</title>
1009 If the waypoint's name is in Geocache form (GCXXXXX) you can launch a web browser to go to the Geocache page.
1013 <section><title>New Waypoint</title>
1015 Same as the layer <link linkend="new_wp">New Waypoint</link>.
1019 </section><!-- WP END -->
1021 <section id="geotagging"><title>Version1.3+: Geotag Images</title>
1023 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.
1026 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.
1030 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.
1034 Various options allow control of how the geotagging process is performed:
1037 <listitem><para>Images - Add the images used for geotagging</para></listitem>
1038 <listitem><para>Create Waypoints</para></listitem>
1039 <listitem><para>Overwrite Existing Waypoints</para></listitem>
1040 <listitem><para>Write EXIF</para></listitem>
1041 <listitem><para>Overwrite Existing GPS Information</para></listitem>
1042 <listitem><para>Interpolate Between Track Segments</para></listitem>
1043 <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>
1044 <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>
1048 </section><!-- TRW Layer END -->
1050 <section id="gps_layer"><title>GPS Layer</title>
1052 The GPS layer is responsible for uploading and downloading GPS data
1053 from a GPS device. It also is responsible for realtime GPS tracking.
1054 Expand the GPS layer in the layers panel to see the two TrackWaypoint layers it
1055 uses for uploading and downloading. To upload, download, or use
1056 realtime tracking, right-click the GPS layer and click the appropiate
1060 <section><title>Download</title>
1062 To download data from the GPS, right-click the GPS layer and click <guimenuitem>Download from GPS</guimenuitem>.
1066 <section><title>Upload</title>
1068 To upload data to the GPS, first populate the GPS Upload child
1069 layer of the GPS layer (either by creating waypoints/tracks/routes in it, or
1070 copying and pasting or dragging waypoints/tracks/routes from another layer).
1071 Then right-click the GPS layer and click <guimenuitem>Upload to GPS</guimenuitem>.
1075 <section><title>Realtime Tracking</title>
1077 You must set up gpsd correctly or use a GPSD server and put the
1078 correct information in the GPS layer properties dialog. Then right-click
1079 the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
1083 <section><title>Empty <emphasis>Item</emphasis></title>
1085 There are several options to quickly delete a subsection of data:
1088 <listitem><para>Empty Realtime</para></listitem>
1089 <listitem><para>Empty Upload</para></listitem>
1090 <listitem><para>Empty Download</para></listitem>
1091 <listitem><para>Empty All</para></listitem>
1095 </section><!-- End GPS -->
1097 <section><title>DEM (Digital Elevation Model) Layer</title>
1099 This layer provides elevation data from the <ulink url="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission (SRTM)</ulink>
1102 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]
1105 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.
1108 The current data server is: <ulink url="http://dds.cr.usgs.gov/srtm/version2_1/">NASA STRM 2.1</ulink>.
1111 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.
1115 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"
1119 </section><!-- End DEM -->
1122 <section><title>Maps Layer</title>
1124 This layer provides a single map resource, you may have multiple map layers but only top one (if enabled) will be visible.
1125 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.
1128 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.
1131 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:
1134 <listitem><para>Bing Bird's Eye (Aerial) Maps (&appname; Version1.2+)</para></listitem>
1135 <listitem><para>Terraserver Topos</para></listitem>
1136 <listitem><para>Terraserver Aerials</para></listitem>
1137 <listitem><para>Terraserver Urban Areas</para></listitem>
1138 <listitem><para>OpenStreetMap (Mapquest) - This is the default (&appname; Version1.3+)</para></listitem>
1139 <listitem><para>OpenStreetMap (Mapnik)</para></listitem>
1140 <listitem><para>OpenStreetMap (Cycle)</para></listitem>
1141 <listitem><para>OpenStreetMap (Transport) (&appname; Version1.3+)</para></listitem>
1142 <listitem><para>NASA BlueMarble</para></listitem>
1143 <listitem><para>SpotMap (&appname; Version1.1+)</para></listitem>
1147 &appname; can be configured to handle additional maps. See <link linkend="extend_viking">Extending &appname;</link> for further detail.
1150 <section><title>Layer Operations</title>
1151 <section><title>Download Missing Onscreen Maps</title>
1153 This requests map tiles for areas of the viewport that do not currently have one.
1157 <section><title>Download New Onscreen Maps</title>
1159 This requests map tiles only if the maps are older than the Tile Age preference.
1163 <section><title>Reload All Onscreen Maps</title>
1165 Force a refresh of all visible map tiles.
1171 </section><!-- End Maps -->
1173 <section><title>Aggregrate Layer</title>
1175 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.
1178 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.
1179 Here are some suggestions:
1181 <listitem><para>Hiking</para></listitem>
1182 <listitem><para>Mountain Biking</para></listitem>
1183 <listitem><para>Road Cycling</para></listitem>
1184 <listitem><para>Car Trips</para></listitem>
1185 <listitem><para>Sailing</para></listitem>
1186 <listitem><para>Holidays</para></listitem>
1187 <listitem><para>UK Points of Interest</para></listitem>
1188 <listitem><para>USA Points of Interest</para></listitem>
1189 <listitem><para>etc...</para></listitem>
1193 Thus one can have a list of all your tracks, but groups can be shown or not using the relevant layers visibility checkbox.
1197 This layer only has one operation: <guilabel>New Layer</guilabel>
1200 <section><title>New Layer</title>
1202 Add a new layer of the selected type.
1206 </section><!-- End Agg -->
1208 <section><title>GeoRef Layer</title>
1210 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.
1212 <section><title>Layer Operations</title>
1213 <section><title>Zoom to Fit Map</title>
1215 Automatically set a zoom level to see the entire map coverage.
1219 <section><title>Goto Map Center</title>
1221 Center the viewport on this map.
1225 <section><title>Export to World File</title>
1227 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>.
1232 </section><!-- End GeoRef -->
1234 <section><title>Coord Layer</title>
1236 This layer is allows drawing of grid lines on the viewport.
1238 </section><!-- End Coord -->
1242 <section id="tools"><title>Tools</title>
1244 &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.
1247 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.
1250 <keycap>Scroll</keycap>: zoom in and out keeping the mouse over same location
1253 <keycap>Ctrl-scroll</keycap>: pan north-south (also <keycap>Ctrl-up</keycap>, <keycap>Ctrl-down</keycap>)
1256 <keycap>Shift-scroll</keycap>: pan east-west (also <keycap>Ctrl-left</keycap>, <keycap>Ctrl-right</keycap>)
1259 <keycap>Ctrl-shift-scroll</keycap>: zoom in and out, without changing the center (also <keycap>Ctrl+</keycap>, <keycap>Ctrl-</keycap> [*not* KeyPad +/-])
1262 <keycap>Middle-click</keycap>: make the clicked point on the map the center
1265 <keycap>Middle-click</keycap> and drag: pan
1268 <section><title>Pan</title>
1270 This is the default mode of operation for &appname;.
1273 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mover_22.png"/></guiicon>
1276 Pan moves the viewpoint. A single click centers the viewport at that point, whereas click and drag dynamically moves the view around.
1277 This is the default tool.
1280 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+P</keycap>
1284 <section><title>Zoom</title>
1286 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/zoom_18.png"/></guiicon>
1289 Zooms in and out on the clicked part of the map or by the selected area.
1292 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+Z</keycap>
1295 <keycap>Ctrl</keycap> + left or right click: Zoom in/out and center the map on the clicked location
1298 <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.
1302 <section><title>Ruler</title>
1304 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/ruler_18.png"/></guiicon>
1307 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.
1308 A second click will 'freeze' the ruler at that point.
1311 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+U</keycap>
1315 <section id="select"><title>Version1.1+: Select</title>
1317 This mode is entered by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/select_18.png"/></guiicon>
1320 The select tool allows one to choose any waypoint or track by clicking on it (or reasonably near) in the viewpoint.
1323 ATM to select a track one must actually click on a trackpoint, which is also selected.
1326 This mode can also be entered by the keyboard shortcut <keycap>Ctrl+Shift+S</keycap>
1330 <section><title>TrackWaypoint Layer Tools</title>
1332 You must have a TrackWaypoint Layer selected to use these tools.
1334 <section><title>Create Waypoint</title>
1336 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addwp_18.png"/></guiicon>
1339 Left click will open the new waypoint dialog using the specified position.
1343 <section><title>Create/Begin Track</title>
1345 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon>
1348 Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track.
1349 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1350 Right click or <keycap>Backspace</keycap>: undo one point.
1353 Double click or <keycap>Escape</keycap>: finish track creation.
1357 <section><title>Edit Waypoint</title>
1359 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edwp_18.png"/></guiicon>
1362 Left Click/drag: select/move a waypoint.
1363 If <keycap>Ctrl</keycap> is held at the same time, it will jump the waypoint position to a nearby existing trackpoint.
1364 If <keycap>Shift</keycap> is held at the same time, it will jump the waypoint position to a nearby existing waypoint.
1366 <para>Right-click on waypoint: opens a menu with waypoint actions (the
1367 same menu accessed by right-clicking the waypoint in the layers panel)
1371 <section><title>Edit Trackpoint</title>
1373 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/edtr_18.png"/></guiicon>
1376 Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint.
1377 Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint.
1378 If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
1381 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.
1385 <section><title>Show Picture</title>
1387 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/showpic_18.png"/></guiicon>
1390 Opens an image viewer with the picture associated with the waypoint.
1391 By default this uses the default system image viewer.
1392 For Linux you can override this with the setting in the <link linkend="prefs_external">preferences.</link>
1396 <section><title>Route Finder</title>
1398 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/route_finder_18.png"/></guiicon>
1400 <para>Creates a track using Google maps routing between two points.
1401 Requires an internet connection. Click one point, then click another to
1405 Right-click: undo last routing (only track removed - not any waypoints)
1408 <keycap>Ctrl</keycap>: continue previous track
1414 <section><title>Georef Map Layer Tools</title>
1416 You must have a Georef Map Layer selected to use these tools.
1418 <section><title>Georef zoom</title>
1420 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geozoom_18.png"/></guiicon>
1422 <para>Changes the zoom level of the georeferenced map and changes the
1423 &appname; zoom level accordingly. Useful if you are trying to match GPS
1424 data to a georeferenced map.
1428 <section><title>Georef move</title>
1430 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/geomove_18.png"/></guiicon>
1433 Drag to move the georeferenced map.
1438 <section><title>Map Download</title>
1440 You must have a Map Layer selected to use this.
1443 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/mapdl_18.png"/></guiicon>
1446 Click to download a single tile. Drag to download tiles in the dragged rectangle area.
1449 Right-click to redownload bad/all tiles. Right-click and drag to redownload bad/all tiles in the dragged rectangle area.
1453 <section><title>DEM Download</title>
1455 You must have a DEM Layer selected to use this.
1458 Enable this tool by clicking on the toolbar icon: <guiicon><inlinegraphic fileref="figures/demdl_18.png"/></guiicon>
1461 Click to download and import a DEM file.
1465 <section><title>Webtools</title>
1467 Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
1470 Jumping from &app; to such service can become annoying.
1473 &appname; allows you to open such service directly at the position currently viewed in &app;.
1476 This feature is called <guilabel>Webtools</guilabel>. It is also known as External Tools.
1482 <!-- Preferences -->
1483 <section id="prefs"><title>Preferences</title>
1484 <section><title>General</title>
1485 <section><title>Localisation</title>
1486 <para>You can select units displayed by &appname; to best fit your usage.</para>
1488 <title>Properties dialog: units part</title>
1490 <graphic format="PNG" fileref="figures/properties_units.png"/>
1493 <para>Concerning degrees, you can select the way to display them:
1496 <term>DDD</term><listitem><para>decimal degree</para></listitem>
1499 <term>DMM</term><listitem><para>partial sexagesimal display: degrees, minutes and decimal part of minutes</para></listitem>
1502 <term>DMS</term><listitem><para>sexagesimal display: degrees, minutes and seconds</para></listitem>
1507 <title>Properties dialog: degree display options</title>
1509 <graphic format="PNG" fileref="figures/properties_degree.png"/>
1513 <section><title>Waypoint Icon Size</title>
1514 <para>An option exists to control the icon (symbol) size used for waypoints
1517 <section><title>'Home' Default Location: Latitude and Longitude</title>
1518 <para>You can set the 'Home' location directly by inputting the latitude and longitude in decimal degrees.
1521 <section><title>Tile's age</title>
1522 <para>This age is used to decided wether or not a new request to tile server must be done.
1524 <para>Changing this value, you will increase or decrese the network load.</para>
1526 <section><title>Default maplayer directory</title>
1527 <para>This property sets the default directory of the tiles cache.
1528 This value is used when you create a new map layer.
1530 <para>You are still able to change this value in each map layer properties.</para>
1532 <section><title>Map Cache Memory Size</title>
1533 <para>This controls the amount of maps that are stored in memory, rather than having to reread from disk.
1534 Generally if you have a system with lots of memory it's recommended to increase this value.
1539 <section id="prefs_external"><title>Export/External</title>
1540 <section><title>KML Export Units</title>
1541 <para>Allows setting the units used when saved as the KML file type, such as Metric or Statue units</para>
1543 <section><title>Image Viewer (Not Windows)</title>
1544 <para>Allows setting the program used to view images associated with Waypoints.</para>
1545 <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>
1546 <para>Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.</para>
1548 <section><title>External GPX programs</title>
1549 <para>Allows setting the programs invoked via the TrackWaypoint Layer -> Export Layer -> Open With 'program'</para>
1550 <para>Two options are given so that it can be configured for various uses such as:</para>
1552 <listitem><para>An OSM editor (default)</para></listitem>
1553 <listitem><para>Some other user defined program</para></listitem>
1558 <section id="prefs_osm"><title>OpenStreetMap Traces</title>
1559 <section><title>OSM Username + Password</title>
1560 <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>
1563 Your OSM password will be stored in plain text.
1572 <section><title>Howto's</title>
1573 <section id="howto_start"><title>Getting Started</title>
1575 To quickly get started using &appname;, follow these instructions.
1577 <section><title>Go to an area of interest</title>
1579 &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.
1582 <title>Method A</title>
1585 Use the online location address/place search.
1588 Use the <guibutton>Go to Location</guibutton> toolbar button or from the menus
1589 <menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>.
1590 You can change the search location provider if desired.
1591 Enter the name of place you wish to go to (you may need to specify the country to refine the search).
1592 Also you can enter a post code or a ZIP code instead.
1595 <para>You will need an internet connection for this search to work</para>
1600 <title>Method B</title>
1603 If you know the coordinates of where you want to view:
1606 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.
1611 <title id="method_c">Method C</title>
1613 <para>Use the GPS Layer or <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice>
1614 to load data directly from your GPS into &appname;.
1616 <para>You can specify the types of data to acquire: Tracks, Routes and/or Waypoints.
1619 <para>You must have write permission to the port used. For <trademark>Unix</trademark> like OS:</para>
1621 <listitem><para>/dev/ttyS0 is the first serial port</para></listitem>
1622 <listitem><para>/dev/ttyUSB0 is the first USB port</para></listitem>
1623 <listitem><para>usb: is any USB port</para></listitem>
1625 <para>Depending on your distribution only one of the USB port types may work</para>
1626 <para>For <trademark>Windows</trademark>:</para>
1628 <listitem><para>com1: is the first serial port</para></listitem>
1629 <listitem><para>usb: is any USB port</para></listitem>
1633 <para>The GPS devices supported are those supported by <application>GPSBabel</application>.</para>
1634 <para>Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.</para>
1639 <title>Method D</title>
1642 Get data from files in GPX or KML format, which can be opened directly.
1643 Use <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice>
1646 Other formats can be imported that are supported by GPSBabel.
1647 <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>Import File With GPSBabel...</guimenuitem></menuchoice>
1652 Expand Tracks or Waypoints. Right-click on the
1653 track or waypoint of interest and select <guimenuitem>Goto "Center"</guimenuitem>.
1658 <section><title>Add a map layer</title>
1660 1. Use Layers - New Map Layer, and choose a suitable cache directory
1661 where you would like to store your tracks and click <guilabel>OK</guilabel>. Zoom to a
1662 comfortable level (I suggest 4 mpp) by clicking the left and right
1663 mouse buttons on the gray area where your tracks are. Now from the menu
1664 choose Tools - Map Download, Click where you would like to download a
1665 map. Regardless of what tool you are using, the middle mouse button
1666 always pans. </para>
1669 You need an open internet connection when you are downloading maps.
1673 1. You will notice the maps are being drawn on top of the tracks, which
1674 is probably not what you want. Look at the Layers Panel to the left.
1675 Notice how the layer named Map is ABOVE your TrackWaypoint layer that
1676 your GPS data is in. This means that it will be drawn last, or on top
1677 of the other layers. Select the Map layer from the list and click the
1678 down arrow button beneath the list. Your tracks will now be drawn over
1682 <section><title>Set Your Home Location</title>
1684 You can save the current center position of the viewport as the default location AKA the Home Location by
1685 <menuchoice><guimenu>Edit</guimenu><guimenuitem>Set the Default Location</guimenuitem></menuchoice>.
1688 Then at any time you can return to this place by clicking on the <guibutton>Home</guibutton> icon on the toolbar.
1691 You can also set the default location via specifing the exact latitude and longitude in the <link linkend="prefs">Preferences</link>.
1696 <section><title>From 1st startup to GPS track (including offline maps)</title>
1698 The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
1699 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'.
1701 <section><title>Fetching the maps</title>
1703 <emphasis role="bold">Map</emphasis>
1706 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
1707 <step><para>in the layer properties dialogue choose e.g. <guilabel>OpenStreetMap (Mapnik)</guilabel>.</para></step>
1709 <para>For the moment, we keep the default <guilabel>Maps Directory</guilabel> (the directory in
1710 which the maps will be stored and can be used for offline usage).</para>
1713 <para>Check <guilabel>Autodownload maps</guilabel> and keep the zoom level as <guilabel>Use Viking
1714 Zoom Level</guilabel>.</para>
1717 however, that these settings will play an important
1718 role in the pre-fetch for offline usage discussed later
1723 <para>You'll see a map of Stuttgart. Using the mouse wheel, you can
1724 zoom in and out. The maps for the choosen resolution will be downloaded
1728 <emphasis role="bold">DEM Layer (Height Map)</emphasis>
1731 <step><para>Zoom out to 512.</para></step>
1732 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New DEM Layer</guimenuitem></menuchoice></para></step>
1733 <step><para>Keep the download source as is (SRTM Global 90m), hit <guilabel>OK</guilabel>.</para></step>
1736 <para>In the layer listing on the left, the DEM layer should reside
1737 above the map layer. If this is not the case, highlight the DEM layer
1738 an shift it one up (using the arrow up button).
1741 <step><para>highlight the DEM layer in the layer listing on the left</para></step>
1742 <step><para>in the toolbar, check DEM layer download/import (the last symbol)</para></step>
1743 <step><para>a left-click in the map window should then fetch the DEM data</para></step>
1746 This might take some time.
1749 Sometimes, a tile does not show up correctly (you might see only a
1750 black frame in the map window) because it got corrupted during
1751 transfer. In order to correct this, you can delete the corresponding
1752 datafile in the cache. <programlisting> right-click the DEM layer properties</programlisting>
1755 The <guilabel>DEM Files</guilabel> listing allows you to delete the specific tiles (alternatively do this from the command line).
1758 You can also alter the Min. and Max. elevation in this dialogue.
1762 <section><title>GPS Track with Height Profile</title>
1764 <step><para>Uncheck the DEM layer (the map is shown again)</para></step>
1766 <para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New TrackWaypoint Layer</guimenuitem></menuchoice></para>
1767 <para>Ensure the new track layer is above the map layer.</para>
1769 <step><para>Expand the TrackWaypoint layer, select <guimenuitem>Tracks</guimenuitem></para></step>
1770 <step><para>In the tools menu choose <guiicon><inlinegraphic fileref="figures/addtr_18.png"/></guiicon> <guibutton>Create Track</guibutton>
1772 <step><para>Leftclick in the map window, enter a name</para></step>
1774 <para>Click several times to generate a track (a right-click removes the last point).</para>
1775 <para>Height data is set automatically since DEM data is available</para>
1777 <step><para>Expand tracks in the layer menu, your track should show up, select it</para></step>
1778 <step><para>Right click your track, select <guimenuitem>Properties</guimenuitem></para></step>
1779 <step><para>Click the tab <guilabel>Elevation-distance</guilabel> - enjoy the plot</para></step>
1782 In order to save this setting for later usage
1785 <step><para>click <guilabel>OK</guilabel> in the <guilabel>Track Properties</guilabel> dialog</para></step>
1786 <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>
1790 <section><title>Usecase: offline data for holiday</title>
1792 Suppose you want to have the map and DEM data offline for your holiday in Italy near Bologna.
1795 <step><para>Start a new &appname; session.</para></step>
1796 <step><para><menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter Bologna</para></step>
1797 <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step>
1798 <step><para>Choose e.g. <guilabel>OpenStreetMap (mapnik)</guilabel>.</para></step>
1799 <step><para>adapt the <guilabel>maps directory</guilabel> e.g. to <filename>/home/user/.viking-map-holiday/</filename>.
1800 This allows you to delete the map stuff after holiday without purging the rest of your maps.
1802 <step><para>check <guilabel>autodownload map</guilabel></para></step>
1803 <step><para>keep <guilabel>viking zoom level</guilabel></para></step>
1804 <step><para>zoom out to 1024</para></step>
1805 <step><para>add a DEM layer (as discussed above)</para></step>
1806 <step><para>download the DEM data</para></step>
1808 <para>In the &app; version discussed here, the DEM data automatically
1809 are stored in <filename>/home/user/.viking-maps/</filename>. You can move the corresponding
1810 tiles into <filename>.viking-map-holiday/</filename> if you like.
1813 <emphasis role="bold">Download map data for all zoom levels</emphasis>
1816 <step><para>uncheck the DEM layer for the map to show up</para></step>
1817 <step><para>navigate the map to be centered at Bologna</para></step>
1818 <step><para>choose the zoom such, that all regions of interest are displayed in the map window (e.g. 1024)</para></step>
1820 <para>follow this sequence until you have all tiles for all zoom levels you need</para>
1822 <step><para>right-click the map layer properties</para></step>
1823 <step><para>set the zoomlevel explicitely one below the last (in the first cycle 512), hit OK</para></step>
1824 <step><para>right click the map layer <guimenuitem>Download Missing Onscreen Maps</guimenuitem></para></step>
1825 <step><para>wait until all tiles for that resolution have been downloaded</para></step>
1829 <para>This may take some time and some hard disk capacity.</para>
1831 Do not forget to save your configuration (as discussed above).
1837 <section><title>OpenStreetMap project</title>
1839 <ulink url="http://openstreetmap.org/">OpenStreetMap (OSM)</ulink> is a collaborative project to create a free editable map of the world.
1840 One of sources of data for this project is GPS tracks.
1841 &appname; supports this project via the GPS Traces methods, both uploading and downloading such data.
1843 <section><title>Uploading data to OpenStreetMap</title>
1845 It is possible to upload data directly from &appname; to OpenStreetMap.
1848 <title>Upload a layer</title>
1850 One solution is to upload whole a TrackWaypoint layer. To do this,
1851 simply select the layer and right click on it. Then, select <guimenuitem>Upload to
1856 <title>Upload a single track</title>
1857 <para>One solution is to upload whole a TrackWaypoint layer. To do
1858 this, simply select the layer and right click on it. Then, select
1859 <guimenuitem>Upload to OSM</guimenuitem>.
1863 <title>Fill in the form</title>
1865 In both cases, &appname; will retain some information.
1866 The email field is the email you used to subscribed into OpenStreetMap.
1867 The password field is the password you used with this account.
1868 The filename is the name you want your upload has on the server. This information is displayed by the osm server.
1869 The description is some descriptive information.
1870 The tags field is a white separated list of tag.
1874 <section id="osm_dl"><title>Downloading traces from OpenStreetMap</title>
1876 It is possible to download GPS traces directly from OpenStreetMap into &appname;.
1877 This feature can be really useful for checking existing data before uploading new ones.
1880 <title>Download all visible tracks</title>
1881 <para>One solution is to select
1883 <guimenu>File</guimenu>
1884 <guisubmenu>Acquire</guisubmenu>
1885 <guimenuitem>OSM traces...</guimenuitem>
1887 Each request can get up to 5,000 points.
1888 The dialog box allows setting which group of 5,000 points to get. These groups are known as 'Page Numbers' which start at 0.
1889 Increasing the page number parameter allows one to request the subsequent sets of point groups.
1890 See <ulink url="http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces"/> for further detail.
1896 <section><title>Geotagging</title>
1898 This assumes you already have a map layer enabled for ease of use (if not see above to get one).
1900 <section><title>Manual Positioning</title>
1902 This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
1903 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.
1904 ATM this process only works on an individual image, so it will be tedious for handling lots of images.
1907 First create a Track Waypoint layer or use an existing one; and select it in the Layers Panel.
1908 NB Make sure this layer is above the map layer in the Layers Panel list.
1909 Create a new waypoint (or move an existing one) to exact location desired:
1911 <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>
1912 <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>
1914 Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
1915 <menuchoice><guimenu>Update Geotag on Image</guimenu><guisubmenu>Update</guisubmenu></menuchoice>
1918 The <guilabel>Update Geotag on Image</guilabel> options are only available when a waypoint has an image associated with it.
1922 <section><title>Automatic Positioning Against a Tracklog</title>
1924 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 -
1925 see <link linkend="howto_start">Getting Started</link>.
1926 It helps if this is the track that was recorded at the time you took some photographs!
1929 Select the track either from the layers panel on the left or via the viewport using the <link linkend="select">Select Tool</link>.
1930 Then right click on it and chose the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> leading you to the <link linkend="geotagging">Geotagging Dialog</link>.
1933 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.
1934 If things are succesful, new waypoints with thumbnail images of the photographs will appear.
1935 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.
1937 <formalpara><title>Option: Overwrite Waypoints</title>
1939 This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
1940 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).
1944 If you have multiple tracks in a TrackWaypoint layer, then invoking the <menuchoice><guimenu>Geotag Images...</guimenu></menuchoice> action on the layer
1945 will search all the tracks to find location matches.
1950 <section><title>GPS Real Time Location (Not <trademark>Windows</trademark>)</title>
1952 &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.
1953 Unfortunately <application>gpsd</application> is not available on <trademark>Windows</trademark>,
1954 so currently this functionality is disabled in <trademark>Windows</trademark> builds of &appname;
1957 This assumes you already have a map layer enabled for ease of use (if not see above to get one).
1960 Turn on the GPS Device, ensure it has figured out it's location and plug it in to your computer.
1962 <section><title>Set Up GPS Layer</title>
1964 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>.
1967 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.
1970 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.
1973 Then right-click the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>.
1974 Hopefully the viewport should jump to the GPS location.
1977 Troubleshooting checklist:
1979 <procedure><step><para>Confirm <application>gpsd</application> is running.</para></step></procedure>
1980 <procedure><step><para>Confirm on the GPS device it has a location.</para></step></procedure>
1981 <procedure><step><para>Confirm the <emphasis>Realtime Tracking Mode</emphasis> settings.</para></step></procedure>
1985 <section id="extend_viking">
1986 <title>Extending Viking</title>
1988 <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>
1989 <para>Here is an example:
1990 <programlisting><![CDATA[
1992 <object class="ClassName">
1993 <property name="property_name1">Property value</property>
1994 <property name="property_name2">Property value</property>
2001 <para>You can find more examples in the documentation part of the distribution.</para>
2003 <title>Map Source</title>
2004 <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>
2005 <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>
2007 <para>The VikSlippyMapSource allows to declare any map's source working like OpenStreetMap. It supports the following properties:
2011 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
2015 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
2018 <term>hostname</term>
2019 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
2023 <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>
2027 <para>The VikTmsMapSource allows to declare any TMS service. It supports the following properties:
2031 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
2035 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
2038 <term>hostname</term>
2039 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
2043 <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>
2047 <para>The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties:
2051 <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem>
2055 <listitem><para>the text displayed in the map's source selection dialog</para></listitem>
2058 <term>hostname</term>
2059 <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem>
2063 <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>
2070 <title>Go-to search engines</title>
2071 <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>
2072 <para>An example of the file in the distribution <filename>doc/examples/goto_tools.xml</filename>.</para>
2073 <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>
2074 <para>The related properties are:
2078 <listitem><para>the text displayed in the <guilabel>Go-To</guilabel> dialog</para></listitem>
2081 <term>url-format</term>
2082 <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>
2085 <term>lat-path</term>
2086 <listitem><para>XML path of the latitude (eg. <literal>/root/parent/elem</literal>)</para></listitem>
2089 <term>lat-attr (optional)</term>
2090 <listitem><para>name of the attribute (of previous element) containing the latitude</para></listitem>
2093 <term>lon-path</term>
2094 <listitem><para>XML path of the longitude (eg. <literal>/root/parent/elem</literal>)</para></listitem>
2097 <term>lon-attr (optional)</term>
2098 <listitem><para>name of the attribute (of previous element) containing the longiude</para></listitem>
2102 <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>
2106 <title>External tools</title>
2107 <para>It is possible to add new external tools. The file is <filename>~/.viking/external_tools.xml</filename>.</para>
2108 <para>An example of the file in the distribution <filename>doc/examples/external_tools.xml</filename>.</para>
2109 <para>The VikWebtoolCenter allows to declare any Webtool using a logic based on center coordinates and zoom level value.</para>
2110 <para>The related properties are:
2114 <listitem><para>this is an integer and should be unique as it used to identify the tool</para></listitem>
2118 <listitem><para>the text displayed in the menu entry</para></listitem>
2122 <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>
2126 <para>The VikWebtoolBounds allows to declare any Webtool using a logic based on bounds coordinates.</para>
2127 <para>The related properties are:
2131 <listitem><para>this is an integer and should be unique as it used to identify the tool</para></listitem>
2135 <listitem><para>the text displayed in the menu entry</para></listitem>
2139 <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>
2147 <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>
2148 <para>The <envar>XDG_DATA_DIRS</envar> environment variable can be used to change these directories.</para>
2149 <para>The <envar>XDG_DATA_HOME</envar> environment variable s also used (if set) to look for these extension files.</para>
2154 <section><title>What to Do if &appname; Does Not Seem to Work</title>
2156 In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
2157 <programlisting>viking -dV</programlisting>
2160 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.
2161 E.g. Something like this for DEMs:
2163 ** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
2164 * About to connect() to dds.cr.usgs.gov port 80 (#0)
2165 * Trying 152.61.128.95... * connected
2166 * Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
2167 GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
2168 User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
2169 Host: dds.cr.usgs.gov
2172 Date: Sun, 26 Jul 2009 18:13:38 GMT
2174 Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
2175 ETag: eac3f8-1828f5-46f3caa76070a
2176 Accept-Ranges: bytes
2177 Content-Length: 1583349
2178 Content-Type: application/zip
2180 * Connection #0 to host dds.cr.usgs.gov left intact
2181 * Closing connection #0
2182 ** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
2184 Or for OSM Mapnik tile server:
2186 * About to connect() to tile.openstreetmap.org port 80 (#0)
2187 * Trying 193.63.75.28... * connected
2188 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2189 GET /13/4065/2748.png HTTP/1.1
2190 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2191 Host: tile.openstreetmap.org
2194 * HTTP 1.0, assume close after body
2196 Date: Thu, 14 Oct 2010 22:18:42 GMT
2197 Server: Apache/2.2.8 (Ubuntu)
2198 ETag: "b66ff9d46474bab68262a3483428a232"
2199 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
2200 Content-Length: 17194
2201 Cache-Control: max-age=94805
2202 Expires: Sat, 16 Oct 2010 00:38:47 GMT
2203 Content-Type: image/png
2205 X-Cache: HIT from konqi.openstreetmap.org
2206 X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
2207 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2210 * Closing connection #0
2211 * About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
2212 * Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
2213 * About to connect() to tile.openstreetmap.org port 80 (#0)
2214 * Trying 193.63.75.28... * connected
2215 * Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
2216 GET /tiles/cycle/13/4065/2747.png HTTP/1.1
2217 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2218 Host: a.andy.sandbox.cloudmade.com
2222 * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
2223 GET /13/4065/2749.png HTTP/1.1
2224 User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
2225 Host: tile.openstreetmap.org
2228 * HTTP 1.0, assume close after body
2230 Date: Thu, 14 Oct 2010 23:44:35 GMT
2231 Server: Apache/2.2.8 (Ubuntu)
2232 ETag: "8e520ad47ce9c1b63430554886eb5fab"
2233 ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
2234 Content-Length: 18094
2235 Cache-Control: max-age=87742
2236 Expires: Sat, 16 Oct 2010 00:06:57 GMT
2237 Content-Type: image/png
2238 X-Cache: MISS from konqi.openstreetmap.org
2239 X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
2240 Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
2248 <section><title>Dependencies</title>
2249 <formalpara><title>gpsbabel</title>
2250 <para>&appname; uses <ulink url="http://gpsbabel.org/">GPSBabel</ulink> to convert data.</para>
2252 <formalpara><title>unbuffer (optional)</title>
2253 <para>&appname; uses unbuffer command to optimize conversion calls.</para>
2255 <formalpara><title>gpsd (optional - but not <trademark>Windows</trademark>)</title>
2256 <para>&appname; can use <ulink url="http://www.catb.org/gpsd/">gpsd</ulink> to get the current location.</para>