X-Git-Url: https://git.street.me.uk/andy/viking.git/blobdiff_plain/7233fcb656b321f5690667077d4c629300fd6ddd..873fc9e4e6711cf2b5586cb8e28eb446e1af1fb6:/help/C/viking.xml
diff --git a/help/C/viking.xml b/help/C/viking.xml
index c8f98544..95c089d4 100644
--- a/help/C/viking.xml
+++ b/help/C/viking.xml
@@ -3,9 +3,9 @@
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
Viking">
-
-
-
+
+
+
]>
@@ -77,9 +78,11 @@
&date;Guilhem Bonnefille guilhem.bonnefille@gmail.com
+ Rob Norris rw_norris@hotmail.comGNOME Documentation Project
+ This document was generated on .
-
+
This manual describes version &appversion; of &appname;.
@@ -105,14 +108,13 @@ variety of tasks. Some of the things you can use &appname; for are:
-Uploading and downloading waypoints, tracks to/from GPS.
+Uploading and downloading waypoints, tracks and routes to/from GPS.
-Preparing tracks and waypoints for trips using maps from services
-such as OpenStreetMap (OSM) and/or Terrasever. The data is only needed to be uploaded to
-your GPS before you leave. The maps together with your tracks and
-waypoints can also be printed and used during the trip.
+Preparing tracks, routes and waypoints for trips using maps from services such as OpenStreetMap (OSM) and/or Terrasever.
+The data is only needed to be uploaded to your GPS before you leave.
+The maps together with your tracks, routes and waypoints can also be printed and used during the trip.
@@ -126,7 +128,7 @@ Analyzing Off Highway Vehicle (OHV) and hiking trips, understanding where you we
-Making waypoints and tracks to follow to easily get someplace
+Making waypoints, tracks and routes to follow to easily get someplace
you've never been before or don't have GPS data for but online
maps exist for it.
@@ -148,17 +150,27 @@ Analyzing speed at different places (to some degree), adding waypoints where you
-Downloading and storing OSM and/or Terraserver maps on your hard drive and looking at them later.
+Downloading and storing OpenStreetMap and/or Terraserver maps on your hard drive and looking at them later.
-Editing tracks and trackpoints, joining and splitting up tracks
+Editing routes or tracks and their trackpoints, joining and splitting up tracks and routes.
-Show the live GPS position on the map (for use on a mobile device - e.g. a laptop)
+Show the live GPS position on the map (for use on a mobile device - e.g. a laptop). Not Windows at the moment.
+
+
+
+
+Import track, route and waypoint files of various types via GPSBabel
+
+
+
+
+View, create and update Geotagged Images (using EXIF data).
@@ -167,14 +179,20 @@ Show the live GPS position on the map (for use on a mobile device - e.g. a lapto
&appname; is under continual improvement: see the potential areas in the Roadmap / Wishlist:
+
General Concepts
-Layers
+Layers
-'Layers' is concept one may know from powerful graphics editors such as Photoshop or GIMP.
+Layers is concept one may know from powerful graphics editors such as Photoshop or GIMP.
Instead of putting all the data on the same level, it is stacked (i.e. layered) with different data over one another.
-This can make useful for analysis and general handling of various sets of data.
+This can be useful for analysis and general handling of various sets of data.
Unfortunately the downside of this complexity is remembering how differing layers of data can obscure other data.
@@ -185,12 +203,12 @@ to create the appearance of partial transparency.
By controlling this value one can see data below it in the layer heirarchy for interesting effects.
-Layers Panel
+Layers Panel
The panel on the left is called the layers panel.
It determines which layers and sublayers (such as tracks and waypoints)
-are shown, and the order in which they are drawn. Layers list on the
-top of the layers panel are drawn last. You can change the order by
+are shown, and the order in which they are drawn. Layers on the
+top of the layers panel list are drawn last. You can change the order by
drag and drop, or by selecting a layer and using the up and down
buttons at the bottom of the layers panel.
@@ -201,362 +219,1508 @@ The main &appname; area where the layer data is drawn, is called the Statusbar
-This provides a readout of various information:
-The currently selected (mouse pointer) tool
-The number of items to process in the background - normally this the number in the map tile download queue
-The zoom factor
-The location of the mouse pointer (and potentially height information if DEM data is available)
-
+
+The currently selected (mouse pointer) tool
+The number of items to process in the background - normally this the number in the map tile download queue
+The zoom factor
+The location of the mouse pointer (and potentially height information if DEM data is available)
+
+When creating a track/route, the statusbar also displays some information about the track/route.
+
+This part of the statusbar displays:
+
+The total distance of the track/route (including currently edited segment).
+The bearing of the currently edited segment.
+The distance of the currently edited segment.
+
+
+For convenience, a zoom selector can be opened from the status bar. Simply left-click on the zoom factor.
+
+
+Projections
+
+&appname; supports differents projections:
+
+
+UTM
+
+
+LatLon (also called EPSG:4326)
+
+
+Mercator (also called Spherical Mercator)
+
+
+
-Layers
-TrackWaypoint Layer
+Map Cache
-TrackWaypoint layers display GPS data (tracks and waypoints).
+&appname; stores downloaded map tiles to disk for a couple of reasons:
-One way to create new waypoints is to copy a
-latitude/longitude coordinate pair, such as the one shown on most
-geocaches, and paste it into an active TrackWaypoint layer. &appname; can
-automatically recognize several variations of the lat/lon format.
+
+Enables off line usage
+Reduces loading on the map tile provider
+
+
+The &appname; automatic caching strategy is two fold:
+
+
-By right-clicking tracks and waypoints in the layers panel, you can do
-many things with tracks and waypoints. You can easily find a specific
-track or waypoint by expanding the Tracks or Waypoints sublayers in the
-layers panel to show all tracks or waypoints, and typing the name of
-the track/waypoint.
+ If the age of the tile on disk is less than the specified tile age (see ),
+ it will not attempt to contact the server to get a new version of the tile.
-Layer Operations
+
+
-The layer has a context menu with several operations.
+ When the tile age has expired &appname; will attempt a refresh 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.
-Export
+
+
-The layer can be exported to a file GPX, GPSPoint or GPSMapper format.
+ You can override the caching scheme by using right-click on the Map on the layers panel and selecting Redownload All Onscreen Maps, or Ctrl+F5 for the top most map displayed. This will get the latest version held by the server.
-Only the entire layer can be exported, it is currently
-not possible to export an individual track.
+ 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 I have made edits but they don't show up on the map)
-
+Shortcut Keys
+
+&appname; has several shortcut keys or key combinations for commands as listed in the main window along side the command.
+
+
+Some function keys follow standard GUI behaviour:
+
+
+F1 Help (view this manual)
+F5 or Ctrl+R Refresh the maps on screen
+F10 Select the Menubar (in built behaviour)
+F11 Full Screen
+Ctrl+F5 or Ctrl+Shift+R Redownload the maps on screen
+
+
+
+Refresh attempts to get new maps only if the local tile cache time period has expired for any particular map tile.
+Redownload gets all on screen maps from the server, ignoring the local tile cache.
+
+
+
+Other function keys control turn on/off visibility of various elements:
+
+
+F3 Toggle visibility of the Toolbar
+F4 Toggle visibility of the Menubar
+Shift+F5 Toggle visibility of the Scale indicator on the viewport
+F6 Toggle visibility of the Center Crosshairs on the viewport
+F7 Toggle showing selected items (e.g. tracks or waypoints) in the highlight colour in the viewport
+F9 Toggle visibility of the Layers Panel
+F12 Toggle visibility of the Statusbar
+
+
+Standard shortcuts are provided for normal GUI operations: such as creating new files, opening, saving and exitting.
+Then there are shortcuts specific to &appname; to switch projection modes, zoom in/out, create layers and switch the active tool mode.
+For these combinations see the menu entry themselves.
+
-Track Properties
+
+Tracks vs Routes
-Show many useful statistics about a track, including a
-elevation-distance graph and a speed-time graph (if data is available).
-You can click these graphs to jump to the point in the track. You can
-also reverse a track, delete duplicates, and split a track from its
-component segments (discontinuous breaks in a track) into separate
-tracks.
+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.
-The following colors are used in the elevation-distance graph:
+Q. When planning a route what difference does it make if it's a route or a track?
-
-
-'Main' colour - this is dependent on your Desktop theme - often blue by default
-elevation data in graph
-
-
-Yellow
-
-no elevation data
-
-
-
-Green
+
+A. One difference is in how a GPS device navigates following the route or track.
+Or you may want to consider interoperability with other software.
+Otherwise it is probably best to use tracks as they are a superset of the route functionality.
+
+
+For example on Garmin Etrex:
+
+
-elevation data from DEM
+Route following: Uses navigation mode with compass and estimated time to next point.
+If following on road it can calculate a route on fly.
+I (RN) always use this mode to follow pre planned routes.
-
-
-Red
-speed
+Track following: Uses a TracBack mode
+I (RN) never use this so I can't comment on how it actually compares to the route mode.
-
-
-
+
+
+There are often restrictions on the numbers of route points the GPS Device can handle - may be 250 or as little as 50.
+This generally not a problem for single day routes, but needs managing for multi-day events or for highly detailed routes.
+
-Track Operations
-Merge by time
+
+
+
+File Types and the Main Window
+
-This operation repeatedly tries to merge the right-clicked track
-with tracks in the same TrackWaypoint layer. The tracks which are
-merged are those which have at least one trackpoint less than some
-threshold time away. This way, if you somehow end up with lots of small
-segments (say, caused by turning the GPS on and off) you can merge them
-easily into one track.
+&appname; has it's own file type traditionally marked by the .vik file extension.
+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...).
-
-
-Split by time
-This operation will split a single track into segments wherever the
-time interval between successive trackpoints is larger than some
-threshold. This is useful when processing raw NMEA GPS data, especially
-taken over a long time.
+Besides it's own file type, &appname; can open (and save to via export methods) GPX and KML file types.
-
-
-Apply DEM data
+
-If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
+&appname; does not handle GPX 1.1 particularly well - it prefers GPX 1.0
-
-
-Extend track end
+
-Change the current tool to add track and add points to the end of the track.
+By default &appname; opens a default blank window centered on the home location. This behaviour can be changed by the .
+Each window contains menus, a toolbar, a viewport, layers panel and a statusbar.
+Each section (apart from the viewport) can be hidden using the or from the
+ViewShow choices.
-
-
-Upload to OSM
-Useful if you are an OSM contributor. &appname;
-allows you to import a track, edit it if you so wish to remove
-duplicate points, perhaps track points leading to your home, and then
-directly export the track to OSM.
+One may consider each &appname; window to be a separate project - each with it's project Viking file.
+However generally one window is enough for most purposes!
+
+
+Several operations apply at the window level as follows next.
+Also see for the operational modes that generally work in conjunction with a selected layer.
-
-View Google Directions
+New
-Launch a web browser to see the Google directions page which
-yielded the route.
+Located on the FileNew menu and on the toolbar New.
-
-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 Magic Scissors tool) this will not
-work correctly.
+This creates a new window with the default settings.
-
-
-
-Waypoint Operations
-Goto Geocache page
+Open
-If the waypoint's name is in Geocache form (GCXXXXX) you can launch a web browser to go to the Geocache page.
+Located on the FileOpen menu and on the toolbar Open.
-
-
-
-
-
-
-GPS Layer
-The GPS layer is responsible for uploading and downloading GPS data
-from a GPS device. It also is responsible for realtime GPS tracking.
-Expand the GP SLayer in the layers panel to see the two TRWLayers it
-uses for uploading and downloading. To upload, download, or use
-realtime tracking, right-click the GPS layer and click the appropiate
-menu item.
+This opens a file chooser dialog to select one (or more) files of the supported GPS data file types:
+
+Viking
+GPX
+KML
+
-
-Download
-To download data from the GPS, right-click the GPS layer and click Download from GPS.
+GPX and KML files will be loaded into the existing &appname; view. A Viking file will be given a new window if the current window is already assigned.
-
-
-Upload
+
-To upload data to the GPS, first populate the GPS Upload child
-layer of the GPS layer (either by creating waypoints/tracks in it, or
-copying and pasting or dragging waypoints/tracks from another layer).
-Then right-click the GPS layer and click Upload to GPS.
+&appname; handles more file types via the Acquire methods below.
-
+
-Realtime Tracking
+
+Save
-You must set up gpsd correctly or use a GPSD server and put the
-correct information in the GPS layer properties dialog. Then right-click
-the layer and select Start Realtime Tracking.
+Located on the FileSave menu and on the toolbar Save.
+
+
+If the current opened file is Viking file, this save will simply update it.
+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 new name to save as a Viking file.
-
-
-(Digital Elevation Model) DEM Layer (todo)
+Save As
-The current NASA SRTM server is: http://dds.cr.usgs.gov/srtm/version2_1/
+Located on the FileSave As menu only.
+
+
+This will ask for a new name to save as a Viking file (even it was already a Viking file).
-
-
-Tools
+Append
-You can use the scroll wheel and the right-click to zoom and pan no matter what tool you are using.
+Located on the FileAppend menu only.
-Scroll: zoom in and out without changing center (also Ctrl+, Ctrl-)
+Selecting a Viking file from this method will join the file contents to the current window (instead of creating a new one).
+GPX and KML files may also be appended, but this is exactly the same as the normal file open method.
+
+
+Acquire
+
-Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down)
+Available on the FileAcquire menu and from the layer menu.
-Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right)
+If used from the File menu and a TrackWaypoint layer is not currently selected, these methods place the results in a new TrackWaypoint layer. When a TrackWaypoint layer is selected, then using the FileAcquire will put the results into the selected TrackWaypoint layer.
-Ctrl-shift-scroll: zoom in and out, keeping mouse over same location (like Google maps)
+If used from the layer menu these methods place the results in that TrackWaypoint layer.
+
+
+From GPS
-Middle-click: make the clicked point on the map the center
+FileAcquireFrom GPS
+Probably the easiest way of getting information from a GPS Device.
-Middle-click and drag: pan
+Select the GPS Device communication settings and then hit OK.
+See the Getting Started section for more info about the settings.
-Zoom
+
-Zooms in and out on the clicked part of the map.
+Some GPS devices (such as the Garmin Nuvi 255) support a native file system and write information to a Current.gpx file or similar. You will have to browse the file system on the device and open it directly.
-
+
-Ruler
+
+
+Import File With GPSBabel
-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.
-A second click will 'freeze' the ruler at that point.
+FileAcquireImport File With GPSBabel
-
-
-TrackWaypoint Layer Tools
-You must have a TrackWaypoint Layer selected to use these.
+Other formats can be imported that are supported by GPSBabel.
-New Waypoint
-
-
-New Track
-Right-click: undo one point
+You need to select the file and the type of the file that is going to be opened,
+since there is no automatic detection of the file kind.
+
+
+
+OSM Traces
-Ctrl: snap to trackpoint
+FileAcquireOSM Traces
-Shift: snap to waypoint
+See section for more information.
-
-Edit Waypoint
+
+
+My OSM Traces
-Click/drag: select/move a waypoint
+FileAcquireMy OSM Traces
-Ctrl: snap to trackpoint
+See section for more information.
+
+
+
+From Geotagged Images
-Shift: snap to waypoint
+FileAcquireFrom Geotagged Images
+Enables automatic creation of waypoints from geotagged images.
-Right-click on waypoint: opens a menu with waypoint actions (the
-same menu accessed by right-clicking the waypoint in the layers panel)
+
+This menu opens a dialog to select such image files.
+If the image files have geotag information in them, then a layer with named waypoints positioned at the location of each image with a thumbnail of that image is created.
-
-Edit Trackpoint
+
+
+From Wikipedia Waypoints
-Ctrl: snap to trackpoint
+FileAcquireFrom Wikipedia Waypoints
-Shift: snap to waypoint
+This gets interesting points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary.
-
-Show Picture
+
+
+From Routing
-Uses eog to open a picture shown as a picture waypoint.
+FileAcquireFrom Directions
+
+
+This gets a route from given directions.
-
-Magic Scissors
-Creates a track using Google maps routing between two points.
-Requires internet connection. Click one point, then click another to
-create a track.
+
+
+
+Print
+
+Located on the FilePrint menu and on the toolbar Print.
-Right-click: undo last routing
+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
+cross hairs and the scale.
-Ctrl: continue previous track
+It uses a standard system print dialog using an image the size of the current viewport in pixel terms.
+On the Image Settings you can move the image around the page and scale the image up / or down.
-
-
-Georef Map Layer Tools
+Generate Image File
-You must have a Georef Map Layer selected to use these tools.
+Located on the FileGenerate Image File menu only.
-Georef zoom
-Changes the zoom level of the georeferenced map and changes the
-&appname; zoom level accordingly. Useful if you are trying to match GPS
-data to a georeferenced map.
+
+Allows generation of larger (pixel) area images than the standard Print method above.
+From the generated image you can use the facilities of the Operating System to print the image
+or perform other actions.
-
-
-Georef move
-Drag to move the georeferenced map.
+You should have previously downloaded the tile images for the chosen zoom level,
+otherwise the image produced will have missing sections.
-
+
+
+Using large areas takes some time to process and due to the method used it may run out of memory to complete the operation.
+Unfortunately under Windows systems it can not detect this failure and may crash the program.
+So the maximum size is dependent on the capabilities of your system.
+For instance the largest successful image generated on my (RN) Debian system is a pixel area of 20,000 x 20,000.
+
+
-
-Map Download
+Generate Directory of Images
-Click to download a single tile. Drag to download tiles in the dragged rectangle area.
+Located on the FileGenerate Directory of Images menu only.
+
-Right-click to redownload bad/all tiles. Right-click and drag to redownload bad/all tiles in the dragged rectangle area.
+This is only available in UTM mode.
-
+
-DEM Download
-
-Click to download and import a DEM file.
-
-
+
+
+Layers
-Webtools
-Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
+Layers supported by &appname; are:
+
+
+
+
+
+
+
+
+
-Jumping from &app; to such service can become annoying.
+For each layer there are a few standard options:
+
+Properties - Layer setup / configuration settings
+Cut
+Copy
+Paste
+Delete
+Visibility - This checkbox on the Layers Panel controls whether the layer is shown in the viewport or not
+
-&appname; allows you to open such service directly at the position currently viewed in &app;.
+The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected:
+
+Standard keys: Ctrl+x|c|v
+Main menu Edit
+From the right click menu
+Buttons at the bottom of the Layers Panel
+
-This feature is called Webtools. It is also known as External Tools.
+Default values used for each layer's properties can be altered via the EditLayer Defaults menu options.
+
+
+See the individual section for detail about each layer.
-
-
-
-Preferences
-Localisation
-You can select units displayed by &appname; to best fit your usage.
-
+Waypoint Icon Size
+An option exists to control the icon (symbol) size used for waypoints
+
+
+Home Default Location: Latitude and Longitude
+You can set the Home location directly by inputting the latitude and longitude in decimal degrees.
+
+Tile's ageThis age is used to decided wether or not a new request to tile server must be done.
@@ -589,83 +1761,175 @@ This value is used when you create a new map layer.
You are still able to change this value in each map layer properties.
+Map Cache Memory Size
+This controls the amount of maps that are stored in memory, rather than having to reread from disk.
+Generally if you have a system with lots of memory it's recommended to increase this value.
+
+
+
+
+Export/External
+KML Export Units
+Allows setting the units used when saved as the KML file type, such as Metric or Statue units
+
+Image Viewer (Not Windows)
+Allows setting the program used to view images associated with Waypoints.
+By default this is set to xdg-open which should open the system's default image viewer, however this can be overridden with this setting.
+Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.
+
+External GPX programs
+Allows setting the programs invoked via the Layer menu Export LayerOpen With 'program'
+Two options are given so that it can be configured for various uses such as:
+
+An OSM editor (default)
+Some other user defined program
+
+
+
+
+OpenStreetMap Traces
+OSM Username + Password
+Store your OSM details here, so that you don't need to enter it in every time in the procedure.
+
+
+Your OSM password will be stored in plain text.
+
+
+
+
+
+Routing
+Routing engine
+You can select the routing engine used by default, ie by features that do not propose a live selection, like .
+
+
+
+Startup
+Naturally since these preferences effect the startup, the values will not be used until &appname; is restarted.
+Restore Window Setup
+When this is enabled, the main window size and layout (such as whether the statusbar or layers panel are shown) is restored to the values from last use.
+
+Default Map Layer
+When this is enabled, a map layer is automatically added whenever &appname; is opened and a &appname; file is not to be loaded.
+The map layer used is defined by the map layer's default values.
-Mini-Howto's
-Getting Started
+Startup Method
+Enables selection of how the startup position should be determined.
+
+Home Location (default) - Position as set by the Set the Default Location
+Last Location - Uses the last position viewed on the viewport
+Specified File - Load the file as specified below
+Auto Location - Use the web service hostip.info to attempt to determine your location via IP lookup
+
+
+Startup File
+Loads this specified file when the Startup method is set to Specified File
+
+Check For New Version
+Periodically (no more than once every 14 days), check to see if there is a new version of &appname; available.
+
+
+
+
+
+
+Howto's
+Getting Started
-To quickly get started using &appname;, follow these instructions.
+&appname; from version 1.5 has several features to ease the start up process.
+On the very first run, you will be asked if you want to enable these features which make use of an Internet connection.
+If you select no or you have upgraded from an earlier version you can choose to enable any of the startup options via the .
+
+
+Some other general use cases for using &appname;, are as follows:
Go to an area of interest
-&appname;'s default location is a Manhatten, New York, USA, so you may need to pick another place that interests you.
+&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.
Method A
-Use View - Go to to move to a coordinate of interest.
+ Use the online location address/place search.
-
-
-
-Method B
-
-Use the GPS Layer or FileAcquireFrom GPS
-to load data directly from your GPS into &appname;.
-Currently Garmin and Magellan are supported.
+
+ Use the Go to Location toolbar button or from the menus
+ ViewGo to Location.
+ You can change the search location provider if desired.
+ Enter the name of place you wish to go to (you may need to specify the country to refine the search).
+ Also you can enter a post code or a ZIP code instead.
-You must have write permission to the port used. For Unix like OS:
-/dev/ttyS0 is the first serial port
-/dev/ttyUSB0 is the first USB port
+ You will need an internet connection for this search to work
-Method C
+Method B
-Get data from files in GPX format. For other formats (kml,
-ozi...), use a converter such as GPSBabel to convert the files to GPX
-format first.
+
+ If you know the coordinates of where you want to view:
-
-
-Open up &appname; and use File - Open or File - Append
-file to open the file.
+Use View and select from either Go to Lat/Lon or Go to UTM and then enter in the specific coordinates.
+
+
+Method C
-
-Expand Tracks or Waypoints. Right-click on the
-track or waypoint of interest and select Goto "Center".
+Use the GPS Layer or FileAcquireFrom GPS
+to load data directly from your GPS into &appname;.
+
+You can specify the types of data to acquire: Tracks, Routes and/or Waypoints.
+
+You must have write permission to the port used. For Unix like OS:
+
+ /dev/ttyS0 is the first serial port
+ /dev/ttyUSB0 is the first USB port
+ usb: is any USB port
+
+Depending on your distribution only one of the USB port types may work
+For Windows:
+
+ com1: is the first serial port
+ usb: is any USB port
+
+
+
+ The GPS devices supported are those supported by GPSBabel.
+ Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.
+Method D
-Use File - Append File to add your track and waypoint data to
-&appname;. This has been tested with Geocaching.com's *.loc format,
-(others(?)).
+Get data from files in GPX or KML format, which can be opened directly.
+Use FileOpen
-
-
-Expand Tracks or Waypoints. Right-click on the tack or
-point of interest and select Goto "Center".
+Other formats can be imported that are supported by GPSBabel.
+FileAcquireImport File With GPSBabel...
+
+
+The viewport will be automatically moved and resized to view the contents of the file.
+
+
-Add a map layer
+Add a Map Layer
-1. Use Layers - New Map Layer, and choose a suitable cache directory
+Use LayersNew Map Layer, and choose a suitable cache directory
where you would like to store your tracks and click OK. Zoom to a
comfortable level (I suggest 4 mpp) by clicking the left and right
mouse buttons on the gray area where your tracks are. Now from the menu
-choose Tools - Map Download, Click where you would like to download a
+choose the Tool. Click where you would like to download a
map. Regardless of what tool you are using, the middle mouse button
always pans.
@@ -674,23 +1938,34 @@ You need an open internet connection when you are downloading maps.
-1. You will notice the maps are being drawn on top of the tracks, which
-is probably not what you want. Look at the Layers Panel to the left.
-Notice how the layer named Map is ABOVE your TrackWaypoint layer that
-your GPS data is in. This means that it will be drawn last, or on top
-of the other layers. Select the Map layer from the list and click the
-down arrow button beneath the list. Your tracks will now be drawn over
-the map.
+If you can no longer see your tracks or waypoints and only the map,
+it is because the layer named Map is ABOVE your TrackWaypoint layer that your GPS data is in.
+This means that it will be drawn last and on top of the other .
+Look at the to the left which shows this order.
+Select the Map layer from the list and click the down arrow button beneath the list until the Map layer is below the TrackWaypoint layer.
+Your tracks will now be drawn over the map.
+
+
+Set Your Home Location
+
+ You can save the current center position of the viewport as the default location AKA the Home Location by
+ EditSet the Default Location.
+
+
+ Then at any time you can return to this place by clicking on the Home icon on the toolbar.
+
+
+ You can also set the default location via specifing the exact latitude and longitude in the .
+From 1st startup to GPS track (including offline maps)
The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
-Before fetching unneeded data, one can position to a location of interest, e.g. Stuttgart: ViewGo to Location, enter 'Stuttgart'.
+Before fetching unneeded data, one can position to a location of interest, e.g. Stuttgart: ViewGo to Location, enter Stuttgart.
-
Fetching the mapsMap
@@ -714,7 +1989,7 @@ role in the pre-fetch for offline usage discussed later
You'll see a map of Stuttgart. Using the mouse wheel, you can
-zoom in and out. The maps for the choosen resoltion will be downloaded
+zoom in and out. The maps for the choosen resolution will be downloaded
automatically.
@@ -726,7 +2001,7 @@ automatically.
Keep the download source as is (SRTM Global 90m), hit OK.
-In the layer listing on the left, the DEM layer should reside
+In the layer listing on the left, the layer should reside
above the map layer. If this is not the case, highlight the DEM layer
an shift it one up (using the arrow up button).
@@ -754,30 +2029,22 @@ You can also alter the Min. and Max. elevation in this dialogue.
GPS Track with Height Profile
-uncheck the DEM layer (the map show up again)
-LayersNew TrackWaypoint Layer
-
-
-Ensure the new track layer is above the map layer.
-
-
-expand trackwaypointlayer, select Tracks
+Uncheck the layer (the map is shown again)
-
-in the tools menu choose Begin Track which looks like this:
-
-Begin Track Icon
-
-
-
-
+ LayersNew TrackWaypoint Layer
+ Ensure the new track layer is above the map layer.
+
+Expand the layer, select Tracks
+In the tools menu choose Create Track
-leftclick in the map window, enter a name
-click several times to generate a track (a right-click removes the last point)
-expand tracks in the layer menu, your track should show up, select it
-right click your track, select Apply DEM data
-right click your track again, select Properies
-click the tab Elevation-distance - enjoy the plot
+Leftclick in the map window, enter a name
+
+ Click several times to generate a track (a right-click removes the last point).
+ Height data is set automatically since DEM data is available
+
+Expand tracks in the layer menu, your track should show up, select it
+Right click your track, select Properties
+Click the tab Elevation-distance - enjoy the plot
In order to save this setting for later usage
@@ -790,7 +2057,7 @@ In order to save this setting for later usage
Usecase: offline data for holiday
-Suppose you want to have the map and DEM data offline for your holiday in Italy near Bologna.
+Suppose you want to have the and data offline for your holiday in Italy near Bologna.
Start a new &appname; session.
@@ -803,7 +2070,7 @@ This allows you to delete the map stuff after holiday without purging the rest o
check autodownload mapkeep viking zoom levelzoom out to 1024
-add a DEM layer (as discussed above)
+add a layer (as discussed above)download the DEM dataIn the &app; version discussed here, the DEM data automatically
@@ -827,101 +2094,271 @@ tiles into .viking-map-holiday/ if you like.
-This may take some time and hd capacity. Lixus wrote a set of
-scripts which allow to download the map tiles for several zoom-level in
-parallel from the command line.
-
+This may take some time and some hard disk capacity.
Do not forget to save your configuration (as discussed above).
-
-Uploading data to OpenStreetMap
-
-It is possible to upload data directly from &appname; to OpenStreetMap.
-
-
-Upload a layer
-
-One solution is to upload whole a TrackWaypoint layer. To do this,
-simply select the layer and right click on it. Then, select Upload to
-OSM.
-
-
-
-Upload a single track
-One solution is to upload whole a TrackWaypoint layer. To do
-this, simply select the layer and right click on it. Then, select
-Upload to OSM.
+
+OpenStreetMap project
+
+OpenStreetMap (OSM) is a collaborative project to create a free editable map of the world.
+One of sources of data for this project is GPS tracks.
+&appname; supports this project via the GPS Traces methods, both uploading and downloading such data.
+
+
+Also see for further detail.
+
+Uploading data to OpenStreetMap
+
+It is possible to upload data directly from &appname; to OpenStreetMap.
+
+
+Upload a layer
+
+One solution is to upload whole a layer. To do this,
+simply select the layer and right click on it. Then, select Upload to
+OSM.
+
+
+
+Upload a single track
+Another solution is to upload an individual track. Simply select the track and right click on it.
+Then select Upload to OSM.
+
+
+
+Fill in the form
+
+In both cases, &appname; will retain some information.
+The email field is the email you used to subscribed into OpenStreetMap.
+The password field is the password you used with this account.
+The filename is the name you want your upload has on the server. This information is displayed by the osm server.
+The description is some descriptive information.
+The tags field is a white separated list of tags.
+
+
+
+
+Downloading Traces from OpenStreetMap
+
+It is possible to download GPS traces directly from OpenStreetMap into &appname;.
+This feature can be really useful for checking existing data before uploading new ones.
+
+
+Download all visible tracks
+One solution is to select
+
+File
+Acquire
+OSM traces...
+.
+Each request can get up to 5,000 points.
+The dialog box allows setting which group of 5,000 points to get. These groups are known as Page Numbers which start at 0.
+Increasing the page number parameter allows one to request the subsequent sets of point groups.
+
+
+
+Downloading Your Own Traces from OpenStreetMap
+
+It is possible to download any of your personal GPS traces previously uploaded to OpenStreetMap into &appname;.
+
+
+You will need to provide your OSM username and password to get the list of your OSM Traces.
+From this list you can select which traces to retrieve.
+This list can be sorted on each column so that it easier to find an individual trace or select a group of traces by similar properties.
+
+
+
+
+
+Geotagging
+
+ This assumes you already have a layer enabled for ease of use (if not see above to get one).
+
+Manual Positioning
+
+ This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
+ 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.
+ ATM this process only works on an individual image, so it will be tedious for handling lots of images.
+
+
+ First create a layer or use an existing one; and select it in the .
+ NB Make sure this layer is above the map layer in the Layers Panel list.
+ Create a new waypoint (or move an existing one) to exact location desired:
+
+ Select the tool, then left click on the map at the location desired, choosing an image to associate with it in the new waypoint dialog
+ Select the tool, then left click on waypoint to be moved. Left click again and drag the waypoint to the location desired
+
+ Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
+ Update Geotag on ImageUpdate
+
+
+ The Update Geotag on Image options are only available when a waypoint has an image associated with it.
+
+
+
+Automatic Positioning Against a Tracklog
+
+ 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 -
+ see Getting Started.
+ It helps if this is the track that was recorded at the time you took some photographs!
+
+
+ Select the track either from the layers panel on the left or via the viewport using the tool.
+ Then right click on it and chose the Geotag Images... leading you to the Dialog.
+
+
+ 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.
+ If things are succesful, new waypoints with thumbnail images of the photographs will appear.
+ 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.
+
+Option: Overwrite Waypoints
+
+ This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
+ 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).
+
+
+
+ If you have multiple tracks in a TrackWaypoint layer, then invoking the Geotag Images... action on the layer
+ will search all the tracks to find location matches.
+
+
+
+
+GPS Real Time Location (Not Windows)
+
+ &appname; relies on gpsd to provide the current location from a real time feed from a GPS device.
+ Unfortunately gpsd is not available on Windows,
+ so currently this functionality is disabled in Windows builds of &appname;
+
+
+ This assumes you already have a layer enabled for ease of use (if not see above to get one).
+
+
+ Turn on the GPS Device, ensure it has figured out it's location and plug it in to your computer.
+
+Set Up GPS Layer
+
+ You will need a layer. One can be added via LayersAdd GPS Layer.
+
+
+ Adjust the Realtime Tracking Mode settings to interface with gpsd as necessary. Normally the defaults should suffice.
+
+
+ Current Linux distributions should run gpsd automatically when a GPS Device is plugged in. Otherwise you may have to run gpsd manually.
+
+
+ Then right-click the layer and select Start Realtime Tracking.
+ Hopefully the viewport should jump to the GPS location.
+
+
+ Troubleshooting checklist:
+
+Confirm gpsd is running.
+Confirm on the GPS device it has a location.
+Confirm the Realtime Tracking Mode settings.
+
+
+
+What to Do if &appname; Does Not Seem to Work
+
+In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
+viking -dV
+
+
+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.
+E.g. Something like this for DEMs:
+
+** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
+* About to connect() to dds.cr.usgs.gov port 80 (#0)
+* Trying 152.61.128.95... * connected
+* Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
+ GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
+User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
+Host: dds.cr.usgs.gov
+Accept: */*
+ HTTP/1.1 200 OK
+ Date: Sun, 26 Jul 2009 18:13:38 GMT
+ Server: Apache
+ Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
+ ETag: eac3f8-1828f5-46f3caa76070a
+ Accept-Ranges: bytes
+ Content-Length: 1583349
+ Content-Type: application/zip
+
+* Connection #0 to host dds.cr.usgs.gov left intact
+* Closing connection #0
+** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
+
+Or for OSM Mapnik tile server:
+
+* About to connect() to tile.openstreetmap.org port 80 (#0)
+* Trying 193.63.75.28... * connected
+* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
+ GET /13/4065/2748.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: tile.openstreetmap.org
+Accept: */*
+
+* HTTP 1.0, assume close after body
+ HTTP/1.0 200 OK
+ Date: Thu, 14 Oct 2010 22:18:42 GMT
+ Server: Apache/2.2.8 (Ubuntu)
+ ETag: "b66ff9d46474bab68262a3483428a232"
+** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
+ Content-Length: 17194
+ Cache-Control: max-age=94805
+ Expires: Sat, 16 Oct 2010 00:38:47 GMT
+ Content-Type: image/png
+ Age: 5153
+ X-Cache: HIT from konqi.openstreetmap.org
+ X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
+ Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
+ Connection: close
+
+* Closing connection #0
+* About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
+* Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
+* About to connect() to tile.openstreetmap.org port 80 (#0)
+* Trying 193.63.75.28... * connected
+* Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
+ GET /tiles/cycle/13/4065/2747.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: a.andy.sandbox.cloudmade.com
+Accept: */*
+
+* connected
+* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
+ GET /13/4065/2749.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: tile.openstreetmap.org
+Accept: */*
+
+* HTTP 1.0, assume close after body
+ HTTP/1.0 200 OK
+ Date: Thu, 14 Oct 2010 23:44:35 GMT
+ Server: Apache/2.2.8 (Ubuntu)
+ ETag: "8e520ad47ce9c1b63430554886eb5fab"
+** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
+ Content-Length: 18094
+ Cache-Control: max-age=87742
+ Expires: Sat, 16 Oct 2010 00:06:57 GMT
+ Content-Type: image/png
+ X-Cache: MISS from konqi.openstreetmap.org
+ X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
+ Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
+ Connection: close
+
-
-
-Fill in the form
-
-In both cases, &appname; will retain some information.
-The email field is the email you used to subscribed into OSM.
-The password field is the password you used with this account.
-The filename is the name you want your upload has on the server. This information is displayed by the osm server.
-The description is some descriptive information.
-The tags field is a white separated list of tag.
-
-
-
-Geocoded Photo
-
-HOWTO GEOCODE YOUR PHOTOS AND SEE THEM IN VIKING
-
-1) Synchronize your camera's clock with your GPS clock. If your
-camera's clock doesn't have a seconds value you can change, you might
-try setting the minute value just when the minute changes.
-
-
-2) Activate the track log on your GPS.
-
-3) Get outside and take some pictures with your camera while
-making sure your GPS has reception. If you forgot to turn your GPS on
-or forgot to bring it when you took a picture but you know where you
-took the picture, you can make a waypoint with a name of the format
-YYMMDDhhmm, representing the time the picture was taken, to record
-where you were at that time.
-
-4) Get home and download your pictures and GPS data. You can
-download the GPS data several ways. The first is using gpspoint to
-download from a Garmin GPS: gpspoint -p /dev/ttyS0 -dw -dt -of 2004-04-02-trip1
-
-
-Where /dev/ttyS0 is the serial port the GPS is connected to. If you
-don't have a Garmin GPS, or if you don't feel like install gpspoint,
-you can use my version of gpsbabel with support for gpspoint files. You
-can use gpsbabel to either translate the GPS data from a format you
-already have the data in or download it directly from your GPS
-reciever. A typical command line would something like this:gpsbabel -i garmin -f /dev/ttyS0 -o gpspoint -F 2004-04-02-trip1
-
-
-5) Launch GPSPhoto.
-
-
-6) You must now bring your photos into GPSPhoto. Either drag them (or
-the directory containing them) from your favorite file manager to the
-list on the left of the GPSPhoto window, or use the buttons below the
-list to find them.
-
-
-7) Do the same for your GPS data file(s), dragging them to the list on the right of the GPSPhoto Window.
-
-8) Click the Execute button, and choose a location to save the
-gpspoint file containing the waypoints for your photos. Then click OK
-to write the waypoints to this file.
-
-
-9) Open Viking and open both your original GPS data file and your image waypoint file just created.
-
+
+
-
+Extending VikingCurrently, &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".
@@ -940,10 +2377,30 @@ to write the waypoints to this file.
You can find more examples in the documentation part of the distribution.Map Source
- It is possible to add new map's sources. The file is ~/.viking/maps.xml.
- An example of the file in the distribution doc/examples/maps.xml.
- Currently, there is a single object class available: VikSlippyMapSource. Such feature allows to declare any map's source working like OpenStreetMap.
- The related properties are:
+ It is possible to add new map's sources. The file is ~/.viking/maps.xml for UNIX like systems and C:\Documents and Settings\username\.viking\maps.xml on Windows XP.
+ An example of the file is in the distribution doc/examples/maps.xml. Further examples and values are online in the Maps Wiki
+
+ The VikSlippyMapSource allows to declare any map's source working like OpenStreetMap. It supports the following properties:
+
+
+ id
+ this is an integer and should be unique as it used to identify the map source
+
+
+ label
+ the text displayed in the map's source selection dialog
+
+
+ hostname
+ the server's hostname (eg. "tile.openstreetmap.org")
+
+
+ url
+ 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")
+
+
+
+ The VikTmsMapSource allows to declare any TMS service. It supports the following properties:
id
@@ -963,13 +2420,33 @@ to write the waypoints to this file.
+ The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties:
+
+
+ id
+ this is an integer and should be unique as it used to identify the map source
+
+
+ label
+ the text displayed in the map's source selection dialog
+
+
+ hostname
+ the server's hostname (eg. "tile.openstreetmap.org")
+
+
+ url
+ 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")
+
+
+ Go-to search enginesIt is possible to add new new search engines for the "Go-To" feature. The file is ~/.viking/goto_tools.xml.An example of the file in the distribution doc/examples/goto_tools.xml.
- Currently, there is a single object class available: VikGotoXmlTool. Such feature allows to declare any search engine using a XML format as result.
+ Currently, there is a single object class available: VikGotoXmlTool. Such feature allows to declare any search engine using a XML format as result.The related properties are:
@@ -1002,122 +2479,233 @@ to write the waypoints to this file.
- Webtools
+ External toolsIt is possible to add new external tools. The file is ~/.viking/external_tools.xml.An example of the file in the distribution doc/examples/external_tools.xml.
- 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.
+ The VikWebtoolCenter allows to declare any Webtool using a logic based on center coordinates and zoom level value.
+ The related properties are:
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url
+ 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")
+
+
+
+ The VikWebtoolBounds allows to declare any Webtool using a logic based on bounds coordinates.
+ The related properties are:
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url
+ 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")
+
+
+
+
+
+
+ Routing engine
+ It is possible to declare new routing engines. The file is ~/.viking/routing.xml.
+ An example of the file in the distribution doc/examples/routing.xml.
+ The VikRoutingWebEngine allows to declare a routing engine available via HTTP.The related properties are:
id
- this is an integer and should be unique as it used to identify the tool
+ a string, should be unique as it used to identify the routing engine
+
+
+ label
+ the text displayed in the menu entry
+
+ url-base
+ the base URL of the web service (eg. "http://hostname/service?")
+
+
+ url-start-ll
+ the part of the URL setting the starting point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&start=%s,%s")
+
+
+ url-stop-ll
+ the part of the URL setting the end point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&stop=%s,%s")
+
+
+ url-via-ll
+ the part of the URL setting via point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&via=%s,%s")
+
+
+ url-start-dir
+ the part of the URL setting the starting point location for direction based routing, parametrized in the spirit of C printf format, with one "%s" for direction (eg. "&start=%s")
+ (Optional)
+
+
+ url-stop-dir
+ the part of the URL setting the end point location for direction based routing, parametrized in the spirit of C printf format, with one "%s" for direction (eg. "&start=%s")
+ (Optional)
+
+
+ referer
+ an URL to serve as referer for the HTTP request (eg. "http://hostname/")
+
+
+ follow-location
+ the max depth of recursive redirections
+
+
+
+
+
+
+ Remote File Datasources
+ It is possible to add web references expected to return a file which can then be opened directly or converted via GPSBabel.
+ The file is ~/.viking/datasources.xml.
+ An example of the file is in the source distribution doc/examples/datasources.xml.
+ The VikWebtoolDatasource allows to declare any URL using logic based on coordinates.
+ The related properties are:
+ labelthe text displayed in the menu entryurl
- 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")
+
+ the parametrized URL to open in the spirit of C printf format, with up to 7 "%s" values. e.g. http://hostname/getfile?lat=%s&lon=%s
+ The order and meaning of these parameters is given by the url_format_code below
+
+
+
+ url_format_code
+
+ A string describing the parametrized URL substitution parameters, each character represents how to translate each term.
+ B = Bottom of the current view i.e. minimum latitude
+ L = Left of the current view i.e. minimum longitude
+ T = Top of the current view i.e. maximum latitude
+ R = Right of the current view i.e. maximum longitude
+ A = center lAtitude of the current view
+ O = center lOngitude of the current view
+ Z = OSM Zoom value of the current view. See Zoom Levels
+ Thus for the url example above then the format code should be AO
+
+
+
+ file_type
+
+ This value is passed on for the -i parameter in interfacing with GPSBabel.
+ If it is not defined then the returned file is interpreted internally as a GPX file.
+ Possible values such as 'kml', 'mapsource' etc.. can be used. See GPSBabel File Formats for the full list.
+
-
-
-What to Do if &appname; Does Not Seem to Work
-
-In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
-viking -dV
-
-
-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.
-E.g. Something like this for DEMs:
-
-** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
-* About to connect() to dds.cr.usgs.gov port 80 (#0)
-* Trying 152.61.128.95... * connected
-* Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
- GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
-User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
-Host: dds.cr.usgs.gov
-Accept: */*
- HTTP/1.1 200 OK
- Date: Sun, 26 Jul 2009 18:13:38 GMT
- Server: Apache
- Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
- ETag: eac3f8-1828f5-46f3caa76070a
- Accept-Ranges: bytes
- Content-Length: 1583349
- Content-Type: application/zip
-
-* Connection #0 to host dds.cr.usgs.gov left intact
-* Closing connection #0
-** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
-
-Or for OSM Mapnik tile server:
-
-* About to connect() to tile.openstreetmap.org port 80 (#0)
-* Trying 193.63.75.28... * connected
-* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
- GET /13/4065/2748.png HTTP/1.1
-User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
-Host: tile.openstreetmap.org
-Accept: */*
+
+ More
+ Note that, on UNIX like systems, the extension files (maps.xml, goto_tools.xml, external_tools.xml, datasources.xml) are also searched in /etc/viking and /usr/share/viking directories (or related in your system).
+ The XDG_DATA_DIRS environment variable can be used to change these directories.
+ The XDG_DATA_HOME environment variable is also used (if set) to look for these extension files.
+
-* HTTP 1.0, assume close after body
- HTTP/1.0 200 OK
- Date: Thu, 14 Oct 2010 22:18:42 GMT
- Server: Apache/2.2.8 (Ubuntu)
- ETag: "b66ff9d46474bab68262a3483428a232"
-** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
- Content-Length: 17194
- Cache-Control: max-age=94805
- Expires: Sat, 16 Oct 2010 00:38:47 GMT
- Content-Type: image/png
- Age: 5153
- X-Cache: HIT from konqi.openstreetmap.org
- X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
- Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
- Connection: close
-
-* Closing connection #0
-* About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
-* Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
-* About to connect() to tile.openstreetmap.org port 80 (#0)
-* Trying 193.63.75.28... * connected
-* Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
- GET /tiles/cycle/13/4065/2747.png HTTP/1.1
-User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
-Host: a.andy.sandbox.cloudmade.com
-Accept: */*
-* connected
-* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
- GET /13/4065/2749.png HTTP/1.1
-User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
-Host: tile.openstreetmap.org
-Accept: */*
+
+ Miscellaneous Settings
+ Various individual values are automatically saved between &app; sessions in the ~/.viking/viking.ini file.
+ This file is not intended to be manually edited, but since it is a plain text file it can be changed if desired.
+ Some values in this file are read only, in the sense that there is no way to set it other than by manually entering in the keys and values (the key will not exist in the file otherwise). This allows some fine tuning of &app; behaviours, without resorting to recompiling the code. However is it not expected that these values should need to be changed for a normal user, hence no GUI options for these have been provided.
+ Here is the list of the read only keys and their default values.
+
+
+ maps_max_tiles=1000
+
+
+ maps_min_shrinkfactor=0.0312499
+
+
+ maps_max_shrinkfactor=8.0000001
+
+
+ maps_real_min_shrinkfactor=0.0039062499
+
+
+ background_max_threads=10
+
+
+ window_menubar=true
+
+
+ version_check_period_days=14
+
+
+ trackwaypoint_start_end_distance_diff=100.0
+
+
+ gps_statusbar_format=GSA
+ This string is in the Message Format Code
+
+
+ trkpt_selected_statusbar_format=KATDN
+ This string is in the Message Format Code
+
+
+
+
+ Message Format Code
+ Currently for ease of implementation the message format code is a string of characters.
+ Each character represents what should be inserted in relation to a Trackpoint.
+ One day it might evolve into something more user friendly with a frontend to control it, perhaps allowing arbitary text too. However for now at least some control is offered :)
+
+
+
+ Character Code
+
+ G = Some text to display at the start of the message - GPSD
+ K = Some text to display at the start of the message - Trkpt
+ A = Altitude of a Trackpoint
+ S = Speed of a Trackpoint
+ C = Course of a Trackpoint
+ L = Location of a Trackpoint
+ T = Time of a Trackpoint
+ M = Time diff of a Trackpoint from the previous trackpoint
+ X = Number of satellites used in the trackpoint fix
+ D = Distance of the trackpoint from the start of a track (following along the track)
+ P = Distance difference of the trackpoint from the previous trackpoint
+ N = Name of track to which the trackpoint belongs
+
+
+
+ Output Notes
+
+ If the output has * after it, then the value has been calculated via interpolation (such as speed when the Trackpoint does not contain a speed value).
+ If the output has ** after it, then difficulties were encountered in trying to work the value so probably a default of 0 will be shown.
+
+
+
+
+
+
-* HTTP 1.0, assume close after body
- HTTP/1.0 200 OK
- Date: Thu, 14 Oct 2010 23:44:35 GMT
- Server: Apache/2.2.8 (Ubuntu)
- ETag: "8e520ad47ce9c1b63430554886eb5fab"
-** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
- Content-Length: 18094
- Cache-Control: max-age=87742
- Expires: Sat, 16 Oct 2010 00:06:57 GMT
- Content-Type: image/png
- X-Cache: MISS from konqi.openstreetmap.org
- X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
- Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
- Connection: close
-
-
+
+Dependencies
+gpsbabel
+&appname; uses GPSBabel to convert data.
+
+unbuffer (optional)
+&appname; uses unbuffer command to optimize conversion calls.
+
+gpsd (optional - but not Windows)
+&appname; can use gpsd to get the current location.
+