X-Git-Url: https://git.street.me.uk/andy/viking.git/blobdiff_plain/269865aadfcdeba128def41c2931d6cf02a0945b..873fc9e4e6711cf2b5586cb8e28eb446e1af1fb6:/help/C/viking.xml diff --git a/help/C/viking.xml b/help/C/viking.xml index 0c4e03ca..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"> - - - + + + ]> - -
Layers - +
Tracks vs Routes -Layers supported by &appname; are: +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. - -Aggregate -TrackWaypoint -GPS -DEM -Coord -Map -GeoRef - -For each layer there are a few standard options: +Q. When planning a route what difference does it make if it's a route or a track? - -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 - -The cut/copy/paste options can be accessed in a variety of ways once the layer has been selected: +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: -Standard keys: Ctrl+x|c|v -Main menu Edit -From the right click menu -Buttons at the bottom of the Layers Panel + +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. + + +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. + +
+ +
+ +
File Types and the Main Window + -See the individual section for detail about each layer. +&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...). - -
TrackWaypoint Layer -TrackWaypoint layers display GPS data (tracks and waypoints). +Besides it's own file type, &appname; can open (and save to via export methods) GPX and KML file types. -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. + + +&appname; does not handle GPX 1.1 particularly well - it prefers GPX 1.0 + -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. +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. - -
Layer Operations -The layer has a context menu with several operations. +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! - -
View Layer -Version1.1+: This will automatically move the viewport and select the best zoom level to see the whole layer (i.e. tracks and waypoints). +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 All Tracks +
New -Version1.1+: This will automatically move the viewport and select the best zoom level to see the all the tracks in the layer (ignoring positions of any waypoints). +Located on the FileNew menu and on the toolbar New. -
- -
View All Waypoints -Version1.1+: This will automatically move the viewport and select the best zoom level to see the all the waypoints in the layer (ignoring positions of any tracks). +This creates a new window with the default settings.
-
Goto Center of Layer +
Open -This will automatically move the viewport to see the whole layer (i.e. tracks and waypoints). It does not adjust the zoom level. +Located on the FileOpen menu and on the toolbar Open. -
- -
Goto Waypoint -This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it. +This opens a file chooser dialog to select one (or more) files of the supported GPS data file types: + +Viking +GPX +KML + - -Note this search is not very clever and only finds exact matches. -You are probably better off expanding the waypoint list and directly start typing, as mentioned above, which finds a match based on each letter typed. +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. - + + +&appname; handles more file types via the Acquire methods below. + +
-
Export Layer +
Save -The layer (all tracks and waypoints) can be exported to a file GPX, GPSPoint, GPSMapper or Google's KML format. +Located on the FileSave menu and on the toolbar Save. -Version1.1+: An individual track can be exported to a GPX file via the track menu. +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.
-
New Waypoint +
Save As -This opens a dialog box to create a new waypoint. A default name will be suggested and the default position is the center of the viewport. +Located on the FileSave As menu only. -
- -
Add Wikipedia Waypoints -This gets 'interesting' points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary. +This will ask for a new name to save as a Viking file (even it was already a Viking file).
-
Geotag Images +
Append -This starts the Geotagging Images dialog against all tracks in the layer. -See Geotagging for further detail. +Located on the FileAppend menu only. + + +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.
-
Upload To OSM +
Acquire + -This opens a dialog to upload all tracks and waypoints to OpenStreetMap traces. -Useful if you are an OpenStreetMap contributor (you will need an OpenStreetMap account), these details can be stored in &appname; preferences. +Available on the FileAcquire menu and from the layer menu. - &appname; allows you to edit a track, e.g. remove duplicate points, perhaps remove track points leading to your home and then upload it to OpenStreetMap. +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. - - Warning! -The password is transferred unencrypted in every request sent to the OpenStreetMap server. This is due to the use of OpenStreetMap's basic authentication method. +If used from the layer menu these methods place the results in that TrackWaypoint layer. -Currently &appname; does not support the OAuth mechanism. - -
-
Filter -
Simplify All Tracks +
+From GPS -This opens dialog to request the number of points each track will be simplified using GPSBabel. The result is put into a new layer. The simplification method removes points considered to be in a 'near straight line', thus reducing the number of points and attempting to keep the most important turning points. +FileAcquireFrom GPS +Probably the easiest way of getting information from a GPS Device. -
-
Remove Duplicate Waypoints -Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer. +Select the GPS Device communication settings and then hit OK. +See the Getting Started section for more info about the settings. -However it only considers a precise position (waypoints only 1 metre away from each other are considered different) and also doesn't consider if the waypoints have different comments, symbols or images. +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.
-
-
Filter With <emphasis>Trackname</emphasis> +
+Import File With GPSBabel -This runs GPSBabel on the layer using information from a previously selected track (select via the track menu "Use With Filter" option) with the following command types: +FileAcquireImport File With GPSBabel - -Waypoints Inside This -Waypoints Outside This - -The result is generated in a new Track/Waypoint layer. +Other formats can be imported that are supported by GPSBabel. -
- -
Geotag Images -This starts the Geotagging Images dialog using the specific track. -See Geotagging for further detail. +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.
-
- -
Track Properties +
+OSM Traces -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. +FileAcquireOSM Traces -The following colors are used in the elevation-distance graph: +See section for more information. - - -'Main' colour - this is dependent on your Desktop theme - often blue by default -elevation data in graph - - -Yellow - -no elevation data - - - -Green - -elevation data from DEM - - - -Red - -speed - - - -
-
Track Operations - -
Goto +
+My OSM Traces -This centers the viewport on the selected position on the track: +FileAcquireMy OSM Traces - -Startpoint -"Center" - the notional center from the bounds of the track -Endpoint -Version1.1+: Highest Altitude -Version1.1+: Lowest Altitude -Version1.1+: Maximum Speed - -
- -
View -Version1.1+: This centers the viewport on the track and selects the best zoom level to see it. +See section for more information.
-
Combine -
Merge By Time +
+From Geotagged Images -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. +FileAcquireFrom Geotagged Images +Enables automatic creation of waypoints from geotagged images. -
- -
Merge With Other Tracks -This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with. +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.
-
Merge Segments +
+From Wikipedia Waypoints -Combines track segments. Effectively removing track segment markers to leave one segment for the whole track. +FileAcquireFrom Wikipedia Waypoints -
- -
Append Track -Enable joining of a single track to the end of the current track. -This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection. +This gets interesting points from Wikipedia for the specified view: either within the extent of layer bounds or within the current viewport boundary.
-
-
Split -
Split By Time +
+From Routing -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. +FileAcquireFrom Directions -
- -
Split By Number of Points -Version1.2+: This operation will split a single track into segments by the number of points specified. -This can be useful with devices which may have limits on the number of points it supports. +This gets a route from given directions.
-
Split Segments - -Splits track segments into new tracks. - -
+
-
Split at Trackpoint +
Print -Splits the track at the currently selected trackpoint. This is only enabled when a trackpoint is selected. +Located on the FilePrint menu and on the toolbar Print. -
-
- -
Delete Points -
Delete Points With the Same Position -Deletes subsequent points that have the same position (but have different timestamps). +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. -
-
Delete Points With the Same Time -Deletes subsequent points that have the same time stamp (but may have different positions). +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.
-
- -
Apply DEM data +
Generate Image File -If any DEM data is loaded, this will apply the DEM data to give the track elevation data. +Located on the FileGenerate Image File menu only. -
- -
Export Track as GPX -Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog. +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. -
- -
Extend Track End -Changes the current tool to add trackpoints to the end of the track. +You should have previously downloaded the tile images for the chosen zoom level, +otherwise the image produced will have missing sections. -
- - -
Upload to OSM +
Generate Directory of Images -Same as the layer Upload to OSM command, but only applies to the track. +Located on the FileGenerate Directory of Images menu only. -
- -
Use With Filter + -This selects the track to be used in the Filter With Trackname feature. +This is only available in UTM mode. + +
+ +
+ +
Layers + + +Layers supported by &appname; are: + + + + + + + + + + + +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 + + +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 + + +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. + +
+ +
TrackWaypoint Layer + +TrackWaypoint layers display GPS data (tracks, routes and waypoints). + +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. + + +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. + + + +The containing Tracks, Routes or Waypoints sublayers are only shown when items of that type exist. +To start creating them enter into a create mode via either the Create toolbar commands or the New menu commands. + + + +The sublayers also offer right click menu options. +These are the same as those available at the TrackWaypoint level, but only those that relate to the sublayer type. + + + +By default routes are coloured red. Tracks are automatically assigned a spread of colours. + + + +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). + + +
Layer Operations + +The layer has a context menu with several operations. + + +
View Layer + +Version1.1+: This will automatically move the viewport and select the best zoom level to see the whole layer (i.e. all tracks, routes and waypoints). + +
+ +
View + +
View All Tracks + +Version1.1+: This will automatically move the viewport and select the best zoom level to see the all the tracks in the layer (ignoring positions of any routes or waypoints). + +
+ +
View All Routes + +Version1.4+: This will automatically move the viewport and select the best zoom level to see the all the routes in the layer (ignoring positions of any tracks or waypoints). + +
+ +
View All Waypoints + +Version1.1+: This will automatically move the viewport and select the best zoom level to see the all the waypoints in the layer (ignoring positions of any tracks or routes). + +
+ +
+ +
Goto Center of Layer + +This will automatically move the viewport to see the whole layer (i.e. tracks, routes and waypoints). It does not adjust the zoom level. + +
+ +
Goto Waypoint + +This opens a dialog box to enter a name of waypoint to search for. If it is found the viewport is centred on it. + + + +Note this search is not very clever and only finds exact matches. +You are probably better off expanding the waypoint list and directly start typing, as mentioned above, which finds a match based on each letter typed. + + +
+ +
Export Layer + +The layer (all tracks, routes and waypoints) can be exported to a file GPX, GPSPoint, GPSMapper or Google's KML format. + + +Version1.1+: An individual track can be exported to a GPX file via the track menu. + +
+ +
Finish Track or Route + +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 +
New Waypoint + +This opens a dialog box to create a new waypoint. A default name will be suggested and the default position is the center of the viewport. + +
+
New Track + +This turns on the tool. + +
+
New Route + +This turns on the tool. + +
+
+ +
Geotag Images + +This starts the Geotagging Images dialog against all tracks in the layer. +See Geotagging for further detail. + +
+ +
Acquire + +This offers the same choice from methods as on the File menu. +However when invoked from here, the results will be stored in this layer (instead of creating a new one). + +
+ +
Upload + +
Upload to GPS + +This opens a dialog to select the GPS Device and port to which the layer information will be transferred. + + +The types of GPS information (tracks, routes or waypoints) to be transferred can be selected. + + +Tracks, Routes or Waypoints that are invisible will not be transferred. + +
+ +
Upload To OSM + +This opens a dialog to upload all tracks and waypoints to OpenStreetMap traces. +Useful if you are an OpenStreetMap contributor (you will need an OpenStreetMap account), these details can be stored in &appname; + + + &appname; allows you to edit a track, e.g. remove duplicate points, perhaps remove track points leading to your home and then upload it to OpenStreetMap. + + + +The password is transferred unencrypted in every request sent to the OpenStreetMap server. This is due to the use of OpenStreetMap's basic authentication method. + +Currently &appname; does not support the OAuth mechanism. + +
+ +
+ +
Delete +Offers deletion of various parts of a TrackWaypoint layer: +
Delete All Tracks +Deletes all the tracks in this layer. +
+
Delete Tracks from Selection +Opens a dialog with list of all the tracks from this layer to choose the ones to delete. +
+
Delete All Routes +Deletes all the routes in this layer. +
+
Delete Routes from Selection +Opens a dialog with list of all the routes from this layer to choose the ones to delete. +
+
Delete All Waypoints +Deletes all the waypoints in this layer. +
+
Delete Waypoints from Selection +Opens a dialog with list of all the waypoints from this layer to choose the ones to delete. +
+
+ +
Filter +
Simplify All Tracks + +This opens dialog to request the number of points each track will be simplified using GPSBabel. The result is put into a new layer. The simplification method removes points considered to be in a 'near straight line', thus reducing the number of points and attempting to keep the most important turning points. + +
+
Remove Duplicate Waypoints + +Remove Duplicate Waypoints - fairly self explainatory, with the results created in a new layer. + + + +However it only considers a precise position (waypoints only 1 metre away from each other are considered different) and also doesn't consider if the waypoints have different comments, symbols or images. + + +
+
+ +
Filter With <emphasis>Trackname</emphasis> + +This runs GPSBabel on the layer using information from a previously selected track (select via the track menu "Use With Filter" option) with the following command types: + + +Waypoints Inside This +Waypoints Outside This + + +The result is generated in a new Track/Waypoint layer. + +
+ +
Geotag Images + +This starts the Geotagging Images dialog using the specific track. +See Geotagging for further detail. + +
+ +
+ +
Track and Route Sublayer Options +Repeats options available at the TrackWaypoint level, but only those for tracks and routes: + +Finish Track or Route. Same as the layer Finish Track or Route +New Track or Route. Same as the layer New Track or New Route +View All Tracks or Routes. Same as the layer View All Tracks or View All Routes +Delete All Tracks or Routes. Same as the layer Delete All Tracks or Delete All Routes +Delete Tracks or Routes from Selection. Same as the layer Delete Tracks from Selection or Delete Routes from Selection + +
+ +
Track and Route Properties + +Show many useful statistics about a track or a route, 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 it, delete duplicates, and split a track from its +component segments (discontinuous breaks in a track) into separate +tracks. + + +The following colors are used in the elevation-distance graph: + + + +Main colour - this is dependent on your Desktop theme - often blue by default +elevation data in graph + + +Yellow + +no elevation data + + + +Green + +elevation data from DEM + + + +Red + +speed + + + + +
+ +
Track and Route Operations + +
Finish Track + +Selecting this option ends the creation of the individual track. + + + +This is only available when a track is being created by the tool. + + +
+ +
Goto + +This centers the viewport on the selected position on the track: + + +Startpoint +"Center" - the notional center from the bounds of the track +Endpoint +Version1.1+: Highest Altitude +Version1.1+: Lowest Altitude +Version1.1+: Maximum Speed (Not Available on Routes) + +
+ +
View + +Version1.1+: This centers the viewport on the track and selects the best zoom level to see it. + +
+ +
Combine +
Merge By Time + +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. + + + +This is not available on routes as they have no timestamps. + + +
+ +
Merge With Other Tracks + +This opens a dialog listing the other tracks in the same TrackWaypoint layer, from which one can select the other tracks to merge with. + +
+ +
Merge Segments + +Combines track segments. Effectively removing track segment markers to leave one segment for the whole track. + +
+ +
Append Track or Route + +Enable joining of a single track to the end of the current track. +This opens a dialog listing the other tracks in the same TrackWaypoint layer from which one can make the selection. + +
+
+ +
Split +
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. + + + +This is not available on routes as they have no timestamps. + + +
+ +
Split By Number of Points + +Version1.2+: This operation will split a single track into segments by the number of points specified. +This can be useful with devices which may have limits on the number of points it supports. + +
+ +
Split Segments + +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. + + + +This is only enabled when a trackpoint is selected. + + +
+
+ +
Delete Points +
Delete Points With the Same Position + +Deletes subsequent points that have the same position (but have different timestamps). + +
+
Delete Points With the Same Time + +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. + + +
+ +
+ +
Apply DEM data + +If any DEM data is loaded, this will apply the DEM data to give the track elevation data. + +
+ +
Export Track as GPX + +Version1.1+: This allows exporting the track as a GPX file by opening a file save dialog. + +
+ +
Extend Track End + +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 the default route service and applied to the track. + +
+ +
Upload + +
Upload to GPS + +Same as the layer Upload to GPS command, but only applies to the track. + +
+ +
Upload to OSM + +Same as the layer Upload to OSM command, but only applies to the track. + +
+ +
+ +
Use With Filter + +This selects the track to be used in the Filter With Trackname feature. + + + +This is not available on routes. + + +
+ +
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. + +
- +
+
Waypoint Sublayer Options +Repeats options available at the TrackWaypoint level, but only those for waypoints: + +New Waypoint. Same as the layer New Waypoint +View All Waypoints. Same as the layer View All Waypoints +Goto Waypoint. Same as the layer Goto Waypoint +Delete All Waypoints. Same as the layer Delete All Waypoints +Delete Waypoints from Selection. Same as the layer Delete Waypoints from Selection + +
+
Waypoint Properties @@ -674,9 +1177,15 @@ 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. + +
+
Visit Geocache Webpage -If the waypoint's name is in Geocache form (GCXXXXX) you can launch a web browser to go to the Geocache page. +If the waypoint's name is in Geocache form (GCXXXXX) then this option is available and allows launching a web browser to go to the Geocache page.
@@ -688,7 +1197,7 @@ Same as the layer New Waypoint.
-
Version1.3+: Geotag Images +
Version1.3+: Geotag Images This dialog allows geotagging images (normally taken with a digital camera) via interpolation against a specific track or all tracks in the TrackWaypoint layer - depending on how it is invoked. @@ -717,11 +1226,11 @@ Various options allow control of how the geotagging process is performed:
-
GPS Layer +
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 GPS layer in the layers panel to see the two TrackWaypoint layers it +Expand the GPS layer in the layers panel to see the two layers it uses for uploading and downloading. To upload, download, or use realtime tracking, right-click the GPS layer and click the appropiate menu item. @@ -736,8 +1245,8 @@ To download data from the GPS, right-click the GPS layer and click
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). +layer of the GPS layer (either by creating waypoints/tracks/routes in it, or +copying and pasting or dragging waypoints/tracks/routes from another layer). Then right-click the GPS layer and click Upload to GPS.
@@ -764,7 +1273,7 @@ There are several options to quickly delete a subsection of data:
-
DEM (Digital Elevation Model) Layer +
DEM (Digital Elevation Model) Layer This layer provides elevation data from the Shuttle Radar Topography Mission (SRTM) @@ -789,13 +1298,13 @@ Using many DEMs is CPU/memory intensive. Depending on your computer's capability
-
Maps Layer +
Maps Layer This layer provides a single map resource, you may have multiple map layers but only top one (if enabled) will be visible. 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: @@ -814,7 +1323,7 @@ Inbuilt maps include various Extending &appname; for further detail. +&appname; can be configured to handle additional maps. See for further detail.
Layer Operations @@ -840,12 +1349,12 @@ Force a refresh of all visible map tiles.
-
Aggregrate Layer +
Aggregate Layer -This layer is a container layer to hold other layers. There is always an initial and controlling 'Top Layer' that can not be removed, although it can be renamed. +This layer is a container layer to hold other layers. There is always an initial and controlling Top Layer that can not be removed or renamed. -This layer type is useful for grouping other layers, especially TrackWaypoint layers, in whatever categories are relevant to you: such as by activity, location or date. +This layer type is useful for grouping other layers, especially layers, in whatever categories are relevant to you: such as by activity, location or date. Here are some suggestions: Hiking @@ -875,7 +1384,7 @@ Add a new layer of the selected type.
-
GeoRef Layer +
GeoRef Layer This layer allows one to use any image as a map. You will need to tell it how to align the map to a position in the world and the scale of map. @@ -901,39 +1410,47 @@ Opens a file save dialog to save the scale and position information as a -
Coord Layer +
Coordinate Layer This layer is allows drawing of grid lines on the viewport.
-
-
Tools +
Tools + +&appname;'s mouse actions on the viewport are controlled by which tool is active. Only one tool can be active at a time. The default mode is pan. + -You can use the scroll wheel and the right-click to zoom and pan no matter what tool you are using. +You can use the scroll wheel, the middle-click, the middle-click+drag to zoom, center map at position and pan respectively no matter what tool you are using. -Scroll: zoom in and out keeping the mouse over same location +Scroll: zoom in and out keeping the mouse over same location -Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down) +Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down) -Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right) +Shift-scroll: pan east-west (also Ctrl-left, Ctrl-right) -Ctrl-shift-scroll: zoom in and out, without changing the center (also Ctrl+, Ctrl- [*not* KeyPad +/-]) +Ctrl-shift-scroll: zoom in and out, without changing the center (also Ctrl+, Ctrl- [*not* KeyPad +/-]) -Left or Middle-click: make the clicked point on the map the center +Middle-click: make the clicked point on the map the center -Middle-click and drag: pan +Middle-click and drag: pan
Pan +This is the default mode of operation for &appname;. + + +This mode is entered by clicking on the toolbar icon: + + Pan moves the viewpoint. A single click centers the viewport at that point, whereas click and drag dynamically moves the view around. This is the default tool. @@ -944,30 +1461,39 @@ This mode can also be entered by the keyboard shortcut Ctrl+Shift+PZoom +This mode is entered by clicking on the toolbar icon: + + Zooms in and out on the clicked part of the map or by the selected area. This mode can also be entered by the keyboard shortcut Ctrl+Shift+Z -Ctrl + left or right click: Zoom in/out and center the map on the clicked location +Ctrl + left or right click: Zoom in/out and center the map on the clicked location -Shift (and hold) + left mouse button: Draws a bounding box area on which to zoom in. The zoom action is performed when the left mouse button is released. +Shift (and hold) + left mouse button: Draws a bounding box area on which to zoom in. The zoom action is performed when the left mouse button is released.
Ruler +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
-
Version1.1+: Select +
Version1.1+: Select + +This mode is entered by clicking on the toolbar icon: + The select tool allows one to choose any waypoint or track by clicking on it (or reasonably near) in the viewpoint. @@ -981,27 +1507,52 @@ This mode can also be entered by the keyboard shortcut Ctrl+Shift+STrackWaypoint Layer Tools -You must have a TrackWaypoint Layer selected to use these tools. +You must have a Layer selected to use these tools. + +
Create Waypoint + +Enable this tool by clicking on the toolbar icon: -
Create Waypoint Left click will open the new waypoint dialog using the specified position.
-
Create/Begin Track +
Create Track + +Enable this tool by clicking on the toolbar icon: + Left click to create a new trackpoint. If it's the initial trackpoint you will be asked to enter a name for the track. If Ctrl is held at the same time, it will jump the new trackpoint position to a nearby existing trackpoint. Right click or Backspace: undo one point. -Double click or Escape: finish track creation. +Double click or Escape: to finish track creation. +Finishing the track is also available via the right click and track menus. + + +One must finish the current track to be able to create another track. + +
+ +
Create Route + +Enable this tool by clicking on the toolbar icon: + + +This operates in exactly the same way as the Create Track above. + + +One must finish the current route to be able to create another route.
Edit Waypoint +Enable this tool by clicking on the toolbar icon: + + Left Click/drag: select/move a waypoint. If Ctrl is held at the same time, it will jump the waypoint position to a nearby existing trackpoint. If Shift is held at the same time, it will jump the waypoint position to a nearby existing waypoint. @@ -1013,6 +1564,9 @@ same menu accessed by right-clicking the waypoint in the layers panel)
Edit Trackpoint +Enable this tool by clicking on the toolbar icon: + + Left click near a trackpoint (in screen pixel terms) to bring up the Track Point Edit dialog on that trackpoint. 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. @@ -1024,15 +1578,20 @@ Options in the Track Point Edit dialog include: change position, go to next, go
Show Picture +Enable this tool by clicking on the toolbar icon: + + Opens an image viewer with the picture associated with the waypoint. By default this uses the default system image viewer. -For Linux you can override this with the setting in the preferences. +For Linux you can override this with the setting in the
- +
Georef Map Layer Tools -You must have a Georef Map Layer selected to use these tools. +You must have a Map Layer selected to use these tools.
Georef zoom + +Enable this tool by clicking on the toolbar icon: + 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. @@ -1059,30 +1621,77 @@ data to a georeferenced map.
Georef move +Enable this tool by clicking on the toolbar icon: + + Drag to move the georeferenced map.
-
Map Download +
Map Download + +You must have a Layer selected to use this. + -You must have a Map Layer selected to use this. +Enable this tool by clicking on the toolbar icon: Click to download a single tile. Drag to download tiles in the dragged rectangle area. -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.
DEM Download -You must have a DEM Layer selected to use this. +You must have a Layer selected to use this. + + +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 @@ -1103,7 +1712,7 @@ This feature is called Webtools. It is also known as Extern
-
Preferences +
Preferences
General
Localisation You can select units displayed by &appname; to best fit your usage. @@ -1137,8 +1746,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 @@ -1159,7 +1768,7 @@ Generally if you have a system with lots of memory it's recommended to increase
-
Export/External +
Export/External
KML Export Units Allows setting the units used when saved as the KML file type, such as Metric or Statue units
@@ -1169,7 +1778,7 @@ Generally if you have a system with lots of memory it's recommended to increase 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 TrackWaypoint Layer -> Export Layer -> Open With 'program' +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) @@ -1178,9 +1787,9 @@ Generally if you have a system with lots of memory it's recommended to increase
-
OpenStreetMap Traces +
OpenStreetMap Traces
OSM Username + Password -Store your OSM details here, so that you don't need to enter it in every time in the Upload to OSM procedure. +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. @@ -1189,13 +1798,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. +
+
+
-
Mini-Howto's +
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 @@ -1231,12 +1877,12 @@ Use View and select from either -Method C +Method C 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 and/or Waypoints. +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: @@ -1269,22 +1915,21 @@ Use FileOpenFileAcquireImport File With GPSBabel... - - + -Expand Tracks or Waypoints. Right-click on the -track or waypoint of interest and select Goto "Center". +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. @@ -1293,13 +1938,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 @@ -1311,7 +1956,7 @@ the map. 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 Preferences. + You can also set the default location via specifing the exact latitude and longitude in the .
@@ -1319,7 +1964,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 @@ -1356,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). @@ -1384,13 +2029,13 @@ You can also alter the Min. and Max. elevation in this dialogue.
GPS Track with Height Profile -Uncheck the DEM layer (the map is shown again) +Uncheck the layer (the map is shown again) LayersNew TrackWaypoint Layer Ensure the new track layer is above the map layer. -Expand the TrackWaypoint layer, select Tracks -In the tools menu choose Begin Track +Expand the layer, select Tracks +In the tools menu choose Create Track Leftclick in the map window, enter a name @@ -1412,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. @@ -1425,7 +2070,7 @@ This allows you to delete the map stuff after holiday without purging the rest o check autodownload map keep viking zoom level zoom out to 1024 -add a DEM layer (as discussed above) +add a layer (as discussed above) download the DEM data In the &app; version discussed here, the DEM data automatically @@ -1463,6 +2108,9 @@ Do not forget to save your configuration (as discussed above). 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. @@ -1470,16 +2118,15 @@ 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, +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 -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. +Another solution is to upload an individual track. Simply select the track and right click on it. +Then select Upload to OSM. @@ -1490,11 +2137,12 @@ 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 tag. +The tags field is a white separated list of tags.
-
Downloading traces from OpenStreetMap + +
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. @@ -1508,17 +2156,27 @@ 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. -See for further detail.
+
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 map layer enabled for ease of use (if not see above to get one). + This assumes you already have a layer enabled for ease of use (if not see above to get one).
Manual Positioning @@ -1527,50 +2185,180 @@ See for fu ATM this process only works on an individual image, so it will be tedious for handling lots of images. - First create a Track Waypoint 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: - Select the New Waypoint tool, then left click on the map at the location desired, choosing an image to associate with it in the new waypoint dialog - Select the Select Tool, then left click on waypoint to be moved. Left click again and drag the waypoint to the 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. + 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 <trademark>Windows</trademark>) + + &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. -
- -
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! + Current Linux distributions should run gpsd automatically when a GPS Device is plugged in. Otherwise you may have to run gpsd manually. - Select the track either from the layers panel on the left or via the viewport using the Select Tool. - Then right click on it and chose the Geotag Images... leading you to the Geotagging Dialog. + Then right-click the layer and select Start Realtime Tracking. + Hopefully the viewport should jump to the GPS location. - 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. + Troubleshooting checklist: -Option: Overwrite Waypoints +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 - 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). +In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line: +viking -dV - - 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. +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 Currently, &app; has some extention points based on configuration files. The file format is heavily inspired by the GtkBuilder file format: you specify the class of the GObject to build and set its properties. Technically, it is a XML file containing a "objects" root element. Inside this element, you set a collection of "object". @@ -1592,7 +2380,7 @@ See for fu 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 @@ -1612,7 +2400,7 @@ See for fu - 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 @@ -1632,7 +2420,7 @@ See for fu - 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 @@ -1658,7 +2446,7 @@ See for fu Go-to search engines It 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: @@ -1694,144 +2482,219 @@ See for fu External tools It 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: + 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 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 engine 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") + 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=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. + + + + +
+
+
Dependencies gpsbabel