Automatically zoom in, at navigation instruction

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

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.

Profile: LocusNextTurnSay (34)

Restore: no

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

Enter: Anon (58)

<we issue a short signal to attract attention>

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

<tell the distance and maneuver>

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

<enabling the navigation command reading profile from the status bar>

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)

<we issue a short signal to attract attention>

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

<tell me how much time is left until the end of the route>

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

<enabling the navigation command reading profile from the status bar>

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)

<saving the Locus command to a variable>

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

<splitting the variable text into parts (separator: comma space)>

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

<we say the right phrase>

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 ]

<we say the right phrase>

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 ]

<disabling this profile>

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

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

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

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

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. 😊

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?

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 ;-)

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. ?)

> What is a "multimedia button"?

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

> 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. ☹

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

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

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

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.

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

I think so that it was integrated only in LM4. It is in the autozoom settings. Activate at the bottom. But with Tasker you can realize it also in LM3. I am currently working on a new solution, since Android 13 no longer allows Logcat in Tasker.

Thanks, this is correct. The feature is available in the Locus Map 4 version.

Ok, thank you. I thaught, it's available in 3.xx, because it's mentioned in the release notes of 3.63.1:

Ah, second issue in news. I'm trying to simplify the writing list of news and this is the result. So sorry, it is incorrect and this auto-zoom system is really implemented only in the Locus Map 4, thanks for understanding.

No problem, it's not essential for me, it would be nice to have. And I could refresh my knowledge in the depths of the settings after a long time again... ;-)

@Menion - "Extra-Zoom" is interesting for me even though I don't use Auto-Zoom at all.

Can you make it independent from other zooms and allow assign it its own zoom level? That would make it more versatile. It should be called "Auto zoom on navigation command" and can stay where it is and be a checkbox, but get additional ZL property - and maybe.. time in seconds, after which it returns to prior zoom level.

Agree

"@Menion - "Extra-Zoom" is interesting for me even though I don't use Auto-Zoom at all.

Can you make it independent from other zooms and allow assign it its own zoom level? That would make it more versatile. It should be called "Auto zoom on navigation command" and can stay where it is and be a checkbox, but get additional ZL property - and maybe.. time in seconds, after which it returns to prior zoom level"

I voice Tapio also tu. I used to have this solution via Tasker.

I do not use autozoom. But would like to zoom to zomlevel 20 for navigation instructions. After xx seconds back to original level. Or when you are past the turn.
If within 2s the next instruction comes then do not zoom out.

Understand. I would still like to keep the current system and improve it, instead of making additional settings in the app. To make it "simple", it makes sense to have only a single preference that controls zoom automatically.

The current system is easy > the app is always able to compute the required zoom level at a certain moment. So no matter if you zoom in/out manually during it, the app is able to restore the expected zoom level. Solution with hardcoded zoom level for navigation point will loss flexibility in higher zoom (low zoom to see far away) etc.

I have no clear idea in my mind for now ...

I have implemented automatic scaling in Tasker. Scaling is controlled not by time, but by the distance to the rotation. Time control is very inconvenient. The scale is selected so that the rotation is always displayed at the top of the map. I have been using it for several years now and am very pleased with this decision.