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...
Hmm...agreed, that looks pretty open according to satellite images. Well...it was just a guess... ;-)
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.
port Viking on aarch (Arm architecture)
Small waypoint symbols are used instead of the large ones
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...
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
Failed to download tile - curl error: 35 for uri
to be deleted duplicate entry. sorry
to be delete duplicate entry sorry
to be delete duplicate entry sorry
Hi, I have created a trace in Viking and I want to transfer it to the Garmin Foretrex 801 which is connected to the computer via USB. Viking doesn't seem to detect the GPS. The GPS is well displayed and connected in my system file. I use Endless OS. I select the trace and select Send / Send to GPS... Here are some screens captures: Thank you for helping. Is there another way I can copy some files directly in Garmin folders maybe?
Hi, I have created a trace in Viking and I want to transfer it to the Garmin Foretrex 801 which is connected to the computer via USB. Viking doesn't seem to detect the GPS. The GPS is well displayed and connected in my system file. I use Endless OS. I select the trace and select Send / Send to GPS... Here are some screens captures: Thank you for helping. Otherwise, Is there another way I can copy some files directly in Garmin folders maybe?
Merge remote-tracking branch 'viking-gps/master'
Merge pull request #316 from oturpe/c23-compatibility
C23 compatibility
[QA] Stricter compiler options for test programs
[QA] Prevent sanitizer runtime error
Github #320: Fix UUID usage in sort children
[QA] Retain extreme debug function for potential reuse
CI: Update runner image to ubuntu-24.04
[QA] No need to repeat code in both branches
Fix mapcache memory misuse flagged by ASAN
[QA] Type improvement in strlen() and strncmp() usage
Enable compiling with older GLIB versions
Support old versions of GPSD in status usage
Sorry for my last message I ve Found the Transparency so I 'm now able to see Shore and Buoys This is GREAT, Thanks Rob
Thanks Rob, it is better I have tried both solutions you explain, they work both but only display buoys and beacon, but no shore, at all (I have the choice between the default map or Openseamap but not buoys on the default as I would like to have, I'm pretty sure I am doing something wrong ...
Issue when try to use OpenSeaMaps in v1.10 Ubuntu
Viking currently does not follow link redirection by default and furthermore defaults to using 'http' when a hostname does not contain such a prefix. Normally web servers redirect http to https - but as Viking is set not to follow the redirect it simply stops. Thus, there are two ways to resolve this; Either specify allowing redirects by adding a line like this: <property name="follow-location">5</property> Or specify the full path in the 'url' property (and remove the hostname property) such as:...
sorry I made a mistake, I am using v1.10
Issue when try to use Opensea Maps in v1.9 Ubuntu
Has anyone else noticed that OTM has not been updated in a year? https://opentopomap.org/about data status Status of the database: January 22, 2023. Parts of the map can be a maximum of 4 weeks older. Does anyone know why? I have now noted some tracks not appearing after been created in OSM and routefinder sending the route down gated tracks. The attached image, shows the routefinder track in red, which goes to a locked gate and private property and the blue track is how you need to get around it....
CI: upload-artifact v3->v4 - since v3 has expired
Allow manual deletion of map file cached tiles
Github #313: Improve documentation for command line lat/lon
I think (especially given the tardiness of this response), that such a feature is unlikely to happen any time soon.
Right click on the TrackWaypoint layer on the left hand panel list. Select Properties. Then in the Layer Properties there are labeling controls: Waypoints tab -> Draw Labels checkbox Tracks tab -> Draw Labels checkbox
Undo
This is a known limitation and long open request feature: https://sourceforge.net/p/viking/feature-requests/83/
Flatpak: Add the actual file used by Flatpak build
Support old versions of GPSD in status usage
Make adding files to an existing project is marked as a change.
Colour parse in GPS layer is not dependent on vp existence.
Only need to parse fixed colours just once.
Make most TRW layer combine options only available if there are multiple tracks/routes
Further method to prevent removing GPS Layer (Realtime) tracks whilst in use.
Fix unbalanced GC create/free calls in GPS Layer
More robust geocluelayer recording.
[QA] Better TRW enum definition.
[QA] Useful comment reminder about properties
Add 'Session' file operations:
[QA] Remove duplicate section in help
Prevent potential use of uninitialised variables
Prevent Valgrind detected error
Fix memory leak in vikgpslayer.c
Extend GPS Layer tooltip to include GPSD Mode and Status for realtime tracking
Remove trigger layer/half-drawn complexities as no longer relevant.
[QA] Remove function definition that doesn't exist
Improve MenuItemsSelection functions to use typedef enum for parameter/return types
[QA] gps layer static functions shouldn't be named starting with 'vik_'
Increased protection in use of single point tracks
[QA] Ensure local variables are static
Ensure socket listener is closed on program exit
Fix memory leak in vikmapslayer.c
Fix memory leak in util.c
Fix memory leak in vikobjectbuilder.c
Add cleanup of memory in vikdemlayer
Fix memory leak in bingmapsource.c
Actually create and use a_logging_uninit()