Messages

"Siehe! Ich bin meiner Weisheit überdrüssig, wie die Biene, die des Honigs zu viel gesammelt hat, ich bedarf der Hände, die sich ausstrecken.
Ich möchte verschenken und austheilen, bis die Weisen unter den Menschen wieder einmal ihrer Thorheit und die Armen wieder einmal ihres Reichthums froh geworden sind."

Also sprach KodelaZarathustra.

Mir ist unklar, warum Beziehungen wichtig sind. Presets gehen in eine Richtung und ich finde das auch OK so.

Ich ahne, nach kurzen Kopfschmerzen, worauf Du hinaus willst. Presets sind eben eine unbestimmte Menge, die wird ausgekippt, während der nicht angefasste Rest historisch und unbestimmt bleibt.

Ich schlug einmal vor, jedem Preset die Möglichkeit der Vererbung zu geben. "Basiert auf...: Preset XY". Technisch wendet Locus dann einfach zwei Presets hintereinander an.

Man kann sich dann umfassende Basis-Presets erzeugen und spezialisierte Presets, die darauf aufbauen.

Menion wollte das System aber einfach halten. Ich denke, es bleibt einfach. Es unterstützt sogar das Verständnis. Denn initial würde folgendes angeboten: "Basiert auf: <Aktuelle Einstellungen>"

Did you already find https://github.com/mapsforge/mapsforge/blob/master/docs/Rendertheme.md
?

Fight, compare, create valid xml

Re: Bookodela: HiLo ist sehr alt, upgedatet 2017, sicher nicht MapsforgeV4+. Da würde ich den Autor kontaktieren. Oder andere Themes nehmen, es besteht ja kein Mangel.

add: option to set an individual track elevation threshold - customizable optimization of the elevation gain (Expert settings)

Some background info please? Hasn't this been discussed somewhere here?

I noticed, initial threshold varies, on what basis? Changing threshold can change elevation gain drastically.

For those who didn't find yet: set setting according to screenshot, then you have a slider in 'edit info' of a track...

Freischneider is talking about OFFLINE maps from openandromaps.org. A good advice.

As I understand you, you talk about "point simplification", where at lower zoom levels the symbols turn to dots.

There is a setting in Android/data/menion.android.locus/files/config.cfg

Search the file for:
map_items_points_simplification_till_zoom

But my main point is not, if city names are shown until a high zoom level. It's personal preference.
My point is, there's some uncertainty of them not showing up as in the example @ZL12 OAM Germany.

I mean I can handle it now. I want perfection here, which is possible and oh, how I hate the old days, where cities/towns sporadically showed up. Endless priority tinkering and still a local Kindergarten name was shown instead of Berlin.

At this level, the name of the city is definitely not needed.

I prefer it. Paper map vibes, where the town name is on top. For detailed POI analysis I may zoom in more or use database anyway.

I'll take a look, but for now, I won't always use display=always. I like my variant so far. The name of the town is now shown at level 12, IMHO this is enough and I have not seen such a glitch anywhere else.

OK. I personally don't see a problem in display=always on town names, for me it solves problems... but I can always edit myself then.

The rule doesn't apply at all (I tested with some ridiculous font sizes), but I don't know why.

display=always doesn't help, the name of the river removes the name of the city.

I disagree, it's the whole option you added, that had no effect. I added display=always in all your recent versions to towns, and it worked. The town name got written on top of the river.
As in my attachment.
IMO it should be added to place=capital?, town, city and village.

As you can see for yourself, the option (display=always) is there, but it doesn't always work. Maybe someone knows the solution, but I do not.

The rule doesn't apply at all (I tested with some ridiculous font sizes), but I don't know why.

I think we don't understand each other. You wanted display=always for place=town and I made it optional, enabled via the menu. And as far as I checked, it works. Or do you want something else?

We're talking about the same. I checked it, and it doesn't work for https://forum.locusmap.eu/index.php?msg=71108 (it's with the full OAM Germany map) - The Town is Lüdinghausen, it's not displayed on level 12 so this cannot be "display=always".

Look at the last menu item: "Always show the name of small towns (12-16 levels)"

Thanks Andrey, good option, but that doesn't solve the problem above in https://forum.locusmap.eu/index.php?msg=71108 - which requires 'display="always"' additionally. I think, in case of town names it is a must-have, they should never be victims of priorities or paint orders.

Am besten bei Brouter nachfragen. Die haben bestimmt ein Forum.

https://groups.google.com/g/osm-android-bikerouting
Man beachte den Namen *hinthint* 😁

Sure, the complete one should be the "Automatic backup" and "Manual backup" should serve as an occasional backup system or for easy sharing of certain content between apps.

No, here it's vice versa. Regular auto backup is without the database, because of permanent settings tinkering.
Full backup only manually.

But I backup the auto exported GPX, so in case disaster there's the missing tracks.