My biggest issue with OrganicMaps is that the search isn't very good. It really struggles to find my destination sometimes. That's the one thing I'm afraid Google will always be better at.

▲

maelito a day ago | parent | next [-]

It doesn't take so much to enable a good server search on top of OSM + openaddresses.

Local search will always be slow and bad.

But server search doesn't need that much. It's just that OS initiatives are severely understaffed. OS apps that have a Photon instance are already rare to find. Let's not talk about having an Overpass instance...

What is very hard to reproduce is Google's place review data.

It's golden to enable good search.

▲

tcfhgj a day ago | parent | next [-]

> What is very hard to reproduce is Google's place review data.

fake anyways (quite easy to get negative comments deleted), and even for bad reviews.

Best look elsewhere or not at all.

▲

maelito 20 hours ago | parent [-]

I'm not talking about stars, we don't care about stars for search engines.

What's important is people talking about "has air conditioner" in a hotel review or "has vegan" in a restaurant. OSM has none of this data.

	▲	baumschubser 16 hours ago \| parent [-]
		I just checked (in CoMaps): A restaurant around the corner is listed as "Pizza, Vegan, no wheelchair access, outdoor seating". No opening hours, though (but other places have).

▲

drnick1 a day ago | parent | prev [-]

It's not like Google reviews can be trusted.

▲

dopidopHN2 a day ago | parent | prev | next [-]

I have the same grippe.

I was talking in deep in the weed OSM signal group and apparently its a split between the address data not being present, and OrganicMap / CoMap being bugged.

The way to triage is asking nominatim, the geocoder from OSM. If it can resolve : its on the client side, if not, its a data problem.

I'm just parroting here. Happy to learn more.

This is THE only issue I have with those OSM client ( I don't care about traffic )

	▲	maelito a day ago \| parent [-]
		For good (server) search, one needs many layers (Photon, Pelias with OpenAdresses, Overpass, in-house pmtiles, etc.) using many DBs, each needing server ressources or expensive paid APIs. It's obvioulsy expensive in terms of ops + dev, but also just to host. It can't scale with only 0,0001 % of users donating to the app. Fortunately, NLNet's there to fund work, but it's still nonethless only a tenth of what would be needed. Plus map applications and general search engines don't talk to each other... I don't know why, but it is so. Maybe because all the well-known search engines are closed-source ?

▲

seb1204 a day ago | parent | prev [-]

This can be due to missing address information in OSM. I also find the grouping sometimes odd, e.g. searching for a street, the place names are from one level higher.