Messages

@freischneider Here is the exact configuration file that determines what is suggested for typed word (or part of a word). If you do a search for "spo" in this file, you will see what is suggested if you type "spo" in Locus using German language. It is (conceptually) as simple as that. This file was created for us by user Balloni, please take it as a reference. If anyone is interested in improving this file -- also applies to other languages -- that's great, but first: I should properly explain how it all works to editors. (It is important, really, you see it). Also we should set up some collaborative platform for this. Let me know if you want to participate here, please.You cannot view this attachment. 

@Andrew Heard - regarding the "cafe" example - for German language -- and actually all languages except EN, CS, SK -- this all depends entirely on quality of our custom dictionaries (done by a few kind volunteers). Again, some community insight will probably be needed. If a german user types "cafe", no cafe is suggested. Type "Kaffe" or "Bistro", and Cafe (category) is there.
@Tapio - "halde" example: german search (not the "hint" or "suggest" part) has been virtually not working  due to some config error. This has been fixed and "halde" should give you a plenty of results.   

Map is on Dortmund, Nordrhein-Westfalen, Germany. GPS off, device located in the area.

I search for "Halde", those are artificial hills, results of former coal mining. There are quite a few in this federal state, they have "Halde" in their osm name, usually.

Now after pressing enter it shows some inappropriate results. In the south of Germany.

https://youtube.com/shorts/fhv1RJWkurw?feature=share

There is something wrong going on. I am looking into it.

@Andrew Heard - offline points and their functionality is not affected at all by this new online search. If it is somehow broken in this version, that is another matter :-(
@freischneider - these configurations are (technically speaking) easily adjusted, it can be done by a well informed native speaker of some language. In fact there will be need to extend these configurations of synonyms to another languages. Sample of such a configuration written by a translator is attached. Solving frequent conflicts: that should be considerably improved once there are some real world data.

@Andrew Heard, @luce: There is an important distinction: Places named "supermarkt", "laundromat" and places that actually are a supermarket or a laundry room.
 - As some of you pointed out, Locus "object repository" does not contain laundromat as a place for washing clothes. The notion of points of interest in Locus so far has been: Laundromats are not that important in the hiking/biking context. I am not overly concerned about missing "objects" - points of interest. A few millions of poi can be added quite easily. Why there are still some - we combine results from our service and some third party service, which is inconsistent, sure we know it.
 - What you do in the video: You search for places named like "supermarkt". It is the name which is important here. Not what it really is.
 - Try to type "shop", "super", "gas", "petrol", "diesel", "emergen" (or some similar german words). You will get some suggestions, like Supermarket, Gas station (category, all of them) e.t.c. Click it and then you get "overlay" of all supermarkets (Tesco, Billa, whatever name). Not places that are named "supermarket", but places that are supermarkets.
 - There is no assumption that you don't mean search by a name if you type and hit magnifying glass. If this is not clear, that means an important UX message.
 - It would be not convenient to search for nearby fire pits, shelters e.t.c by name. Usually, there is no name.
 - It would be not convenient to search for "Riffugio Auronzo" by browsing all accommodation.
 - It would be confusing to mix both approaches outlined here IMO

Regarding the cursor location vs GPS location as the online search parameter. Please see  this post in the dedicated thread.
The intended behavior is: Cursor position has priority over GPS position and this is what we observe. Can you give us an example of wrong behavior? 

I tried to reproduce the cursor vs GPS location problem. Currently I am in Prague, but my cursor is near Pilsen. See the screenshots. If I search for "Shell", all top results are situated around Pilsen. This is expected and in accordance with the logic: In case that map window is available, use it, otherwise use the fallback to GPS location. 

4 months and 3 versions ago I reported this issue with the planners
https://forum.locusmap.eu/index.php?msg=69978
still not solved

Military road
access = no
but ...
foot = permissive
https://www.openstreetmap.org/way/220542005

I "relaxed" the policy towards permissive access in hike and bike routing profiles. Routing is already changed on web, the app will soon follow.
https://link.locusmap.app/r/nsuqvf

Dobrý den - rozhledny v online bodech a nemožnost zobrazit je jako body v okolí: To by se mělo brzy změnit, online search v aplikaci významně předěláváme. Offline body: Aha, díky, to nám uteklo. Radim.

 Hello Tobias. If you copy the profile files as you mentioned, they should work, using the in-build LoRouter offline, which is currently based on version 1.6.x of Brouter. Radim.

Time for routing development is coming, I keep notes on this.

I remember this
https://forum.locusmap.eu/index.php?topic=8235.msg69978#msg69978
2 months and 2 versions ago and still not solved.

I tried the openstreetmap planner and all the possible profiles (Valhalla, OSRM, GraphHopper) they allow passage on the military road while locus does not.

@Radim V

As I agree on "One text field" completely, deciding what is important enough to deserve user attention may be just guesswork. Even if we keep track of history by users, it may be easier if you just tell us e.g. "don't want to search my personal content now".

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.

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.

Even worse is when I start typing, realize I got the wrong "place" to search in, change it, and the input field is cleared - why's that? Makes no sense and would be easy to fix...

Hi all, thanks for reporting this problem! There is of course no "tram"=no_go. The reason why this is happening is the less common surface=chipseal tag. (I think there is no significant occurrence of this surface in Europe, not even creators of the original brouter considered it). Also handling of defaults used to be less than ideal in the car profiles. Today I reviewed surface handling in all car profiles (Publicly visible are just 2 profiles). After new tiles are produced, the change will eventually make it to the public environment - after testing internally (By us).   

@lor74cas - this denial of access is due to the access=no and foot=permissive character of a military road. It can be fixed and I make a remark for another round of profiles-fixes. But also this is a good example of a segment, where some kind of warning should be issued anyway. A military road can be closed (at least from OSM point of view) anytime. These warnings are something we started to consider.   

Hello all.
@francisco, thanks for your evaluation of trail grades (How much region specific it is?). If the decision of Locus supporting 4x4 vehicles or dual sport bikes is made, we will use it. There is 4UMaps already available in Locus (small areas can be downloaded for offline use) which displays MTB grades. Why we think this 4x4 routing is tricky: In west Europe where most of Locus users reside the legal 4x4 overlanding is virtually impossible due to many mapped and not mapped restrictions and barriers. So there would be the router which produces routes that we know to be very unreliable. In the other parts of the world such profiles may work.