Messages

@tapio

Genau das ist es....ich habe die Linien deaktiviert.....

Danke

TAPIOLA theme ;-)
love it

I also really like the new content. Especially the track hiding. And so that you can omit certain areas altogether. Since I don't use the shading normally (only makes sense in the mountains). Would be nice if you could also deselect that.

[Beta version 4.17.1.3]

New Beta version with some fixed crashes etc. and mainly a new side map-content panel with hopefully useful improvements. Feedback is welcome of course, thanks.

Beta version 4.17.1.3, download.

[few new DTMs have been released]

Just an update:
Quite a few new DTMs have been released during the last months, especially in Middle- and Eastern Europe.
Have fun with them!

[_]

@john_percy
The naming convention for "poi" theme is nameOfBaseMapTheme_layerId.poi.xml
When the layerId id of layer is defined in <stylemenu> of the base map theme.

Anyway, only the internal theme supports this special "poi" themes. It is not yet fully implemented for alternative themes, but there are plans to support it...

@Tapio
Please see https://github.com/asamm/lomaps-mapsforge#poi-themes

Very interesting! I came across this discussion by chance only a week ago.

I myself had noticed only a few weeks ago that Locus suddenly caused very high battery consumption, always when navigation and/or track recording was running. On day trips, a power bank had to be connected after only 3-4 hours.

Now we were hiking in the Liberec area (Czech Republic) for about 2 weeks. Very beautiful area by the way! Every day with track navigation along planned routes and track recording. Strangely enough, there were days when the battery lasted through the day without any problems, but on other days it was already empty after a few hours.

After reading this discussion I remembered that in March I had downloaded the 1" files of the elevation data (24.7 MB each) for the whole of Germany from Sonny, which coincides with the beginning of the high battery consumption.

These were not available for the Czech Republic, where I still have the small 3" files (2.7 MB). 

Now the region west of Liberec is still covered by the Sonny file N50E14.hgt, while those from the city and further east are covered by the 3" file N50E15.hgt. And indeed, it was the tours in the west (Ještěd Mountains, etc.) where the battery consumption was extremely high. In the eastern Jizera Mountains, the battery lasted the whole day.

I would never have thought that this could be the cause without these posts on the forum. I then replaced all the 1" files with the small 3" files and the battery consumption was normal again. Even with another hike in the N50E14 range. 😊


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

[version 4.17.1/3.68.1]

Hi guys,
bug-fix version 4.17.1/3.68.1 published!

Can you tell, what and if there are general differences and what they are about?

Contour data is very different, OAM is much more accurate. Lomaps needs to be zoomed in closer to see "meadows" etc. The same with buildings. Some tags are missing. OAM has tricks so that the name on one large object (for example - lakes, islands) is drawn once, there is no such thing in Lomaps. There are no island names if this name is specified not directly ("place=island"), but through "Relations" (type=multipolygon).

If you are using my theme, then you do not currently have the names of lakes (all).

@Menion: I rushed to see the results from taking the Tab S6l config, so I did not care about wrong paths (EXT SD IDs of course differ). After the that test I started to correct the 4 of them:
1) backup - no problem while processing, neither after restart
2) maps - on the Tab (small INT SD), this is on EXT SD; on S10 it used to be in the main Locus folder (INT SD/Locus). Processing: a list of maps, well known to me, runs across the screen; after restart, maps is EMPTY !! (Real losses, as I did not expect such and did not backup those upfront)
There is definitely a logic error. Locus must NEVER delete anything from the target folder; IN PARTICULAR if the source is non-existent!
3) mapsVector - same amok. That one did not hurt, because it were LM3 maps, supposed to be updated anyway
4) srtm - OK, like #1
So I have been busy for a while ...

Config difference analysis to come later.

Sorry, I completely forgot to upload the graphics for OSMC. Hopefully now corrected!
Screenshot is v5 on OAM on my phone, so it does work!

Locus Map icon? 

[Locus Map (4)]

New Locus Map (4) version

Important links
- list of news of public versions
- Public versions
- Beta versions

Versions
16. 5. 2023 - Locus 4.17.0
24. 5. 2023 - Locus 4.17.1
15. 6. 2023 - Locus 4.17.2

[@joeloc]

Hi guys,
some crashes and problems/questions regards the search should be solved or discussed by Marek and Radim in a separate topic. Thanks for your help here!

---

@joeloc
- so the last used point folder will be saved only when you confirm the point to edit.
- recording button with 50% opacity > I think this still won't solve your "burning" issue, so the best is really using a side panel with an auto-hide option.

So the only that remains is the copyright button ... hmm, there will be also a solution I believe.

@balloni55
notification on the new Beta version is not available, but I more and more think, it will be needed. Also for the AFA version!

Adding a "hidden WPT" > interesting. I have no such problem. May you post a GC code of the cache so I test it on the same point? Is it downloaded over Locus Map and stored in the database?

@CabrioTourer
thanks for the detailed description of the "double-point problem". I've noted it and will look at it.

@Viajero Perdido
All themes were temporarily removed from the Locus Store and @voldapet is migrating them (or helping theme authors migrate) to the new V4 system.

Also, I really would like to add more nice themes to the Store (mainly now, when the system for themes is identical to other apps), so anyone interested in publishing theme over Locus Store, feel free to contact Petr.

@Tapio
side "Map content" panel is in rewrite - it will be introduced in the next version.

@TrulloF
I'm a little lost here. The first screenshot is a new LoMap with offline LoPoints? Where these icons are from? . Looks like your own personal points.

@Michael Bechtold
Eh, never saw such a destroyed device ... I forget to respond to your email from April, sorry.
There is nothing to see in the log and can't imagine what the app has to do, to consume 24% of battery/h when the screen is off and the battery is disabled. Maybe if I integrate some Bitcoin miner, but it isn't there, I promise.

The app consumes so much battery for you even during normal daily usage? So even if you simply open the app and just watch the map?

If I explicitely search for health, then I explicitly search for health. Sure, there might be a pet shop nearby. Honestly I currently have no idea of an usecase of such extended results without any differentiation.

Ah, then it is something else than to what I replied before. You are referring to cumulating child categories under "top level" one like "Health", which are all highlighted in such case, I get it now. Yep, there is some definition of hiearchery of POIs categories, which we might review based on such feedbacks. Thanks

Clicking somewhere else was intuitively to get more map screen space, no bottom point detail, and also by mistake, sometimes i don't hit a POI precisely.

I understand what you mean now I think. Yep, when you are in search screen, you will "lost" it when doing long-press only, however when in POI detail from search, short-press cancels everything. This is by design, as when users are in POI details, most likely higher probability is they already found what they wanted and doesn't need to go back. This of course brings mentioned issue for other cases, where they want to go through more POI details listed in search results. We will think about this.

I noticed it zooms to the first result

In case you don't go directly from suggestions to POI/adress detail, you will always have even your previous map position on screen when opening search results exactly for reasons you mentioned: To not loose idea where nearest results are related to your previous map area. So the map area is calculated to show your your previous position and nerest one now with same safe margins as most general behavior rule to any search case. Before we will as planned split it to more distinct behaviours based on spread of search results.

POI on the map do not open.

That is not correct behaviour - can you please record screen video of this? I can't simulate it.

Also with search: Fountain I would like C. Drinking water and C. Source. At the moment there is no category at all.

As Radim wrote, that thesaurus file is something else than defined hirearchy of POIs.
1) If "fountain" word is used in the german, you should get related fountain category under this search. That is to be added to thesaurus file.   
2) What other categories are related with category fountain are based on defined (somewhere else) category hirearchy. We  welcome  all specific suggestions here, but please keep in mind that they might be highly subjective. I definitely don't think that "drinking water" category should appear under "fountain", as this is not case in real world in many places of earth.