Messages

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

[@lor74cas]

@lor74cas
...
because with the switch to android 13, I can't place them in the folder.
...

I just tested with x-plore on Android 13: even on EXT SD, this app can write to the private folders of /Android/data.
BTW: 1" alone is not delivering better results per se; only 1" plus LIDAR (Sonny's DTMs) will do.

HI,
I finally managed to install the 1" hgt files plus LIDAR (Sonny's DTMs) and they really make a difference.
To get around the problems accessing the srtm folder, I copied the files from the PC with adb by connecting the mobile phone to the PC with a USB cable.
There are several hurdles here as well:
you must have adb installed
You must have developer options enabled on your phone
you must have a good usb cable
you need to authorize the phone to connect
and you need to locate the full path to the srtm folder
but if you already have all or most of what you need then everything is resolved in a single command:
adb push /home/lorenzo/Scrivania/hgt/*.hgt /storage/self/primary/Android/data/menion.android.locus/files/Locus/data/srtm

I am more and more convinced that the webplanner must have 1" plus LIDAR data (Sonny's DTMs). There is too much difference between what locus compute with LIDAR data on the same trace computed on the webplanner.
If, for reasons of occupied space, it is reasonable that not all the 1" data be downloaded to the mobile phone, but only those of the most used areas, I don't see why on the server hosting the palnner it is not possible to have this data for all areas where they are available.

You cannot view this attachment.

Hello,
search for hardware (not for volume or button)

I think they are exaggerating a bit here. Why do they always have the screen on ? Normally they are hiking or biking and look at the path. On Locus you look only if you need information. So the screen can stay off 70% of the time.

Yes, I agree, but everyone uses his device as he sees fit, in my case:
I start recording with Locus and only use the phone to take pictures or at crossroads when I have to choose which way to go, so during any excursion Locus is only active for a few minutes.
I prefer to turn it on for a few seconds and thanks to the high contrast of the icons I can see all the details even in full light, changing these settings in my case would be worse.
The copyright symbol could be less shiny (it's only there as a requirement) and that wouldn't be a problem, but the other icons the way I use them shouldn't be changed.

In addition, the displays have timers that first reduce the brightness and then turn off the display to avoid this type of problem, just set a timer that suits your needs.

Perhaps the problem arises for those who use Locus as a navigator in the car and want to leave it always active. If this is the problem, it would be useful to tie the brightness of the icons to a profile for example for use in the car.

I believe that instead of only checking the accessibility values ��there is a filter on the name, just like I don't allow to pass "military road" so in your case it does not allow you to pass on "tram route"
https://forum.locusmap.eu/index.php?topic=8235.msg69978#msg69978

Hello,
with this bookmark setup you have access to the Strava Heatmap in the desired location.
You cannot view this attachment.
The first time the browser opens you only need to log in to see the higher zoom level.

The zoom I used is fixed at 15, because using the same Locus zoom level the two maps differ too much.

No need to manage with config file, cookies, edit file as in this old post https://help.locusmap.eu/topic/strava-heatmap-requires-now-authentification-at-higher-zoom#comment-54089

Obviously a different result is obtained, but for someone it could be useful to easily see the most popular routes