Activity for Viking GPS data editor and analyzer
-
Andrew Hobbs posted a comment on discussion General Discussion
I am interested in being able to access the data, in particular the time stamp, for each individual point on a track. This allows me to determine when I was at a particular point. Is that available. I can't seem to find it if it is available. Cheers Andrew
-
Stephen Meatheringham posted a comment on discussion General Discussion
Well. I am guessing that it is just me having the problem as no one has replied.
-
Good Morning I wonder if it is just me, or are other users of Viking having problems with DEM downloads? I am running Viking 1.10 under Manjaro Linux. If I create a DEM layer and click on "DEM Download" I receive the following error: Warning curl_download_uri: http response: 404 for uri https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL1.003/2000.02.11/S36E148.SRTMGL1.hgt.zip Indeed, the MEASURES directory on e4ftl01.cr.usgs.gov in blank. Perhaps this is some restriction the US Government have placed on...
-
Rob Norris modified a wiki page
Main_Page
-
Version 1.11
-
MasterHelp
-
Rounding issue in test/check_parse_latlon.sh on i386
-
Small waypoint symbols are used instead of the large ones
-
Viking 1.11 - Released - 2026-01-11
-
Viking 1.11 - Released - 2026-01-11
-
Red, yellow, and green squares, showing cache state
-
Ability to rotate a GeoRef layer
-
GeoRef layer rotation support has now been added to the latest source code. NB1 Note that this rotation support is specific for GeoRef layers, rather than a general display rotation as mentioned by @Rick Bragg above. NB2 I'm not a great fan of map rotation for direction of travel, although it is possible for the future. The main downside of map rotation is that Viking currently only uses raster maps, which normally have the text labels of places horizontally aligned, thus when rotated it makes the...
-
Viking 1.11 - Released - 2026-01-11
-
Viking GPS data editor and analyzer updated /VERSION
-
Developers
-
-
-
-
-
-
-
-
-
-
-
-
Releasing Viking 1.11
-
Merge branch 'masterGithub'
-
GitHub committed [71f5c3] on Code
Merge pull request #347 from goeranu/master
-
Göran Uddeborg committed [5958bd] on Code
Style adjustments of comments.
-
Use Wayland-safe pixbuf retrieval in print-preview:get_thumbnail
-
Fix printing on Wayland
-
Releasing Viking 1.11
-
[WINDOWS] further support for build under 'osc'
-
Switch back to OSM Mapnik for default map tiles
-
[WINDOWS] Installer: prefer https
-
Flatpak: upgrade runtime to KDE 5.15-24.08
-
Flatpak: Various small improvements
-
Specific disallow of OSM bulk downloading
-
Explicitly ignore returned value from g_array_free() and whitespace tidy.
-
Fit memory leak in fit.c
-
Fix memory leak after maps_layer_register_map_source() usage.
-
Cross platform build fixes/improvements.
-
New (slightly experimental) trackpoint insert option in Track Edit tool
-
Allow changing which tab is shown by default for properties.
-
Improve trackpoint interpolation to consider extended properties.
-
Further GTK2 (GDK2) deprecations
-
[QA] Small indentation fix
-
Mark returned function value as deliberately unused.
-
Rename variable after functionality
-
Fix crashing on Reload when something is already selected.
-
Make everything https where possible.
-
Ensure default GTK3 scrollbar overlay is disabled on property dialogs
-
Github #345: Remove maths functions from AC_CHECK_FUNCS
-
Remove signal name (accidentally) being marked for translation.
-
Improve startup failure messages.
-
Use mkdir with parent function to ensure directory creation.
-
Flatpak: Upgrade dependencies
-
Github #327: Fix .vik test, as revised default ordering of waypoint properties in .vik file
-
Merge remote-tracking branch 'origin/master' into masterGithub
-
GitHub committed [b98e55] on Code
Merge pull request #329 from guyou/fix-devcontainer
-
Guilhem BONNEFILLE committed [71a3d4] on Code
fix: no more needed to set network
-
T4d3o posted a comment on ticket #51
Hi Guillaume. I was able to fix this error in the following way (it's a bit messy but it works) Download compiled curl for your windows version, find libcurl.dll in zip, copy to your viking installation folder, in this folder rename libcurl-4.dll to libcurl-4.dll.bck (also you can delete but I prefer backup) change your copied libcurl.dll to libcurl-4.dll after that, you can able download map files, dem... etc
-
Small waypoint symbols are used instead of the large ones
-
Fix spin button initialisation
-
[QA] Fix layer parameter union initialisation
-
Allow more Track List dialog columns to be reorderable.
-
Extend date based rename to work on TrackWaypoint layers.
-
Printing improvements: Mainly to report any errors rather than silently ignoring them
-
Github #336: Allow changing Paper size and Orientation on Page Setup tab.
-
Github #337: Ensure print preview has GTK3 implementation
-
SF Bugs#171: Fix loading large waypoint symbols.
-
Add aggregate layer option to load external files on Viking file load
-
[QA] Use const variables in heatmap calculations.
-
TAC: Cache results from previous calculation and use for quick redraw
-
Add ability to export TRW sublayers as separate GPX files.
-
Github #327: Part 2: Revised Waypoint properties.
-
Github #339: Change default download setting to follow all redirects
-
Enable clearing the message log via middle click without opening the dialog
-
Github #327: Part 1: Support new UI layout builder widget option of a 'separator'.
-
Add separator around delete tile menu entry
-
For multi-track statistics, monitor on which track they occur and show as a tooltip.
-
Add method to allow deletion of multiple layer items from an aggregate layer
-
Github #317: Ensure Default Layers dialog updates widget sensitivities
-
Configure fails because C++17 is required for mapnik and boost
-
Elevation is notoriously difficult to get reliable answers. Feeding tracks/planning routes with various services Strava, Garmin, OpenRunner. etc.. vs device itself often give differing values - although generally turn out to be roughly in the same ball park (depending how big you think a ball park should be). Viking literally (attempts to**) sums up the difference using every single point - so it is: a) Susceptible to individual data 'rogue' points - that would lead to overall high values. b) General...
-
rooots posted a comment on ticket #172
Hmm...agreed, that looks pretty open according to satellite images. Well...it was just a guess... ;-)
-
Matthias Kaehlcke posted a comment on ticket #172
Most of my hikes are mixed terrain, some forest covered areas and open alpine terrain. The attached track is from primarily open terrain as far as I recall. Viking reports a total elevation gain of 1077m, Garmin Connect says it was 858m. A similar delta as for the first track, which was more mixed terrain.
-
Just a guess: could it be that the difference originates from Viking only using GPS data of the track to calculate vertical gain, while Garmin also uses barometric data to correct for GPS inaccuracies? That would also explain why in my first example, recorded mostly in forest, the relative difference is a lot larger, while with the second example, recorded in open alpine terrain, it is just a couple of %. Do you have tracks recorded under such different conditions as well?
-
Just a guess: could it be that the difference originates from Viking only using GPX data of the track to calculate vertical gain, while Garmin also uses barometric data to correct for GPS inaccuracies? That would also explain why in my first example, recorded mostly in forest, the relative difference is a lot larger, while with the second example, recorded in open alpine terrain, it is just a couple of %. Do you have tracks recorded under such different conditions as well?
-
Thanks for looking into this! What device are you using? It's a Fenix 6.
-
I can confirm this, just compared some recent and old tracks and got for example, 417 vs. 292m and 1701 vs. 1593m. What device are you using? Mine are FR965 and 970. Until some while ago, I only used to see this when using "Apply DEM Data" to a track, where the total elevation gain would also depend on the density of trackpoints, even if neighbouring trackpoints were shown to have the same DEM altitude.
-
I can confirm this, just compared some recent and old tracks and got for example, 417 vs. 292m and 1701 vs. 1593m. What device are you using? Mine is FR965 and 970. Until some while ago, I only used to see this when using "Apply DEM Data" to a track, where the total elevation gain would also depend on the density of trackpoints, even if neighbouring trackpoints were shown to have the same DEM altitude.
-
Statistics report too high elevation gain
-
Oops, I appear to have broken it v1.9 (in commit SHA:031b138e0796ec3631d87cb4c736c26cdaae4d66) A fix will be applied to the latest source code in due course.
-
Aubiwan Kenobi created ticket #166
port Viking on aarch (Arm architecture)
-
P. Sonic created ticket #171
Small waypoint symbols are used instead of the large ones
-
Jean-Francois Moulin posted a comment on discussion General Discussion
I am trying to figure out how to control the hillshading with Viking. There are two aspects that interest me: 1) darkness level: sometime the hillshading is so dark that it makes reading topographic indication very difficult. It looks nice but makes it close to useless for navigation for me. 2) On a more sophisticated level: Is there a way to select the azimuth and height of the sun to show the shading? I guess I have to play with Mapnik settings but I do not know where to start with.... I would...
-
guillaume posted a comment on ticket #51
Hello, I followed the advice given in this post https://github.com/viking-gps/viking/issues/69; I added the instruction "curl_ssl_verifypeer=0" to the viking.ini file. Without success. Guillaume
1 >
