You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already stated in #7, the heatmap is kind of useless if the track collection is wide spread. Still, I'm a big fan of having a look at my complete route net.
My current solution is to reduce line widths by hand, e.g.
That is: 0.02, 0.5 and 0.05, 0.2 instead of 0.1, 5.0 and 0.2, 2.0 (for ~2.600 activities from Sweden till the Alps). A high resolution image is required, but it works.
Maybe it's possible to automatically calculate line widths based on d_y and d_x. We could define limits for the values (e.g. both version from above as upper and lower limit respectively).
The text was updated successfully, but these errors were encountered:
As already stated in #7, the heatmap is kind of useless if the track collection is wide spread. Still, I'm a big fan of having a look at my complete route net.
My current solution is to reduce line widths by hand, e.g.
That is:
0.02, 0.5
and0.05, 0.2
instead of0.1, 5.0
and0.2, 2.0
(for ~2.600 activities from Sweden till the Alps). A high resolution image is required, but it works.Maybe it's possible to automatically calculate line widths based on
d_y
andd_x
. We could define limits for the values (e.g. both version from above as upper and lower limit respectively).The text was updated successfully, but these errors were encountered: