Quote from: michaelbechtold on Yesterday at 20:22:01Using online search a little bit and thinking about it a bit more, this is my summary: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.
- 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