App: Speed based auto zoom control

This feature topic is about speed based auto zoom control.

For new suggestions please create a separate topic for each idea.
Then community can discuss and we can see if it’s needed and if / how it can be implemented.

Regarding the new auto-zoom scaling, however, it’s not as good for me as I initially thought. I am still not able to configure it so that while driving 80-90 km/h I can see the ~3 km route ahead.

The current settings are: Min 13.0 / Max 17.0 / Scale 50%; Samsung Tab Active2 with 8” / 254 dpi / landscape screen.

I’m not sure if I understand the algorithm correctly, but maybe extending the scale from a minimum of 50% to e.g. 20% would help?

Depends also on screen dpi / size, larger screens show more map.

What is your desired zoom? (if zoom via gestures / buttons)
Is the min zoom option set less than that?

I could extend the slider, but need first to collect user preferences about this new feature.

Yesterday I experimented a little bit with the scale factors: 50% 100% 200%
My Impression was that the difference could be more.
Maybe 25%-400%
Maybe 15%-200%
:thinking:

min zoom 13.6
max zoom 16.1

Kurviger Pro 1.14.1
Android 8.0.0 (API 26)
samsung SM-G930F
1080 x 1920 (480 dpi)

I noticed that min zoom was never reached.

Those are your min / max zoom settings?

What was your device’s real min / max map zoom based on speed?

The desired 3 km ahead are achieved at level ~14. But even if I set the automatic minimum to level 12 (it can’t be less), at the speed of 80-90 kph I can “see” only slightly more than 1 km ahead.

Uhh I am not sure.
I think 14.1% - 16.0%
Never reached zoom beyond 14% even at a speed of 150km/h

Note that besides screen dpi / size, auto zoom is affected also by the available screen:

  • Screen orientation: Portrait or Landscape
  • Map orientation: No rotation or Movement direction 2D / 3D

Summary of my short test above

Kurviger Pro 1.14.1
Android 8.0.0 (API 26)
samsung SM-G930F
1080 x 1920 (480 dpi)

Settings:

  • min zoom 13.6
  • max zoom 16.1
  • auto-zoom scale 50%
  • Screen orientation: Portrait
  • Map orientation: Movement direction 2D

Device’s real min / max map zoom based on speed:
14.1 - 16.0 (out of my memory not 100% sure)

And would you also like smaller speed zooms?

Well, I would have expected the actual min zoom closer to the min zoom in settings.
Maybe reach min zoom at lower speed (e.g. min zoom at ~100km/h)
What do others think?

Limits don’t do interpolations in both auto zoom modes (distance or speed).
Min / max auto zoom settings are just bounds applied on top of algorithms.
Auto zoom scale’s purpose is really “moving” the result towards min or max.

here are my settings:
Samsung SM-G970F
1080x2280 (480 dpi)

Auto zoom: speed
min 16.4
max 17.5

I d’like to see the road ahead. To get quick access to an overview, I prefer the bluotooth button :slight_smile:

Would you like smaller speed zooms?
(min / max limits are too close and min zoom seems too large)

I prefer only a small change in zoom because I use kurviger to give me an idea what road profile is in front of me. Just to know, a hairpin is ahead, is good. To know its 200m in front of me is perfect. And this works only if the zoom doesn’t changes to much.

Kurviger 1.14.2 (Beta) has extended min / max in auto zoom scale (20% - 300%).

Please test how it works with your devices. :slightly_smiling_face:

1 Like

A post was merged into an existing topic: App: “Simulate navigation” function

Today I did a short test with 20%.
IMO the scale range seems to be sufficient now.
Need to test more, but my personal preference will probably be near 50%
Edit: my device settings above

If you want to do even more fine tuning:

Manfred

The not fast adjustment is for my opinion advantageous. It would make me nervous when the scale wobbles like a jelly.
I don’t need the view of the next 3 km, about 1 km is enough for me.
Currently use 150%. This is optimal for me at unclear crossings/turns (scale 18+) and at higher speeds still allows a good assessment for not quite visible curves (scale 16).

Implemented in Kurviger 1.14.13.