News for hackers. Stuff that matters.
Re:Tell HN: We just launched GeoAPI.com (read/write geo API) by barmstrong on Thursday November 12, 2009 @08:33PM (#939164)
It looks good but my biggest unanswered question when I saw it: What's the difference between this and the Google Geocode API?
Re:Tell HN: We just launched GeoAPI.com (read/write geo API) by othman on Thursday November 12, 2009 @09:18PM (#939214)
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 simple geocoding functionality, so stay tuned for that as well :).

Re:Tell HN: We just launched GeoAPI.com (read/write geo API) by othman on Thursday November 12, 2009 @10:03PM (#939265)
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 layers: For most entities, you can get media layers such as Twitter and Flickr. For example, you can get tweets around the mission (http://api.geoapi.com/v1/e/mission-san-francisco-ca/view/twi...). We're adding more layers as we go. - UserView: Each developer gets a private namespace into which they can add information and run geo queries on it. Basically, you can annotate the world with close to zero effort.
Re:Tell HN: We just launched GeoAPI.com (read/write geo API) by lilypad on Friday November 13, 2009 @06:28PM (#941083)
The query syntax is pretty cool, but as far as raw geocoding I don't really get it -- Google has a much bigger dataset than this, offers reverse geocoding just fine (With good neighborhood data in the US and Europe). And I gather you are just proxying requests to twitter and flickr (and not actually storing all this for all places yourself) -- why wouldn't I just query their APIs directly?

Not trying to be snarky, I just don't understand....

Re:Tell HN: We just launched GeoAPI.com (read/write geo API) by bbsabelli on Friday November 13, 2009 @05:10AM (#939714)
Huh?

New York: http://maps.google.com/maps/geo?q=40.724039,-74.00176

What am I missing here?