I once was on a project that started out with OSM, but then realised there was nothing that compared to Google's Places API (might be different now) in terms of completeness and correctness. And your are not (or at least were not) allowed to use Places API on top of / in combination with OSM).
That's what you get when your consumer directed products are 'free' and thus widely used and thus lot's of stake holders ensure their place is correctly in their database (probably in combination with other, possibly community based, efforts).
We relied heavily on Places API and thus were bound to Google Maps API, we did just not see a reasonable way around that.
That's what you get when your consumer directed products are 'free' and thus widely used and thus lot's of stake holders ensure their place is correctly in their database (probably in combination with other, possibly community based, efforts).
We relied heavily on Places API and thus were bound to Google Maps API, we did just not see a reasonable way around that.