Hi dev.at.twitter, Yes, Local Trends are only available by one of the 42 currently supported WOEIDs (including "Worldwide"/WOEID==1).
However, the GET http://api.twitter.com/1/trends/available.json method will take a lat and long parameter set to return supported WOEIDs for a location (see the end of this message for a brief summary on WOEIDs we have trends for now). Finally, the trends/:woeid call is meant to tell you what the current trends are, not to provide the actual tweets that make up that trend. Each trend in the array will have a name, a URL pointing to the search.twitter.com WEB UI (which can easily be munged into a Search API URL), and the actual query criteria that is considered part of the trend. For finding WOEIDs for lat/longs that aren't necessarily reflected in Trending Topics, look here: http://developer.yahoo.com/geo/geoplanet/ Summary on current local trends areas: > [ > { > "label":"Ireland", > "woeid":23424803 > }, > { > "label":"United Kingdom", > "woeid":23424975 > }, > { > "label":"Mexico", > "woeid":23424900 > }, > { > "label":"Boston", > "woeid":2367105 > }, > { > "label":"Washington", > "woeid":2514815 > }, > { > "label":"Miami", > "woeid":2450022 > }, > { > "label":"Su00e3o Paulo", > "woeid":455827 > }, > { > "label":"Baltimore", > "woeid":2358820 > }, > { > "label":"India", > "woeid":23424848 > }, > { > "label":"Worldwide", > "woeid":1 > }, > { > "label":"Colombia", > "woeid":23424787 > }, > { > "label":"Italy", > "woeid":23424853 > }, > { > "label":"Detroit", > "woeid":2391585 > }, > { > "label":"Argentina", > "woeid":23424747 > }, > { > "label":"Netherlands", > "woeid":23424909 > }, > { > "label":"New York", > "woeid":2459115 > }, > { > "label":"Australia", > "woeid":23424748 > }, > { > "label":"United States", > "woeid":23424977 > }, > { > "label":"San Antonio", > "woeid":2487796 > }, > { > "label":"France", > "woeid":23424819 > }, > { > "label":"Chile", > "woeid":23424782 > }, > { > "label":"Minneapolis", > "woeid":2452078 > }, > { > "label":"Philadelphia", > "woeid":2471217 > }, > { > "label":"Chicago", > "woeid":2379574 > }, > { > "label":"Brazil", > "woeid":23424768 > }, > { > "label":"Houston", > "woeid":2424766 > }, > { > "label":"San Francisco", > "woeid":2487956 > }, > { > "label":"Los Angeles", > "woeid":2442047 > }, > { > "label":"Venezuela", > "woeid":23424982 > }, > { > "label":"Canada", > "woeid":23424775 > }, > { > "label":"Spain", > "woeid":23424950 > }, > { > "label":"Sydney", > "woeid":1105779 > }, > { > "label":"Singapore", > "woeid":23424948 > }, > { > "label":"Atlanta", > "woeid":2357024 > }, > { > "label":"Indonesia", > "woeid":23424846 > }, > { > "label":"Germany", > "woeid":23424829 > }, > { > "label":"Dallas-Ft. Worth", > "woeid":2388929 > }, > { > "label":"Rio de Janeiro", > "woeid":455825 > }, > { > "label":"London", > "woeid":44418 > }, > { > "label":"Toronto", > "woeid":4118 > }, > { > "label":"Turkey", > "woeid":23424969 > }, > { > "label":"Seattle", > "woeid":2490383 > } > ] On Mon, Jan 31, 2011 at 9:21 AM, twitter dev <dev.at.twit...@gmail.com>wrote: > Hi Guys, > > I've few questions on topics trending nearby, > 1. Trends are based on WOEID. Can we get the twitter trends based on > lat/long geo-coords ? > 2. If 1 is not possible then, what is the best way to get the accurate > WOEID for a lat/long geo-coords ? > 3. I tried http://api.twitter.com/version/trends/:woeid.format , which > gives only the topic name and a link to that page. How do I get some > more info from this call ? > > I'm stuck here now, guys help is much appreciated. > > Thank you all, > -dev. > > -- > 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 > -- 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
