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

Topics - Graf Geo

#1
I had recently wondered several times why the calculated time with LoRouter, profile walking/hiking, was often significantly longer, even though I had planned the routes on flat terrain. Sometimes 20-25% longer than the average speed set with the slider.

The only explanation for me is that the surface/trail condition is taken into account to a large extent if it is poor. In some cases, after checking in openStreetMap, I found that large parts of the route were labelled with surface = sand and smoothness = very bad, for example. This didn't always correspond to reality, but of course Locus can't help that. But where the paths were actually bad, you can still walk almost as fast as on normal paths, and by no means 20 or 25% slower. In my opinion, the condition of the path is weighted far too heavily for the calculation. In most cases, 10 % would be more realistic. But I realise that it is not easy to find a generally good factor.

But: in the bicycle profiles, the surface condition is apparently not or hardly taken into account at all! I have planned several routes for testing in different bike modes, the surface of which consists of sand and is labelled with smoothness = horrible. LoRouter calculates the same time as on a smooth tarmac road, i.e. at pretty much exactly the speed I set with the slider.

This is bad, especially as the influence of a poor surface on the time required for cycling is much greater than for walking or hiking. Cycling on sand or on tarmac makes a huge difference!

Take this route as an example: 2 km of flat sandy track (and really bad loose sand) through the pine forest:

https://link.locusmap.app/t/8g4c6s

In the LoRouter walking profile with the average speed set to 4 km/h (navigation commands ON), Locus calculates 39 minutes, which corresponds to 3.1 km/h. (However, we needed considerably less).

The same route is calculated in the LoRouter bicycle Touring profile (set to 14 km/h) with 8 minutes, which corresponds to 15 km/h. And that's on a terrible sandy track!

I have tried it on several routes in flat regions, and the bicycle profile apparently ignores a poor surface. Why?
#2
During my recent vacation, I again noticed some inconsistencies in the track navigation. Specifically, it concerns the recalculation in the event of a deviation from the planned route. It is not entirely clear to me which parameters are used for this.

As soon as I deviate from the planned route (beyond the set value, in my case 100 m), the route is recalculated. The entire route is then given a new name consisting of the date and time of the recalculation (see screenshot 1). In one case, a new track name was even generated, which was completely cryptic and contained the name "brouter" (see screenshot 2), although I created all routes offline with the LoRouter.

Unfortunately, after the recalculation I sometimes got the wrong ETA or time to target again, even if we only made a small detour.

After doing a few tests yesterday, I have the impression that the recalculation is not done with the parameters I used to create the route. Instead, it uses the last set parameters. For example, if I later created a different route with a different average speed.

I first created a test route with an average speed of 2 km/h (slider). Then I created a second route with an average speed of 10 km/h. I then navigated along the first route and deliberately deviated further and further from it. The route was then recalculated every approx. 100 m, which is correct. However, the time to target was calculated shorter and shorter and at some point corresponded to 5, then 7, then 10 km/h. Obviously, the recalculated additional distance is calculated using the last set average speed and not the one that was set when the route was planned. is that right?

In my opinion, it would be better if the recalculation was always based on the speed of the planned route.
As I said, this is my assumption based on my experience and tests. Hence my question, what parameters are used for recalculation during track navigation? I just want to understand how it works.

Translated with DeepL.com (free version)
#3
Troubles & Questions / Two issues with LoPoint photos
September 22, 2024, 11:05:07
Two issues with LoPoint photos:

I open My LoPoint photos and see a thumbnail list of my photos.
I click on any photo and see it at display width. The photo cannot be zoomed! And this is a new bug, on my old SG7 with beta 4.25.1.3 the zoom works.

At the bottom left of the bottom panel, the name of the LoPoint and the icon to the left of it are displayed.
If I click on the icon, the detailed view of this LoPoint opens. A narrow map section with its position is displayed in the upper part. At the top right is the round icon with the point and the four arrows (see screenshot).
If I click on it, the map view should open full page with the position of the LoPoint in the centre. At least that was the case in earlier Locus versions and that would be the expected behaviour.

Now it just opens the photo again when I click on the icon, not the map. Only when I close "My LoPoint photos" completely, the map is displayed.
#4
I use the map rotation function very rarely and in these few cases I activate the function with a preset.
So I don't really need the map rotation button (small red arrow next to the map centering button). It's more of a nuisance because I keep touching it accidentally and unintentionally activate the rotation.
Even as a dual centering button, this happens again and again and annoys me.

So it would be nice if you could disable the map rotation button completely.
(I often need the map centering button, however. Unfortunately, the two functions are linked. )
#5
I created a profile with Tasker that automatically activates the location services (GPS) in the smartphone for certain apps. This includes Locus, of course.

What I can't do: If none of these apps are active (not even in the background), the location services should be switched off automatically. This means after actively closing/switching off the apps.

Unfortunately, location services are switched off immediately if none of these apps are running in the foreground. This is of course bad and fatal in the case of active track recording. 😎

Can this be fixed with Tasker? That location services are only switched off when I actively exit Locus (Do you really want to exit) and none of the other apps are active?

Thanks in advance and best regards.
#6
Under controlling > map screen, you can set whether and how panels and buttons should be displayed or hidden.

I have set all panels to auto-hide, hiding timeout is 7 seconds.

If the panels are hidden by double-clicking on the display or after 7 seconds, they remain hidden even when the display is switched off and on again or when switching to another app in the meantime. They are only shown by double-clicking on the display. That's how it should be.

However, as soon as I activate any dashboard, the top panel is shown every time I reactivate the display or switch back to Locus. The other panels (and the buttons set to auto-hide) remain hidden.

I would prefer the top bar to remain hidden like the other panels.
#7
I don't know if this behaviour has been reported before:

When I search for a LoPoint category (e.g. supermarket), the results are displayed on the map as icons (screenshot 1).

If I zoom a little further into the map, more and more LoPoints of other categories are displayed as red square icons: Peaks, churches, other... (screenshots 2 and 3).

(I have set the red icon as the default point icon in the Expert Settings under Points).

Of course you can live with this, the LoPoints you are looking for can be easily distinguished visually from the red icons, but it would make more sense to display only the LoPoints you are looking for.
#8
I have about 20 dashboards, many of them for testing purposes only. In the "Select dashboard" list, the three "last used" dashboards are listed at the top and the others below ("other"). The sorting appears to be primarily alphabetical. However, I have individual dashboards that are always sorted in the wrong alphabetical position. They also remain in the wrong position when I rename them. See screenshots.
That is strange. What could be the reason for this?
#9
Not a bug, but a bit of a nuisance:

I create a route or record a track. This is saved in folder xy and automatically receives the style of the folder. So far so good.

If I want to change the line style of a track later (and don't want to keep the style of the folder), all style properties are first reset to the default style (line red). Only width is retained.
Everything else (patterns, colouring mode, outline) is reset.

If I only want to change a single property, e.g. the type of patterns, I still have to set again everything else.

It would be better if all line properties of the track to be changed were retained in the menu so that I can only change the desired detail.
Maybe optionally with a button "set default style", if someone prefers that.

Screenshot 1: Style of the folder
Screenshot 2: Edit dialogue
Screenshot 3: Use style of the folder deactivated. All properties are reset (except width)
#10
Hi, I have just discovered this forum section on Tasker.  :)

I recently installed Tasker for the first time and have already created some useful profiles. So far I have only created a profile for Locus that automatically activates GPS when Locus is running in the foreground. It works fine.

What I would like to have: I have a recording profile "Running" that I have always used for jogging. When I'm jogging, I always switch on flight mode so that I'm not disturbed when I'm out and about. Of course, I forget to do this from time to time and then an incoming message or call annoys me in the middle of the run.

Is there any way to get Tasker to automatically activate flight mode when the recording is started in the Running profile (and only in the Running profile)?

I think I read somewhere on the web that someone has set this up, but I can no longer find the page. ChatGPT has given me instructions, which are unfortunately not useful.

I am an absolute beginner with tasker and am still finding it quite difficult.

Translated with www.DeepL.com/Translator (free version)
#11
I have a default value for the altitude threshold of 3 (I'm quite sure I set this myself in the past). Now I would like to change it permanently to 5, but I don't know how.
#12
After the last update (4.24) and the new features for LoPoints, I tried a few things.

The captions for LoPoints photos can neither be edited after uploading nor added later. In the field, I usually don't have the time or inclination to write a caption, or I make a mistake and want to correct it later. Unfortunately this is not possible, or am I missing something?
#13
After I recently had to reinstall Locus, I realised that my audio coaches and quick new points were not included in the backup and I had to create them all again.

I only have a few audio coaches, so that was done quickly. But I have a lot of quick new points for various use cases, so it was a bit of a pain to create them all again.

EDIT: I have just seen in the backup settings that Audio Coach and Quick new points should be included in the backup. The option "Settings" was definitely activated and everything was activated when the backup was imported. However, my audio coaches and quick new points were not there afterwards (all other settings have been restored correctly).

Perhaps there is a problem with the backup function?
#14
I have a request for improvement when creating a new route in the route planner:

I am planning a route. Then, for example, there is a small bridge over a stream that is missing from the OSM map. The route planner doesn't want to take me along it. No problem, I create this section of the route "manually" in drawing mode. Or I want to take a shortcut somewhere cross-country. Here, too, I can insert a manual segment. Wonderful.

But: Whenever I recalculate the entire route ("recalculate all"), the manually drawn segments are ignored and the route is routed via existing paths, which ruins my planning.  See screenshot.

Would it be possible for manually drawn segments to be regarded as "unchangeable" during the recalculation and thus be retained? That would be great!

(If the manual segment cannot be reached in another profile (Car instead of Hike etc.), the orange error message "Routing service can't find the start point..." may appear. Just like when recalculating in car mode if shaping points are on hiking trails.)
#15
Since I sometimes have problems with the ETA during (track)navigation in the current version (unrealistic, sometimes nonsensical times are displayed from time to time, usually much too short), I took a look at the planned routes as a gpx file:

The LoRouter generates timestamps when creating a route. Unfortunately, this is now also the case if you create a route without navigation commands. It is completely unclear to me what the purpose of timestamps is for a planned route. Logically, they make sense for a recorded track, but for a planned route?

Are they needed for the navigation commands and if so, why? The time is irrelevant, and they would be unnecessary for a planned route without navigation commands.

Just to calculate a fictitious route time in the planned route? Which is also too short by default (5 km/h or even more is always assumed for "walking", which is definitely too fast). 

No other route planner generates time stamps. Not GraphHopper, not BRouter Web, not openrouteservice.org and not even the Locus web planner. And you can navigate with their tracks without any problems.

If someone can explain this to me briefly and clearly (unfortunately I am not a geoinformatics specialist), I would be grateful. I couldn't find anything useful on the Internet.

It would also be interesting to know how the ETA is calculated during track navigation. All you really need is the current speed, the length of the remaining distance and (if available) the gradients. As I said, the values are sometimes given in an absurdly short form and are therefore not reliable.


EDIT: I just found my posts (in german) in this 3 year old thread. There were already problems back then.
 
#16
Small issue with the navigation commands switches on/off:

I open the route planner and choose p.e. hiking or walking mode. I select "include navigation commands" on. (Important: the last time I planned a route, it was off).
However, the route is initially created without navigation commands. Only "recalculte all" creates navigation commands.
Then I create another route and select "include navigation commands" off. However, the route is created with navigation commands, only "recalculte all" deletes them.

This means that the route planner remembers the last setting, which is not changed simply by ticking "include navigation commands", you first have to recalculate.

LM 4.20.1 Afa

Translated with www.DeepL.com/Translator (free version)

#17
Hallo, ich versuche es erstmal hier im deutschen Forum.

Ich bin bisher nicht besonders begeistert von der neuen Version 4.20, der Routenplaner wurde angeblich komplett überarbeitet und soll mehr/bessere Konfigurationsmöglichkeiten bieten.

Irgendwie finde ich ihn umständlich und kann viele Einstellungen nicht mehr finden. Wo z.B finde ich denn die Zuordnung von Profilen wir "shortest" usw. zum Modus Gehen, die ich vorher problemlos im Routenplaner auswählen konnte. Und wo kann ich neue/eigene Profile erstellen?

Danke für einen Anstupser, vielleicht bin ich ja nur blind...
#18
I often want to create points with attached photos. In doing so, I want to have a clearly visible geometric icon and attach one or more photos to it.

There are 2 ways to do this, both of which require too many clicks:
 
1. "Quick new point": Here I can set default icons that will be used. Great. But if I make a photo as attachment, I have to choose every time if the photo should be used as icon or not (I don't want to, because the photo icons are badly visible on the map). Then still save. That's quite a lot of clicks. Here it would be nice to save at least the photo icon query by a default setting.

2. "Photo point". Actually great, as it is much faster. But in doing so, the photo is used as a point icon by default, and I have to manually set another icon again afterwards.

Ideally it would be, if one could specify an own Icon, which is used by default.

Or is there already a corresponding possibility or setting that I have overlooked?


Translated with www.DeepL.com/Translator (free version)
#19
A small problem with the displayed track statistics for merged tracks:

Sometimes I forget to activate the track recording at the start of a tour and do this only after, for example, 0,56 km.
I then create the first 0,56 km with the route planner and then merge the two tracks. The part with the route planner logically does not contain any time values.

The merged total track then contains the correct total distance (e.g. 20,93 km, of which 20,36 km was recorded and 0,56 km was created with the route planner). The altitude profile is also correct.

However, nonsense is displayed for the track time: 469238:54:07.
Likewise with the pace: 1344958:37

I know that Locus cannot calculate correct values in this case. However, it would be more elegant if then nothing or 0,0 is displayed than such fantasy numbers.

Screenshot 1 shows the statistics of a recorded tour. Length 20.36 km.
The first 560 m are missing and were created with the route planner.
Screenshot 2 shows the statistics of the merged track (20.93 km).

(Such nonsensical values always occur when a recorded track and a track created with the route planner are merged).
#20
Hallo,

ich benutze überwiegend die OAM Karten, gelegentlich aber auch LoMaps (offline).

Bei einem Kartenwechsel von einer OAM Karte zu einer LoMaps Karte wurde m. E. früher automatisch auch das Theme gewechselt von z. B. Elevate bei OSM zu einem internen Theme. Jedenfalls hatte ich damals bei einem Kartenwechsel immer gleich die typische LoMaps Optik, wie sie auch bei den LoMaps online zu sehen ist.

Seit einiger Zeit muss ich das Thema zusätzlich manuell wechseln. Bei einem reinen Kartenwechsel sieht die Karte sonst praktisch identisch aus, da das letzte Theme weiterhin aktiv ist. Das erschient mir nicht wirklich sinnvoll, denn letzlich könnte ich dann nur mit OAM Karten arbeiten und ausschließlich das Theme wechseln, um generell die "LoMaps Optik" zu bekommen.

Hat sich da mal was geändert oder fehlt mir eine entsprechende Einstellung?

LM 4.17.2 Gold, SGS10