Messages

when I tap on the red circle-arrow map icon, two items are listed, tapping the 1st is ignored, tapping the 2nd pans the map to the point. intended?

note, the 2nd search item for "Patisserie" is a record 18,000km away! As mentioned many a time, I'm sure there are far more relevant results.

This composition logic needs rewrite, I agree. The reason why this is happening is something like "We trust the geocoding provider we use in terms of order of results. They know why they ordered results like that." Or there is something I missed. But the most important fact here is this project has seen no development for months and that is the first thing to change.

The current state of "veg_food" in Locus: 1. Places with "vegan" tagging. As mentioned above, that should mean "One full vegan meal at least". 2. Places with diet:vegetarian=only. That means translating is tricky and I make a mental note about that. Basically we wanted to give green V to places that indicate "veggie" people friendliness. But the current state is compromise, of course. We thought Veggie places are different from other minor cuisine distinctions, so they are given extra treatment, being directly search-exposed and being given special icon. (I know, koscher, glutten-free can be seen important by some people too). What we plan to do: POIs have "labels". These are qualities, such as wheelchair accessible, children-friendly e.t.c. Cuisines can be added, so even offline we can see what a restaurant is about.
McDonalds: Believe or not, there is something called McPlant, which is meant to be some veg(an)? burger. Here in Prague they are meant to be served at the airport. I have not been there, but formally: Given the above described logic, some McDonalds are vegan places, at least they say "We serve at least one full vegan meal". For a moment we used some "filter", so McDonalds, KFCs could not be "veggie", whatever they say about themselves but currently this ad-hoc extra logic is not used.

Hi all. I believe some background context would be beneficial to this discussion. When we want to "browse", or "traverse" interactive map content, we deal with a tree-like structure seen on the white picture. So we traverse (in UI) cca 150 nodes. This number will grow over time, but there hardly ever will be 500+ nodes. When we search, using the current approach, we have a name and perhaps some close synonyms attached to every point (node). So no need (ideally) to know what name is used for "brewery". "Beer" works too. And here is the Devil in details in my opinion. These terms (dark picture) are 90% human generated. We have them just for a few languages. Even German can be improved greatly I believe. There are false positives for short terms, but "ho" is hotel, hostel, hospital, hot spring...

Dobrý den. Případ les u Jedovnic: Je tam skutečně zákaz vstupu kvůli kalamitě. Jak kalamitu dostal Seznam formou "no-go polygonu" do svých map a plánovače? Podle fcb odkazu na mapách (viz obrázek) nejspíš ručně. O spolehlivé, aktualizované databázi všech možných uzavírek nevíme ani pro ČR, natož třeba pro Evropu nebo dokonce svět. (Locus má uživatele po celém světě a věnovat velké redakční úsilí jen v ČR prostě nestačí). Technicky by rozšíření LoRouteru o možnost uzavírek problém nebyl, problém je management těch uzavírek, a to alespoň pro Evropu. Řešením by bylo pečlivé mapování v OSM datasetu, který náš routing využívá. Pak by nic externího nebylo třeba. (To je nejčistší a správné řešení).   

I have tried routing with the LoRouter without my own shaping points. I set a starting point and then had a circular route suggested. The MTB profile was set. Latest beta from 19.01.2024.
The route is very bad. It runs on roads although there is a gravel path in parallel and even an MTB trail with S1 (red-blue).

I have set all shaping points myself in the past to force the path. I thought I would try again to see if the profile got better. But unfortunately it still doesn't suggest any good MTB trails. So I will probably do everything by hand as I have done since then.

Hi, freischneider
Here is a link to the first half of the route from the attached txt file.
https://link.locusmap.app/r/5o6vai
I can see some places where maybe the cycling route does not need to be strictly followed (while riding MTB).
Please show specifically what is wrong here.
The red blue path we see on your screenshot is followed. (Althougt a path is not followed just because somebody mapped its mtb difficulty).

But unless I have a look into map data, this is just my guess. Please specify the location more.

sure: shared track @ web.locusmap.app-planner

Yes, the segment with warning is a secondary road without a (mapped) sidewalk. 

Hello all. There is a fully automated process that updates (changes e.g. names, websites, opening hours), disables or adds new points of interest. No human interaction involved. The logic may be sometimes a bit complex - e.g. "planed" or "demolished" map features are not added or are disabled, some frequent objects (cliffs, trees) have to be named or marked as a landmark, e.t.c. Yesterday some of you mapped in the osm db the wreck as inaccessible tourist attraction, so in a few days (during next update run) the point with red fence in detail (inaccessible place) should pop up in Locus. There will be no wikipedia - an id pointing to wikidata knowledge graph is currently needed for that. If somebody adds this link to osm, wiki will be processed on the 22 this month. There is already related tourist attraction - a propeller from this ship. Propeller Anyway wrecks in general (not tourist attraction tagged) are not considered and it is a good idea to include them. They will be added in the next batched addition.         

handling Google Maps share button should be fixed

thanks @Marek, and the issue reported many times, of search results from > 10,000km away at the top of the list, when there are closer matches on the map < 10km away?

This is not forgotten, just there is no "fix". There is tons of work to determine relevance of results and: Not everything is under my control. Also the rule that closer "match" is more important is oversimplification as we (not just me) agree. I may do some tweaks but proper solution takes time.

Hello Lupin,
sorry for being late, but this is hard to investigate.
 - Locus router (both offline and online) is not guarantied to give results identical to Brouter project. Why is that: 1.not identical data are used for calculation. (This seems not to be the case here as your profiles work in both Locus router and Brouter). 2.There is constant development on both projects which we sync only sometimes (there may be minor changes in the algorithms e.t.c). We aim to keep online and offline version of Locus router identical.
 - Maybe more appropriate question here is: Is the calculated route wrong? How much error is there regarding your routing profile? Which one is the "right" one?
Would you share your custom profile please?
Radim.

Using online search a little bit and thinking about it a bit more, this is my summary:
- Google data repository is unmatched, beating Locus and any other searches hands down, whatever they try, for years to come
- Locus, for strategic reasons, also with iOS support in mind needs this independent online search
- on Android the Google API search is at no cost to Asamm, as Menion stated
- combining both searches technically seems not feasible, as per Menion's response
- to me, the obvious approach is
-- to have a Locus Search for Android and iOS alike
-- put a Google Search as separate function into the Android version

That would stop any need for tough comparisons and discussions, a d empower users to make their own choice, based on their needs.
Giving USERS a choice may not be a technician's first emotional approach, but is beneficial for all parties in the end.

And above approach would not add complexity to the UI a d user experience.

Hope is the last thing to die ;-)

Cheers
Michael

Hi Michael, just a few notes. Of course I agree Google (and few others big boys too) are rather impossible to match. But the current state of what we have in terms of "data repository", as you put it, is just the first step really. In terms of quantity of data it is easy to add dozens of millions of items by mining the OSM dataset. That is a matter of configuration and will be done. (Not all at once). Accuracy outside well mapped areas is not so great, sadly, as we know. Better search engine is hard but doable of course, that is just a lot of work again - these real world data use cases are not typically solved by technology providers. There is also tons of work making all this machinery to update data and talk to other pieces of machinery. But I don't see an easier way how to put together a consistent, world wide dataset of places and "points of interest" relevant to hike bike context. Of course G will find you the nearest "laundromat" way better than L. But how would you search for the nearest fire pits (worldwide). Of course there are some datasets available but maintaining all this together is a hell we (I) don't want to enter. I am an expert in the osm inconsistencies and weaknesses but IMHO this dataset is really needed here.

@Andrew Heard
- There is some change: The first result in the list one gets when types a term and hits "find", is the nearest one. There will still be map view change as this cannot be done server-side, only in new app version. But drastic changes (thousand miles away zoom&pan) should only happen sometimes, if there is no nearby result. Anyway there is (now) no sort based on distance entirely.   
- "Glitches", or "Timing issue": This indeed looks like some async programming error but it is unfortunately not that simple. The reason is: For < 1% of the questions (queries) one of the engines is not performant enough. (Think too many disk reads as opposed to fast memory reads). Once there is a migration to some other solution, this should be solved.   

GM share - we just probably forgot to test it. 
Zoom level affecting the composition of results, or maybe even search engines low level - this can be quite easily done (simple version) and I agree it is a next logical step.
Which bar is important and which is not: in the world of AI, some improvement over what we have now is IMHO quite possible, but very labourious and from the "data work" point of view also very hard.
Clusters of pois displaying numbers - server side this should be easy, front - end boys will hopefuly cope :-)

More thoughts bubble to the surface after a sleep... a better example, maybe - online search for "bar" (I'm in Dingle, Ireland, so plentiful POI). I don't yet tap the Find button. 1st item is "bar, pub - category" - good. The 2nd item is city of Barcelona - really? Maybe 2000km away. The 3rd item is "McCarthys Bar" 1km away - good. Now on 2nd test of same sequence Barcelona is 1st item.

This time I tap the Find button - "Paudies Bar" is maybe 800m way - good, but 2nd & 3rd list items are places in France with "bar" in their name eg. "19800 Bar, France" - bad, and"McCarthys bar" is lost. I now tap SEARCH THIS AREA - only 1 more local bar icon is shown, whereas there are dozens.

When tested with a phone there are only a few search results, but when tested with a tablet there are many more results.

When compared to LoPoints(offline)  with a Locus map there are 20+ bars within 500m.

1) should it even be necessary to tap Find? Just populate list after a pause in typing?

2) should it even be necessary to have a SEARCH THIS AREA button? Wouldn't most common search to be of visible map? When results are empty or scrolled to end of list, maybe the last item is "search wider area"?

3) I think @tapio suggested showing distance to each list item.

4) hover over any Search icon could display a popup or scroll the list otherwise it's not obvious which icon is which.

5) I think it is bad to zoom out (at all) to show icons in the list until one is even tapped, or at least restore original zoom/ position if Back button is pressed.

I hope this is constructive, and not just a rant.

The idea how to find a nearby bar is like this: Type "bar", "pub". Something like "Public service", "Bar, pub" is suggested. These are bars like category of places, whatever name they have. Then if you tap Bar, pub (category), the first item actually suggested, you will see some. No need to use "Find" at all for nearby bars. Not all of bars will pop up necessarily, because in many cases there would be no map, just icons. If you pan or zoom, more bars come and go. If there are many of them, close to each other, only a few are visible. If this does not work in Dingle, then the server must be down or something drastic must be happening.
Problems, or maybe problems:
 - Nobody tells you "zoom in to see them all" (Like Gmaps tells you)
 - Which bar is better, more important, thus visible first or recommended first place?: The Small Bridge or The Dingle Pub? We don't know yet and it is very difficult to answer this for the world wide data.
 - Sometimes only one icon is seen when there is a large cluster of places. Zoom in to see them all.
IMHO this approach makes sense. It has confusing aspects (mostly because we don't know what is important in the real world, and some ordering is virtually random), but it works and is not that pathetic.
The same way this category based search works for waterfalls, shelters, glaciers e.t.c
 1) unless there is some server problem, this is happening.   
A note about ordering: Order by distance exclusively is not used. There is a lot of work to do, but I don't think Barcelona for "Bar" is that irrelevant.

[o]

I am also willing to support, maybe collaborative country-teams might be a solution.

I guess you already have special characters in view, e.g. german umlauts, ö<>oe etc.
tourism is 'Tourimus' and generally the words should also be added separately, like some others already (Essen, Trinken).

Popular searches (fast food, discounters, gas stations, etc.) might help, whatever that might include and it will extend and grow with more and more searches. Sure, advanced and just a filter that might be added anytime somewhere in your lookup-filter-chain. Just a thought.

This is tricky sure, see my vid, searching for 'mc do' needs to  trigger search 'mcdo', whitespaces, and very probably the popular 'Mc Donalds' is meant. Just as stupid example.
'mc dö' might possibly be a search-suggestion as list-item for searches around german locations. Some might be looking for 'Mc Döner', like suggested in the vid, just zillion miles alway.
What if you type 'mill' ? are you searching for categories or specific names, windmill, million..mispelling millitary, and some people also name modern wind turbines a windmill..just for fun. World searches will be versatile
I guess also a list for popular typos might be of help, to suggest replacement or even trigger further searchs.

Special characters - of course, there is "unaccent" procedure. Mc Do - we do not think names of companies are synonyms of categories. This is never done, at least so far. Typos, popular misspellings e.t.c: Yes, especially for short terms guessing what is actually meant can be very, very tricky. Not from technical point of view, but from "how to go about this?" point of view. So I suggest to focus on plain, simple and thoroughly considered configuration. Then the categories suggestion module will be ...not super smart, but definitely good enough.

No hierarchy in the JSON file? If I type "accommodation" for example, should I also expect to see hotel, hostel, motel, camping?

Exactly. Hierarchy exists there and is fully supported, but not defined here. "Hotel" is just hotel, "ubernachtung" is accommodation, "Emergency" is more generic, "Hospital" is specific. e.t.c