Messages

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

In the ideal world yes. But we noticed that OAM use some hack and special tags so the content of this file won't be identical ... for now ... unfortunately. It is not on me, but @voldapet should discuss this with anyone responsible for OAM maps and unite map content. Ah, this should be amazing 

I'm biased, as you know, but I think that Christian's tag mapping in coop with Tobias' themes is more powerful and comprehensive than LoMaps. voldapet should reach out to Christian ...

You needs to append your information to providers.xml file mapsOnline -> custom. Existing entries will tell you formats etc.

No version of Locus Map supports ".poi" files. As far as I know, OpenAndroMaps provide also ".osm.db" files that should be most probably supported on your device. These files brings support for offline LoPoints and offline address search.

Yes to statement #1, but there is no address data in the OAM osm.db files, only the OSM POIs

I'm curious if this "high quality" line breakup/hyphenation from Android (see github from other thread) library will deal nicely with geo names like in your examples ... :-)

...
How "position" works together with wrapping may be visible in the new pull-request here.

@Menion: I suspect you are employing the Android high quality text break feature now; right?

Hi Menion, appreciate the new algorithm. And there are parameters that control this algorithm. Those 5m you mention are not carved in stone, but could be an expert setting. So people can change according their liking - and take responsibility for the outcomes themselves :-)

PS: I just scrolled through the MOBAC OUTPUT formats: while I do not know all of them, they all smell like raster maps (with different image format outputs and wrappings). But of course Mapsforge INPUT can be processed by MOBAC since many years.

OAM does suffer from the effect. Screenshot is Germany/NRW OAM with VolUK theme.

Seems I checked in the wrong places :-)

Fully agree - one text input field only.
However, sometimes there is a reason to restrict scope (latest when you are swamped by the all-in results.
Hence, there should be a expando below the text field, that has all buttons ticked by default, so people CAN restrict at will, in case of need. The buttons may mimick the current list of search sources.
Just my 2c :-)

You will also need to improve search. It should work simultaneously in addresses and points.

I completely agree. Locus search is pure usability horror from last century. A proper search is ONE SINGLE TEXT FIELD that simply searches EVERYTHING at once and shows results as they come in.

Making me decide in advance on where I want to search is just wrong on every level imaginable.

Question: as LoMaps are going to be MapsForge 4+, they would use the same engine as e.g. OAM, right?
Yet, OAM, does not suffer from this effect.
On the other hand, the font sizes of these run-away texts are extreme. Font sizes, however, are defined in the theme XML.

Correct. In case of OAM maps, the level of detail is higher (contours, if I recall correctly, plus something, on lower zoom levels) for the Alps map(s), compared to Italy whole.
Same is true for Bundesländer versus Germany south/mid/north, and Germany full. The difference between Bundesländer total versus Germany full is one GB, which not only comes from Bundesländer overlaps.

There must have been a reason to download overlapping maps in the first place, I suppose. Based on my own experience, having both (or more than one in general) does not really disturb, except you see them in the "nearest map" list.
What do I miss here, @Borger83?
Cheers
Michael

I'm not suffering like Andrew did, vector and raster maps fast and smooth. However, all vector maps show up in maps manager and in nearby list THREE times. I've imported one V4 LoMap and only then noticed. So I cannot tell if that issue was present before tth import already.
Regardless of the beta pain to come still, I'm happy about your contributions to MF and the move of LoMpas to V4. I.e. pain well spent :-)
Cheers
Michael

I've been using both, the Personal and the Supplementary download feature successfully recently. And I just checked on my Tab S6l which got Android 13 recently: I can navigate freely where to put the target.
Yet, a couple of things:
- while I'm using the AFA version, too, I kept the Locus root at IntSD/Locus, which makes life much easier
- in any case, with x-plore you can copy/paste/move files from, in and into the private /Android/data structures at will (after granting all the permissions)
Cheers
Michael