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.

Messages - Christian

Pages: [1] 2 3 ... 52
Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )
« on: October 12, 2018, 22:37:53 »
The value of elevation gain in Route Planer is much too high. After saving the planned track the new value looks better. Approximatly -20% than in Route Planer.
Minion - may i ask you to fix this because i use Route Planer in the field often to get quick information to decide to go right or left without saving the track.
Thank you.

V 3.33
mit der neuen Version hat menion das "Development menu" auch in der offiziellen Version freigegeben ;D
Nach einem langen Klick links oben auf den "Hamburger Button" erscheint dieses und man kann u.a. die "Experimental settings" ein/ausschalten ;)
nach dem Einschalten erscheint unter "Einstellungen" ganz unten "Experimental" und hier kann man u.a "Confirm on exit" einschalten
Dann erscheint beim "Beenden" wieder die Schaltfläche 8)
Danke für den Tip.

Kann man nicht mehr einstellen. Ist wegrationalisiert worden. Du kannst das im aktuellen Versions-Thread reklamieren.

Ich glaube, ich habe das Problem gefunden:
In der Doku steht:
"Der Trackpunkt wird in einen Zwischenpunkt umgewandelt mit einem neuen Hilfspunkt dazwischen"

Da fehlt ein Satz, wie "Wenn Sie an dem Hilfspunkt ziehen, wird eine Neuberechnung zwischen den zwei Zwischenpunkten durchgeführt.".
Also nur den Track in den Routenplaner laden langt nicht...

Kann ich nicht erkennen?! - ein aus dem Routenplaner exportierter Track ist wohl kleiner, verläuft aber über dem zackigen Original.
da läuft irgendwas schief. Lädst Du einen zackeligen Track in den Routenplaner, setzt Zwischenpunkte und läßt Brouter neu berechnen? Dann solltr der originale Track schön glatt übrr die Wege verlaufen und auch die richtigen Anweisungen haben...
Zeig doch mal ein paar Screenshots.
Es gibt in Locus ein paar unausgegorene Funktionen, aber diese gehört definitiv nicht dazu.


Das "bindet" verzackelte und totkomprimierte Garmin-Tracks wieder auf die Wege. Die Infos dazu sind nicht in der Karte sondern in den Routing-Dateien.


Hier wünsche ich mir mehr Bearbeitungsmöglichkeiten von Tracks. Glätten nach Algorithmus, oder anpassen an den Weg auf der Karte...
Das macht der Routenplaner, wenn Du den Track da reinlädst. Bei der Gelegenheit kann man auch gleich gescheite Anweisungen generieren lassen - solange die Routing Engine "Brouter" heißt...

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 18, 2018, 13:47:31 »
Is the 'confirmation on exit' back in the Beta?

Troubles & Questions / Re: Kilometers of track
« on: August 09, 2018, 19:16:06 »
Thanks. Voted.

Troubles & Questions / Re: Kilometers of track
« on: August 09, 2018, 10:37:54 »
There is no such a setting to display distance marks automatically.
I would like to use it also. You can put this as an feature request on the help desk.

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 07, 2018, 15:24:35 »
So both GraphHopper and BRouter should return computed ETA times and the app should only modify these values little bit based on previous user activities.
I'm not sure about "the app should only modify these values little bit".  There is no absolute truth in calculated ETAs, looking at the users tracks will not help, our actions may be too versatile. You add unnecessary complexity.

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 06, 2018, 21:27:45 »
I've read about the swiss formula; looks like we need a realistic example here. I've searched quite a lot and did not find what those magic constants are.

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 06, 2018, 18:35:40 »
Interesting algorithm, I tried to insert my current trailrunning data and return a satisfactory ETA. Maybe the fatigue factor is missing, as the number of kilometers increases or the difference in height takes over the fatigue that makes slowing down, while the proposed formula is linear, the reality is a curve.
Obviously you have to compare similar data to get reliable results, you can not enter a time on 100 meters to look for time in the marathon.
However, it has a very good approximation to reality, thanks.
You can use the swiss formula and you will geht mor accurate values.
Code: [Select]
t_t0 = {L · [C0 + (C1 · S) + (C2 · S2) + (C3 · S3) + (C4 · S4) + (C5 · S5) + (C6 · S6) + (C7 · S7) + (C8 · S8) + (C9 · S9) + (C10 · S10) + (C11 · S11) + (C12 · S12) + (C13 · S13) + (C14 · S14) + (C15 · S15)]} / 1000
(L = Horizontaldistanz; S = Steigung; C = Konstante)
And you can insert conditions of the pathes into the formula also / or use different values for running and trailrunning and alpin trail running...
End of OT.

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 06, 2018, 18:29:19 »
Tapio was faster then me. The hint for the DIN in Germany and for the original Swiss Standard is here on the right place. Thank you for this.
I have a huge database with all my activities including times and elevation, distances etc. And also a simple tool in Excel to calculate the needed time based on the DIN Standard. Computing the average of the appropriate values of my tracks from my db leads always to wrong values, only the values computed from the DIN are right.
The ETA value in Route Planner are always empty in my case because mostly i use a mix of profiles and sometimes the designed tracks are from Brouter Web or i use profile "hiking beta" oder another custom profile template for mountain biking. So no information about the used profiles are available / reliable and the ETA function are not available to me :(

I want Locus to be the "Swiss knife" for my purposes = all-in-one tool. The ETA / needed time is one of the key features i need for planning my routes. Just now i do this within an Excel sheet (and link / compare the values with the time between Sunrise / Sunset <- this idea is free of charge for menion). I would like to have this stuff inside Locus and in a way that work (from within the first track). So @menion, please check the Standard and check your algorithm. Please give us the overkill of "setup of climbing/descending/flat speeds" because it is the only way to get reliable values. Thank you.

For those who are interested in the meantime in calculation. xls or online
I adapted the values in the xls sheet for biking, trail running a.s.o. Works fine.

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« on: August 02, 2018, 22:48:02 »
why you need this confirmation dialog? We removed it as non-standard, useless feature. Does it have any possitive effect on usage of app for You?
The dialog prevented unwanted exit by tapping back buttons by accident with wet fingers, gloves or when out of breath and have shaking fingers. To have to restart Locus in the wild when i only wanted to have a look on the map is a real PITA and should not happen at all.
I could not find any user request to remove this nor a poll either.
The confirmation dialog is an essential thing in Locus like running as a service imho. So please bring it back.
Thank you for understanding.

Pages: [1] 2 3 ... 52