Messages

I do not want so that important users (geeks) are annoyed and jump off.

Nobody jumps off or should jump off just because of search. And there's no alternative to LM anyway. People shouldn't forget what we have.
Personally I don't care about the new search too much. For some reason, I don't like the presentation of the new searches results.
Offline POI handling needs improvement, Menion knows that.
I either use Gmaps->Locus or do Nominatim based search, Tasker->Locus.

This is not practical. So the user must first set the zoom level and can only then search.

No I'm saying it could use the maps current zoom level (and map position) for its priority decisions. But well, they may already do that.

Maybe zoom level as an indicator of users scope wish? Zoom level low: User likely wants to find "New York City" in the US. ZL high: wants to find the local "NYC brothel".

Works fine (Google Drive app), I was just stupid and checked the beta folder instead of the release one.

https://forum.locusmap.eu/index.php?topic=8572.msg72908#msg72908

OLC Search (4.18.1) failure:

HGVV+465, Lünen - not found.
should be
51.592763,7.543109

but tell that to the confused user - what is the purpose of the "Share" button otherwise?

Transporting one fixed format information to another user. This cannot work for inter-app communication, with target app being an unknown entity for the sender.

What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

++
You may be interested in my Pluscode<->Latlon converter. Supports both types of Pluscode. Works locally, except Pluscode with city name needs a www lookup.
Intermediate Tasker users will know how to use this function. https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Task%3AfGPS_Pluscode
See: https://youtu.be/N5vhMGWpFs8

You have to change encoding to utf8 before saving. It's under the triple dot menu on the top right.
I think your situation is probably recoverable

Edit2: Set "default encoding" to utf8 in settings, instead of auto detect. Works.

I've added emojis to the latest release.

the slope is mostly green because there is a segment with a huge slope value. So a limit to -50/50% is necessary.

Ah, yes. Those local extrema easily make auto slope color useless, maybe let algo look more broadly?

There's no 100% right or wrong but yes, drastic differences. You noticed the "Altitude threshold" slider in track options? That's the recent change in LM.

Let's just talk about that fixed track from OA. I have attached it.

And there is a bug. I have attached it slope colored (auto range) and the result ist mostly green.

If anyone has experience with emoji representation in text files, I'm all ears. Quickedit+ now slaughtered it after I included them. It picked Windows-1252 encoding and now see screenshots...

Latest Google Maps. No improvement with Share to LM4. Exactly the same poor behavior.

But in the other thread they said it's fixed - new version just isn't out yet.

v1.2.6

• Renamed "Power lines" category to "Electricity". Included wind turbines.
• Roads and railways can be turned off.
• New icon for watering_place (Requires delete cache in Locus settings).

I think Wind Turbines are currently only in Lomaps, didn't check yet, if maybe they're in OAM under a different name.

I've created another icon for watering_place.

I allowed turning off roads and railways . So we can exclusively display whatever we wish. Why? Analysis purposes maybe. Or because we can! See screenshot with only railway and only hiking/cycling routes.

Changes are uploaded, but not in the release yet.