[APP] - version 4.17.+ ( 5/2023 )

[slarti76]

Small bug regarding "Altitude threshold":
First change the threshold, then use Tools>Update Elevation => Threshold reset to 3m.
I realize that the changing of the threshold triggers an elevation update, but I'm pretty sure it's not the intention for that to be reset with the other command...

Also, I can confirm that sharing location from Google doesn't do anything.
And I second the idea to add Pluscode in Locus Search - we have what3words already, so Pluscode should be easy. And, whether we like it or not, it's much more common than what3words, being that it's supported by Google Maps...

[Menion]

The altitude threshold is, after using "Update elevation", correctly set to a value of 3m. It is an intent. This method completely changes elevation values so the app set the threshold to get the expected result. The previous value is no longer valid.

[slarti76]

The altitude threshold is, after using "Update elevation", correctly set to a value of 3m. It is an intent. This method completely changes elevation values so the app set the threshold to get the expected result. The previous value is no longer valid.

I respectfully disagree: The Altitude threshold is part of the track settings, so a mere "recalculate" shouldn't change that. As far as I see it, "Update elevation" is needed when you recorded a track with GPS altitude values and want to switch to SRT-based values. Or you have newer SRT files. Why would that mean that you want your threshold to be reset?
I mean, it's OK, can live with that, just don't think it's intuitive to change settings from the settings dialog as a side-effect of some other function - no other track menu function has such a side-effect...

[Menion]

I also respectfully disagree. The threshold parameter is part of the track, but it also reflects the quality of elevation values. The default value is set to 5, but during recording, this value changes based on current active parameters on your device (SRTM usage, pressure sensor). Using offline elevation files causes a major change in the quality of elevation values = the threshold should reflect it!

[Andrew Heard]

Unfortunately I can't download the latest beta from Google Drive. It always gives me
a 404 error.

just rechecked - file download (4.17.2.4) OK for me; see https://en.wikipedia.org/wiki/HTTP_404

[Radim V]

handling Google Maps share button should be fixed

thanks @Marek, and the issue reported many times, of search results from > 10,000km away at the top of the list, when there are closer matches on the map < 10km away?

This is not forgotten, just there is no "fix". There is tons of work to determine relevance of results and: Not everything is under my control. Also the rule that closer "match" is more important is oversimplification as we (not just me) agree. I may do some tweaks but proper solution takes time.

[Menion]

Hi to all,
it took me quite a long to prepare a new version even there aren't any major changes, just a few very interesting tweaks. Well, the new map-screen content panel of course ... thanks for a big help with it. Hope it will be a useful tool for everyone.

And enjoy the new app version!