Yes, t-mo, I'm talking about an INCLUSIVE AND.
Yet, not behind the scenes, as this would violate the new Locus search architecture (or at least would complicate things), and on iOS this even might be impossible (I cannot judge here).
This is the reason I propose to follow the path Radim and Menion et.al have described and are going. BUT leave the Google API based search as a separate feature (with its own name), on Android.
As I pointed out earlier, OSM is not anywhere near a reliable or complete model of the world, even for hike/bike aspects, in particular for countries outside CZ/SK/AT/D scope.
BTW: even Bikers appreciate a laundromat from time to time :-)
Again, this is NOT playing one against the other, but COMBINING the strengths of both data sets in a minimal effort way.
Cheers
Michael
PS: there is a difference between Google Maps mobile data hunger and a (Google) API call size in bytes - orders of magnitude. Proven just today, in the middle of Germany.
Yet, not behind the scenes, as this would violate the new Locus search architecture (or at least would complicate things), and on iOS this even might be impossible (I cannot judge here).
This is the reason I propose to follow the path Radim and Menion et.al have described and are going. BUT leave the Google API based search as a separate feature (with its own name), on Android.
As I pointed out earlier, OSM is not anywhere near a reliable or complete model of the world, even for hike/bike aspects, in particular for countries outside CZ/SK/AT/D scope.
BTW: even Bikers appreciate a laundromat from time to time :-)
Again, this is NOT playing one against the other, but COMBINING the strengths of both data sets in a minimal effort way.
Cheers
Michael
PS: there is a difference between Google Maps mobile data hunger and a (Google) API call size in bytes - orders of magnitude. Proven just today, in the middle of Germany.