Yes Thanks a lot for your reply. I'm curious how client like tweetie and tweetmap does in their application.
For example, the nearby feature in tweetie looks pretty good. It can drop more than 20 pins on each load; however, I can't get that many results from the api search with "valid" location like "location":"37.818300,-122.245000" I did load 100 results in each page. The only way I'm thinking is just keep loading the pages(next page- >next page until num result>20). Is this easy to be blocked by twitter? Because my app will try to load more results when user move the map. Thanks! On Nov 25, 1:59 pm, Raffi Krikorian <ra...@twitter.com> wrote: > hi! > > i think you're confusing two different things here. the "location" is > what is set in the user's account settings > (https://twitter.com/account/settings > ) if it is not a geotweet. the geo tag is set if the tweet is sent > using the geotagging API. > > the number of geotweets (tweets sent using the geotagging API) is on > the rise, but its definitely still small as there is a limited number > of applications that currently support it (birdfeed, foursquare, > gowalla, etc.). but, for example, if somebody checks in using > foursquare, and they have geotagging turned on, then you should see it. > > try a search that looks > likehttp://search.twitter.com/search.json?from=raffi&geocode=37.77%2C-122... > . that should search for my tweets that are within 50 miles of san > francisco. the results look like the following (abbreviated): > > { > "results": > [ > { > "location":"San Francisco, California", > > "profile_image_url":"http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_no... > ", > "created_at":"Tue, 24 Nov 2009 17:57:52 +0000", > "from_user":"raffi", > "to_user_id":null, > "text":"Standards were invented for me to accidentally > break.", > "id":6014464536, > "from_user_id":278432, > "geo":null, > "iso_language_code":"en", > "source":"<a href="http://www.atebits.com/" > rel="nofollow">Tweetie</a>" > }, > ... > { > "location":"37.818300,-122.245000", > > "profile_image_url":"http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_no... > ", > "created_at":"Sun, 22 Nov 2009 21:13:39 +0000", > "from_user":"raffi", > "to_user_id":null, > "text":"Mmm. Brunch. Dr. Lady Friend. Good. (@ Camino in > Oakland)http://bit.ly/2cJV9";, > "id":5955787968, > "from_user_id":278432, > "geo": > { > "type":"Point", > "coordinates": > [ > 37.8183, > -122.245 > ] > }, > "iso_language_code":"en", > "source":"<a href="http://foursquare.com" > rel="nofollow">foursquare</a>" > }, > ], > ... > > } > > in both of these, the location attribute appears and is populated > because i used the geocode operator on search. in the first returned > tweet, the location is set to San Francisco, California because that's > what i have in my account settings and because that tweet was not sent > using the geotagging API (its not a geotweet). the second, however, > has its location set to that latitude and longitude from the > geotagging API, and the geo attribute is populated -- that one is a > geotweet. > > there is no current way to filter search results so that you only get > geotweets. > > does this help? > > > > > Hi everyone, I have a question regarding the search API. > > > Take a look at these two tweets return from the API. > > { > > > * location: "Santa Clara, CA" > > * geo: null > > } > > { > > > * location: "iPhone: 37.313690,-122.022911" > > * geo: null > > } > > > { > > > * location: "ÜT: 37.293106,-121.969004" > > * geo: null > > } > > > 1) im not sure why I haven't seen any tweet with geo filed included(I > > go through more than 20 pages). Is this normal? Is that possible to > > get only tweet with geo included? > > > 2) if 1) won't work, I want to filter all the tweets with valid > > location like the second one, therefore, I can push the tweet on map. > > Is the keyword also apply for the location? It's hard for the first > > one cuz it doesn't have the detail address. > > > Thanks! > > -- > Raffi Krikorian > Twitter Platform Team > ra...@twitter.com | @raffi
