One of the main things that keeps me from using essentially all OSM-based mapping apps as my primary is that search seems incredibly bad. I can't blend city and name, road and category, can't usually filter by features or open time, and results are almost always something like:

    - a result 500 feet away that sounds nothing like what you searched for
    - a result 23 miles away that shares one word but nothing else
    - a result 572 miles away that has a business name that contains exactly what was searched
    - ... nowhere is there an exact full-name match that is 1.3 miles away, which can easily be found by exploring the map

Are there any apps that do this better? Android and desktop (e.g. linux) ideally. I'd love to use them more, but I've had endless problems using them. Good map data is kinda useless if it can't be retrieved, and trying to work around it by panning around and manually saving a hundred or so favorites really kinda sucks.

▲ stevage a day ago | parent | next [-]

True, although I do also have a lot of problems with Google Maps. Particularly, when I search for a small town 100km away, and instead it brings up a medium sized down in the USA. Or even more ridiculous cases, like I slightly got the name of a business wrong, so it went with a different business in the USA.

Yeah, it really loves to suggest US options.

▲ maelito a day ago | parent | prev | next [-]

Could you try https://cartes.app and share your search terms and expectations ? We're using Photon, an OpenSearch search engine. We've build a dictionary of place categories to help in-browser with FuseJS.

Also thinking about using embeddings to complement this.

	▲	Handrail 17 hours ago \| parent \| next [-]
		Cartes search and user experience was surprisingly good! Well done. I was caught off guard by having the requirement for a Bluesky account for reviews instead of something open source/federated but wasn't able to read the explanation page as it was french only, but I think the international version is still work in progress, so I'll gladly return in the future.
	▲	Groxx 7 hours ago \| parent \| prev [-]
		Initial attempts and results: https://cartes.app/#8.61/37.5261/-121.7338 constant up and down movement at any middle zoom level, e.g. this one. zoomed far out or far in (<20km or so visible) it's stable, e.g. https://cartes.app/?allez=San+Francisco+Bay%7Cr9451753%7C-12... moves most of the screen up and down, while https://cartes.app/?allez=San+Francisco+Bay%7Cr9451753%7C-12... is stable. (this appears to be the case roughly anywhere, this is just an example) https://www.dropbox.com/scl/fi/orfhap34liecdon618wkv/Screenc... for a screen recording. for below, all have "here" selected (not "everywhere") and this same view: https://cartes.app/#12.41/43.0435/-87.89962 "coffee": shows city names in other states, and two places in Iraq. "valentine": shows... house icons? and a business icon in other states and countries. (top result is apparently a "commune" in France. not sure I'd use a house icon for that tbh) "valentine coffee": good substring matches for the business name (3 results) and two results in other countries. "val coffee" (exploring substring behavior): finds one good match from the previous search... but it also shows "Stone Creek Coffee"? what part of that node matches "val" but not "coffee" on its own? https://cartes.app/?allez=Stone+Creek+Coffee%7Cn5066972575%7... -> https://www.openstreetmap.org/node/5066972575 "vendetta": finds 3 good results, e.g. https://cartes.app/?allez=Vendetta+Coffee+Bar%7Cn11268671206... , but why does this work when "valentine" does not? so... pretty normal results for open-source OSM apps afaict. maybe slightly better than average.

▲ throwaway284534 18 hours ago | parent | prev | next [-]

Search is a really tough problem in OSM for a few reasons, but I think a lot it stems from bad address parsing.

I’ve been working on geocoder which uses a trained model to parse and classify address queries into a tokenized form. In addition to being more accurate than traditional rule-based parsing, this approach also gives the search engine more to work with beyond the tokenized boundaries of each word. The model also attaches provenance annotations to the address components, allowing the geocoder to have a better understanding of the geographic hierarchy of the components makes sense, rather than matching a string in a database.

The code is changing fast but you can try it out entirely in your browser here! Let me know if you’d like to see any specific features not on the roadmap :)

https://mailwoman.sister.software/

▲

Groxx 8 hours ago | parent [-]

Is this referring to the difficulty of figuring out what "123 w dhuwdaodks plk" means? I can certainly see that (especially internationally - model-based parsing makes a lot of sense there, assuming enough good training data exists), but like I reliably can't even find precise matches in dedicated fields like "business name" or "city". Sometimes it works, sometimes it doesn't, and no open source app I've found yet seems to offer any way to select or filter on fields that definitely exist across locations that definitely exist (I've checked the data by hand). It feels extremely strange, like they're all trying to copy each other without stepping back and figuring out if any of it makes any sense at all to their stated audience.

	▲	Groxx 5 hours ago \| parent [-]
		(as I can no longer edit) concretely, here's an example search session: https://news.ycombinator.com/item?id=48825127 I mean it when I say that's "maybe slightly better than average". When it gets extra weird I generally go check the OSM node data out of curiosity, and fairly often I find searches returning things where literally no field at all matches any word I searched for, across many different apps. I don't really think that's an address parsing issue, though I have definitely noticed many apps being picky (but completely unspecified) about search formatting when looking for addresses.

▲ stevage 18 hours ago | parent | prev | next [-]

> Good map data is kinda useless if it can't be retrieved, and trying to work around it by panning around and manually saving a hundred or so favorites really kinda sucks.

There are different ways of using maps. A lot of the stuff I do with mapping apps I really do just pan and zoom, and that works for me.

▲ kQq9oHeAz6wLLS a day ago | parent | prev [-]

Open source? Not that I've found. I use HERE WeGo for searching and driving, and CoMaps for walking around.