Messages

Can someone please tell me when I import a route (track) into Locus web planner whether the track point elevations <ele> are maintained? I have just downloaded Sonny DTM France 1asec v3 HGT files (2.4GB!!) in order to improve the slope accuracy of some planned routes.

Hello,
+1
If the web planner had the best altitude data (Sonny's data), we would have solved half the problem already, this has already been requested in the past.
Also when importing a gpx you should be able to choose whether to keep the original elevation data or apply the planner's data.

Custom WMS > a little hidden. Map manager > WMS/WMTS tab > "+" > Add from library > "+" > and here you go ... this does not make sense right? Hmm ...

It is not very clear, because the first option says "add from library" and therefore the user thinks it can only be done from the library. Then the library list opens with the + button that seems to be used to add a further WMS to the library itself and not to the WMS chosen by the user. In my opinion from the WMS/WMTS menu when you press the + it should propose the options one to search in the library and one for manual insertion.

and in those moments I seek silence and tranquility, so having a device that makes itself heard at intervals disturbs me.

I use a cuckoo sound 😊

better than the one of the wild boar in love

could you share your Tasker profile anyway, please?

I removed unrelated parts and added in some configurability. If you have questions, best is you create a topic in Tasker forum then. Feel free to ask.
Important, this requires the Locus Tasker plugin, see Play Store.

https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Profile%3AHike_Ping

Great idea, I simplified the task even more to give feedback only when the recording fails, increasing the number of audio reminders and also inserting vibrations. The verification interval is defined only in the set up of the TICK event that I set to 100 seconds and it is not necessary to create loops in the task because it is the event itself that activates it at each interval.
The interval should not exceed two minutes according to what is reported in the TICK guide.
You must remember to activate it, but there is no danger of forgetting to turn it off, it will automatically remind you 100 seconds after you have closed the track.

https://taskernet.com/shares/?user=AS35m8kc9lYIafma1bmhSsdc5aW41wXP5NeuM1RwE0hptzS4hAh4n%2Fj3ZJVJ%2BEksDoEnzn7H%2FxM%2BAQ%3D%3D&id=Profile%3ALocus_Rec_Ping

There are a lot of posts on this forum for the exclusive use of DE or CZ that deal with topics that could interest everyone. In this case the topic had already been discussed several times so I also used Italian to guide the user in the menus translated into Italian. Easier for me and for him, just the hassle of using a translation system for others.

[Event]

Event
Owner: Locus Map (use the app selector)
Title: *Laufen*

Task
airplane mode

Well, do you really think there's another person on earth using orux maps in Locus?

It's supported, and it worked before the initial display of map name was fixed (which it is), so am I not allowed to report that bug?

I find it a little weird that two people thank you for a post basically telling me my bug report is of no importance? I don't complain when others report bugs that are of no concern for me...

The many options provided by Locus make it very versatile on the one hand, and on the other very prone to having ultra-complicated menus that scare the average user who seeks simplicity as a first approach. Some of these options are used by maybe 10 people so it makes me smile when someone finds a bug on one of them, even more so when it relates to maps of an application in direct competition with Locus. My "thank you" was not a personal attack, if a function exists it is right that it works properly, but it is more to point out the fact that sometimes we should also think about removing and simplifying instead of always adding something new.

Thank you Menion,
Are you perhaps planning to manage LoPoints on the web too?
Insertion, comments, rating ...
For me it would be much more convenient to do it on the PC than on the smartphone.

App (if we will talk about track recording), is prepared to accidentally shutdown of the whole system. So when you restore the power of the device within 10 minutes, the recording should even start again automatically.

Thanks Menion,
it's something that I, like Andrew Heard, have also tested and I confirm that it is truly a great feature of Locus.
I didn't know about the 10 minute limit, if it is exceeded Locus creates two tracks, closes the abruptly interrupted one and opens a new one?
Maybe 10 are few, especially if you don't notice that the battery has abandoned you, the low battery warning on Android has never been very relevant, perhaps you could put in place a proper acoustic warning below a certain charge threshold directly in Locus.

Hello, in the daily forecast detail panel it would be useful to have a link to the next and previous day at the bottom, avoiding having to go back to the main forecast menu each time.

But isn't "search this area" exactly this? Or do you missing it even for category highlighting?

I usually use a zoom that allows me to see a very small area on the screen because I prefer to see the details.
So when I do a search as the area is small I get few results as they depend on the zoom. I would prefer to set up the search with a filter of, for example, a fixed radius of 5 km. So I would always have the list of found items regardless of zoom.
Or
You could show on the map the elements found that obviously fit on the screen, but also list those that don't fit in order of distance.
So if in the list I see what I was looking for that is outside the on-screen map, I can click on it without having to zoom out on the map and be directly centered to that point

A filter could be introduced to limit searches to a radius of x kilometers.
We thus avoid useless occurrences of results that are too distant both on the map and in the list.

@lor74cas It is correct behavior - this just indicates directions of results outside of your map while you can be anywhere else in the real. We plan to add distances from GPS position to the list of results bellow the map.

IMHO It's not what I would have expected.
If the search is done from the center of the map or from the GPS position, it is from that point that I would like the distance to be measured.

For me, track recording is 4%, and optional navigation increases that to 8% (total). Will depend completely on battery size & condition & screen brightness. I therefore (mostly) never use navigation, and simply turn on the screen briefly before any potential turn. I find looking at the map far more informative & reliable than turn instructions. I have the screen timeout for 6s. Sometimes I use POI alert but to replace navigation commands would be very tedious if lots of turns.

I agree with Andrew.
In addition to keeping the consumption of Locus under control, it is also necessary to reduce that of the device.
If you don't need to be contacted by phone, you can put it in airplane mode.
If, on the other hand, a telephone connection is needed, but it is possible to give up the internet connection, data connectivity can be disabled.

The reason is currently pretty simple. We do not have (yet) a system for the automatic distribution of 1' files on mobile devices. Because of this, web and also LoRouter data are computed with 3'' SRTM data > to make it "wrong" identically on all platforms.

Btw. did anyone notice the "Altitude threshold" parameter in the track edit screen? I'm experimenting with this value. For now, this may be set only for single route. Automatically is used value 5, when using SRTM data it is equal to 3.

For my use, the app and the PC are two separate worlds that communicate with each other thanks to the cloud.
On the app, to avoid memory saturation, I would be inclined not to install the LIDAR data (only let expert and aware users do it) while maintaining the updating of altimetric data as it now happens in an automatic and precise way.
But the web server doesn't have space problems, so it could contain LIDAR data where available, updates can also be made periodically based on communications from Sonny.
You could also add a feature like this:

• in Locus, in tracks settings an option "update altitude automatically during cloud sync"
• tracks are sent from the app to the cloud where the altimetry is reprocessed and then sent back to the app with a flag or description indicating that the altimetry has been reprocessed
• if you don't want an automatism, you could add an item to the already present "update altitude" in the tools with an "update altitude in cloud"

If then the problem is that of having two instruments that return two different results, just put a link on the web planner that explains what and how the altitude is calculated on the web and on the app.
Obviously it would be good to specify that it makes little sense to use a 1' reticle if you don't have a gps accuracy filter set at least below 50mt, preferably under 20mt.