I've been testing with averaging the points to get the centerpoint and
passing to Twitter with the Search API.  Seems to be working.

On Sep 14, 12:20 pm, johnw <john.we...@gmail.com> wrote:
> I have the results from Geo Search coming back and I want to feed this
> into a subsequent Search API query to base the tweet search radius on.
>
> However,  I'm not sure the best means to use the bounding box
> coordinates.  Given this:
>
>       "bounding_box": {
>           "coordinates": [
>             [[
>                 -82.437165,
>                 41.065485
>               ], [
>                 -82.387024,
>                 41.065485
>               ], [
>                 -82.387024,
>                 41.094768
>               ],  [
>                 -82.437165,
>                 41.094768
>               ]
>             ]
>           ],
>
> The (tweet) Search API requires a single lat/long for a geo radius,
> not a bounding box.  I am assuming that it would be best to calculate
> the central point of the four coordinates and pass that onto Search?
> I wonder what Twitter does in their advanced search, under the covers,
> as they would have the same issue.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to