+
+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. Opens the Properties dialog on the tab. Note this will close the track list dialog.
+Copy Data. Copy the data fields as text.
+
+
+
+If multiple entries are selected the only right click option is Copy Data.
+This copies the individual data fields as plain text separated by tab characters, ideal for pasting into other applications in particular spreadsheet programs.
+Note that the order of the fields copied is the default column ordering (irrespective to how they may have been rearranged).
+
+
+
+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.
+You can also rearrange the columns via dragging the column header to the new location.
+
+
+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.
+Copy Data. Copy the data fields as text.
+
+
+
+If multiple entries are selected the only right click option is Copy Data.
+This copies the individual data fields as plain text separated by tab characters, ideal for pasting into other applications in particular spreadsheet programs.
+Note that the order of the fields copied is the default column ordering (irrespective to how they may have been rearranged).
+
+
+
+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.
+
+
+
+
+Search by Date
+
+This opens calendar dialog to select a date to search by within this Aggregate layer.
+The first item that is found on that date will be selected.
+Tracks are searched first in preference over waypoints.
+
+
+
+
+
+
+
+
+
+Coordinate Layer
+
+This layer is allows drawing of grid lines on the viewport.
+
+
+
+
+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, 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
+
+
+Ctrl-scroll: pan north-south (also Ctrl-up, Ctrl-down)
+
+
+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 +/-])
+
+
+Middle-click: make the clicked point on the map the center
+
+
+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.
+
+
+This mode can also be entered by the keyboard shortcut Ctrl+Shift+P
+
+
+Double clicking the left mouse button will zoom the map in.
+Shift + double clicking the left mouse button will zoom the map out.
+Double clicking the right mouse button will also zoom the map out.
+
+
+
+Zoom
+
+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
+
+
+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 + left click button: Jump Zoom In by up to factor of 3 standard zooms.
+
+
+Shift + right click button: Jump Zoom Out by up to factor of 3 standard zooms.
+
+
+
+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.
+
+
+This mode can also be entered by the keyboard shortcut Ctrl+Shift+U
+
+
+
+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.
+
+
+ATM to select a track one must actually click on a trackpoint, which is also selected.
+
+
+This mode can also be entered by the keyboard shortcut Ctrl+Shift+S
+
+
+
+TrackWaypoint Layer Tools
+
+You must have a Layer selected to use these tools.
+
+Create Waypoint
+
+Enable this tool by clicking on the toolbar icon:
+
+
+Left click will open the new waypoint dialog using the specified position.
+
+
+
+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: 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.
+
+
+One can switch between the Create Route and Route Finder tools while editing routes.
+
+
+
+Create Route Using the Route Finder
+
+Enable this tool by clicking on the toolbar icon:
+
+
+Requires an internet connection.
+Left click to create a new trackpoint.
+If it's the initial trackpoint you will be asked to enter a name for the route, otherwise the default routing engine will be queried to find a route to the new trackpoint.
+Right click or Backspace: remove the last added route.
+
+
+Escape: to finish route creation.
+Finishing the track is also available via the right click and track menus.
+
+
+One must finish the current route to be able to create another route.
+
+
+One can switch between the Create Route and Route Finder tools while editing routes.
+
+
+
+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.
+
+Right-click on waypoint: opens a menu with waypoint actions (the
+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.
+
+Edit Trackpoint Dialog
+
+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
+
+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
+
+
+
+
+
+Georef Map Layer 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.
+
+
+
+Georef move
+
+Enable this tool by clicking on the toolbar icon:
+
+
+Drag to move the georeferenced map.
+
+
+
+
+Map Download
+
+You must have a 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 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 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
+
+Many services are available only via a web browser (Google Maps, OpenStreetMap Potlach editor, etc.).
+
+
+Jumping from &app; to such service can become annoying.
+
+
+&appname; allows you to open such service directly at the position currently viewed in &app;.
+
+
+This feature is called Webtools. It is also known as External Tools.
+
+
+
+
+
+
+Preferences
+General
+Localisation
+You can select units displayed by &appname; to best fit your usage.
+
+Properties dialog: units part
+
+
+
+
+Concerning degrees, you can select the way to display them:
+
+
+DDDdecimal degree
+
+
+DMMpartial sexagesimal display: degrees, minutes and decimal part of minutes
+
+
+DMSsexagesimal display: degrees, minutes and seconds
+
+
+
+
+Properties dialog: degree display options
-Tile's age
-This age is used to decided wether or not a new request to tile server must be done.
+Waypoint Icon Size
+An option exists to control the icon (symbol) size used for waypoints
+
+
+<emphasis>Home</emphasis> Default Location: Latitude and Longitude
+You can set the Home location directly by inputting the latitude and longitude in decimal degrees.
+
+
+Time Display
+This controls the reference timezone that times are shown in.
+Locale is the current user's system preference. This was how all times were shown up to version 1.5.
+World will attempt to determine the timezone at an object's position.
+UTC enforces this standard timezone.
+
+Tile's age
+This age is used to decided wether or not a new request to tile server must be done.
+
+Changing this value, you will increase or decrese the network load.
+
+Default map layer directory
+This property sets the default directory of the tiles cache.
+This value is used when you create a new map layer.
+
+You are still able to change this value in each map layer properties.
+
+Map Cache Memory Size
+This controls the amount of maps that are stored in memory, rather than having to reread from disk.
+Generally if you have a system with lots of memory it's recommended to increase this value.
+
+
+
+
+Export/External
+KML Export Units
+Allows setting the units used when saved as the KML file type, such as Metric or Statue units
+
+GPX Track Order
+
+ Other software may display tracks in a particular order (often the order saved into the file).
+ This allows you to control the order they are saved when exporting to a GPX file.
+
+
+GPX Waypoint Symbols
+Some GPS devices require waypoint symbols to be in a particular case.
+E.g. On a Garmin Oregon 450 they must be in Title Case to be recognized.
+
+Image Viewer (Not Windows)
+Allows setting the program used to view images associated with Waypoints.
+By default this is set to xdg-open which should open the system's default image viewer, however this can be overridden with this setting.
+Note: for Windows systems, viewing images associated with Waypoints always uses the system's default image viewer.
+
+External GPX programs
+Allows setting the programs invoked via the Layer menu Export LayerOpen With 'program'
+Two options are given so that it can be configured for various uses such as:
+
+An OSM editor (default)
+Some other user defined program
+
+
+GPSBabel
+This allows setting the specific location of GPSBabel.
+&appname; will need to be restarted for this setting to take effect.
+
+Auto Read World Files
+If this is on, when a new image is selected for the GeoRef layer then the associated world file will be read to find the scale and positional properties.
+The associated file is based on filename patterns; e.g. if the image is filename.jpg - then the world file may be filename.jpgw or filename.jgw
+
+
+
+Advanced
+Save File Reference Mode
+
+ Files referenced within project files can be saved with either absolute or relative paths.
+ Using relative paths can be useful when copying the project file and the associated files between different systems.
-Changing this value, you will increase or decrese the network load.
-Default maplayer directory
-This property sets the default directory of the tiles cache.
-This value is used when you create a new map layer.
+Ask for Name before Track Creation
+A setting to control whether an automatic name is used when creating a new track or route, or whether you are asked to enter a name.
+
+Show Tooltip during Track Creation
+A setting to control whether the tooltip with the cumulative track or route distance is shown when creating tracks and routes.
+
+The number of recent files
+
+ The number of recent files shown in the FileOpen Recent File menu.
+ A value of -1 means all files. The new value applies to New Windows only (or on application restart).
-You are still able to change this value in each map layer properties.
-Mini-Howto's
-Getting Started
+
+OpenStreetMap Traces
+OSM Username + Password
+Store your OSM details here, so that you don't need to enter it in every time in the procedure.
+
+
+Your OSM password will be stored in plain text.
+
+
+
+
+
+Mapnik
+
+If any changes to these settings are made, you will need to restart &appname; to make them be applied.
+
+
+Plugins Directory
+The location of Mapnik plugins. An attempt is made to automatically determine the initial value,
+ however if this is wrong or Mapnik is upgraded then the directory can be set here.
+
+Fonts Directory
+
+The location of fonts for use with Mapnik. Normally it is best to simply use the System's font directory.
+
+
+Recurse Fonts Directory
+Load fonts in any sub-directories of the main font directory.
+
+Rerender Timeout
+The time in hours before any tile is rerendered.
+This is useful in case the underlying source data for the tiles changes (e.g. OSM data is continually evovling).
+ &appname; normally has no way of knowing when the data has changed, so this simple timeout method is provided to maintain consistency of the tile images.
+
+CartoCSS
+This allows setting the specific location of the carto executable.
+
+Threads
-To quickly get started using &appname;, follow these instructions.
+ The number of threads to use for Mapnik rendering tasks.
+ By default the value is set to the 1 in case of any multi-threading rendering code chain crashes.
+ Otherwise trying setting the value to the number of the CPUs of the system minus one (so as not to overload the system), in order to minimise the overall rendering times.
+
+
+
+
+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.
+
+
+
+Toolbar
+Append to Menu
+Allows setting the toolbar on the same vertical space as the menu, thus increasing vertical space for the map.
+
+Icon Size
+Allows configuration of the icon size, including overiding the system's default preference to the setting desired just for &appname;
+
+Icon Style
+Allows configuration of the icon style, including overiding the system's default preference to the setting desired just for &appname;
+
+Customize
+Opens the Customize Toolbar dialog.
+From this dialog the items in the toolbar can be added, removed and reordered. Reordering of items is performed by drag and drop.
+
+Customize Toolbar dialog
+
+
+
+
+
+
+
+
+
+
+Howto's
+Getting Started
+
+&appname; from version 1.5 has several features to ease the start up process.
+On the very first run, you will be asked if you want to enable these features which make use of an Internet connection.
+If you select no or you have upgraded from an earlier version you can choose to enable any of the startup options via the .
+
+
+Some other general use cases for using &appname;, are as follows:
Go to an area of interest
-&appname;'s default location is a Manhatten, New York, USA, so you may need to pick another place that interests you.
+&appname;'s default location is a Manhatten, New York, USA, so you may need to pick another place that interests you - such as where you live.
Method A
-Use View - Go to to move to a coordinate of interest.
+ Use the online location address/place search.
-
-
-
-Method B
-
-Use the GPS Layer or FileAcquireFrom GPS
-to load data directly from your GPS into &appname;.
-Currently Garmin, Magellan, DeLorme and Navilink protocols are supported.
+
+ Use the Go to Location toolbar button or from the menus
+ ViewGo to Location.
+ You can change the search location provider if desired.
+ Enter the name of place you wish to go to (you may need to specify the country to refine the search).
+ Also you can enter a post code or a ZIP code instead.
-You must have write permission to the port used. For Unix like OS:
-/dev/ttyS0 is the first serial port
-/dev/ttyUSB0 is the first USB port
+ You will need an internet connection for this search to work
-For DeLorme device support you will need GPSBabel v1.4.0+ installed
-Method C
+Method B
-Get data from files in GPX format. For other formats (kml,
-ozi...), use a converter such as GPSBabel to convert the files to GPX
-format first.
+
+ If you know the coordinates of where you want to view:
-
-
-Open up &appname; and use File - Open or File - Append
-file to open the file.
+Use View and select from either Go to Lat/Lon or Go to UTM and then enter in the specific coordinates.
+
+
+Method C
-
-Expand Tracks or Waypoints. Right-click on the
-track or waypoint of interest and select Goto "Center".
+Use the GPS Layer or FileAcquireFrom GPS
+to load data directly from your GPS into &appname;.
+You can specify the types of data to acquire: Tracks, Routes and/or Waypoints.
+
+
+You must have write permission to the port used. For Unix like OS:
+
+ /dev/ttyS0 is the first serial port
+ /dev/ttyUSB0 is the first USB port
+ usb: is any USB port
+
+Depending on your distribution only one of the USB port types may work
+For Windows:
+
+ com1: is the first serial port
+ usb: is any USB port
+
+
+
+ The GPS devices supported are those supported by GPSBabel.
+ Garmin and Magellan GPS devices supported by all versions, later versions of GPSBabel support more devices such as DeLorme and Navilink.
+Method D
-Use File - Append File to add your track and waypoint data to
-&appname;. This has been tested with Geocaching.com's *.loc format,
-(others(?)).
+Get data from files in GPX or KML format, which can be opened directly.
+Use FileOpen
-
-
-Expand Tracks or Waypoints. Right-click on the tack or
-point of interest and select Goto "Center".
+Other formats can be imported that are supported by GPSBabel.
+FileAcquireImport File With GPSBabel...
+
+
+
+The viewport will be automatically moved and resized to view the contents of the file.
+
-Add a map layer
+Add a Map Layer
-1. Use Layers - New Map Layer, and choose a suitable cache directory
+Use LayersNew Map Layer, and choose a suitable cache directory
where you would like to store your tracks and click OK. Zoom to a
comfortable level (I suggest 4 mpp) by clicking the left and right
mouse buttons on the gray area where your tracks are. Now from the menu
-choose Tools - Map Download, Click where you would like to download a
+choose the Tool. Click where you would like to download a
map. Regardless of what tool you are using, the middle mouse button
always pans.
@@ -1048,23 +2550,34 @@ You need an open internet connection when you are downloading maps.
-1. You will notice the maps are being drawn on top of the tracks, which
-is probably not what you want. Look at the Layers Panel to the left.
-Notice how the layer named Map is ABOVE your TrackWaypoint layer that
-your GPS data is in. This means that it will be drawn last, or on top
-of the other layers. Select the Map layer from the list and click the
-down arrow button beneath the list. Your tracks will now be drawn over
-the map.
+If you can no longer see your tracks or waypoints and only the map,
+it is because the layer named Map is ABOVE your TrackWaypoint layer that your GPS data is in.
+This means that it will be drawn last and on top of the other .
+Look at the to the left which shows this order.
+Select the Map layer from the list and click the down arrow button beneath the list until the Map layer is below the TrackWaypoint layer.
+Your tracks will now be drawn over the map.
+
+
+Set Your Home Location
+
+ You can save the current center position of the viewport as the default location AKA the Home Location by
+ EditSet the Default Location.
+
+
+ Then at any time you can return to this place by clicking on the Home icon on the toolbar.
+
+
+ You can also set the default location via specifing the exact latitude and longitude in the .
+From 1st startup to GPS track (including offline maps)
The first you'll see is an empty map, because &appname; in its default configuration will download maps only on demand.
-Before fetching unneeded data, one can position to a location of interest, e.g. Stuttgart: ViewGo to Location, enter 'Stuttgart'.
+Before fetching unneeded data, one can position to a location of interest, e.g. Stuttgart: ViewGo to Location, enter Stuttgart.
-
Fetching the mapsMap
@@ -1088,7 +2601,7 @@ role in the pre-fetch for offline usage discussed later
You'll see a map of Stuttgart. Using the mouse wheel, you can
-zoom in and out. The maps for the choosen resoltion will be downloaded
+zoom in and out. The maps for the choosen resolution will be downloaded
automatically.
@@ -1100,7 +2613,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).
@@ -1128,30 +2641,22 @@ You can also alter the Min. and Max. elevation in this dialogue.
GPS Track with Height Profile
-uncheck the DEM layer (the map show up again)
-LayersNew TrackWaypoint Layer
-
-
-Ensure the new track layer is above the map layer.
-
-
-expand trackwaypointlayer, select Tracks
+Uncheck the layer (the map is shown again)
-
-in the tools menu choose Begin Track which looks like this:
-
-Begin Track Icon
-
-
-
-
+ LayersNew TrackWaypoint Layer
+ Ensure the new track layer is above the map layer.
+
+Expand the layer, select Tracks
+In the tools menu choose Create Track
-leftclick in the map window, enter a name
-click several times to generate a track (a right-click removes the last point)
-expand tracks in the layer menu, your track should show up, select it
-right click your track, select Apply DEM data
-right click your track again, select Properies
-click the tab Elevation-distance - enjoy the plot
+Leftclick in the map window, enter a name
+
+ Click several times to generate a track (a right-click removes the last point).
+ Height data is set automatically since DEM data is available
+
+Expand tracks in the layer menu, your track should show up, select it
+Right click your track, select Properties
+Click the tab Elevation-distance - enjoy the plot
In order to save this setting for later usage
@@ -1164,7 +2669,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.
@@ -1177,7 +2682,7 @@ This allows you to delete the map stuff after holiday without purging the rest o
check autodownload mapkeep viking zoom levelzoom out to 1024
-add a DEM layer (as discussed above)
+add a layer (as discussed above)download the DEM dataIn the &app; version discussed here, the DEM data automatically
@@ -1201,10 +2706,7 @@ tiles into .viking-map-holiday/ if you like.
-This may take some time and hd capacity. Lixus wrote a set of
-scripts which allow to download the map tiles for several zoom-level in
-parallel from the command line.
-
+This may take some time and some hard disk capacity.
Do not forget to save your configuration (as discussed above).
@@ -1218,6 +2720,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.
@@ -1225,16 +2730,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.
@@ -1245,11 +2749,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.
@@ -1263,66 +2768,209 @@ 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 layer enabled for ease of use (if not see above to get one).
+
+Manual Positioning
+
+ This is useful for instances when you already know exactly where the image was taken (no need for tracklog).
+ Or maybe you want to adjust an automatically generated waypoint for the position of the subject of the image rather than the location that the photograph is taken from.
+ ATM this process only works on an individual image, so it will be tedious for handling lots of images.
+
+
+ First create a layer or use an existing one; and select it in the .
+ NB Make sure this layer is above the map layer in the Layers Panel list.
+ Create a new waypoint (or move an existing one) to exact location desired:
+
+ Select the tool, then left click on the map at the location desired, choosing an image to associate with it in the new waypoint dialog
+ Select the tool, then left click on waypoint to be moved. Left click again and drag the waypoint to the location desired
+
+ Then using the Select tool left click on waypoint to select it, then right click to access the Waypoint properties menu, then choose
+ Update Geotag on ImageUpdate
+
+
+ The Update Geotag on Image options are only available when a waypoint has an image associated with it.
+
+
+
+Automatic Positioning Against a Tracklog
+
+ First you will need a tracklog with timestamps in it. Either load one from a previously saved file or freshly acquired from a GPS device -
+ see Getting Started.
+ It helps if this is the track that was recorded at the time you took some photographs!
+
+
+ Select the track either from the layers panel on the left or via the viewport using the tool.
+ Then right click on it and chose the Geotag Images... leading you to the Dialog.
+
+
+ Load some images that where taken around the time the track log was recorded. Confirm the other options in the dialog - normally the defaults should be alright and select OK.
+ If things are succesful, new waypoints with thumbnail images of the photographs will appear.
+ You should probably check they are really in the right place as often the timestamp of the camera may not be aligned to the GPS correctly leading to inferring incorrect locations.
+
+Option: Overwrite Waypoints
+
+ This is particularly useful when one finds an attempt at geotagging gives wrong locations, often due to time offset issues.
+ Simply try again with a new time offset (often 1 hour adjustments due to Daylight Savings or Summer Time times) and the old waypoints will be updated (instead of creating new ones).
+
+
+
+ If you have multiple tracks in a TrackWaypoint layer, then invoking the Geotag Images... action on the layer
+ will search all the tracks to find location matches.
+
+
+
+
+GPS Real Time Location (Not <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.
+
+
+ Current Linux distributions should run gpsd automatically when a GPS Device is plugged in. Otherwise you may have to run gpsd manually.
+
+
+ Then right-click the layer and select Start Realtime Tracking.
+ Hopefully the viewport should jump to the GPS location.
+
+
+ Troubleshooting checklist:
+
+Confirm gpsd is running.
+Confirm on the GPS device it has a location.
+Confirm the Realtime Tracking Mode settings.
+
+
+
+What to Do if &appname; Does Not Seem to Work
+
+In order to get some information about what &appname; is doing, start it in verbose debug mode via the command line:
+viking -dV
+
+
+For instance you can check the correct URLs &appname; is using in requesting remote data for DEMs or map tiles in the verbose debug output.
+E.g. Something like this for DEMs:
+
+** (viking:28778): DEBUG: curl_download_uri: uri=http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip
+* About to connect() to dds.cr.usgs.gov port 80 (#0)
+* Trying 152.61.128.95... * connected
+* Connected to dds.cr.usgs.gov (152.61.128.95) port 80 (#0)
+ GET /srtm/version2_1/SRTM3/Eurasia/N48E008.hgt.zip HTTP/1.1
+User-Agent: viking/0.9.8 libcurl/7.18.2 GnuTLS/2.4.2 zlib/1.2.3.3 libidn/1.8
+Host: dds.cr.usgs.gov
+Accept: */*
+ HTTP/1.1 200 OK
+ Date: Sun, 26 Jul 2009 18:13:38 GMT
+ Server: Apache
+ Last-Modified: Tue, 21 Jul 2009 19:57:35 GMT
+ ETag: eac3f8-1828f5-46f3caa76070a
+ Accept-Ranges: bytes
+ Content-Length: 1583349
+ Content-Type: application/zip
+
+* Connection #0 to host dds.cr.usgs.gov left intact
+* Closing connection #0
+** (viking:28778): DEBUG: dem_layer_add_file: /home/username/.viking-maps/srtm3-Eurasia/N48E008.hgt.zip
+
+Or for OSM Mapnik tile server:
+
+* About to connect() to tile.openstreetmap.org port 80 (#0)
+* Trying 193.63.75.28... * connected
+* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
+ GET /13/4065/2748.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: tile.openstreetmap.org
+Accept: */*
+
+* HTTP 1.0, assume close after body
+ HTTP/1.0 200 OK
+ Date: Thu, 14 Oct 2010 22:18:42 GMT
+ Server: Apache/2.2.8 (Ubuntu)
+ ETag: "b66ff9d46474bab68262a3483428a232"
+** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "b66ff9d46474bab68262a3483428a232"
+ Content-Length: 17194
+ Cache-Control: max-age=94805
+ Expires: Sat, 16 Oct 2010 00:38:47 GMT
+ Content-Type: image/png
+ Age: 5153
+ X-Cache: HIT from konqi.openstreetmap.org
+ X-Cache-Lookup: HIT from konqi.openstreetmap.org:3128
+ Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
+ Connection: close
+
+* Closing connection #0
+* About to connect() to a.andy.sandbox.cloudmade.com port 80 (#0)
+* Trying 178.63.75.195... ** (viking:16704): DEBUG: curl_download_uri: uri=http://tile.openstreetmap.org/13/4065/2749.png
+* About to connect() to tile.openstreetmap.org port 80 (#0)
+* Trying 193.63.75.28... * connected
+* Connected to a.andy.sandbox.cloudmade.com (178.63.75.195) port 80 (#0)
+ GET /tiles/cycle/13/4065/2747.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: a.andy.sandbox.cloudmade.com
+Accept: */*
+
+* connected
+* Connected to tile.openstreetmap.org (193.63.75.28) port 80 (#0)
+ GET /13/4065/2749.png HTTP/1.1
+User-Agent: viking/0.9.96 libcurl/7.20.1 GnuTLS/2.8.6 zlib/1.2.3.4 libidn/1.18
+Host: tile.openstreetmap.org
+Accept: */*
+
+* HTTP 1.0, assume close after body
+ HTTP/1.0 200 OK
+ Date: Thu, 14 Oct 2010 23:44:35 GMT
+ Server: Apache/2.2.8 (Ubuntu)
+ ETag: "8e520ad47ce9c1b63430554886eb5fab"
+** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
+ Content-Length: 18094
+ Cache-Control: max-age=87742
+ Expires: Sat, 16 Oct 2010 00:06:57 GMT
+ Content-Type: image/png
+ X-Cache: MISS from konqi.openstreetmap.org
+ X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
+ Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
+ Connection: close
+
+
-Geocoded Photo
-
-HOWTO GEOCODE YOUR PHOTOS AND SEE THEM IN VIKING
-
-1) Synchronize your camera's clock with your GPS clock. If your
-camera's clock doesn't have a seconds value you can change, you might
-try setting the minute value just when the minute changes.
-
-
-2) Activate the track log on your GPS.
-
-3) Get outside and take some pictures with your camera while
-making sure your GPS has reception. If you forgot to turn your GPS on
-or forgot to bring it when you took a picture but you know where you
-took the picture, you can make a waypoint with a name of the format
-YYMMDDhhmm, representing the time the picture was taken, to record
-where you were at that time.
-
-4) Get home and download your pictures and GPS data. You can
-download the GPS data several ways. The first is using gpspoint to
-download from a Garmin GPS: gpspoint -p /dev/ttyS0 -dw -dt -of 2004-04-02-trip1
-
-
-Where /dev/ttyS0 is the serial port the GPS is connected to. If you
-don't have a Garmin GPS, or if you don't feel like install gpspoint,
-you can use my version of gpsbabel with support for gpspoint files. You
-can use gpsbabel to either translate the GPS data from a format you
-already have the data in or download it directly from your GPS
-reciever. A typical command line would something like this:gpsbabel -i garmin -f /dev/ttyS0 -o gpspoint -F 2004-04-02-trip1
-
-
-5) Launch GPSPhoto.
-
-
-6) You must now bring your photos into GPSPhoto. Either drag them (or
-the directory containing them) from your favorite file manager to the
-list on the left of the GPSPhoto window, or use the buttons below the
-list to find them.
-
-
-7) Do the same for your GPS data file(s), dragging them to the list on the right of the GPSPhoto Window.
-
-8) Click the Execute button, and choose a location to save the
-gpspoint file containing the waypoints for your photos. Then click OK
-to write the waypoints to this file.
-
-
-9) Open Viking and open both your original GPS data file and your image waypoint file just created.
-
+
-
+Extending VikingCurrently, &app; has some extention points based on configuration files. The file format is heavily inspired by the GtkBuilder file format: you specify the class of the GObject to build and set its properties. Technically, it is a XML file containing a "objects" root element. Inside this element, you set a collection of "object".
@@ -1339,17 +2987,21 @@ to write the waypoints to this file.
You can find more examples in the documentation part of the distribution.
-
+ Map Source
- It is possible to add new map's sources. The file is ~/.viking/maps.xml for UNIX like systems and C:\Documents and Settings\username\.viking\maps.xml on Windows XP.
+ It is possible to add new map's sources. The file is ~/.viking/maps.xml for UNIX like systems, C:\Documents and Settings\username\.viking\maps.xml on Windows XP or C:\Users\username\.viking\maps.xml on Windows 7 onwards.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:
idthis is an integer and should be unique as it used to identify the map source
+
+ name
+ a string (should be unique) that is used for the OSM style cache directory name when the Map Cache directory is the default (~/.viking-maps)
+ labelthe text displayed in the map's source selection dialog
@@ -1360,47 +3012,148 @@ to write the waypoints to this file.
url
- the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for X, Y and Z (zoom level) (eg. "/%d/%d/%d.png")
+ the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for Z, X and Y (in that order) (eg. "/%d/%d/%d.png")
+
+
+ zoom-min (optional)
+ The minimum zoom value supported by the tile server. The Default is 0 if not specified.
+
+
+ zoom-max (optional)
+
+ The maximum zoom value supported by the tile server. The Default is 18 if not specified.
+ See Zoom Levels
+
+
+
+ lat-min (optional)
+ The minimum latitude value in degrees supported by the tile server. The Default is -90 degrees if not specified.
+
+
+ lat-max (optional)
+ The maximum latitude value in degrees supported by the tile server. The Default is 90 degrees if not specified.
+
+
+ lon-min (optional)
+ The minimum longitude value in degrees supported by the tile server. The Default is -180 degrees if not specified.
+
+
+ lon-max (optional)
+ The maximum longitude value in degrees supported by the tile server. The Default is 180 degrees if not specified.
+
+
+ file-extension (optional)
+
+ The file extension of the files on disk. The default is .png
+ If the tile source URL ends in something other than .png, then this parameter will need to match it.
+ This can also be useful in reading a tileset from other software which may name tiles in an alternative form,
+ e.g. for Mobile Atlas creator it names them .png.tile
+ The file types actually usable are those supported by GDK Pixbuf Library, which includes at least PNG and JPEG.
+ Remember to include the beginning '.' when specifying this parameter.
+
+
+
+ use-direct-file-access (optional)
+
+ Only use files on disk. The default is FALSE
+ This can also be useful for tilesets already on disk as it will avoid attempting to download any tiles.
+ Thus with this type the hostname and url parameters are not necessary and are ignored.
+
+
+
+ switch-xy (optional)
+
+ Swap the X,Y values around in the URL parametrized ordering.
+ The default is false.
+
+
+
+ check-file-server-time (optional)
+
+ Sends the timestamp of the tile to the server, so the server can decide whether it should send a new tile or not.
+ The default is false.
+
+
+
+ use-etag (optional)
+
+ Use and compare the ETag value in determining whether to download a newer tile. The default is false.
+ The ETag value is stored in a separate file in the same directory as the tile to enable checking the value across multiple runs of the program.
+
- 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 (as per VikSlippyMapSource above):
- id
- this is an integer and should be unique as it used to identify the map source
+ id
- label
- the text displayed in the map's source selection dialog
+ label
- hostname
- the server's hostname (eg. "tile.openstreetmap.org")
+ hostname
- url
- the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for X, Y and Z (zoom level) (eg. "/%d/%d/%d.png")
+ url
+
+
+ check-file-server-time (optional)
+
+
+ zoom-min (optional)
+
+
+ zoom-max (optional)
+
+
+ lat-min (optional)
+
+
+ lat-max (optional)
+
+
+ lon-min (optional)
+
+
+ lon-max (optional)
- 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 (as per VikSlippyMapSource above):
- id
- this is an integer and should be unique as it used to identify the map source
+ id
- label
- the text displayed in the map's source selection dialog
+ label
- hostname
- the server's hostname (eg. "tile.openstreetmap.org")
+ hostname
- url
- the parametrized address of the tile, in the spirit of C printf format, with 4 "%s" fields for bounding box coordinates (eg. "/coord=%s,%s,%s,%s")
+ url
+
+
+ check-file-server-time (optional)
+
+
+ zoom-min (optional)
+
+
+ zoom-max (optional)
+
+
+ lat-min (optional)
+
+
+ lat-max (optional)
+
+
+ lon-min (optional)
+
+
+ lon-max (optional)
@@ -1410,7 +3163,7 @@ to write the waypoints to this file.
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:
@@ -1443,131 +3196,300 @@ to write the waypoints to this file.
- Webtools
+ External toolsIt is possible to add new external tools. The file is ~/.viking/external_tools.xml.An example of the file in the distribution doc/examples/external_tools.xml.
- Currently, there is a single object class available: VikWebtoolCenter. Such feature allows to declare any Webtool using a logic based on center coordinates and zoom level value.
+ The VikWebtoolCenter allows to declare any Webtool using a logic based on center coordinates and zoom level value.
+ The related properties are:
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url
+ the parametrized URL to open, in the spirit of C printf format, with 2 "%s" and a "%d" fields for X, Y and Z (zoom level) (eg. "http://hostname/?lat=%s&lon=%s&zoom=%d")
+
+
+
+ The VikWebtoolBounds allows to declare any Webtool using a logic based on bounds coordinates.
+ The related properties are:
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url
+ the parametrized address of the tile, in the spirit of C printf format, with 4 "%s" fields for left, right, bottom and top (eg. "http://hostname:8111/load_and_zoom?left=%s&right=%s&bottom=%s&top=%s")
+
+
+
+
+
+
+ Routing engine
+ It is possible to declare new routing engines. The file is ~/.viking/routing.xml.
+ An example of the file in the distribution doc/examples/routing.xml.
+ The VikRoutingWebEngine allows to declare a routing engine available via HTTP.The related properties are:
id
- this is an integer and should be unique as it used to identify the tool
+ a string, should be unique as it used to identify the routing engine
+
+
+ label
+ the text displayed in the menu entry
+
+
+ url-base
+ the base URL of the web service (eg. "http://hostname/service?")
+
+
+ url-start-ll
+ the part of the URL setting the starting point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&start=%s,%s")
+
+ url-stop-ll
+ the part of the URL setting the end point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&stop=%s,%s")
+
+
+ url-via-ll
+ the part of the URL setting via point location, parametrized in the spirit of C printf format, with 2 "%s" for coordinates (eg. "&via=%s,%s")
+
+
+ url-start-dir
+ the part of the URL setting the starting point location for direction based routing, parametrized in the spirit of C printf format, with one "%s" for direction (eg. "&start=%s")
+ (Optional)
+
+
+ url-stop-dir
+ the part of the URL setting the end point location for direction based routing, parametrized in the spirit of C printf format, with one "%s" for direction (eg. "&start=%s")
+ (Optional)
+
+
+ referer
+ an URL to serve as referer for the HTTP request (eg. "http://hostname/")
+
+
+ follow-location
+ the max depth of recursive redirections
+
+
+
+
+
+
+ Remote File Datasources
+ It is possible to add web references expected to return a file which can then be opened directly or converted via GPSBabel.
+ The file is ~/.viking/datasources.xml.
+ An example of the file is in the source distribution doc/examples/datasources.xml.
+ The VikWebtoolDatasource allows to declare any URL using logic based on coordinates.
+ The related properties are:
+ labelthe text displayed in the menu entryurl
- the parametrized address of the tile, in the spirit of C printf format, with 3 "%d" fields for X, Y and Z (zoom level) (eg. "http://hostname/%d/%d/%d.png")
+
+ the parametrized URL to open in the spirit of C printf format, with up to 9 "%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
+ P = selected Point's latitude
+ N = selected poiNt's longitude
+ S = A user specified input string requested from the user via a dialog box
+ 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.
+
+
+
+ babel_filter_args
+
+ This value is passed on for the filter arguments interfacing with GPSBabel.
+ E.g. "-x nuketypes,routes" can be used to filter all routes from the results.
+
+
+
+ input_label
+
+ This value is used when requesting input from the user.
+ It is the label of the text input box.
+
-
+
+ More
+ Note that, on UNIX like systems, the extension files (maps.xml, goto_tools.xml, external_tools.xml, datasources.xml) are also searched in /etc/viking and /usr/share/viking directories (or related in your system).
+ The XDG_DATA_DIRS environment variable can be used to change these directories.
+ The XDG_DATA_HOME environment variable is also used (if set) to look for these extension files.
+
-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: */*
+
+ 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.
+
+
+ layers_create_trw_auto_default=false
+ Create new TrackWaypoint layers without showing the layer properties dialog first.
+
+
+ maps_max_tiles=1000
+
+
+ maps_min_shrinkfactor=0.0312499
+
+
+ maps_max_shrinkfactor=8.0000001
+
+
+ maps_real_min_shrinkfactor=0.0039062499
+
+
+ maps_scale_inc_down=4
+
+
+ maps_scale_inc_up=2
+
+
+ maps_scale_smaller_zoom_first=true
+
+
+ mapnik_buffer_size=128 (in pixels)
+
+
+ background_max_threads=10
+
+
+ background_max_threads_local=Number of CPUs
+
+
+ window_menubar=true
+
+
+ window_copy_centre_full_format=false
+
+
+ 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
+
+
+ utils_nearest_tz_factor=1.0
+
+
+ viewport_history_size=20
+
+
+ viewport_history_diff_dist=500
+ In metres.
+
+ Go Back or Go Forward requests over this range from the last history location will move back to that position.
+ If within this range it will skip over this location and move on to the next saved history location.
+
+
+
+ external_diary_program=rednotebook
+ Or in Windows it uses C:/Progra~1/Rednotebook/rednotebook.exe - This string value must use Unix separators and not have spaces.
+
+
+ external_astro_program=stellarium
+ Or in Windows use C:/Progra~1/Stellarium/stellarium.exe - This string value must use Unix separators and not have spaces.
+ Further note due to this Bug in Stellarium means this does not actually work. You will need to reference a shortcut, rather than the executable directly.
+
+
+
+
+ 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
+ B = Vertical Speed (Climb)
+ 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)
+ F = Distance of the trackpoint from the finish (end) 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.
+
+
+
+
+
-* 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: */*
+
+ Keyboard Shortcuts (Accelerator) Settings
+ This is held in the file ~/.viking/keys.rc
+ It is in the standard GTK Accelerator map format. Values are automatically read in and saved between &app; sessions.
+ This file is not intended to be manually edited, but since it is a plain text file it can be changed if desired.
+
-* HTTP 1.0, assume close after body
- HTTP/1.0 200 OK
- Date: Thu, 14 Oct 2010 23:44:35 GMT
- Server: Apache/2.2.8 (Ubuntu)
- ETag: "8e520ad47ce9c1b63430554886eb5fab"
-** (viking:16704): DEBUG: curl_get_etag_func: ETAG found: "8e520ad47ce9c1b63430554886eb5fab"
- Content-Length: 18094
- Cache-Control: max-age=87742
- Expires: Sat, 16 Oct 2010 00:06:57 GMT
- Content-Type: image/png
- X-Cache: MISS from konqi.openstreetmap.org
- X-Cache-Lookup: MISS from konqi.openstreetmap.org:3128
- Via: 1.1 konqi.openstreetmap.org:3128 (squid/2.7.STABLE7)
- Connection: close
-
-
+
-
+
-Dependencies
-gpsbabel
-&appname; uses GPSBabel to convert data.
-
-unbuffer (optional)
-&appname; uses unbuffer command to optimize conversion calls.
-
-
+
+
+