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 - michaelbechtold

Pages: [1] 2 3
Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: November 03, 2017, 22:56:58 »
Oki, thanks Michael. I'm surprised, there is any difference as I expected, results will be exactly same. I'll check it ...
The following users thanked this post: michaelbechtold

Troubles & Questions / Re: change number of top panel buttons
« on: September 21, 2017, 11:44:01 »
Here is simple improvement - I love the right hand side panel - you can add any number of buttons and simply drag up or down to display all those buttons. A hidden feature! So why not use similar system for top panel buttons? My topic has 8 votes.
The following users thanked this post: michaelbechtold

Troubles & Questions / Re: Annoying default behavior of WP/Track "Edit"
« on: September 12, 2017, 08:47:32 »
+1  The same thing when exporting a recorded route.

IMHO this is not exactly comparable.
Exporting/saving a new item usually follows a certain workflow that begins with providing a name for the new item, as you typically want to replace the auto-generated Date-Time Tag. So having everything set up for entering a new name is desirable here. My trouble occurs when working with existing items.

But in my particular case you are even right. Often, when I stop recording a track in the field, I am very bad at typing: fingers are wet or dirty, the display may be covered with raindrops after a bike ride so you cannot type well or  I may simply be too exhausted after a run. In these cases I initially accept the auto-generated name and just save. Later, in relaxed and dry conditions I make the modifications. So yes, even when newly creating a track/WP/route entering a name may not be the thing you do by default. But here I admit that this is subject to personal preference.
However: not so for the edit-later case, this really should be changed.
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: July 19, 2017, 07:59:04 »
@balloni55: complicated task ... what about people (I believe most of users), who does not use "Presets"?
I'd strongly advise against removing customization options just because they're also doubled in the presets feature. As Menion says, many users, especially beginners, won't use presets, so they'll be put off if they don't find an intuitive way to change the buttons or other settings.
Granted, as is obvious even among us power users, the presets feature is easily mistaken for a "profile" feature and therefore misunderstood. However, it is what it is now and should stay like this - once you understand it, it can be extremely useful. But those who don't use it shouldn't "lose" anything!
The following users thanked this post: michaelbechtold

[DE] - deutschsprachiger Forumsbereich / Re: Punkt eingeben
« on: July 16, 2017, 15:53:50 »
Danke. Ich nehme an, dass Du "Karte verschieben" meinst, anstatt "Gehe zu" ?!


The following users thanked this post: michaelbechtold

Discussion/New features / Re: Offline POI database
« on: July 04, 2017, 06:04:27 »
Menion, are you working on the POI system? I think the current state is something that can be improved. E.g., loading 100 by 100 is not perfec and rather clunkyt, also loading POIs in a radius around the center is not perfect, while POIs along a track are of interest... Hey, Locus could, as a track option, auto load POIs in a radius around the track... Probably a can of worms :D Are POIs your unloved child ;)?
The following users thanked this post: michaelbechtold

Since a while Mapsforge offers the priority key for better arranging tags like town names before other tags.
Is it possible to implement it into Locus maps rendering engine?
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 31, 2017, 14:46:33 »
No serious news in latest version, but still some usable improvements I believe. Hope you will enjoy new 3.24 version. Thanks as usually for a very valuable feedback! Seems that time for more active lifestyle again comes ( more friendly temperatures ) in Europe, so hope you find Locus Map useful!
The following users thanked this post: michaelbechtold

Ich denke, die Routing-Dateien von BRouter sind stets aktueller.
Selbst nutze ich seit Jahren LocusPro + BRouter, ...das Paket hat mich überzeugt.  ;)
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.22.+ ( 7. 3. 2017 )
« on: March 10, 2017, 09:06:32 »
@twil69 - the notification button is not permanent - I'd complain too if that were the case. Easy to dismiss any new items and button will hide. Don't stress too much.

Well, technically you may be right.
But lor74cas described quite nicely what will happen most of the time: this thing will disturb you when you have no time to deal with it and just want it to go away. And when you do have time you will not remember.

So it is more about the perception as something useful or something annoying. And since there are established notification alternatives (that most apps seem to agree upon) I dont see why Locus needs something different.

I always prefer pull mode (deal with things when I have time for them) instead of push mode (being interrupted).
The status of a download is visible in the Android status bar and when I want to read the Locus blog I go to feedly. Everything is already there. I personally dont need more. But let the user community decide.
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.22.+ ( 7. 3. 2017 )
« on: March 09, 2017, 10:17:35 »
All settings in apps has it's unique key and value values. These has nothing to with texts that user see on screen. These texts are generated on the fly in moment, they are needed. And they are needed in moment, any screen from settings is visible. So this whole system needs to write somewhere list of all preferences that may appear on screen, get all possible texts for them and then iterate over these texts and test them. I have partially useful solution thanks to new presets system, but there is still a lot work to do, because almost all settings has to be changed to new system (while currently only around 10% was rewrote).
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.22.+ ( 7. 3. 2017 )
« on: March 09, 2017, 08:46:56 »
You eventually added Profiles/Presets!  ;D
Garmin has this in the Oregons since almost a decade and I was always hoping that this would be offered for Locus as well. Given the overwhelming plethora of settings this is only a logical step. How often did I find myself roaming the settings tree to find a particular knob. Worse, the settings tend to move every now and then, so you need to memorize where they currently are. Since I use locus for geocaching, bike riding, running and hiking each time I changed the activity I needed to tweak the settings. Now consider you are e.g. on a geocaching tour by bike.... :-\
Definitely will give (custom) presets a go.

What I dislike is the notification center. I bought Pro to get rid of ads and now it sneaks back in by the app itself. Other apps also manage to notify you without cluttering the main application. I am fine with the Android notification bar, I dont want to waste precious real estate of my screen with a permament button. Please make this an opt-in instead of an opt-out.
The following users thanked this post: michaelbechtold

Hallo, ich versuche es so "kurz"  ;) und verständlich wie möglich zu erklären:

Für jene Gebiete wo es bereits meine LIDAR-DTMs gibt, z.b. für Österreich , lädst du dir jeweils die 1"-DTM runter. Hier findest du übrigens auch einen Link zum Kartenvergleich meiner LIDAR-Daten zu denen der SRTM-Kacheln:

Das 1" ist das genaueste DTM, es gäbe auch noch die 3" die aber ungenauer sind. Mit den 20m und 50m-DTMs kann Locus sowieso nicht umgehen.

Du entpackst alle Dateien und schiebst die .hgt Dateien rüber in den data/srtm-Ordner von Locus. Dort liegen ev. schon Dateien mit dem gleichen Kachelnamen drin, die überschreibst du einfach, denn dabei handelt es sich vermutlich um die "alten" wesentlich ungenaueren SRTM-Höhendaten.

Sodala, da war's schon. Ab nun nimmt Locus zur dynamischen Anzeige der Höhe deiner aktuellen Position ("Dynamic Elevation", zur Berechung von Höhenunterschieden eines Tracks, zum Erzeugung der Kartenschattierungen ("Map shading") dieso genauen Höhenkacheln her.

Diese Höhendaten sind so gut wie immer genauer und zuverlässiger als die Höhenbestimmung per GPS oder auch per Barometer (dieser folgt zwar Höhenänderungen sehr genau, muss aber manchmal nachkalibriert werden, da sich der örtliche Luftdruck ändern kann).
In den Locus-Einstellungen (Menü > Settings > GPS > Altitude manager > "SRTM DATA" kannst du einstellen:
"Optimimize GPS values" (gerade in Zusammenspiel mit einem Barometer sicher eine interessante Sache) oder gleich "Replace GPS values", dann werden ausschließlich diese Höhenkacheln zu Höhenberechnung herangezogen.

Etwas anderes ist die Lage für Länder, wo es solche LIDAR-basierten DTMs noch nicht gibt, sonder nur die SRTM-Kacheln. Diese können zuverlässiger sein als GPS-Höhenempfang, aber auch ungenauer sein, da die SRTM-Kacheln stellenweise Abweichungen von 50m,100m oder mehr haben können, z.B. im alpinen Gelände, in Schluchten etc.
Speziell in gebirgenen Regionen und/oder dicht bewaldeten Flächen würde ich hier zuerst auf barometrische Höhenmessung zurückgreifen falls im Gerät vorhanden.

Zu deinen Zusatzfragen:

- Es kann immer nur eine gleichbenannte Kachel geben und diese erwartet Locus im data/srtm ordner.
Dabei sollte es sich hier immer um die genauest möglichen Kacheln eines Landes handeln (1"-Lidar besser als 3"-Lidar besser als 1"-SRTM besser als 3"-SRTM)
- Wenn du einen Track z.B. für eine Navigation im Vorhinein erzeugst, dann basiert das Höhendiagramm definitiv auf den Höhenkacheln.
Wie dies aber bei der Aufzeichnung eines Tracks ist während du unterwegs bist, weiß ich nicht. Entweder es werden auch hier standardmäßig nur die Höhenkacheln genommen oder aber jene Höhe die Locus live ermittelt anhand der obigen einstelllungen bei (Menü > Settings > GPS > Altitude manager > SRTM).

Müsstest du menion dazu fragen, oder jemand anders der das weiß.
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.21.x (21. 12. 2016+)
« on: February 20, 2017, 01:03:47 »
Vector maps have themes which have different style options, selected either by drop down menus or check boxes.
ahh yes, excellent suggestion to add these settings to (advanced) presets
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.21.x (21. 12. 2016+)
« on: February 19, 2017, 11:09:03 »
For presets, can we have styles as well as themes, please.
The following users thanked this post: michaelbechtold

Pages: [1] 2 3