X-Git-Url: https://git.street.me.uk/andy/viking.git/blobdiff_plain/29c93cc57d2f7715c58b4e577440bc580a47bd8a..f85716b8f60aeede60363de7e7bb7968a8cc70ff:/help/C/viking.xml?ds=sidebyside
diff --git a/help/C/viking.xml b/help/C/viking.xml
index a8eaa7b1..e0a016aa 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">
-
-
-
+
+
+
]>
@@ -626,6 +644,9 @@ The cut/copy/paste options can be accessed in a variety of ways once the layer h
Buttons at the bottom of the Layers Panel
+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.
@@ -640,7 +661,7 @@ geocaches, and paste it into an active TrackWaypoint layer. &appname; can
automatically recognize several variations of the lat/lon format.
-By right-clicking on tracks, routes or waypoints in the layers panel, you can access many commands on them.
+By right-clicking on tracks, routes or waypoints in the , you can access many commands on them.
You can easily find a specific track, route or waypoint by expanding the appropriate containing Tracks, Routes or Waypoints sublayer in the
layers panel to show all the individual items and then typing the name of the track, route or waypoint.
@@ -660,7 +681,7 @@ By default routes are coloured red. Tracks are automatically assigned a spread o
-Most operations are available on tracks are available on routes, except for functionality that relies on having timestamps - since routes by definition have no timing information. Thus for example, uploading a route to OpenStreetMap Traces is not available nor is Geotagging on a route.
+Most operations available on tracks are available on routes, except for functionality that relies on having timestamps - since routes by definition have no timing information. Thus for example, uploading a route to OpenStreetMap Traces is not available nor is Geotagging on a route.
It is possible to convert between Tracks and Routes, although converting from a Track to a Route may involve a loss of information (hence you are required to confirm this operation before it happens).
@@ -726,9 +747,13 @@ Version1.1+: An individual track can be exported to a GPX file via the track men
Finish Track or Route
-This is only available when a track or route is being created by the or tools.
Selecting this option ends the creation of that individual track or route.
+
+
+This is only available when a track or route is being created by the or tools.
+
+New
@@ -855,6 +880,18 @@ See Geotagging for further detail.
+List Tracks or Routes
+
+Opens a new dialog with the list. As described in the Aggregrate layer
+
+
+
+List Waypoints
+
+Opens a new dialog with the list. As described in the Aggregrate layer
+
+
+
Track and Route Sublayer Options
@@ -865,6 +902,12 @@ See Geotagging for further detail.
View All Tracks or Routes. Same as the layer View All Tracks or View All RoutesDelete All Tracks or Routes. Same as the layer Delete All Tracks or Delete All RoutesDelete Tracks or Routes from Selection. Same as the layer Delete Tracks from Selection or Delete Routes from Selection
+List Tracks or Routes. Opens a new dialog with the list. As described in the Aggregrate layer
+
+Also gives other options for handling multiple items:
+
+Sort. Gives the ability to sort the items in the treeview alphabetically
+Visibility. Offers options to quickly control the visibility of all items within the sublayer, as per
@@ -882,7 +925,7 @@ The following colors are used in the elevation-distance graph:
-'Main' colour - this is dependent on your Desktop theme - often blue by default
+Main colour - this is dependent on your Desktop theme - often blue by defaultelevation data in graph
@@ -911,9 +954,13 @@ The following colors are used in the elevation-distance graph:
Finish Track
-This is only available when a track is being created by the tool.
Selecting this option ends the creation of the individual track.
+
+
+This is only available when a track is being created by the tool.
+
+Goto
@@ -946,9 +993,11 @@ 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.
+
This is not available on routes as they have no timestamps.
+Merge With Other Tracks
@@ -979,9 +1028,11 @@ 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.
+
This is not available on routes as they have no timestamps.
+Split By Number of Points
@@ -995,19 +1046,60 @@ This can be useful with devices which may have limits on the number of points it
Splits track segments into new tracks.
+
This is not available on routes as they do not have route segments.
+
+
+
+Split at Trackpoint
+
+Splits the track at the currently selected trackpoint.
+
+
+The current track will finish at this trackpoint.
+A new track will start from a copy of this trackpoint.
+
+
+
+This is only enabled when a trackpoint is selected.
+
+
+
-Split at Trackpoint
+Insert Points
+
+
+These options are only enabled when a trackpoint is selected.
+
+
+Insert Point Before Selected Point
+
+Inserts a track point halfway between the previous track point and the current track point.
+All track point properties are interpolated between the two points.
+
+
+Insert Point After Selected Point
-Splits the track at the currently selected trackpoint. This is only enabled when a trackpoint is selected.
+Inserts a track point halfway between the current track point and the next track point.
+All track point properties are interpolated between the two points.
Delete Points
+Delete Selected Point
+
+Deletes the currently selected track point.
+
+
+
+This is only enabled when a trackpoint is selected.
+
+
+Delete Points With the Same Position
Deletes subsequent points that have the same position (but have different timestamps).
@@ -1017,18 +1109,71 @@ Deletes subsequent points that have the same position (but have different timest
Deletes subsequent points that have the same time stamp (but may have different positions).
+
This is not available on routes as they have no timestamps.
+
+Transform
+
+These options alter the data of trackpoints of a track but not add or remove trackpoints.
+And don't seem to fit any other category :)
+Apply DEM data
If any DEM data is loaded, this will apply the DEM data to give the track elevation data.
+Two ways of applying DEM data are offered:
+
+Keep. Retains the existing elevation data of trackpoints and only those missing an elevation value are set.
+Overwrite. Elevation data are set on all trackpoints even if they already elevation values.
+
+
+
+Smooth Missing Elevation data
+
+In various locations across the world, there are missing DEM values (AKA DEM Holes) from the SRTM data.
+This is particularly noticeable in mountainous areas.
+Two ways of applying elevation data to trackpoints that do not have elevation values are offered:
+
+Interpolated. Missing elevation data is interpolated between the previous and next known values.
+Flat. Elevation data is filled in from the last previously known value.
+
+
+
+
+Convert to Track or Route
+
+If this is a Route then it will convert it to a Track.
+
+
+If this is Track then convert it to a Route.
+
+
+
+Converting from a Track to a Route may involve a loss of information, in particular timestamp values (hence you are required to confirm this operation before it happens).
+
+
+
+
+Anonymize Times
+
+Timestamp information of a track can be shifted to be all offset from 1901-01-01.
+
+
+Thus the timestamps themselves will no longer reveal exactly when a track was taken.
+However the relative difference between the timestamps is kept thus one is still able to calculate some properties such as speeds along the track.
+
+
+
+This is not available for routes, as they have no timestamps.
+
+Export Track as GPX
@@ -1044,7 +1189,7 @@ Changes the current tool to add trackpoints to the end of the track.
Extend Using Route Finder
-Enables the Route Finder tool. Thus on a subsequent left click in the viewport, a route is calculated from the end of track to that point using Google's route service and applied to the track.
+Enables the Route Finder tool. Thus on a subsequent left click in the viewport, a route is calculated from the end of track to that point using the default route service and applied to the track.
@@ -1068,9 +1213,35 @@ Same as the layer Upload to OSM command, but o
This selects the track to be used in the Filter With Trackname feature.
+
This is not available on routes.
+
+
+
+Edit Trackpoint
+
+This opens the Trackpoint edit dialog. See .
+
+
+
+This is only enabled when a trackpoint is selected.
+
+
+
+
+Refine Route...
+
+This function allows to request a Routing Engine in order to refine a given route.
+By "refining" we mean computing all real intermediates points between some given major points.
+This could be useful to compute a trip giving only the wished important steps.
+
+
+
+This is only available on routes.
+
+View Google Directions
@@ -1097,6 +1268,7 @@ The record of the Google route is stored in the track's comment, so if the comme
Goto Waypoint. Same as the layer Goto WaypointDelete All Waypoints. Same as the layer Delete All WaypointsDelete Waypoints from Selection. Same as the layer Delete Waypoints from Selection
+List Waypoints. Opens a new dialog with the list. As described in the Aggregrate layer
@@ -1122,7 +1294,7 @@ This centers the viewport on the selected waypoint.
Visit Webpage
-If the waypoint's comment (or description) starts with 'http:' then this option is available and allows launching a web browser to go to the webpage.
+If the waypoint's comment (or description) starts with http: then this option is available and allows launching a web browser to go to the webpage.
@@ -1247,7 +1419,7 @@ This layer provides a single map resource, you may have multiple map layers but
You will need an open internet connection when you are downloading maps, but once downloaded they are available from the hard disk cache. When map are avaliable from the disk cache it is much faster and can be used offline.
-Some maps are continually improving over time (e.g. OpenStreetMap) and so in order to not to have to (re)download the data all the time &appname; employs a timeout method - 'Tile Age' to determine whether to access the server. However a forced refresh for the current view can be made via the Reload All Onscreen Maps option.
+Some maps are continually improving over time (e.g. OpenStreetMap) and so in order to not to have to (re)download the data all the time &appname; employs a timeout method - Tile Age to determine whether to access the server. However a forced refresh for the current view can be made via the Reload All Onscreen Maps option.
Inbuilt maps include various Terraserver (Primarily USA coverage) and OpenStreetMap (OSM) ones and more:
@@ -1287,6 +1459,30 @@ This requests map tiles only if the maps are older than the Tile Age preference.
Force a refresh of all visible map tiles.
+
+Download Maps in Zoom Levels
+
+This opens a dialog to enable requesting the download of maps for the region in the viewport over a specified number of zoom levels.
+The download method type can be specified to help limit the number of requests.
+
+
+
+There are some inbuilt limits to prevent downloading large amounts of map tiles.
+
+
+Please respect the usage policy of the tile set provider.
+Such as OSM Tile Usage Policy.
+
+
+
+
+Maps Download Dialog: Example
+
+
+
+
+
+
@@ -1315,9 +1511,11 @@ Here are some suggestions:
Thus one can have a list of all your tracks, but groups can be shown or not using the relevant layers visibility checkbox.
+Layer Operations
-This layer only has one operation: New Layer
+The following are available on Aggregate Layers:
+New Layer
@@ -1325,6 +1523,97 @@ Add a new layer of the selected type.
+Sort
+
+The list within the treeview can be sorted.
+
+
+Currently alphabetical (A to Z or Z to A) sorts are available, since only the name can be seen in the treeview.
+
+
+
+Track List
+
+Selecting this opens a dialog listing all the tracks in a table along side statistics such as track length and maximum speed.
+Each column header is clickable and will reorder the list according to that particular column.
+
+
+This table may be invoked from a variety of different layer levels and will then list only the relevant tracks (and/or routes).
+
+Aggregate Layer: Lists Tracks and Routes and the TrackWaypoint Layer they are in
+TrackWaypoint Layer: Lists Tracks and Routes
+TrackWaypoint Track sublayer: Lists Tracks only
+TrackWaypoint Route sublayer: Lists Routes only
+
+
+
+
+Track List Dialog: Example
+This is showing all tracks and routes (although there are no actual routes here!) in multiple TrackWaypoint layers, that has been sorted by height.
+Note that routes will not have timestamps or speeds, but may have elevations and should have some distance!
+
+
+
+
+
+
+Hovering the mouse over an entry will show a tooltip of the comment or description if it is available.
+
+
+Each entry in the track list can be selected and on mouse right click offers these options:
+
+View. Move the viewport to the area of the item and highlight it.
+Statistics. Open the properties dialog on the Statistics tab. Note this will close the track list dialog.
+
+
+
+
+Waypoint List
+
+Selecting this opens a dialog listing all the waypoints to give a overview of the waypoint information.
+Each column header is clickable and will reorder the list according to that particular column.
+
+
+This table may be invoked from a variety of different layer levels and will then list only the relevant waypoints.
+
+Aggregate Layer: Lists Waypoints and the TrackWaypoint Layer they are in
+TrackWaypoint Layer: : Lists Waypoints
+TrackWaypoint Waypoint sublayer: Lists Waypoints
+
+
+
+
+Waypoint List Dialog: Example
+This was invoked on a TrackWaypoint layer and shows all waypoints from that single layer. It has been sorted by the symbols.
+
+
+
+
+
+
+Hovering the mouse over an entry will show a tooltip of the description if it is available.
+
+
+Each entry in the list can be selected and on mouse right click offers these options:
+
+View. Move the viewport to the area of the item and highlight it.
+Properties. This will open the properties dialog. Note this will close the waypoint list dialog.
+Show Picture. If enabled, this will open the associated image in an external Image Viewer program.
+
+
+
+
+Visibility Options
+
+This offers a quick way to set all the visibilities of each item within the containing layer, rather than having to change each one individually.
+
+Show All. Ensures all items are set to be visible.
+Hide All. Ensures all items are set to be invisible. This is useful for then turning on single items afterwards so the display is not cluttered.
+Toggle. Inverts the visibility status of each item.
+
+
+
+
GeoRef Layer
@@ -1426,7 +1715,7 @@ This mode is entered by clicking on the toolbar icon:
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.
+A second click will freeze the ruler at that point.
This mode can also be entered by the keyboard shortcut Ctrl+Shift+U
@@ -1514,10 +1803,39 @@ Left click near a trackpoint (in screen pixel terms) to bring up the Track Point
Whilst the edit dialog is already open, left click again and drag enables moving of the trackpoint.
If Ctrl is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint.
+Edit Trackpoint Dialog
-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.
+Editing options in the Trackpoint Edit dialog include:
+
+Edit the trackpoint name
+Changing raw lat/long position and altitude
+Forward (go to the next trackpoint)
+Back (go to the previous trackpoint)
+Delete
+Insert. Inserts a point halfway to next trackpoint
+Split.
+
+
+
+Several fields are read only for reference purposes, values are shown if the trackpoint has such information:
+
+Time.
+Speed and course.
+'Between' values: Speed, Time Difference and Distance Difference. When moving between trackpoints (via the Back and Forward buttons) these values are calculated.
+GPS precision factors.
+
+
+
+
+Trackpoint Edit Dialog: Example
+
+
+
+
+One must have been going downhill here to get a reasonable speed by bicycle!
+Show Picture
@@ -1530,11 +1848,11 @@ For Linux you can override this with the setting in the Route Finder
Enable this tool by clicking on the toolbar icon:
-Creates a track using Google maps routing between two points.
+Creates a track using default routing engine between two points.
Requires an internet connection. Click one point, then click another to
create a track.
@@ -1572,7 +1890,7 @@ Drag to move the georeferenced map.
-Map Download
+Map Download
You must have a Layer selected to use this.
@@ -1583,7 +1901,30 @@ Enable this tool by clicking on the toolbar icon:
-Right-click to redownload bad/all tiles. Right-click and drag to redownload bad/all tiles in the dragged rectangle area.
+Right-click to redownload tiles via the selected method. Right-click and drag to redownload tiles in the dragged rectangle area by the selected method.
+The possible methods to redownload one or more tiles are:
+
+
+
+Bad - Only if the tile is corrupt in some way or missing, then this will download a new copy
+New - Refresh the tile according to the local map cache and if server has a newer version
+All - Redownload the tile
+
+
+Map Tile Information
+
+By right clicking on viewport and selecting Show Tile Information you can see the tile properties of this location for the current map layer and current zoom level.
+This includes the remote source URL for the tile and the cached version on the local filesystem with timestamp details.
+
+
+
+
+Map Tile Info Dialog: Example
+
+
+
+
+This is using MapQuest at &appname; zoom level 128 over the Isle of Wight, UK.
@@ -1597,6 +1938,21 @@ Enable this tool by clicking on the toolbar icon:
Click to download and import a DEM file.
+DEM File Information
+
+By right clicking on viewport and selecting Show DEM File Infomation you can see the file properties of the DEM file for this location.
+This includes the remote source URL for the file and the cached version on the local filesystem with timestamp details.
+
+
+
+
+DEM File Info Dialog: Example
+
+
+
+
+This is for block 51N, 003W - covering Bristol in the UK.
+Webtools
@@ -1651,8 +2007,8 @@ This feature is called Webtools. It is also known as Extern
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.
+<emphasis>Home</emphasis> Default Location: Latitude and Longitude
+You can set the Home location directly by inputting the latitude and longitude in decimal degrees.
Tile's age
@@ -1703,13 +2059,50 @@ 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.
+
+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'sGetting 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
@@ -1791,13 +2184,13 @@ The viewport will be automatically moved and resized to view the contents of the
-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.
@@ -1806,13 +2199,13 @@ 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
@@ -1832,7 +2225,7 @@ the map.
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 maps
@@ -2024,7 +2417,7 @@ This feature can be really useful for checking existing data before uploading ne
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.
+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.
@@ -2053,7 +2446,7 @@ This list can be sorted on each column so that it easier to find an individual t
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 Layers Panel.
+ 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:
@@ -2131,6 +2524,101 @@ This list can be sorted on each column so that it easier to find an individual t
+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
+
+
+
+
+
+
+
Extending Viking
@@ -2153,7 +2641,7 @@ This list can be sorted on each column so that it easier to find an individual t
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:
+ The VikSlippyMapSource allows to declare any map's source working like OpenStreetMap. It supports the following properties:
id
@@ -2173,7 +2661,7 @@ This list can be sorted on each column so that it easier to find an individual t
- The VikTmsMapSource allows to declare any TMS service. It supports the following properties:
+ The VikTmsMapSource allows to declare any TMS service. It supports the following properties:
id
@@ -2193,7 +2681,7 @@ This list can be sorted on each column so that it easier to find an individual t
- The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties:
+ The VikWmscMapSource allows to declare any WMS or WMS-C service. It supports the following properties:
id
@@ -2219,7 +2707,7 @@ This list can be sorted on each column so that it easier to find an individual t
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:
@@ -2255,144 +2743,220 @@ This list can be sorted on each column so that it easier to find an individual t
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.
- The VikWebtoolCenter 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:
- id
- this is an integer and should be unique as it used to identify the tool
+ 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:
+ labelthe text displayed in the menu entryurl
- 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 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")
- The VikWebtoolBounds allows to declare any Webtool using a logic based on bounds coordinates.
+
+
+
+ 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 enginelabelthe 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")
+ 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:
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url
+
+ 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.
+
+
+
+
+
+
More
- Note that, on UNIX like systems, the extension files (maps.xml, goto_tools.xml, external_tools.xml) are also searched in /etc/viking and /usr/share/viking directories (or related in your system).
+ 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 s also used (if set) to look for these extension files.
+ The XDG_DATA_HOME environment variable is also used (if set) to look for these extension files.
-
-
-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
-
-
-
+
+ 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=KEATDN
+ 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
+ E = Name of the trackpoint
+
+
+
+ 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.
+
+
+
+
+
+
+
Dependenciesgpsbabel