Messages

Hi,

sorry I missed this thread. Such manual track editing is not yet implemented both on iOS and web. Honestly it is only rarely  requested feature so it didn't have high priority for us so far. I don't expect this will change in near future for iOS app which has still huge amount of stuff to catch up, but we will definitely consider to add this to the plan for web portal for the next year.

For now one of the option, although little bit nerdy, is to export track to GPX, removed unwanted track points in text editor manually and import it again. Or sync data with some Android and do it there of course. Sorry I don't have better solution for you for now.

For the web planner to better store its state so you would not need to "start from the beginning" every time after reload of the page is currently under development and require huge changes under the hood. Hopefully in few next weeks it will be out.

Most likely to remember position within MyLibrary will have to wait for second phase sometimes later in the summer though, but we are on the right track.

Hi, yes. We know it take longer than you and even us probably anticipated. We wanted to cover missing key features before the springtime initially. But in the end we chose harder path in order for the app to be better in the long-term. In case you don't loose patience with us, I am confident to say you will be using better product in the end because of this seemingly "empty" period.

But it definitely isn't empty for us, we are still rushing towards our goals with the app in the development!

1) We spent significant time to upgrade MyLibrary as it was mandatory due to technical reasons to keep compatibility with its huge scheduled redesign on backend servers, Android and Web. And it resulted in better experience with it even on iOS, although we know that wasn't highest priority for users.. But we had to do it anyway. By the way, in the process the iOS version have its first "win" against its older Android sibling - you can now browse your library while see the data immediately on the "live" map on same screen.

2) The next big thing are offline maps. We are in the finish line with the development here. In the process we built completely new vector online/offline LoMaps and offline POI dataset which will upgrade experience even compared to their current versions available on Android. During spring we will launch them on iOS and some time later even on remaining platforms.

3) The next quest will be to deliver 1.gen planner and navigation/guidance features. We will see if we manage to release them during summer, but we will do our best.

So yeah, for this year, the app will definitely keeps its Lite postfix in the name. But we definitely didn't slowed down in the team. Of course, more users willing to support us with activating Premium, bigger change we will be able to speed up the development with additional team member.

Thanks for both positive and negative feedbacks guys. Believe us, we know that our web app is still lacking and we are definitely not on the previously projected track with the development. But I can confidently say now, that we recently managed to speed up the development and I hope you will start to see that!

Regarding the topic of reloading the page in particular: I can't promise that the web will soon be able to reload to the same state even with thousands of user-content pre-loaded on map. But the current situation when it doesn't remember almost any state is really bad and we are finally also close to start moving with this issue forward.

Hi Stefan, place the ideas to our helpdesk portal, in this case particulary here:  https://help.locusmap.eu/topics/idea/status/all/category/37/sort/new_updated/page/1

There, others would also be able to vote for them.

Hello to everyone who is waiting for Locus Map on iOS.

We are not there yet, but we believe we are on right track. We just released our first version of Locus Map Lite in Apple Store. Click on the link to learn about its current capabilities and download it.

https://www.locusmap.app/ios/

For some of you, current feature set will not be enough, but some will be glad to use the app even now. And we will be working hard to bring missing and most requested features, with offline maps being one of the highest priority.

It was long way from there: https://www.youtube.com/watch?v=oYn0u-0yuCA 

Tell us your feedback and help us to shape the app for the future!

Hi freischneider, thanks for the ideas. Yes, both are planned, we only had to put bigger search upgrades on hold due to other dev priorities, so hopefully we will get back to it in the mid of this year. So sorry it takes so long to continue on this.

Hi, just additional note to 5)  - we are planning to bring login also to our main page (to the top bar just like on web planner), so I guess it will be less confusing then.

Again that Google Maps sharing. Wait please for next release of the app, I believe it will have major impact on your experience in this. Marek and Menion are doing their magic tricks there now. Lets just hope Google don't change the things on their side soon again..

On other hand, all reports of bad experience while using our new online search are welcomed as we are able to separate/sort  them into technical aspects which we are planning to focus on. This give us better ability to determine whether our expected implementations will make significant change for you or not. Thanks.

@Andrew Heard I replied to your question regarding search here:
https://forum.locusmap.eu/index.php?topic=8436.msg72936#msg72936

I only use this as a workaround. The combination of the app that @0709 suggested has really improved this method of sharing greatly.

Yep, it is handy tool, but unfortunately the app isn't compatible with recent Android versions, nor is working offline.

Locus on Apple/iOS??? When did I miss that? Definitely can't find it...

See:
https://help.locusmap.eu/topic/32424-locus-map-lite-ios-beta-program-open-for-new-testers

Hi, I posted few notes regarding search and sharing from Google Maps here:
https://forum.locusmap.eu/index.php?topic=8572.msg72919#msg72919

I should have post it here and send link to that topic, but nevermind.

sorry for late reply. 

@mfink Whole Garmin For Locus addon is waiting for some "restart" as the current app can't be updated at all because
Garmin again unexpectedly broke backward compatibility of some important Connect IQ SDK features which Locus Map rely on. So I can't even add support for latest devices now unfortunately.

This prompt is another example of the state of CIQ platform. It never properly worked until I finally this year on latest devices like EPIX. But If it still behaves the same for you, I don't expect it will ever change for Fenix 6 family.


@winice not possible. CIQ is very limited in such areas. 

@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 see, there are some confusions in overlapping category highlighting and text search. It is true, that latter is currently unusable to do searches for "bar" etc. as it search only in name of the POI or address, where category name is not usually present. That is why you get that distant results.

Basically the idea is:
1) you want to find some bar - use category highlighting - write "bar" and tap the category in suggestion list.
2) you want to find specific bar and know its name - write down its name without "bar" and hit magnifying glass.
We already have in mind some changes which makes this more intuitive.

@Andrew Heard we found the issue for zooming out during text search - it will be fixed, so the map move will always follow only nearest result.

@T-mo we will try to address issue leading to "loosing" the search when accidentally tap or long-press to something else with some tweaks.

A filter could be introduced to limit searches to a radius of x kilometers.
We thus avoid useless occurrences of results that are too distant both on the map and in the list.

But isn't "search this area" exactly this? Or do you missing it even for category highlighting?