]>
Commit | Line | Data |
---|---|---|
f8b8a0b5 GB |
1 | <?xml version="1.0"?> |
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>"> | |
05593e97 | 6 | <!ENTITY appversion "1.0"> |
f8b8a0b5 | 7 | <!ENTITY manrevision "0.1"> |
7233fcb6 | 8 | <!ENTITY date "October 2010"> |
f8b8a0b5 GB |
9 | ]> |
10 | <!-- | |
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 | |
16 | ||
17 | --> | |
18 | <!-- =============Document Header ============================= --> | |
19 | <article id="index" lang="en"> | |
20 | <articleinfo> | |
21 | <title>&app; Manual</title> | |
22 | <abstract role="description"> | |
23 | <para>&app; is a free/open source program to manage GPS data.</para> | |
24 | </abstract> | |
25 | ||
26 | <copyright> | |
27 | <year>2009</year> | |
28 | <holder>Guilhem Bonnefille</holder> | |
29 | </copyright> | |
30 | ||
31 | <!-- An address can be added to the publisher information. --> | |
32 | <publisher role="maintainer"> | |
33 | <publishername>GNOME Documentation Project</publishername> | |
34 | </publisher> | |
35 | ||
36 | <xi:include href="legal.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> | |
37 | <!-- The file legal.xml contains link to license for the documentation, | |
38 | and other legal stuff such as "NO WARRANTY" statement. | |
39 | Please do not change any of this. --> | |
40 | ||
41 | <authorgroup> | |
42 | <author> | |
43 | <firstname>Guilhem</firstname> | |
44 | <surname>Bonnefille</surname> | |
45 | </author> | |
25c0a45b RN |
46 | <author> |
47 | <firstname>Rob</firstname> | |
48 | <surname>Norris</surname> | |
49 | </author> | |
a43e638f RN |
50 | <!-- Contributors from the Wiki history --> |
51 | <author> | |
52 | <firstname>username:</firstname> | |
53 | <surname>Alexxy</surname> | |
54 | </author> | |
55 | <author> | |
56 | <firstname>username:</firstname> | |
57 | <surname>Vikingis</surname> | |
58 | </author> | |
59 | <author> | |
60 | <firstname>username:</firstname> | |
61 | <surname>Tallguy</surname> | |
62 | </author> | |
63 | <author> | |
64 | <firstname>username:</firstname> | |
65 | <surname>EliotB</surname> | |
66 | </author> | |
67 | <author> | |
68 | <firstname>Alex</firstname> | |
69 | <surname>Foobarian</surname> | |
70 | </author> | |
71 | <!-- END --> | |
f8b8a0b5 GB |
72 | </authorgroup> |
73 | ||
74 | <revhistory> | |
75 | <revision> | |
76 | <revnumber>&appname; Manual V&manrevision;</revnumber> | |
77 | <date>&date;</date> | |
78 | <revdescription> | |
79 | <para role="author">Guilhem Bonnefille <email>guilhem.bonnefille@gmail.com</email></para> | |
80 | <para role="publisher">GNOME Documentation Project</para> | |
81 | </revdescription> | |
82 | </revision> | |
83 | </revhistory> | |
84 | ||
4502fc82 | 85 | <releaseinfo>This manual describes version &appversion; of &appname;.</releaseinfo> |
f8b8a0b5 GB |
86 | |
87 | <legalnotice> | |
88 | <title>Feedback</title> | |
89 | <para>To report a bug or make a suggestion regarding the &app; application or | |
90 | this manual, follow the directions in the | |
91 | <ulink url="ghelp:user-guide?feedback-bugs" type="help">Feedback section of the GNOME User Guide</ulink>. | |
92 | </para> | |
93 | </legalnotice> | |
94 | </articleinfo> | |
95 | ||
96 | <indexterm zone="index"> | |
97 | <primary>&app;</primary> | |
98 | </indexterm> | |
99 | <!-- ============= Document Body ============================= --> | |
4502fc82 | 100 | <section id="introduction"> |
f8b8a0b5 | 101 | <title>Introduction</title> |
6928e16b | 102 | <para> |
7233fcb6 RN |
103 | &appname; aims to be easy to use, yet powerful in accomplishing a wide |
104 | variety of tasks. Some of the things you can use &appname; for are: | |
6928e16b GB |
105 | </para> |
106 | <itemizedlist mark="opencircle"><listitem> | |
107 | <para> | |
108 | Uploading and downloading waypoints, tracks to/from GPS. | |
109 | </para> | |
110 | </listitem> | |
111 | <listitem> | |
112 | <para>Preparing tracks and waypoints for trips using maps from services | |
7233fcb6 | 113 | such as OpenStreetMap (OSM) and/or Terrasever. The data is only needed to be uploaded to |
6928e16b GB |
114 | your GPS before you leave. The maps together with your tracks and |
115 | waypoints can also be printed and used during the trip. | |
116 | </para> | |
117 | </listitem> | |
118 | <listitem> | |
119 | <para> | |
120 | After trips, tracks and waypoints from GPS can be downloaded, stored, managed and reused in your (or your friends') later trips. | |
121 | </para> | |
122 | </listitem> | |
123 | <listitem> | |
124 | <para> | |
9ca89c29 | 125 | Analyzing Off Highway Vehicle (OHV) and hiking trips, understanding where you went and how far you were from something. |
6928e16b GB |
126 | </para> |
127 | </listitem> | |
128 | <listitem> | |
129 | <para>Making waypoints and tracks to follow to easily get someplace | |
9ca89c29 | 130 | you've never been before or don't have GPS data for but online |
6928e16b GB |
131 | maps exist for it. |
132 | </para> | |
133 | </listitem> | |
134 | <listitem> | |
135 | <para> | |
136 | Making maps with coordinate lines. | |
137 | </para> | |
138 | </listitem> | |
139 | <listitem> | |
140 | <para> | |
141 | Grouping data from multiple trips using a hierarchical data manager. | |
142 | </para> | |
143 | </listitem> | |
144 | <listitem> | |
145 | <para> | |
146 | Analyzing speed at different places (to some degree), adding waypoints where you forgot to mark one but did slow down or stop. | |
147 | </para> | |
148 | </listitem> | |
149 | <listitem> | |
150 | <para> | |
9ca89c29 | 151 | Downloading and storing OSM and/or Terraserver maps on your hard drive and looking at them later. |
6928e16b GB |
152 | </para> |
153 | </listitem> | |
154 | <listitem> | |
155 | <para> | |
156 | Editing tracks and trackpoints, joining and splitting up tracks | |
157 | </para> | |
158 | </listitem> | |
0ef60ec1 | 159 | <listitem> |
6928e16b | 160 | <para> |
9ca89c29 | 161 | Show the live GPS position on the map (for use on a mobile device - e.g. a laptop) |
6928e16b GB |
162 | </para> |
163 | </listitem> | |
9ca89c29 RN |
164 | </itemizedlist> |
165 | <note> | |
6928e16b | 166 | <para> |
9ca89c29 | 167 | &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>: |
6928e16b | 168 | </para> |
9ca89c29 | 169 | </note> |
4502fc82 | 170 | </section> |
7233fcb6 | 171 | |
6928e16b | 172 | <section><title>General Concepts</title> |
7233fcb6 RN |
173 | <section><title>Layers</title> |
174 | <para> | |
175 | 'Layers' is concept one may know from powerful graphics editors such as Photoshop or GIMP. | |
176 | Instead of putting all the data on the same level, it is stacked (i.e. layered) with different data over one another. | |
177 | This can make useful for analysis and general handling of various sets of data. | |
178 | </para> | |
179 | <para> | |
180 | Unfortunately the downside of this complexity is remembering how differing layers of data can obscure other data. | |
181 | </para> | |
182 | <para> | |
183 | The Map layers have <ulink url="http://en.wikipedia.org/wiki/Alpha_compositing"><citetitle>Alpha Compositing</citetitle></ulink>, | |
184 | to create the appearance of partial transparency. | |
185 | By controlling this value one can see data below it in the layer heirarchy for interesting effects. | |
186 | </para> | |
187 | </section> | |
188 | <section><title>Layers Panel</title> | |
6928e16b GB |
189 | <para> |
190 | The panel on the left is called the <emphasis role="bold">layers panel</emphasis>. | |
191 | It determines which layers and sublayers (such as tracks and waypoints) | |
192 | are shown, and the order in which they are drawn. Layers list on the | |
193 | top of the layers panel are drawn last. You can change the order by | |
194 | drag and drop, or by selecting a layer and using the up and down | |
195 | buttons at the bottom of the layers panel. | |
196 | </para> | |
7233fcb6 RN |
197 | </section> |
198 | <section><title>Viewport</title> | |
6928e16b | 199 | <para> |
7233fcb6 | 200 | The main &appname; area where the layer data is drawn, is called the <emphasis role="bold">viewport</emphasis>. |
6928e16b | 201 | </para> |
6928e16b | 202 | </section> |
7233fcb6 | 203 | <section><title>Statusbar</title> |
7233fcb6 | 204 | <para>This provides a readout of various information:</para> |
eabf51fc GB |
205 | <itemizedlist> |
206 | <listitem><para>The currently selected (mouse pointer) tool</para></listitem> | |
207 | <listitem><para>The number of items to process in the background - normally this the number in the map tile download queue</para></listitem> | |
208 | <listitem><para>The zoom factor</para></listitem> | |
209 | <listitem><para>The location of the mouse pointer (and potentially height information if DEM data is available)</para></listitem> | |
210 | </itemizedlist> | |
7233fcb6 | 211 | </section> |
d587678a GB |
212 | |
213 | <section><title>Projections</title> | |
214 | <para> | |
215 | &appname; supports differents projections: | |
216 | <itemizedlist> | |
217 | <listitem> | |
218 | <para>UTM</para> | |
219 | </listitem> | |
220 | <listitem> | |
221 | <para>LatLon (also called EPSG:4326)</para> | |
222 | </listitem> | |
223 | <listitem> | |
224 | <para>Mercator (also called Spherical Mercator)</para> | |
225 | </listitem> | |
226 | </itemizedlist> | |
227 | </para> | |
228 | </section> | |
7233fcb6 RN |
229 | </section> |
230 | ||
6928e16b | 231 | <section><title>Layers</title> |
036c28fc | 232 | |
6928e16b GB |
233 | <section><title>TrackWaypoint Layer</title> |
234 | <para> | |
235 | TrackWaypoint layers display GPS data (tracks and waypoints). | |
236 | </para> | |
7233fcb6 | 237 | <para>One way to create new waypoints is to copy a |
6928e16b | 238 | latitude/longitude coordinate pair, such as the one shown on most |
0ef60ec1 GB |
239 | geocaches, and paste it into an active TrackWaypoint layer. &appname; can |
240 | automatically recognize several variations of the lat/lon format. | |
241 | </para> | |
6928e16b GB |
242 | <para> |
243 | By right-clicking tracks and waypoints in the layers panel, you can do | |
244 | many things with tracks and waypoints. You can easily find a specific | |
245 | track or waypoint by expanding the Tracks or Waypoints sublayers in the | |
246 | layers panel to show all tracks or waypoints, and typing the name of | |
247 | the track/waypoint. | |
248 | </para> | |
036c28fc | 249 | |
6928e16b GB |
250 | <section><title>Layer Operations</title> |
251 | <para> | |
252 | The layer has a context menu with several operations. | |
253 | </para> | |
036c28fc RN |
254 | |
255 | <section><title>View Layer</title> | |
256 | <para> | |
257 | Version1.1+: This will automatically move the viewport and select the best zoom level to see the whole layer (i.e. tracks and waypoints). | |
258 | </para> | |
259 | </section> | |
260 | ||
261 | <section><title>View All Tracks</title> | |
262 | <para> | |
263 | 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). | |
264 | </para> | |
265 | </section> | |
266 | ||
267 | <section><title>View All Waypoints</title> | |
268 | <para> | |
269 | 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). | |
270 | </para> | |
271 | </section> | |
272 | ||
273 | <section><title>Goto Center of Layer</title> | |
274 | <para> | |
275 | This will automatically move the viewport to see the whole layer (i.e. tracks and waypoints). It does not adjust the zoom level. | |
276 | </para> | |
277 | </section> | |
278 | ||
279 | <section><title>Goto Waypoint</title> | |
280 | <para> | |
281 | This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it. | |
282 | </para> | |
283 | <note> | |
284 | <para> | |
285 | Note this search is not very clever and only finds exact matches. | |
286 | 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. | |
287 | </para> | |
288 | </note> | |
289 | </section> | |
290 | ||
291 | <section><title>Export Layer</title> | |
292 | <para> | |
293 | The layer (all tracks and waypoints) can be exported to a file GPX, GPSPoint or GPSMapper format. | |
294 | </para> | |
295 | <para> | |
296 | Version1.1+: An individual track can be exported to a GPX file via the track menu. | |
297 | </para> | |
298 | </section> | |
299 | ||
cc1083b3 | 300 | <section id="new_wp"><title>New Waypoint</title> |
036c28fc RN |
301 | <para> |
302 | 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. | |
303 | </para> | |
304 | </section> | |
305 | ||
306 | <section><title>Add Wikipedia Waypoints</title> | |
307 | <para> | |
308 | This gets 'interesting' points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary. | |
309 | </para> | |
310 | </section> | |
311 | ||
312 | <section id="osm_upload"><title>Upload To OSM</title> | |
313 | <para> | |
314 | This opens a dialog to upload all tracks and waypoints to OSM traces. | |
315 | Useful if you are an OSM contributor (you will need an OSM account), these details can be stored in &appname; preferences. | |
316 | </para> | |
6928e16b | 317 | <para> |
036c28fc | 318 | &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 OSM. |
6928e16b | 319 | </para> |
0ef60ec1 | 320 | <note> |
6928e16b | 321 | <para> |
036c28fc RN |
322 | <emphasis role="bold">Warning!</emphasis> |
323 | The password is transferred <emphasis role="bold">unencrypted</emphasis> in every request sent to the OSM server. This is due to OSM's basic authentication method. | |
6928e16b | 324 | </para> |
0ef60ec1 | 325 | </note> |
036c28fc | 326 | </section> |
6928e16b | 327 | |
036c28fc RN |
328 | <section><title>Filter</title> |
329 | <section><title>Simplify All Tracks</title> | |
330 | <para> | |
331 | 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. | |
332 | </para> | |
333 | </section> | |
334 | <section><title>Remove Duplicate Waypoints</title> | |
335 | <para> | |
336 | Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer. | |
337 | </para> | |
338 | <note> | |
339 | <para> | |
340 | 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. | |
341 | </para> | |
342 | </note> | |
343 | </section> | |
6928e16b GB |
344 | </section> |
345 | ||
036c28fc RN |
346 | <section id="filter_with_track"><title>Filter With <emphasis>Trackname</emphasis></title> |
347 | <para> | |
348 | 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: | |
349 | </para> | |
350 | <itemizedlist> | |
351 | <listitem><para>Waypoints Inside This</para></listitem> | |
352 | <listitem><para>Waypoints Outside This</para></listitem> | |
353 | </itemizedlist> | |
354 | <para> | |
355 | The result is generated in a new Track/Waypoint layer. | |
356 | </para> | |
6928e16b | 357 | </section> |
036c28fc RN |
358 | |
359 | </section><!-- End TRW Layer Options --> | |
360 | ||
6928e16b GB |
361 | <section><title>Track Properties</title> |
362 | <para> | |
363 | Show many useful statistics about a track, including a | |
364 | elevation-distance graph and a speed-time graph (if data is available). | |
365 | You can click these graphs to jump to the point in the track. You can | |
366 | also reverse a track, delete duplicates, and split a track from its | |
367 | component segments (discontinuous breaks in a track) into separate | |
368 | tracks. | |
369 | </para> | |
370 | <para> | |
371 | The following colors are used in the elevation-distance graph: | |
372 | </para> | |
0ef60ec1 GB |
373 | <variablelist> |
374 | <varlistentry> | |
7233fcb6 | 375 | <term>'Main' colour - this is dependent on your Desktop theme - often blue by default</term> |
0ef60ec1 GB |
376 | <listitem><para>elevation data in graph</para></listitem> |
377 | </varlistentry> | |
378 | <varlistentry> | |
379 | <term>Yellow</term> | |
6928e16b | 380 | <listitem> |
0ef60ec1 | 381 | <para>no elevation data</para> |
6928e16b | 382 | </listitem> |
0ef60ec1 GB |
383 | </varlistentry> |
384 | <varlistentry> | |
385 | <term>Green</term> | |
6928e16b | 386 | <listitem> |
0ef60ec1 | 387 | <para>elevation data from DEM</para> |
6928e16b | 388 | </listitem> |
0ef60ec1 GB |
389 | </varlistentry> |
390 | <varlistentry> | |
391 | <term>Red</term> | |
6928e16b | 392 | <listitem> |
0ef60ec1 | 393 | <para>speed</para> |
6928e16b | 394 | </listitem> |
0ef60ec1 GB |
395 | </varlistentry> |
396 | </variablelist> | |
6928e16b GB |
397 | |
398 | </section> | |
399 | <section><title>Track Operations</title> | |
400 | <section><title>Merge by time</title> | |
0ef60ec1 GB |
401 | <para> |
402 | This operation repeatedly tries to merge the right-clicked track | |
6928e16b GB |
403 | with tracks in the same TrackWaypoint layer. The tracks which are |
404 | merged are those which have at least one trackpoint less than some | |
405 | threshold time away. This way, if you somehow end up with lots of small | |
406 | segments (say, caused by turning the GPS on and off) you can merge them | |
0ef60ec1 GB |
407 | easily into one track. |
408 | </para> | |
6928e16b GB |
409 | |
410 | </section> | |
411 | <section><title>Split by time</title> | |
412 | <para> | |
413 | This operation will split a single track into segments wherever the | |
414 | time interval between successive trackpoints is larger than some | |
415 | threshold. This is useful when processing raw NMEA GPS data, especially | |
0ef60ec1 GB |
416 | taken over a long time. |
417 | </para> | |
6928e16b GB |
418 | |
419 | </section> | |
420 | <section><title>Apply DEM data</title> | |
421 | <para> | |
422 | If any DEM data is loaded, this will apply the DEM data to give the track elevation data. | |
423 | </para> | |
424 | ||
425 | </section> | |
426 | <section><title>Extend track end</title> | |
427 | <para> | |
428 | Change the current tool to add track and add points to the end of the track. | |
429 | </para> | |
430 | ||
431 | </section> | |
432 | <section><title>Upload to OSM</title> | |
433 | <para> | |
7233fcb6 | 434 | Useful if you are an OSM contributor. &appname; |
9ca89c29 | 435 | allows you to import a track, edit it if you so wish to remove |
6928e16b | 436 | duplicate points, perhaps track points leading to your home, and then |
9ca89c29 | 437 | directly export the track to OSM. |
6928e16b GB |
438 | </para> |
439 | ||
440 | </section> | |
441 | <section><title>View Google Directions</title> | |
0ef60ec1 GB |
442 | <para> |
443 | Launch a web browser to see the Google directions page which | |
444 | yielded the route. | |
445 | </para> | |
446 | <note> | |
447 | <para> | |
448 | The record of the Google route is stored in | |
6928e16b GB |
449 | the track's comment, so if the comment is changed (or the route was |
450 | created by something other than the Magic Scissors tool) this will not | |
451 | work correctly. | |
452 | </para> | |
0ef60ec1 | 453 | </note> |
6928e16b GB |
454 | |
455 | </section> | |
456 | ||
457 | </section> | |
cc1083b3 | 458 | |
6928e16b | 459 | <section><title>Waypoint Operations</title> |
cc1083b3 RN |
460 | |
461 | <section><title>Goto</title> | |
6928e16b | 462 | <para> |
cc1083b3 | 463 | This centers the viewport on the selected waypoint. |
6928e16b | 464 | </para> |
cc1083b3 | 465 | </section> |
6928e16b | 466 | |
cc1083b3 RN |
467 | <section><title>Visit Geocache Webpage</title> |
468 | <para> | |
469 | If the waypoint's name is in Geocache form (GCXXXXX) you can launch a web browser to go to the Geocache page. | |
470 | </para> | |
6928e16b GB |
471 | </section> |
472 | ||
cc1083b3 RN |
473 | <section><title>New Waypoint</title> |
474 | <para> | |
475 | Same as the layer <link linkend="new_wp">New Waypoint</link>. | |
476 | </para> | |
6928e16b GB |
477 | </section> |
478 | ||
cc1083b3 RN |
479 | </section><!-- WP END --> |
480 | ||
036c28fc RN |
481 | </section><!-- TRW Layer END --> |
482 | ||
7233fcb6 | 483 | <section><title>GPS Layer</title> |
0ef60ec1 | 484 | <para> |
7233fcb6 | 485 | The GPS layer is responsible for uploading and downloading GPS data |
6928e16b | 486 | from a GPS device. It also is responsible for realtime GPS tracking. |
7233fcb6 | 487 | Expand the GP SLayer in the layers panel to see the two TRWLayers it |
6928e16b | 488 | uses for uploading and downloading. To upload, download, or use |
7233fcb6 | 489 | realtime tracking, right-click the GPS layer and click the appropiate |
6928e16b GB |
490 | menu item. |
491 | </para> | |
0ef60ec1 | 492 | |
6928e16b GB |
493 | <section><title>Download</title> |
494 | <para> | |
7233fcb6 | 495 | To download data from the GPS, right-click the GPS layer and click <guimenuitem>Download from GPS</guimenuitem>. |
6928e16b GB |
496 | </para> |
497 | ||
498 | </section> | |
499 | <section><title>Upload</title> | |
0ef60ec1 GB |
500 | <para> |
501 | To upload data to the GPS, first populate the GPS Upload child | |
6928e16b GB |
502 | layer of the GPS layer (either by creating waypoints/tracks in it, or |
503 | copying and pasting or dragging waypoints/tracks from another layer). | |
7233fcb6 | 504 | Then right-click the GPS layer and click <guimenuitem>Upload to GPS</guimenuitem>. |
6928e16b GB |
505 | </para> |
506 | ||
507 | </section> | |
7233fcb6 | 508 | <section><title>Realtime Tracking</title> |
0ef60ec1 GB |
509 | <para> |
510 | You must set up gpsd correctly or use a GPSD server and put the | |
7233fcb6 RN |
511 | correct information in the GPS layer properties dialog. Then right-click |
512 | the layer and select <guimenuitem>Start Realtime Tracking</guimenuitem>. | |
6928e16b GB |
513 | </para> |
514 | ||
515 | </section> | |
516 | ||
517 | </section> | |
7233fcb6 | 518 | <section><title>(Digital Elevation Model) DEM Layer (todo)</title> |
6928e16b | 519 | <para> |
7233fcb6 | 520 | The current NASA SRTM server is: http://dds.cr.usgs.gov/srtm/version2_1/ |
6928e16b GB |
521 | </para> |
522 | ||
523 | </section> | |
524 | ||
525 | </section> | |
f95c9f7c | 526 | |
6928e16b GB |
527 | <section><title>Tools</title> |
528 | <para> | |
529 | You can use the scroll wheel and the right-click to zoom and pan no matter what tool you are using. | |
530 | </para> | |
531 | <para> | |
f95c9f7c | 532 | Scroll: zoom in and out without changing the center (also Ctrl+, Ctrl- [*not* KeyPad +/-]) |
6928e16b GB |
533 | </para> |
534 | <para> | |
535 | Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down) | |
536 | </para> | |
537 | <para> | |
538 | Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right) | |
539 | </para> | |
540 | <para> | |
541 | Ctrl-shift-scroll: zoom in and out, keeping mouse over same location (like Google maps) | |
542 | </para> | |
543 | <para> | |
f95c9f7c | 544 | Left or Middle-click: make the clicked point on the map the center |
6928e16b GB |
545 | </para> |
546 | <para> | |
547 | Middle-click and drag: pan | |
548 | </para> | |
f95c9f7c | 549 | |
6928e16b GB |
550 | <section><title>Zoom</title> |
551 | <para> | |
552 | Zooms in and out on the clicked part of the map. | |
553 | </para> | |
6928e16b | 554 | </section> |
f95c9f7c | 555 | |
6928e16b | 556 | <section><title>Ruler</title> |
9ca89c29 RN |
557 | <para> |
558 | 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. | |
559 | A second click will 'freeze' the ruler at that point. | |
6928e16b | 560 | </para> |
6928e16b | 561 | </section> |
f95c9f7c | 562 | |
6928e16b GB |
563 | <section><title>TrackWaypoint Layer Tools</title> |
564 | <para> | |
f95c9f7c | 565 | You must have a TrackWaypoint Layer selected to use these tools. |
6928e16b | 566 | </para> |
f95c9f7c | 567 | <section><title>Create Waypoint</title> |
6928e16b | 568 | <para> |
f95c9f7c | 569 | Left click will open the new waypoint dialog using the specified position. |
6928e16b | 570 | </para> |
f95c9f7c RN |
571 | </section> |
572 | ||
573 | <section><title>Create/Begin Track</title> | |
6928e16b | 574 | <para> |
f95c9f7c RN |
575 | Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track. |
576 | If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint. | |
577 | Right click or <keycap>Backspace</keycap> : undo one point. | |
6928e16b GB |
578 | </para> |
579 | <para> | |
f95c9f7c | 580 | Double click or <keycap>Escape</keycap> : finish track creation. |
6928e16b | 581 | </para> |
6928e16b | 582 | </section> |
f95c9f7c | 583 | |
6928e16b GB |
584 | <section><title>Edit Waypoint</title> |
585 | <para> | |
f95c9f7c RN |
586 | Left Click/drag: select/move a waypoint. |
587 | If <keycap>Ctrl</keycap> is held at the same time, it will jump the waypoint position to a nearby existing trackpoint. | |
588 | If <keycap>Shift</keycap> is held at the same time, it will jump the waypoint position to a nearby existing waypoint. | |
6928e16b GB |
589 | </para> |
590 | <para>Right-click on waypoint: opens a menu with waypoint actions (the | |
591 | same menu accessed by right-clicking the waypoint in the layers panel) | |
592 | </para> | |
6928e16b | 593 | </section> |
f95c9f7c | 594 | |
6928e16b GB |
595 | <section><title>Edit Trackpoint</title> |
596 | <para> | |
f95c9f7c RN |
597 | Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint. |
598 | Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint. | |
599 | If <keycap>Ctrl</keycap> is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint. | |
6928e16b GB |
600 | </para> |
601 | <para> | |
f95c9f7c | 602 | 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. |
6928e16b | 603 | </para> |
6928e16b | 604 | </section> |
f95c9f7c | 605 | |
6928e16b GB |
606 | <section><title>Show Picture</title> |
607 | <para> | |
f95c9f7c RN |
608 | Opens an image viewer with the picture associated with the waypoint. |
609 | On Linux this uses <application>eog</application>. | |
610 | On Windows this uses the default system image viewer. | |
6928e16b | 611 | </para> |
6928e16b | 612 | </section> |
f95c9f7c | 613 | |
6928e16b GB |
614 | <section><title>Magic Scissors</title> |
615 | <para>Creates a track using Google maps routing between two points. | |
f95c9f7c | 616 | Requires an internet connection. Click one point, then click another to |
6928e16b GB |
617 | create a track. |
618 | </para> | |
619 | <para> | |
f95c9f7c | 620 | Right-click: undo last routing (only track removed - not any waypoints) |
6928e16b GB |
621 | </para> |
622 | <para> | |
f95c9f7c | 623 | <keycap>Ctrl</keycap>: continue previous track |
6928e16b | 624 | </para> |
6928e16b GB |
625 | </section> |
626 | ||
627 | </section> | |
f95c9f7c | 628 | |
6928e16b GB |
629 | <section><title>Georef Map Layer Tools</title> |
630 | <para> | |
631 | You must have a Georef Map Layer selected to use these tools. | |
632 | </para> | |
633 | <section><title>Georef zoom</title> | |
634 | <para>Changes the zoom level of the georeferenced map and changes the | |
7233fcb6 | 635 | &appname; zoom level accordingly. Useful if you are trying to match GPS |
6928e16b GB |
636 | data to a georeferenced map. |
637 | </para> | |
6928e16b | 638 | </section> |
f95c9f7c | 639 | |
6928e16b GB |
640 | <section><title>Georef move</title> |
641 | <para> | |
642 | Drag to move the georeferenced map. | |
643 | </para> | |
6928e16b | 644 | </section> |
6928e16b | 645 | </section> |
f95c9f7c | 646 | |
6928e16b GB |
647 | <section><title>Map Download</title> |
648 | <para> | |
f95c9f7c RN |
649 | You must have a Map Layer selected to use this. |
650 | </para> | |
651 | <para> | |
6928e16b GB |
652 | Click to download a single tile. Drag to download tiles in the dragged rectangle area. |
653 | </para> | |
654 | <para> | |
655 | Right-click to redownload bad/all tiles. Right-click and drag to redownload bad/all tiles in the dragged rectangle area. | |
656 | </para> | |
6928e16b | 657 | </section> |
f95c9f7c | 658 | |
6928e16b GB |
659 | <section><title>DEM Download</title> |
660 | <para> | |
f95c9f7c RN |
661 | You must have a DEM Layer selected to use this. |
662 | </para> | |
663 | <para> | |
6928e16b GB |
664 | Click to download and import a DEM file. |
665 | </para> | |
6928e16b GB |
666 | </section> |
667 | ||
7233fcb6 | 668 | <section><title>Webtools</title> |
5ab84304 GB |
669 | <para> |
670 | Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.). | |
671 | </para> | |
672 | <para> | |
673 | Jumping from &app; to such service can become annoying. | |
674 | </para> | |
675 | <para> | |
0ef60ec1 | 676 | &appname; allows you to open such service directly at the position currently viewed in &app;. |
5ab84304 GB |
677 | </para> |
678 | <para> | |
7233fcb6 | 679 | This feature is called <guilabel>Webtools</guilabel>. It is also known as External Tools. |
5ab84304 | 680 | </para> |
5ab84304 GB |
681 | </section> |
682 | ||
3e850af1 | 683 | </section> |
f95c9f7c | 684 | |
0ef60ec1 | 685 | <!-- Preferences --> |
3e850af1 GB |
686 | <section><title>Preferences</title> |
687 | <section><title>Localisation</title> | |
688 | <para>You can select units displayed by &appname; to best fit your usage.</para> | |
689 | <figure> | |
690 | <title>Properties dialog: units part</title> | |
691 | <screenshot> | |
692 | <graphic format="PNG" fileref="figures/properties_units.png"/> | |
693 | </screenshot> | |
694 | </figure> | |
695 | <para>Concerning degrees, you can select the way to display them: | |
696 | <variablelist> | |
697 | <varlistentry> | |
698 | <term>DDD</term><listitem><para>decimal degree</para></listitem> | |
699 | </varlistentry> | |
700 | <varlistentry> | |
701 | <term>DDD</term><listitem><para>partial sexagesimal display: degrees, minutes and décimal part of minutes</para></listitem> | |
702 | </varlistentry> | |
703 | <varlistentry> | |
704 | <term>DMS</term><listitem><para>sexagesimal display: degrees, minutes and seconds</para></listitem> | |
705 | </varlistentry> | |
706 | </variablelist> | |
707 | </para> | |
708 | <figure> | |
709 | <title>Properties dialog: degree display options</title> | |
710 | <screenshot> | |
711 | <graphic format="PNG" fileref="figures/properties_degree.png"/> | |
712 | </screenshot> | |
713 | </figure> | |
714 | </section> | |
a067ca58 GB |
715 | <section><title>Tile's age</title> |
716 | <para>This age is used to decided wether or not a new request to tile server must be done. | |
717 | </para> | |
718 | <para>Changing this value, you will increase or decrese the network load.</para> | |
719 | </section> | |
897e919b GB |
720 | <section><title>Default maplayer directory</title> |
721 | <para>This property sets the default directory of the tiles cache. | |
722 | This value is used when you create a new map layer. | |
723 | </para> | |
724 | <para>You are still able to change this value in each map layer properties.</para> | |
725 | </section> | |
6928e16b GB |
726 | </section> |
727 | <section><title>Mini-Howto's</title> | |
728 | <section><title>Getting Started</title> | |
729 | <para> | |
0ef60ec1 | 730 | To quickly get started using &appname;, follow these instructions. |
6928e16b GB |
731 | </para> |
732 | <section><title>Go to an area of interest</title> | |
733 | <para> | |
9ca89c29 | 734 | &appname;'s default location is a Manhatten, New York, USA, so you may need to pick another place that interests you. |
6928e16b | 735 | </para> |
0ef60ec1 GB |
736 | <procedure> |
737 | <title>Method A</title> | |
738 | <step> | |
6928e16b | 739 | <para> |
0ef60ec1 | 740 | Use View - Go to to move to a coordinate of interest. |
6928e16b | 741 | </para> |
0ef60ec1 GB |
742 | </step> |
743 | </procedure> | |
744 | <procedure> | |
745 | <title>Method B</title> | |
746 | <step> | |
7233fcb6 RN |
747 | <para>Use the GPS Layer or <menuchoice><guimenu>File</guimenu><guimenuitem>Acquire</guimenuitem><guimenuitem>From GPS</guimenuitem></menuchoice> |
748 | to load data directly from your GPS into &appname;. | |
4136d029 | 749 | Currently Garmin, Magellan, DeLorme and Navilink protocols are supported. |
0ef60ec1 | 750 | </para> |
7233fcb6 RN |
751 | <note> |
752 | <para>You must have write permission to the port used. For Unix like OS:</para> | |
753 | <para>/dev/ttyS0 is the first serial port</para> | |
754 | <para>/dev/ttyUSB0 is the first USB port</para> | |
755 | </note> | |
ad606d98 | 756 | <note><para>For DeLorme device support you will need GPSBabel v1.4.0+ installed</para></note> |
0ef60ec1 GB |
757 | </step> |
758 | </procedure> | |
759 | <procedure> | |
760 | <title>Method C</title> | |
761 | <step> | |
762 | <para>Get data from files in GPX format. For other formats (kml, | |
763 | ozi...), use a converter such as GPSBabel to convert the files to GPX | |
764 | format first. | |
6928e16b | 765 | </para> |
0ef60ec1 GB |
766 | </step> |
767 | <step> | |
6928e16b | 768 | <para> |
7233fcb6 | 769 | Open up &appname; and use File - Open or File - Append |
0ef60ec1 | 770 | file to open the file. |
6928e16b | 771 | </para> |
0ef60ec1 GB |
772 | </step> |
773 | <step> | |
6928e16b | 774 | <para> |
0ef60ec1 | 775 | Expand Tracks or Waypoints. Right-click on the |
7233fcb6 | 776 | track or waypoint of interest and select <guimenuitem>Goto "Center"</guimenuitem>. |
6928e16b | 777 | </para> |
0ef60ec1 GB |
778 | </step> |
779 | </procedure> | |
780 | <procedure> | |
781 | <title>Method D</title> | |
782 | <step> | |
6928e16b | 783 | <para> |
0ef60ec1 | 784 | Use File - Append File to add your track and waypoint data to |
7233fcb6 | 785 | &appname;. This has been tested with Geocaching.com's *.loc format, |
0ef60ec1 GB |
786 | (others(?)). |
787 | </para> | |
788 | </step> | |
789 | <step> | |
790 | <para> | |
791 | Expand Tracks or Waypoints. Right-click on the tack or | |
7233fcb6 | 792 | point of interest and select <guimenuitem>Goto "Center"</guimenuitem>. |
0ef60ec1 GB |
793 | </para> |
794 | </step> | |
795 | </procedure> | |
6928e16b GB |
796 | </section> |
797 | <section><title>Add a map layer</title> | |
798 | <para> | |
799 | 1. Use Layers - New Map Layer, and choose a suitable cache directory | |
0ef60ec1 | 800 | where you would like to store your tracks and click <guilabel>OK</guilabel>. Zoom to a |
6928e16b GB |
801 | comfortable level (I suggest 4 mpp) by clicking the left and right |
802 | mouse buttons on the gray area where your tracks are. Now from the menu | |
803 | choose Tools - Map Download, Click where you would like to download a | |
804 | map. Regardless of what tool you are using, the middle mouse button | |
805 | always pans. </para> | |
0ef60ec1 | 806 | <note> |
6928e16b | 807 | <para> |
9ca89c29 | 808 | You need an open internet connection when you are downloading maps. |
6928e16b | 809 | </para> |
0ef60ec1 | 810 | </note> |
6928e16b GB |
811 | <para> |
812 | 1. You will notice the maps are being drawn on top of the tracks, which | |
813 | is probably not what you want. Look at the Layers Panel to the left. | |
814 | Notice how the layer named Map is ABOVE your TrackWaypoint layer that | |
815 | your GPS data is in. This means that it will be drawn last, or on top | |
816 | of the other layers. Select the Map layer from the list and click the | |
817 | down arrow button beneath the list. Your tracks will now be drawn over | |
818 | the map. </para> | |
819 | ||
820 | </section> | |
821 | ||
822 | </section> | |
7233fcb6 | 823 | <section><title>From 1st startup to GPS track (including offline maps)</title> |
6928e16b | 824 | <para> |
7233fcb6 RN |
825 | The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand. |
826 | 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'. | |
6928e16b GB |
827 | </para> |
828 | ||
6928e16b GB |
829 | <section><title>Fetching the maps</title> |
830 | <para> | |
0ef60ec1 | 831 | <emphasis role="bold">Map</emphasis> |
6928e16b | 832 | </para> |
0ef60ec1 | 833 | <procedure> |
7233fcb6 | 834 | <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step> |
4502fc82 | 835 | <step><para>in the layer properties dialogue choose e.g. <guilabel>OpenStreetMap (Mapnik)</guilabel>.</para></step> |
0ef60ec1 | 836 | <step> |
4502fc82 GB |
837 | <para>For the moment, we keep the default <guilabel>Maps Directory</guilabel> (the directory in |
838 | which the maps will be stored and can be used for offline usage).</para> | |
0ef60ec1 GB |
839 | </step> |
840 | <step> | |
841 | <para>Check <guilabel>Autodownload maps</guilabel> and keep the zoom level as <guilabel>Use Viking | |
842 | Zoom Level</guilabel>.</para> | |
843 | <note> | |
844 | <para> | |
845 | however, that these settings will play an important | |
846 | role in the pre-fetch for offline usage discussed later | |
847 | </para> | |
848 | </note> | |
849 | </step> | |
850 | </procedure> | |
6928e16b GB |
851 | <para>You'll see a map of Stuttgart. Using the mouse wheel, you can |
852 | zoom in and out. The maps for the choosen resoltion will be downloaded | |
853 | automatically. | |
854 | </para> | |
855 | <para> | |
7233fcb6 | 856 | <emphasis role="bold">DEM Layer (Height Map)</emphasis> |
4502fc82 | 857 | </para> |
0ef60ec1 | 858 | <procedure> |
7233fcb6 RN |
859 | <step><para>Zoom out to 512.</para></step> |
860 | <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New DEM Layer</guimenuitem></menuchoice></para></step> | |
4502fc82 | 861 | <step><para>Keep the download source as is (SRTM Global 90m), hit <guilabel>OK</guilabel>.</para></step> |
0ef60ec1 | 862 | </procedure> |
4502fc82 | 863 | |
6928e16b GB |
864 | <para>In the layer listing on the left, the DEM layer should reside |
865 | above the map layer. If this is not the case, highlight the DEM layer | |
0ef60ec1 | 866 | an shift it one up (using the arrow up button). |
4502fc82 | 867 | </para> |
0ef60ec1 | 868 | <procedure> |
4502fc82 GB |
869 | <step><para>highlight the DEM layer in the layer listing on the left</para></step> |
870 | <step><para>in the toolbar, check DEM layer download/import (the last symbol)</para></step> | |
871 | <step><para>a left-click in the map window should then fetch the DEM data</para></step> | |
0ef60ec1 | 872 | </procedure> |
0ef60ec1 | 873 | <para> |
7233fcb6 | 874 | This might take some time. |
6928e16b GB |
875 | </para> |
876 | <para> | |
877 | Sometimes, a tile does not show up correctly (you might see only a | |
878 | black frame in the map window) because it got corrupted during | |
0ef60ec1 | 879 | transfer. In order to correct this, you can delete the corresponding |
7233fcb6 | 880 | datafile in the cache. <programlisting> right-click the DEM layer properties</programlisting> |
6928e16b GB |
881 | </para> |
882 | <para> | |
0ef60ec1 | 883 | The <guilabel>DEM Files</guilabel> listing allows you to delete the specific tiles (alternatively do this from the command line). |
6928e16b GB |
884 | </para> |
885 | <para> | |
0ef60ec1 | 886 | You can also alter the Min. and Max. elevation in this dialogue. |
6928e16b GB |
887 | </para> |
888 | ||
889 | </section> | |
7233fcb6 | 890 | <section><title>GPS Track with Height Profile</title> |
0ef60ec1 GB |
891 | <procedure> |
892 | <step><para>uncheck the DEM layer (the map show up again)</para></step> | |
7233fcb6 | 893 | <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New TrackWaypoint Layer</guimenuitem></menuchoice></para></step> |
0ef60ec1 | 894 | </procedure> |
6928e16b | 895 | <para> |
7233fcb6 | 896 | Ensure the new track layer is above the map layer. |
4502fc82 | 897 | </para> |
0ef60ec1 GB |
898 | <procedure> |
899 | <step><para>expand trackwaypointlayer, select <guimenuitem>Tracks</guimenuitem></para></step> | |
7233fcb6 RN |
900 | <step> |
901 | <para> | |
902 | in the tools menu choose <guimenuitem>Begin Track</guimenuitem> which looks like this: | |
903 | <figure> | |
904 | <title>Begin Track Icon</title> | |
905 | <screenshot> | |
906 | <graphic format="PNG" fileref="figures/begintr_18.png"/> | |
907 | </screenshot> | |
908 | </figure> | |
909 | </para></step> | |
0ef60ec1 GB |
910 | <step><para>leftclick in the map window, enter a name</para></step> |
911 | <step><para>click several times to generate a track (a right-click removes the last point)</para></step> | |
912 | <step><para>expand tracks in the layer menu, your track should show up, select it</para></step> | |
7233fcb6 RN |
913 | <step><para>right click your track, select <guimenuitem>Apply DEM data</guimenuitem></para></step> |
914 | <step><para>right click your track again, select <guimenuitem>Properies</guimenuitem></para></step> | |
915 | <step><para>click the tab <guilabel>Elevation-distance</guilabel> - enjoy the plot</para></step> | |
0ef60ec1 | 916 | </procedure> |
6928e16b | 917 | <para> |
0ef60ec1 | 918 | In order to save this setting for later usage |
4502fc82 | 919 | </para> |
0ef60ec1 | 920 | <procedure> |
7233fcb6 RN |
921 | <step><para>click <guilabel>OK</guilabel> in the <guilabel>Track Properties</guilabel> dialog</para></step> |
922 | <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> | |
0ef60ec1 | 923 | </procedure> |
6928e16b GB |
924 | |
925 | </section> | |
926 | <section><title>Usecase: offline data for holiday</title> | |
927 | <para> | |
0ef60ec1 GB |
928 | Suppose you want to have the map and DEM data offline for your holiday in Italy near Bologna. |
929 | </para> | |
930 | <procedure> | |
7233fcb6 RN |
931 | <step><para>Start a new &appname; session.</para></step> |
932 | <step><para><menuchoice><guimenu>View</guimenu><guimenuitem>Go to Location</guimenuitem></menuchoice>, enter Bologna</para></step> | |
933 | <step><para><menuchoice><guimenu>Layers</guimenu><guimenuitem>New Map Layer</guimenuitem></menuchoice></para></step> | |
4502fc82 GB |
934 | <step><para>Choose e.g. <guilabel>OpenStreetMap (mapnik)</guilabel>.</para></step> |
935 | <step><para>adapt the <guilabel>maps directory</guilabel> e.g. to <filename>/home/user/.viking-map-holiday/</filename>. | |
0ef60ec1 | 936 | This allows you to delete the map stuff after holiday without purging the rest of your maps. |
4502fc82 GB |
937 | </para></step> |
938 | <step><para>check <guilabel>autodownload map</guilabel></para></step> | |
939 | <step><para>keep <guilabel>viking zoom level</guilabel></para></step> | |
7233fcb6 | 940 | <step><para>zoom out to 1024</para></step> |
4502fc82 GB |
941 | <step><para>add a DEM layer (as discussed above)</para></step> |
942 | <step><para>download the DEM data</para></step> | |
0ef60ec1 GB |
943 | </procedure> |
944 | <para>In the &app; version discussed here, the DEM data automatically | |
945 | are stored in <filename>/home/user/.viking-maps/</filename>. You can move the corresponding | |
946 | tiles into <filename>.viking-map-holiday/</filename> if you like. | |
947 | </para> | |
948 | <para> | |
949 | <emphasis role="bold">Download map data for all zoom levels</emphasis> | |
950 | </para> | |
951 | <procedure> | |
4502fc82 GB |
952 | <step><para>uncheck the DEM layer for the map to show up</para></step> |
953 | <step><para>navigate the map to be centered at Bologna</para></step> | |
7233fcb6 | 954 | <step><para>choose the zoom such, that all regions of interest are displayed in the map window (e.g. 1024)</para></step> |
0ef60ec1 GB |
955 | <step> |
956 | <para>follow this sequence until you have all tiles for all zoom levels you need</para> | |
957 | <substeps> | |
7233fcb6 | 958 | <step><para>right-click the map layer properties</para></step> |
4502fc82 | 959 | <step><para>set the zoomlevel explicitely one below the last (in the first cycle 512), hit OK</para></step> |
7233fcb6 RN |
960 | <step><para>right click the map layer <guimenuitem>Download Missing Onscreen Maps</guimenuitem></para></step> |
961 | <step><para>wait until all tiles for that resolution have been downloaded</para></step> | |
0ef60ec1 GB |
962 | </substeps> |
963 | </step> | |
964 | </procedure> | |
965 | <para>This may take some time and hd capacity. Lixus wrote a set of | |
6928e16b | 966 | scripts which allow to download the map tiles for several zoom-level in |
0ef60ec1 | 967 | parallel from the command line. |
6928e16b GB |
968 | </para> |
969 | <para> | |
970 | Do not forget to save your configuration (as discussed above). | |
971 | </para> | |
972 | ||
973 | </section> | |
974 | ||
975 | </section> | |
976 | <section><title>Uploading data to OpenStreetMap</title> | |
977 | <para> | |
7233fcb6 | 978 | It is possible to upload data directly from &appname; to OpenStreetMap. |
6928e16b | 979 | </para> |
0ef60ec1 GB |
980 | <formalpara> |
981 | <title>Upload a layer</title> | |
6928e16b GB |
982 | <para> |
983 | One solution is to upload whole a TrackWaypoint layer. To do this, | |
0ef60ec1 GB |
984 | simply select the layer and right click on it. Then, select <guimenuitem>Upload to |
985 | OSM</guimenuitem>. | |
6928e16b | 986 | </para> |
0ef60ec1 GB |
987 | </formalpara> |
988 | <formalpara> | |
989 | <title>Upload a single track</title> | |
6928e16b GB |
990 | <para>One solution is to upload whole a TrackWaypoint layer. To do |
991 | this, simply select the layer and right click on it. Then, select | |
0ef60ec1 | 992 | <guimenuitem>Upload to OSM</guimenuitem>. |
6928e16b | 993 | </para> |
0ef60ec1 GB |
994 | </formalpara> |
995 | <formalpara> | |
996 | <title>Fill in the form</title> | |
6928e16b | 997 | <para> |
7233fcb6 | 998 | In both cases, &appname; will retain some information. |
6928e16b | 999 | The email field is the email you used to subscribed into OSM. |
6928e16b | 1000 | The password field is the password you used with this account. |
6928e16b | 1001 | The filename is the name you want your upload has on the server. This information is displayed by the osm server. |
6928e16b | 1002 | The description is some descriptive information. |
0ef60ec1 GB |
1003 | The tags field is a white separated list of tag. |
1004 | </para> | |
1005 | </formalpara> | |
6928e16b GB |
1006 | |
1007 | </section> | |
1008 | <section><title>Geocoded Photo</title> | |
1009 | <para> | |
1010 | HOWTO GEOCODE YOUR PHOTOS AND SEE THEM IN VIKING | |
1011 | </para> | |
1012 | <para>1) Synchronize your camera's clock with your GPS clock. If your | |
1013 | camera's clock doesn't have a seconds value you can change, you might | |
1014 | try setting the minute value just when the minute changes. | |
1015 | </para> | |
1016 | <para> | |
1017 | 2) Activate the track log on your GPS. | |
1018 | </para> | |
1019 | <para>3) Get outside and take some pictures with your camera while | |
1020 | making sure your GPS has reception. If you forgot to turn your GPS on | |
1021 | or forgot to bring it when you took a picture but you know where you | |
1022 | took the picture, you can make a waypoint with a name of the format | |
1023 | YYMMDDhhmm, representing the time the picture was taken, to record | |
1024 | where you were at that time. | |
1025 | </para> | |
1026 | <para>4) Get home and download your pictures and GPS data. You can | |
1027 | download the GPS data several ways. The first is using gpspoint to | |
1028 | download from a Garmin GPS: <programlisting>gpspoint -p /dev/ttyS0 -dw -dt -of 2004-04-02-trip1</programlisting> | |
1029 | </para> | |
1030 | <para> | |
1031 | Where /dev/ttyS0 is the serial port the GPS is connected to. If you | |
1032 | don't have a Garmin GPS, or if you don't feel like install gpspoint, | |
1033 | you can use my version of gpsbabel with support for gpspoint files. You | |
1034 | can use gpsbabel to either translate the GPS data from a format you | |
1035 | already have the data in or download it directly from your GPS | |
1036 | reciever. A typical command line would something like this:<programlisting>gpsbabel -i garmin -f /dev/ttyS0 -o gpspoint -F 2004-04-02-trip1</programlisting> | |
1037 | </para> | |
1038 | <para> | |
1039 | 5) Launch GPSPhoto. | |
1040 | </para> | |
1041 | <para> | |
1042 | 6) You must now bring your photos into GPSPhoto. Either drag them (or | |
1043 | the directory containing them) from your favorite file manager to the | |
1044 | list on the left of the GPSPhoto window, or use the buttons below the | |
1045 | list to find them. | |
1046 | </para> | |
1047 | <para> | |
1048 | 7) Do the same for your GPS data file(s), dragging them to the list on the right of the GPSPhoto Window. | |
1049 | </para> | |
1050 | <para>8) Click the Execute button, and choose a location to save the | |
1051 | gpspoint file containing the waypoints for your photos. Then click OK | |
1052 | to write the waypoints to this file. | |
1053 | </para> | |
1054 | <para> | |
1055 | 9) Open Viking and open both your original GPS data file and your image waypoint file just created. | |
1056 | </para> | |
1057 | </section> | |
1058 | ||
ba322d06 GB |
1059 | <section> |
1060 | <title>Extending Viking</title> | |
1061 | ||
1062 | <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> | |
1063 | <para>Here is an example: | |
1064 | <programlisting><![CDATA[ | |
1065 | <objects> | |
1066 | <object class="ClassName"> | |
1067 | <property name="property_name1">Property value</property> | |
1068 | <property name="property_name2">Property value</property> | |
1069 | </object> | |
1070 | ... | |
1071 | <objects> | |
1072 | ]]> | |
1073 | </programlisting> | |
1074 | </para> | |
1075 | <para>You can find more examples in the documentation part of the distribution.</para> | |
4502fc82 | 1076 | <section> |
ba322d06 GB |
1077 | <title>Map Source</title> |
1078 | <para>It is possible to add new map's sources. The file is <filename>~/.viking/maps.xml</filename>.</para> | |
1079 | <para>An example of the file in the distribution <filename>doc/examples/maps.xml</filename>.</para> | |
90f15672 | 1080 | <para>The VikSlippyMapSource allows to declare any map's source working like OpenStreetMap. It supports the following properties: |
ba322d06 GB |
1081 | <variablelist> |
1082 | <varlistentry> | |
1083 | <term>id</term> | |
1084 | <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem> | |
1085 | </varlistentry> | |
1086 | <varlistentry> | |
1087 | <term>label</term> | |
1088 | <listitem><para>the text displayed in the map's source selection dialog</para></listitem> | |
1089 | </varlistentry> | |
1090 | <varlistentry> | |
1091 | <term>hostname</term> | |
1092 | <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem> | |
1093 | </varlistentry> | |
1094 | <varlistentry> | |
1095 | <term>url</term> | |
1096 | <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> | |
1097 | </varlistentry> | |
1098 | </variablelist> | |
1099 | </para> | |
1b6659bd GB |
1100 | <para>The VikTmsMapSource allows to declare any TMS service. It supports the following properties: |
1101 | <variablelist> | |
1102 | <varlistentry> | |
1103 | <term>id</term> | |
1104 | <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem> | |
1105 | </varlistentry> | |
1106 | <varlistentry> | |
1107 | <term>label</term> | |
1108 | <listitem><para>the text displayed in the map's source selection dialog</para></listitem> | |
1109 | </varlistentry> | |
1110 | <varlistentry> | |
1111 | <term>hostname</term> | |
1112 | <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem> | |
1113 | </varlistentry> | |
1114 | <varlistentry> | |
1115 | <term>url</term> | |
1116 | <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> | |
1117 | </varlistentry> | |
1118 | </variablelist> | |
1119 | </para> | |
90f15672 GB |
1120 | <para>The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties: |
1121 | <variablelist> | |
1122 | <varlistentry> | |
1123 | <term>id</term> | |
1124 | <listitem><para>this is an integer and should be unique as it used to identify the map source</para></listitem> | |
1125 | </varlistentry> | |
1126 | <varlistentry> | |
1127 | <term>label</term> | |
1128 | <listitem><para>the text displayed in the map's source selection dialog</para></listitem> | |
1129 | </varlistentry> | |
1130 | <varlistentry> | |
1131 | <term>hostname</term> | |
1132 | <listitem><para>the server's hostname (eg. "tile.openstreetmap.org")</para></listitem> | |
1133 | </varlistentry> | |
1134 | <varlistentry> | |
1135 | <term>url</term> | |
1136 | <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> | |
1137 | </varlistentry> | |
1138 | </variablelist> | |
1139 | </para> | |
4502fc82 | 1140 | </section> |
ba322d06 | 1141 | |
4502fc82 | 1142 | <section> |
ba322d06 GB |
1143 | <title>Go-to search engines</title> |
1144 | <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> | |
1145 | <para>An example of the file in the distribution <filename>doc/examples/goto_tools.xml</filename>.</para> | |
1146 | <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> | |
1147 | <para>The related properties are: | |
1148 | <variablelist> | |
1149 | <varlistentry> | |
1150 | <term>label</term> | |
1151 | <listitem><para>the text displayed in the <guilabel>Go-To</guilabel> dialog</para></listitem> | |
1152 | </varlistentry> | |
1153 | <varlistentry> | |
1154 | <term>url-format</term> | |
1155 | <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> | |
1156 | </varlistentry> | |
1157 | <varlistentry> | |
1158 | <term>lat-path</term> | |
1159 | <listitem><para>XML path of the latitude (eg. <literal>/root/parent/elem</literal>)</para></listitem> | |
1160 | </varlistentry> | |
1161 | <varlistentry> | |
1162 | <term>lat-attr (optional)</term> | |
1163 | <listitem><para>name of the attribute (of previous element) containing the latitude</para></listitem> | |
1164 | </varlistentry> | |
1165 | <varlistentry> | |
1166 | <term>lon-path</term> | |
1167 | <listitem><para>XML path of the longitude (eg. <literal>/root/parent/elem</literal>)</para></listitem> | |
1168 | </varlistentry> | |
1169 | <varlistentry> | |
1170 | <term>lon-attr (optional)</term> | |
1171 | <listitem><para>name of the attribute (of previous element) containing the longiude</para></listitem> | |
1172 | </varlistentry> | |
1173 | </variablelist> | |
1174 | </para> | |
1175 | <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> | |
4502fc82 | 1176 | </section> |
ba322d06 | 1177 | |
4502fc82 | 1178 | <section> |
7233fcb6 | 1179 | <title>Webtools</title> |
ba322d06 GB |
1180 | <para>It is possible to add new external tools. The file is <filename>~/.viking/external_tools.xml</filename>.</para> |
1181 | <para>An example of the file in the distribution <filename>doc/examples/external_tools.xml</filename>.</para> | |
1182 | <para>Currently, there is a single object class available: VikWebtoolCenter. Such feature allows to declare any Webtool using a logic based on center coordinates and zoom level value.</para> | |
1183 | <para>The related properties are: | |
1184 | <variablelist> | |
1185 | <varlistentry> | |
1186 | <term>id</term> | |
1187 | <listitem><para>this is an integer and should be unique as it used to identify the tool</para></listitem> | |
1188 | </varlistentry> | |
1189 | <varlistentry> | |
1190 | <term>label</term> | |
1191 | <listitem><para>the text displayed in the menu entry</para></listitem> | |
1192 | </varlistentry> | |
1193 | <varlistentry> | |
1194 | <term>url</term> | |
1195 | <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. "http://hostname/%d/%d/%d.png")</para></listitem> | |
1196 | </varlistentry> | |
1197 | </variablelist> | |
1198 | </para> | |
4502fc82 | 1199 | </section> |
ba322d06 GB |
1200 | |
1201 | </section> | |
1202 | ||
7233fcb6 RN |
1203 | <section><title>What to Do if &appname; Does Not Seem to Work</title> |
1204 | <para> | |
1205 | In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line: | |
1206 | <programlisting>viking -dV</programlisting> | |
1207 | </para> | |
1208 | <para> | |
1209 | 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. | |
1210 | E.g. Something like this for DEMs: | |
1211 | <screen> | |
1212 | ** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip | |
1213 | * About to connect() to dds.cr.usgs.gov port 80 (#0) | |
1214 | * Trying 152.61.128.95... * connected | |
1215 | * Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0) | |
1216 | GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1 | |
1217 | User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8 | |
1218 | Host: dds.cr.usgs.gov | |
1219 | Accept: */* | |
1220 | HTTP/1.1 200 OK | |
1221 | Date: Sun, 26 Jul 2009 18:13:38 GMT | |
1222 | Server: Apache | |
1223 | Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT | |
1224 | ETag: eac3f8-1828f5-46f3caa76070a | |
1225 | Accept-Ranges: bytes | |
1226 | Content-Length: 1583349 | |
1227 | Content-Type: application/zip | |
1228 | ||
1229 | * Connection #0 to host dds.cr.usgs.gov left intact | |
1230 | * Closing connection #0 | |
1231 | ** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip | |
1232 | </screen> | |
1233 | Or for OSM Mapnik tile server: | |
1234 | <screen> | |
1235 | * About to connect() to tile.openstreetmap.org port 80 (#0) | |
1236 | * Trying 193.63.75.28... * connected | |
1237 | * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0) | |
1238 | GET /13/4065/2748.png HTTP/1.1 | |
1239 | User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18 | |
1240 | Host: tile.openstreetmap.org | |
1241 | Accept: */* | |
1242 | ||
1243 | * HTTP 1.0, assume close after body | |
1244 | HTTP/1.0 200 OK | |
1245 | Date: Thu, 14 Oct 2010 22:18:42 GMT | |
1246 | Server: Apache/2.2.8 (Ubuntu) | |
1247 | ETag: "b66ff9d46474bab68262a3483428a232" | |
1248 | ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232" | |
1249 | Content-Length: 17194 | |
1250 | Cache-Control: max-age=94805 | |
1251 | Expires: Sat, 16 Oct 2010 00:38:47 GMT | |
1252 | Content-Type: image/png | |
1253 | Age: 5153 | |
1254 | X-Cache: HIT from konqi.openstreetmap.org | |
1255 | X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128 | |
1256 | Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7) | |
1257 | Connection: close | |
1258 | ||
1259 | * Closing connection #0 | |
1260 | * About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0) | |
1261 | * Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png | |
1262 | * About to connect() to tile.openstreetmap.org port 80 (#0) | |
1263 | * Trying 193.63.75.28... * connected | |
1264 | * Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0) | |
1265 | GET /tiles/cycle/13/4065/2747.png HTTP/1.1 | |
1266 | User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18 | |
1267 | Host: a.andy.sandbox.cloudmade.com | |
1268 | Accept: */* | |
1269 | ||
1270 | * connected | |
1271 | * Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0) | |
1272 | GET /13/4065/2749.png HTTP/1.1 | |
1273 | User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18 | |
1274 | Host: tile.openstreetmap.org | |
1275 | Accept: */* | |
1276 | ||
1277 | * HTTP 1.0, assume close after body | |
1278 | HTTP/1.0 200 OK | |
1279 | Date: Thu, 14 Oct 2010 23:44:35 GMT | |
1280 | Server: Apache/2.2.8 (Ubuntu) | |
1281 | ETag: "8e520ad47ce9c1b63430554886eb5fab" | |
1282 | ** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab" | |
1283 | Content-Length: 18094 | |
1284 | Cache-Control: max-age=87742 | |
1285 | Expires: Sat, 16 Oct 2010 00:06:57 GMT | |
1286 | Content-Type: image/png | |
1287 | X-Cache: MISS from konqi.openstreetmap.org | |
1288 | X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128 | |
1289 | Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7) | |
1290 | Connection: close | |
1291 | </screen> | |
1292 | </para> | |
1293 | </section> | |
1294 | ||
6928e16b | 1295 | </section> |
f8b8a0b5 GB |
1296 | |
1297 | </article> |