[twitter-dev] Multiple Resutls for Twitter Place IDS
I notice that in the example of the Staples Center in Los Angeles, the best choice for Staples Center is the second result. We would like to automate our script; do you have any suggestions for determining in code which of the 5 responses is best? Meaning, for a given venue, Twitter has multiple Place IDS - how can we automate it to select the most relevant one? Just *conceivably* some simple algorithm like (a) ruling out results that do not have an exact match somewhere inside the result, and (b) then choosing the result that has the *fewest* extra characters outside the match, might give good results much of the time. That is one idea - any others? also, as an aside, we can't find documentation for this geo/search API. Do you know if documentation has been put up yet? Specifically, though, is there a way to control the number of results - say, to provide 10 results rather than just 5?
[twitter-dev] Re: Twitter Places Follow Up
Currently we call the exact same endpoint to get the Tweets from a given place, but we pass the latitude and longitude, rather than the Place ID. The Latitude/Longitude method forces a 1 km radius around the endpoint. So, when we get the tweets via the Place ID method at the same endpoint - will it only show tweets from the actual place or will it show us Tweets from the place and the surroinding 1km radius? On Jun 23, 11:59 am, David Helder da...@twitter.com wrote: Sure, do this: 1) Find the place ID of the Staples Center:http://api.twitter.com/1/geo/search.json?query=Staples%20Centerlat=3... = The place ID is 7893eab4ca4c1efb (second result) 2) Get all tweets from that ID:http://search.twitter.com/search.json?q=place:7893eab4ca4c1efb If you only have 100 places, you could probably do 100 searches and find the best result by hand when there are multiple results. David On Tue, Jun 22, 2010 at 9:35 AM, ELB ebrit...@gmail.com wrote: The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update orhttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?- Hide quoted text - - Show quoted text -
[twitter-dev] Twitter Places Follow Up
The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update or http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?
[twitter-dev] Twitter Places
Hello, I read on the Twitter blog that: (http://blog.twitter.com/2010/06/ twitter-places-more-context-for-your.html) We are releasing API functionality that lets developers integrate Twitter Places into their applications.“ I wanted to check in to see where we could learn about what functionality has been released. We have 100 places, ie: Staples Center, LAX Airport, Grand Central Terminal, etc that we want to publish Tweets from. Are we able to use the Twitter API to publish the current Tweets from a given place? if so, where in the API is the documentation to do this? ELB
[twitter-dev] Suggested method for getting GEO results
Hello, We are looking at getting city based search results for 14 major cities. The current method we use is to plug in a cities Geo Coordinates into the search API and then include a 25KM radius around the city. This works well and allows us to get true results of people inside or around a given city. However, for maybe a 20 minute period once or twice per day, the results are empty. We go from 50-100+ results for a given keyword to 0 - 5 results. Then, 20 minutes later there will again be 50 - 100+ results including several results for the time period whereby the results were blank. So, its not a case of Twitter not having results, it is a case of a 10 - 20 minute window whereby Twitter's results with the GEO filter don't show up - or barely show up for a given time period. This has led us to consider using the Near API. From what I understand, the Near API will give us results near a given city based off of GEO data as well as profile data. I would assume this may be a more stable option - but the option we use now is great except for those rare instances whereby Twitter shows us little to no results for a keyword they clearly have a lot of results for within our GEO coordinates. ELB
[twitter-dev] Re: Suggested method for getting GEO results
thanks Taylor for the reply. I am referring to user-initiated queries. We have users that type in a keyword to a search box, and we then return results from the Search API with the corresponding Geo Coordinates included with the request On Jun 2, 5:51 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Have you considered using the Streaming API for this purpose?http://apiwiki.twitter.com/Streaming-API-Documentation#locations-- we encourage those with heavy search needs to use it as an alternative. Search is meant much more for servicing search results based off of user-initiated queries, and is most tuned for that purpose. Taylor On Wed, Jun 2, 2010 at 2:37 PM, ELB ebrit...@gmail.com wrote: Hello, We are looking at getting city based search results for 14 major cities. The current method we use is to plug in a cities Geo Coordinates into the search API and then include a 25KM radius around the city. This works well and allows us to get true results of people inside or around a given city. However, for maybe a 20 minute period once or twice per day, the results are empty. We go from 50-100+ results for a given keyword to 0 - 5 results. Then, 20 minutes later there will again be 50 - 100+ results including several results for the time period whereby the results were blank. So, its not a case of Twitter not having results, it is a case of a 10 - 20 minute window whereby Twitter's results with the GEO filter don't show up - or barely show up for a given time period. This has led us to consider using the Near API. From what I understand, the Near API will give us results near a given city based off of GEO data as well as profile data. I would assume this may be a more stable option - but the option we use now is great except for those rare instances whereby Twitter shows us little to no results for a keyword they clearly have a lot of results for within our GEO coordinates. ELB
[twitter-dev] No Results returned
We seem to have been getting an error with the search API whereby results aren't returned for a few minutes at a time... This happened one day last week, and again this evening.. anyone else noticing this?
[twitter-dev] Re: Current Trends
Hey Raffi, Baiscaily, the current trends, and even the daily trends, as I mentioned, this API call has a lot of noise/spam in it such as nowplaying, which always shows up as a trend... on the Twitter homepage, however, it looks like some of the non- relevant trends were removed from the list - for example nowplaying isn't currently showing up on the homepage of Twitter even though the API currently has nowplaying both in the current trends and daily trends call... thanks again for your time... On Apr 4, 2:34 pm, Raffi Krikorian ra...@twitter.com wrote: can you please be more specific? which API calls are you comparing to the homepage? On Fri, Apr 2, 2010 at 6:05 PM, ELB ebrit...@gmail.com wrote: The current list of 10 trends often has non-relevant trends such as nowplaying or FF . The new Twiitter homepage seems to remove these trends as it only shows more relevant trends. Will there be a new way in the API to get the current trends with some of the spam/non relevant replaced with trends that are more meaningful -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] New Popular Results Set
Hellom If we decide to just pull just the popular results – ie: http://search.twitter.com/search.json?q=gamesresult_type=popular it seems that there is a maximum of 3 results listed... Is there anyway to get up to 10 popular results for a given search query? or, is 3 the maximum it can give us at this time? if it is - is there plans in the future to display more than 3 popular results for this query http://search.twitter.com/search.json?q=gamesresult_type= ELB -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Current Trends
The current list of 10 trends often has non-relevant trends such as nowplaying or FF . The new Twiitter homepage seems to remove these trends as it only shows more relevant trends. Will there be a new way in the API to get the current trends with some of the spam/non relevant replaced with trends that are more meaningful -- To unsubscribe, reply using remove me as the subject.
