Messages

Hi luxacalor,

I guess you mean the the screenshots of my latest draft of the lomap/oam v4 map theme.

It is pretty close to release now, just working on the pdf legends and final few fixes to the theme.

I was going to update the v3 theme to match, but with the v4 lomaps out now and the difficulty of doing this with less tags available and lack of time on my part, I think I'll leave the v3 map theme stay unchanged.

There is one thing I can't get to work on my phone, using zipped themes. Should work as I have latest Locusmap and android 11...

Watch this space for the new release.

There are no such settings that may increase GPS frequency. There exist external devices, like Garmin GLO and some other, that allows increasing frequency to 10x per second.

Anyway, if the problem you "feel" is really only a movement that is not fluent ... in other apps, they most probably do transition between two locations with map animation. It does not give any extra accuracy or more frequent location > it "only" polishes usability a little.

I was already thinking about it some time ago and decided, that battery is priority no 1.

---

Let's try a quite simple attempt ... next (Beta) version, Expert settings, a new option "Fluent movement". It changes a simple jump between coordinates, to a small 1/4 sec long animation. A one second-long animation does not make sense, because in the end of animation, the location will be almost one second old. So 1/4s is a good compromise and it looks quite good.

---

And usage ... 25% of users use Locus Map for cars & motorcycles. So it is not so simple. We try to focus on hike & bike > This means that when I have to decide something, I optimize the app for the hike & bike rather than for the cars, but ... 

Understand, but this defines the time after which the map screen center returns to the current GPS location (center map) after you move with the map to a different place. It does not affect the movement of the map when centered (so during navigation etc.).

My explanation is probably too complicated, sorry 

I need the Afa Version and get into trouble when downloading from Google Drive.
Hitting the download button effects nothing and clicking the linktext leads to a 404 Error.

I have checked it with every browser on my phone.

@joeloc @michaelbechtold

Guys, I think you already forgot that our old search definitely wasn't the same as the one available in Google Maps app/web. You describe it as it was and we ruin it with new search. In fact, that "bike shop" example was completely unusable before as it is now. I understand what could be the ideal state, and believe us, we know the importance of the search capability.

So,
1) The new search what we introduced this year is far from final. Even thanks to your feedbacks, we have clear vision what should be our next steps in order to significantly improve it. But for summer, we had to relocate our limited resources also to other tasks. We plan to get back to it during fall.
2) Yes, it is technically possible to implement Google Search/Maps API (not the one which was in app before), but if we did "just" that, it would bring several MAJOR downsides for us, not mentioning that it would still don't fully replicate search experience as on Google Maps. Some of these are for example limitation of use by only portion of our users, queries limits, inability to search our own/future content and interconnectedness with it, costs, and so on. So we anyway had to start with revamping our own search platform from the ground which will be able to get several search feeds together. What you have in the app now is its first iteration.
3) iOS is definitely not the reason why we choose this path, it is much wider than that. Remember, to find shops in the city around you, Google will always be ahead of us. We are not aiming in exactly same direction as they are. Only after we reach the point when we are unable to do improvement on top of current solution and still be too week in some search use-cases, we will merge it with another search provider to get better results.
4) Smart search MUST be able to return result >1000km far away if it might be relevant. You can already filter results to your map area. I don't consider this to be problem, I believe all issues related to this is rather that search is unable to find places what you expect to find (for example those around you). And this is matter of improving search in general. 
5) There are few main areas to work on now.
- The current implementations of POI category search and search by POIs names are too separated now
- improvements of "search dictionaries" so it will better understand what user want to get
- better data for determining POI significance.
- better work with different languages
These might have significant impact, but they will be tough to conquer, so which us luck.

@Andrew Heard
6) Topic with sharing data from Google Maps is only indirectly relevant with search capabilities. First, it is not "meant" to be used this way - it is implemented primarily for sharing data via emails/messages etc. where receiver ends up on Google Maps again. Note, that not many of other navigation apps registers this command and shows itself in such sharing dialog. Locus Map is, and we are trying to overcome this by parsing provided data and in case we can't determine its location, we throws its name to search.

But Google recently changed something and what previously partially worked now throws unusable URL to search field. Current app version didn't change anything in this and as Marek stated above, he already fixed it again for new upcoming version.

As stated above, our priority is now to get better search relevance on top of data we are working with, which might increase change you find shared location from Google Maps in Locus Map. Indeed parsing name from Google Maps might probably work better even with old Google SDK which we used in the app before. On other hand, we will have hard time to pair the result with data of POI in our DB with this approach. So the final solution to this remains to be seen, I can assure you we are aware of your feedback in this.

I think it is time for a drastic correction of approach here: whatever you do for iOS should not screw the 100000s of users from whom you make your living.
As long as the new search function is not professional, give the Android users back the Google based search.
Equal functionality is not a valid argument against this request, as the iOS version will lack essentials for years to come anyway.
At least give the existing and fully functional Google based search as an option to your (Android) users, PLEASE!

[Locus Map (4)]

New Locus Map (4) version

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

Versions
2. 8. 2023 - Locus 4.18.0
4. 8. 2023 - Locus 4.18.1
15. 8. 2023 - Locus 4.18.2

Hello arnor,
no worry. LoMaps are not attached to any account and may be freely distributed to other own devices or even other users. So simply copy downloaded maps to the wife's phone and it should work without a problem no matter if she has any active Premium or not.

Those are the changes:
- The OAM background from ZL 8 up now is rendered from the July 2023 edition of Christian's OAM vector maps (YES, OAM goes on - thank you, Christian!).
- Increased and earlier visibility of offshore energy and power sources for ZL 4 to 8, while reducing visibility of the land based installations for those low zoom levels.
Have a good time
Michael

An example of how amenity:watering_place is displayed in Magellan OpenMaps themeYou cannot view this attachment.

Hi guys,

handling Google Maps share button should be fixed. Please check the next version of Locus Map and if you still encounter some problems, please let us know.

could it be shown from a lower zoom level?

Redownload. In which Theme did you see it?

OpenMaps (Magellan)👇
https://github.com/IgorMagellan/OpenMaps/releases/tag/v-21-11-27

Hi Tapio,
First, I would thank you for this theme, which I use now quite often. It is very clear.

Second, I have a question, surely off topic, as same behaviour is happening with all theme. Don't hesitate to tell me and I will open a new topic 

I discovered a place where there is a fountain (in real), and despite the search I can do in Locus, enabling everything in themes, or search in points (online or offline) nothing is found nor displayed on map. But information is there in OSM (I use Openandromap for France).
It is this fountain :
https://www.openstreetmap.org/way/300121927

I am attaching screenshots from OSM (in Vespucci app), and Locus.

You cannot view this attachment.

You cannot view this attachment.

Thanks in advance.

[@Tapio]

@Tapio
I believe that color under the "brush" icon is not necessary here. You are usually not toggling visibility on/off here. So it will only confuse (at least me) that something is enabled even if I do not want it.

Distance circles > hmm, should not. Works fine for me, just move to your current GPS location. Isn't this your case as well? 

What should I do to simulate your issue with "shaping points"? The latest BRouter app used, tried two different profiles, all were correct. So please share the profile you use because it will most probably be because of it.

[4]

The latest LM4 beta 4.17.2.3 online search appears to have gone "backwards" regards to sharing with Google Maps....

The latest LM4 beta 4.17.2.4 appears to have gone further "backwards" or at least sideways? My simple use-case, which to be honest is just a hack workaround, because LM4 search is not capable (sorry guys), is

• Google Maps app
• long tap to create red push-pin
• drag-scroll to find the Share option
• tap Share
• tap LM
• now observe, even worse than in 4.17.2.3 LM displays a list of POI over 20,000km away

BUT with correct local address 1km away and no way I can find to re-position to that local address - "so close yet so far" ;-( Funny - at least the list items are sorted by distance ;-(

Google Maps app:
You cannot view this attachment.

LM4 Online Search results after tapping the GMap Share button:
You cannot view this attachment.

BUT I can confirm that a long tap in LM4 will also display the correct address:
You cannot view this attachment.

The Google Maps website shows many results much closer than 20,000km, including the desired one, and which LM would also correctly find:
You cannot view this attachment.