Earlier quoted context omitted.
Hi - it's actually quite different. As of now, we don't (yet) have a forward geocoding api exposed. Rather, most of the API functionality that's live is for backward geocoding. As in, with Google's Geocoder, you give a string and you get back a place. With us, you give a place (i.e. lat/lon) and you get where that place is and what's around it. That being said, a number of people have been pinging us about getting si…
BTW, there are also a number of other differences - below is a quick list: - Type of data: One of things we do is combine a number of different datasets (16+ M businesses, points of interest, intersections, etc...) - Query type: You get very powerful expressiveness in the types of queries you do. You can literally make a request for 'Japanese restaurants that are within 1 mile and that are open at 10pm.' - Media laye…
Not trying to be snarky, I just don't understand....