Automatically zoom in, at navigation instruction

1

freischneider ●

We have already discussed in the German forum

https://forum.locusmap.eu/index.php?topic=6740.0

Reply URL

1

0709 ●

+1 Vote

Reply URL

2

zossebart ●

+1

I suggest to zoom in not by a number of steps relative to the current zommlevel, but to a fixed (configurable) zoomlevel instead. This way you would always get a consistent view when nearing a nav instruction, regardless of the previous zoom.

Also, it would be nice if this could also work with enabled autozoom feature.

Reply URL

1

Herbert Kramer ●

I totally agree and I would like to have a configurable zoom level (according to the zoom, one needs).

URL

1

Menion ●

Hi guys,

I've always wanted to integrate something similar to existing auto-zoom feature, so thanks for bringing this here.

Does anyone have an idea for some automatic system based on current defined auto-zoom parameters? We have 7 votes here and already two ideas (increase zoom by 2-3 levels or change to a specific value). Both needs configuration and I definitely prefer as the first step settings-free option.

From my point of view, I see as ideal to really improve the scale of the map based on the distance to navigation point (defined in seconds) and also based on auto-zoom value.

So this means: for speed 100 kph is zoom defined as 14, for 50 kph it is 16. You start to slow down from 100 to 50 kph before turn left the order. When you will be 30 seconds before the cross, app will start to increase zoom in value up to next two levels so 10 seconds before cross it will be defined zoom + 2 levels. In this case for speed 50, it will be 16 + 2. Maybe complicated on explanation, but it should work I believe :).

Reply URL

1

zossebart ●

What you described here is the relative approach I think. You want to increase zoom by 2 levels from the current level (may be dynamic because of autozoom) 10 seconds before crossing.

I think a distict "target zoomlevel" would be better, because with autozoom on, your approach is dependand on the current speed (and corresponding very configurable autozoom setting) when nearing a crossing. Also speeds may vary very much (for example on a bike...~5-10 kph uphill but sometimes 30-50 kph downhill). This would result in inconsistent views of the crossings.

I think we should try to find a zoom where crossings are nicely visible with most maps (Z19?) and use this as a "target zoomlevel" when nearing a crossing. Maybe in the future this setting could be made configurable (expert mode?).

The zoom would have to return to either the defined zoomlevel (without autozoom) or to the autozoom level according to the then current speed (may be different from before the crossing).

I wonder how the experience would be with many turn instructions shortly one after another, though.

URL

1

freischneider ●

I abe with autzoom no experience. I never use it. I have set navigation instruction and screen at 15s before. Zoom I have set so I see what I want. Times so and times so. If you program it as write, what happens in case (autozoom is off)

Reply URL

1

freischneider ●

Fixed values ...

Advantage: No matter what zoom I have before. It is ensured that I see the turn exactly.

Disadvantage: If, for once, I am very fast, it may be that I am still too far away (15s before) and I still do not see the turn at this zoom.

I like both ideas. Can not decide for me, because I could not make any experience.

Reply URL

1

0709 ●

Auto zoom according to speed, I do not use. Navigation instruction and screen @ 15 s. Short auto zoom when near a command and than back to previous zoom level I know from the car gps.

Reply URL

1

Jürgen keim ●

The idea is very good. +1 from me. I am for the variant with a fixed zoom level. Whenever an instruction comes for example. zoom 18 use. No matter which zoom was before.

Reply URL

1

dermannvommond ●

also for the Variant with fixed zoom level

Reply URL

1

Andrew Heard ●

Great suggestion. I like the fixed zoom level idea. When I come to some complex roundabout I don't want to zoom in by 2 or 3 steps, rather I just want to see all of the exits maximized within the screen. Especially while driving when there is very little time to make a decision.

Reply URL

1

Racer ●

I like the idea "zoom in x steps, but you can also implement both variants, because one wants it that way and another wants it differently.

1. nothing

2. zoom in x steps

3. fixed zoom level

Best in presets or even better in the navigation profile.

Because I do not want to go hiking. When MTB I want xx step and quad yy steps.

Reply URL

1

Mic Tie ●

Yes, this would be a wonderful improvement! Locus could become almost perfect for car navigation!

Reply URL

1

Tobse ●

This idea is very good. Google Maps does that too. Will the idea be implemented in the near future? If not, is there a way through Tasker?

Reply URL

1

Yoannjap ●

I agree this option of fixed autozoom in function of the distance you are from the next crossing is just essential! Especially when you cycle.

Especially for a suscribtion paid app...

Reply URL

1

Yoannjap ●

I have seen that on Tasker, when Locus Tasker Add-on is installed, when you edit a task selecting 'Plugin', 'Locus', 'Request sensors', there are options that could let you know that when you are from, for example, 40 meters from a crossing point, you could command to Locus to zoom map at, for example, value 24!

But how to do that with Tasker?

I am sure there is a way...

If someone can help :)

Files:

Reply URL

2

Vyacheslav Rotko ●

Profile: LocusNextTurnSay (34)

Restore: no

State: Media Button [ Button:Previous Held Down:Off Grab:On Stop Event: Off ]

Enter: Anon (58)

A1: Beep [ Frequency:2000 Duration:101 Amplitude:50 Stream:3 ]

A2: Variable Set [ Name:%Say To:1 Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 Structure Output (JSON, etc):On ]

A3: Profile Status [ Name:LocusReadNextCMD Set:On ]

Profile: LocusEndRouteSay (59)

Restore: no

State: Media Button [ Button:Next Held Down:Off Grab:On Stop Event: Off ]

Enter: Anon (60)

A1: Beep [ Frequency:2000 Duration:101 Amplitude:50 Stream:3 ]

A2: Variable Set [ Name:%Say To:2 Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 Structure Output (JSON, etc):On ]

A3: Profile Status [ Name:LocusReadNextCMD Set:On ]

Profile: LocusReadNextCMD (46)

Restore: no

Event: Notification [ Owner Application:Locus Map Pro Title:Tracking Text:* Subtext:* Messages:* Other Text:* Cat:* New Only:Off ]

Enter: Anon (51)

A1: Variable Set [ Name:%prf To:%evtprm3 Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 Structure Output (JSON, etc):Off ]

A2: Variable Split [ Name:%prf Splitter:, Delete Base:Off Regex:Off ]

A3: Say [ Text:Via %prf2 %prf1. Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:On Network:Off Continue Task Immediately:Off ] If [ %Say eq 1 ]

A4: Say [ Text:Until the end of the route %prf3. Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:On Network:Off Continue Task Immediately:Off ] If [ %Say eq 2 ]

A5: Profile Status [ Name:LocusReadNextCMD Set:Off ]

URL

1

freischneider ●

Is that a Tasker profile to automatically zoom in on navigation announcements?

If so, you could share the profile as a file on Drive.

URL

2

Yoannjap ●

Thanks a lot Vyacheslav, but yes, could you share the profile file please ? To test it

URL

1

Vyacheslav Rotko ●

Friends.

These profiles are not designed to automatically scale the map. This is a hint on how to implement it.

I published these profiles in response to the topic under discussion, because based on the LocusReadNextCMD profile, through intent management, it is possible to implement scaling of the locus map depending on the distance to the maneuver point. This is an interesting idea and I will definitely implement it in the near future and share the result with you.

I am almost sure that publishing the profile file will not be useful, since it will certainly not work "out of the box". Because we all have different versions of the Locus and different languages. And the operation of the profile is based on reading the status line, which the Locus updates in route mode about 40-50 times per minute. I have a Locus PRO version 3.53.1 the language is Russian. The profiles are quite simple, you need minimal knowledge of the tasker and you will be able to write them yourself, taking into account all the features of your Locus implementation.

I have tried to describe in detail why these profiles are needed below.

Profile: LocusNextTurnSay:

When you press the Media Button, "Previous" gives a short signal to attract attention,

Sets the global variable %Say=1

Activates Profile LocusReadNextCMD

Profile: LocusEndRouteSay:

When you press the Media Button, "Next" gives a short signal to attract attention,

Sets the global variable %Say=2

Activates Profile LocusReadNextCMD

Profile: LocusReadNextCMD:

Reads the "Tracking" message from the status bar from the "Locus Map Pro" application and saves it to the %prf variable. Then divides the text variable into parts using delimiter: ", " (comma space)

Then, depending on the condition variable %Say says a phrase such as:

"In 500 feet, turn right"

Or

"Until the end of the route is 5 kilometers and 200 meters,"

Then this profile disables itself until the next power buttons.

Now the need to turn on the screen to find out when and what the next turn will be has disappeared. This is very important in winter, when the phone is in a warm pocket. 😊

Friends.

These profiles are not designed to automatically scale the map. This is a hint on how to implement it.

I published these profiles in response to the topic under discussion, because based on the LocusReadNextCMD profile, through intent management, it is possible to implement scaling of the locus map depending on the distance to the maneuver point. This is an interesting idea and I will definitely implement it in the near future and share the result with you.

I am almost sure that publishing the profile file will not be useful, since it will certainly not work "out of the box". Because we all have different versions of the Locus and different languages. And the operation of the profile is based on reading the status line, which the Locus updates in route mode about 40-50 times per minute. I have a Locus PRO version 3.53.1 the language is Russian. The profiles are quite simple, you need minimal knowledge of the tasker and you will be able to write them yourself, taking into account all the features of your Locus implementation.

I have tried to describe in detail why these profiles are needed below.

Profile: LocusNextTurnSay:

When you press the Media Button, "Previous" gives a short signal to attract attention,

Sets the global variable %Say=1

Activates Profile LocusReadNextCMD

Profile: LocusEndRouteSay:

When you press the Media Button, "Next" gives a short signal to attract attention,

Sets the global variable %Say=2

Activates Profile LocusReadNextCMD

Profile: LocusReadNextCMD:

Reads the "Tracking" message from the status bar from the "Locus Map Pro" application and saves it to the %prf variable. Then divides the text variable into parts using delimiter: ", " (comma space)

Then, depending on the condition variable %Say says a phrase such as:

"In 500 feet, turn right"

Or

"Until the end of the route is 5 kilometers and 200 meters,"

Then this profile disables itself until the next power buttons.

Now the need to turn on the screen to find out when and what the next turn will be has disappeared. This is very important in winter, when the phone is in a warm pocket. 😊

URL

1

Yoannjap ●

What is the 'media button' ?

In profile LocusNextTurnSay, do I have to set 'Application' and select 'Locus'? Or iwhat do I have to set corresponding to this profile?

URL

1

Andrew Heard ●

Even though I've written a lot of Tasker code, it's clearly obvious it would be a lot easier/ more reliable if Locus provided the zoom rather than Tasker ;-)

URL

1

Yoannjap ●

Ok, I tried to test your profile, but I have no zoom during navigation.

Not sure neither having understood what button I have to press (volume / etc. ?)

Files:

URL

1

Vyacheslav Rotko ●

> What is a "multimedia button"?

https://aliexpress.ru/item/1005001388320314.html?spm=a2g0s.12269583.0.0.1e787192IJwkmy

634e6485f3339054043d58b75bf68cf6

> In the LocusNextTurnSay profile, do I need to install "App" and select "Locus"?

If you are using a remote control to control the Locus screen, then this is not necessary. The algorithm of operation will be as follows: When the Locus screen is turned on, the buttons will control the screen. When the screen is turned off or the Locus is not an active application, the LocusNextTurnSay and LocusEndRoute profiles will work.

> could you please share the profile file?

I decided to publish them anyway. But again, you'll have to figure out how it works and edit it for yourself.

> it would be much easier / more reliable if the Locus provided scaling, and not Tasker ; -)

Yes, I agree with you,

> I am not sure and did not understand which button to press (volume / etc.?)

you need to press the button that you have set in the profile. I use the remote control, the link to it is above. Try, for example, to work with the buttons of a Bluetooth headset.

> This is an interesting idea, and I will definitely implement it in the near future and share the result with you.

Unfortunately, it turned out that there are no intentions that allow you to control the scale of the map, so, alas, it is impossible to do this. ☹

Files:

URL

1

Yoannjap ●

Well... Thanks a million Vyacheslav for your help.

You made LocusMap at long last usable when cycling!! :D

URL

1

Andrew Heard ●

I'm sure I wrote a similar help topic suggestion a year or so back, but now can't find it - the # votes would be even higher if the topics were merged. I recall Menion saying the current zoom will increase 10% at an upcoming navigation instruction, but I think this is much too small.

Reply URL

1

Yoannjap ●

Thanks for your reply Andrew. Was this solution held with Tasker?

URL

1

Andrew Heard ●

No it was a Locus suggestion. It may have been in the "forum" rather than the "help system", and maybe not it's own topic/ subject. It's confusing having two separate systems to search across.

URL

1

sonkei ●

I can not do that with tactor. Better if Locus is power.

Reply URL

1

readonly24 ●

Last week I used Locus as a car navigation and I really missed that feature. Especially in the cities where roads a close to the next one can easily go wrong if not zoomed in.

+1 from me.

Reply URL

1

Vyacheslav Rotko ●

I think the map zoom should depend on the distance to the rotation. Time dependence will not work well at different speeds.

Reply URL

1

freischneider ●

Until Locus offers a solution here, there is a solution via Tasker.

https://forum.locusmap.eu/index.php?topic=8047.0

Reply URL

2

Menion ●

Hi guys,

this idea is already implemented in recent app versions. Does anyone already have experience with it? App currently should noticeably zoom in when approaching to any navigation point. It may need some fine-tuning so feedback is welcome.

Also in the bug-fix version, I'm just preparing, will be an option to disable this behavior so it will be optional (enabled by default).

Reply URL

2

Andrew Heard ●

I didn't notice the note in the change log. sounds great. what settings are needed to enable it? setting(s) in presets?

Reply URL

1

freischneider ●

Can't test it right now. Later
Is it possible to set a fixed zoom level ? Or which zoom level is stored ? Presets would be great. Since I use it only when cycling.

Reply URL

1

Menion ●

It works automatically. App currently detects that you are 40 seconds to the command and since then, starts to increase the computed expected scale. And closer to the point you are, a higher rescale is applied up to 400% (so two zoom levels).

So there is no fixed zoom level (this is also an interesting idea). The current solution is more flexible because it just increases the expected zoom level based on current speed.

Reply URL

1

Andrew Heard ●

interesting, will give it a try

to minimise battery my strategy is mostly not to use navigation at all, this reduces power by 50%

i just turn on the screen before possible turn to check against displayed route, with Android 6s display timeout

URL

1

freischneider ●

My experience looking at the turn is at zoom level 20.
If I had 17 or 18 before, that's still ok. But if I had previously set An overview at 14, 2 levels are too little.
Maybe this works with automatic zoom. I have not set automatic zoom. The problem is: When I want to look at the environment, I zoom out. But when I look at the surroundings I drive very slowly or stop. But then automatik zoom zooms in.
It would be very helpful to be able to set a fixed level.

How long does this zoom stay until it jumps back to the old value ? I have stored a value in seconds here (currently 7s).

You start 40 seconds before to increase the zoom. I think this is too early. But this is only my opinion, for others it might be ok.
I have set so that it zooms when the announcement. This is currently set to 15s before. I would make it 2 s before the announcement. But I can't, because the announcement is my trigger in Tasker.
Maybe my experience will help to improve it.

Reply URL

Automatically zoom in, at navigation instruction

Replies (25)