Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - alang

#1
Troubles & Questions / Re: hours for angles
June 29, 2026, 13:32:23
The two conversion references given refer to "Hour Angle". This is a value used in astronomical positioning/navigation which is definitely not suitable for e.g hiking, cycling etc:
See:  https://en.wikipedia.org/wiki/Hour_angle. 

Menion used instead the "Clock Position/Bearing" which is completely different and is simple, widely known (but not in France apparently ?), and very suitable for hiking etc.  It uses a 12 hour clock. I've been familiar with it since I was a child as I guess most will be in at least English speaking countries, though younger generations might not be as familiar with it perhaps.
See: https://en.wikipedia.org/wiki/Clock_position

It was (maybe still is) famously used by pilots in WW2, as in "Bandits at 6 O'Clock" for enemy fighters at the rear, also in the Oscar winning film "Twelve O'Clock High"
In a vehice the direction is relative to the heading - i.e. the long axis of the vehicle body - in an aircraft or boat this is probably not the direction of motion because of cross-winds or currents.

Not sure of the context it was being used in, in the example, but for e.g. hiking the only thing to be careful about is to be clear what it is relative to.  For example:

The two things I most often want to know when hiking, without having to refer to my map/phone are: 
"What direction should I be heading to follow the planned route"
"How far am I from the route"

I use a custom announcement system which speaks, on-demand, something like:
"Current direction: West North West. Distance to track: 5 m. Follow track on bearing, East North East, at 4 o clock. After 372 meters, Bear left. Next waypoint, after 4.9 kilometers, is xxxxxx"

Or if off course by greater than a limit:
Warning. Distance to track: 113 meters. Current direction: West. Follow track on bearing, West North West, at 1 o clock.

The clock directions here, however, are relative to direction of motion as that is better defined than the direction the phone happens to be pointing in - if it's in my pocket that would be random.
The following users thanked this post: 0709
#2
Maps / Re: Online LoMaps V2
June 22, 2026, 16:27:50
Feedback when using on PC (Chrome):

Map Content  - It's a bit difficult to see what has changed as the old one isn't there any more. Anyway, from memory....
Pros:
1/ Major peaks now captioned at zoom 13.
2/ Some tracks are now shown at zoom 14 where they were not previously.
3/ Hiking/cycling tracks - have they got a bit less prominent ? - thinner and maybe not as bold ? or am I imagining it? The planned route seems to be more visible when overlaying these tracks, also helped by the recent change that makes it dashed. In some locations they were a multi-colored spiders-web which made the planned route hard to see, especially for those of us with imperfect color vision. Seems better now. 

Cons:
1/ As per Graf Geo post.... really want to be able to control layers - hill shading, and those pesky hiking/cycling routes which I always disable in the android app.
2/ Some tracks can be a bit faint so hard to see where there is strong hillshading, and that can't be disabled or adjusted. Having said that, the hill shading does look very nice - visualising the terrain is good. Ideally it would be possible to adjust the strength/opacity of it (and maybe other parameters) or if that isn't possible then to hide it, or else have two versions of the map one with hill shading, one without, so we can switch betweeen them when needed.
3/ Still can't control the style of the planned route (width/color/opacity/dasharray).  Not strictly map related but thought I'd bang the drum again. The planned route is what it's all about !

Rendering:
1/ Panning:  Vector: When panning quickly the map is rendered seamlessly;  raster: the tiles can be seen being drawn (blank until they are drawn). Minor thing really.
2/ Captions:  are sometimes inconsistent in the Vector Map. e.g. Look at Ben Nevis at  56.796853, -5.003524.  Caption is present at zooms 13 and 19,  but in between it briefly appears then disappears.    It is OK in the raster map.  Similarly, Yr Wyddfa  (Snowdon) at  53.068453, -4.076301 the caption disappears at zooms 15 and 16 on the Vector map.  There was a similar but worse problem on the old map, different cause perhaps,  which was fixed.

No performance issues with vector.

Other:
Are you intending in future to provide other maps, like OAM, OS Maps, etc. ?

I never liked the "flying" map - i.e. if you drag and let go -  still don't. I don't see the point of it - seems like a gimmick. Sometimes if you lift your finger slightly too soon it "flies" when you don't want it to then you have to move it back. If you are in planner mode, then if you stop it by clicking on the map then you get an unwanted route point.

Since WebPlanner V2 the planned route and selected track are now part of the canvas graphics along with the map, previously they were SVG paths. Was this really necessary ? It makes them "invisible" programmatically.

General comment: great to see all these infrastructure changes - but now really looking forward to the rewards, addressing some of the many usability ideas/suggestions pending.  e.g. Number 1 priority for myself: VIA point management - currently it has to be a two stage process - create the route in Web Planner then edit and refine it in the android app.  I'd like to be able to do everything in one go, on my PC with big screen and mouse/keyboard.
The following users thanked this post: Jan Čapek
#3
Tasker / Re: nearest point
January 02, 2025, 19:32:46
I raised this as an "idea" 3 years ago but it still hasn't gathered any votes unfortunately.
See   https://help.locusmap.eu/topic/26875-broadcast-intent-navigation-to-nearest-point.

Currently I think Tasker Autoinput is the only way to do it but that's unreliable IMO.

I don't understand why Navigation "stop" and "recalculate" are available but not "nearest-point".
Maybe it could be reconsidered ? 
Please. :)
The following users thanked this post: 40°
#4
Tasker / Re: Tasker task trigger in menubar
September 05, 2024, 12:34:02
Haven't seen anything about app factory problems in Android 14 but I dont use myself so don't know. Have you tried the obvious things like rebooting and/or recreating the app ? 
However, if stuck then you could try these alternatives.

1/ Install Locus/Tasker plugin.
Run plugin app; Settings;   Ensure "Run Task From Functions" enabled. Set Regex to match just your tasker task. (format "Projectname/Taskname"  - Default Project is named "Base")
Locus: configure menu; Add Function - add "Run task" from "Add-ons" section.
One tap needed to run, provided Regex matches just one task else it shows a selection list.

2/ Quick BookMark
URL    tasker://assistantactions?task=YourTaskName&par1=YourValue1&par2=YourValue2
Two taps needed to run.

3/ Tasker secondary app.
Tasker: Preferences/ActionTab - ensure "Secondary App Enabled" set. Create profile using "Secondary App Opened" event and map to your task.
Locus: configure menu; Add app - Tasker Secondary.   
One tap needed to run.

There might well be other ways. (e.g if Locus can trigger app shortcuts or send user defined Intents then Tasker can react to those and map to Tasker task)
The following users thanked this post: zossebart