nah - no worries. data is coming in and the rate at which geotags come in increases every day.
On Fri, Feb 12, 2010 at 4:19 PM, Eric Marcoullier @ Gnip < [email protected]> wrote: > Raffi -- you are absolutely correct. It turns out it's a frequency > thing. I've done a whole bunch of random looks at result data in the > last couple of months and I've never seen one. Now that I know what > to look for, I just grabbed a batch of 50,000 search results and found > several. > > Many apologies for any work you had to do to drop some knowledge on > me :) > > Eric > > On Feb 12, 9:22 am, Raffi Krikorian <[email protected]> wrote: > > hi eric. > > > > just to make sure i understand what you're saying - you're saying that > the > > geo tag (from the geotagging API) is not showing up from search? i beg > to > > disagree > > > > deskdog:Desktop raffi$ *curlhttp:// > search.twitter.com/search.json?q=tomcoates* > > { > > "results": > > [ > > ... > > { > > "profile_image_url":" > http://a1.twimg.com/profile_images/523070730/twitterProfilePhoto_norm... > > ", > > "created_at":"Fri, > > 12 Feb 2010 05:05:51 +0000", > > "from_user":"vicchi", > > "to_user_id":1292126, > > "text":"@tomcoates You did really well today. Rest. Relax. > Blog. > > Sleep. See you tomorrow.", > > "id":8995500197, > > "from_user_id":59842, > > "to_user":"tomcoates", > > *"geo":* > > * {* > > * "type":"Point",* > > * "coordinates":* > > * [* > > * 37.2655,* > > * -121.9648* > > * ]* > > * },* > > "iso_language_code":"en", > > "source":"<a href="http://www.tweetdeck.com/"; > > rel="nofollow">TweetDeck</a>" > > }, > > ... > > "max_id":9014080861, > > "since_id":0, > > "refresh_url":"?since_id=9014080861&q=tomcoates", > > "next_page":"?page=2&max_id=9014080861&q=tomcoates", > > "results_per_page":15, > > "page":1, > > "completed_in":0.053853, > > "query":"tomcoates" > > > > } > > > > seems to be working for me? > > > > On Fri, Feb 12, 2010 at 6:59 AM, Eric Marcoullier @ Gnip < > > > > > > > > [email protected]> wrote: > > > I apologize if this has been previously covered, but it appears that > > > explicit geotag info is not shown for any tweet returned via the > > > search API, regardless of whether a user has authorized public geo > > > reporting. > > > > > As a result, it is possible to determine what is being said in a > > > specific location, but it is not possible to determine where people > > > are talking about a specific subject. > > > > > I understand you not wanting to show all the signals that lead to a > > > geo search match, but I can't grok why you're witholding specific > > > metadata from the search results. > > > > > Any light you can shed would be valuable to my customers. Any plans to > > > change this policy would be rad. > > > > > Thanks! > > > Eric > > > > > (on my iPhone. Sorry for typeos) > > > > > On Feb 11, 8:20 pm, Raffi Krikorian <[email protected]> wrote: > > > > each user has a location field associated with it - but that is self > > > > reported. > > > > > > On Thu, Feb 11, 2010 at 2:17 PM, don <[email protected]> wrote: > > > > > Thanks for the reply. Thats what I was thinking. > > > > > > > Would there be any way to return the location data of user with the > > > > > search results for a word? > > > > > > > So that I didn't need to make seperate calls for each user? > > > > > > > thanks so much for your help. > > > > > > > On Feb 12, 3:20 am, Raffi Krikorian <[email protected]> wrote: > > > > > > twitter only returns data back in its "geo" field if the tweet > has > > > been > > > > > > explicitly geotagged. > > > > > > > > search, however, attempts to use other signals to determine where > the > > > > > tweet > > > > > > is, and will attempt to return "more" tweets when you use its > > > "search" > > > > > > parameter. it does not, however, expose those signals in the > search > > > > > > results. > > > > > > > > On Wed, Feb 10, 2010 at 1:39 PM, don <[email protected]> > wrote: > > > > > > > Hi All, > > > > > > > > > I'm trying to determine the location where a tweet came from. > > > > > > > > > I know you can do a search specifying the location you want to > look > > > at > > > > > > > and this checks againist any geo data and then against the > location > > > > > > > data. I'm guessing that twitter does a lot of error checking > and > > > > > > > transforms the location data into a geo coord on the backend > when > > > you > > > > > > > do this search. > > > > > > > > > My question is: if I do a search for say a "word" and get my > > > results > > > > > > > back I want to be able to check where each of the returned > tweets > > > came > > > > > > > from. Not just using the geo data that the user may have > allowed > > > but > > > > > > > also the location data (just like the search for location based > > > tweets > > > > > > > does). > > > > > > > > > Essentially getting back a geo coord for each tweet if there is > any > > > > > > > releveant geo data or location data given by the tweeter. > > > > > > > > > this site would be doing something similar: > http://trendsmap.com/ > > > > > > > > > any ideas? sorry if this is really obvious, I have searched and > > > just > > > > > > > can't find it. > > > > > > > > > thanks > > > > > > > don > > > > > > > > -- > > > > > > Raffi Krikorian > > > > > > Twitter Platform Teamhttp://twitter.com/raffi > > > > > > -- > > > > Raffi Krikorian > > > > Twitter Platform Teamhttp://twitter.com/raffi > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
