[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-28 Thread Joe Critchley
Hi, In terms of both technicalities and appropriate semantics, will it be ok to use the attached 'place' to annotate past or future places, as well as the present location? This could play a key part in my development, so any help would be great. Thanks. On Jun 14, 7:43 pm, Taylor Singletary

Re: [twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-22 Thread znmeb
Quoting David Helder da...@twitter.com: The geo field is the user's (or tweet's) exact location. The place field, whether a POI, neighborhood, city, or admin, contains the place's location. Today POIs are always points, but in the future there may be some polygons (e.g. stadiums, malls,

Re: [twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-21 Thread David Helder
The geo field is the user's (or tweet's) exact location. The place field, whether a POI, neighborhood, city, or admin, contains the place's location. Today POIs are always points, but in the future there may be some polygons (e.g. stadiums, malls, amusement parks). In this case the exact

[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-17 Thread tsmango
Just to answer my own question in case others were wondering, what I found was that: If you use geo/reverse_geocode, you can specify the granularity as either 'city' or 'neighborhood'. The default is 'neighborhood'. Places are never returned. The documentation states that this endpoint will

[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-17 Thread Taylor Singletary
Thanks for sharing your tips. I'll make sure this is all covered in the expanded documentation I'm working on! On Thursday, June 17, 2010, tsmango tsma...@gmail.com wrote: Just to answer my own question in case others were wondering, what I found was that: If you use geo/reverse_geocode, you

[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-17 Thread harrisj
Hello, Currently, using places doesn't modify the 'geo' field. This makes sense for neighborhoods or cities, because picking a centroid is a little arbitrary and those users might get freaked out if we place them at a specific point on a map. However, I would argue that this behavior is

[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-15 Thread Ramanean
Whether it would be better to use authentication for it? Thanks Shan On Jun 15, 4:43 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, Today we're launching some of the functionality around Places that we announced at Chirp. You can read more about the feature

[twitter-dev] Re: Recent Places-related API enhancements more to come...

2010-06-15 Thread tsmango
I can't really test this right now because geo services are currently disabled, but does this mean that the geo/reverse_geocode and geo/ search api methods both return places in addition to neighborhoods and cities now? I understand they are all technically places but I mean business entities