Hi Raffi,

I am not seeing the geo data for this query:

http://search.twitter.com/search.json?from=adityakothadiya or for
http://search.twitter.com/search.json?q=adityakothadiya

Where as adityakothadiya as a twitter user has enabled the geotagging
for his account. Can you suggest and tell if i am not using the api
correctly?

Thanks in advance,
Sushil

On Dec 2, 5:50 pm, Raffi Krikorian <ra...@twitter.com> wrote:
> hi luca.
>
> yup -geodata should be everywhere a status is rendered.  on the REST  API, on 
> streaming, and onsearch.  if its not there, please feel free  
> to reach out to me.
>
>
>
>
>
> > Hi Raffi,
>
> > our app (www.kirigo.com) currently fills thegeotag of status updates
> > - since we also want to extract this info from tweets from others, my
> > question is:
> > is thesearchthe only way to extract thegeocoordinates of a tweet?
> > I would rather been interested in the timeline and I can see from the
> > doc that the method statuses/public_timeline has a <geo/> section - is
> > that implemented?
>
> > Thanks a lot for your time!
>
> > Luca
>
> > -------
> > Luca Faggioli
> >www.kirigo.com
> > follow me on Twitter:http://twitter.com/lfaggioli
>
> > On 25 Nov, 19:59, 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.  thegeotag is set if the tweet is sent
> >> using the geotaggingAPI.
>
> >> the number of geotweets (tweets sent using the geotaggingAPI) 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 asearchthat looks 
> >> likehttp://search.twitter.com/search.json?from=raffi&geocode=37.77%2C-122
> >> ...
> >> .  that shouldsearchfor 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":"&lt;a href=&quot;http://www.atebits.com/";
> >> rel=&quot;nofollow&quot;&gt;Tweetie&lt;/a&gt;"
> >>          },
> >>         ...
> >>          {
> >>              "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":"&lt;a href=&quot;http://foursquare.com";
> >> rel=&quot;nofollow&quot;&gt;foursquare&lt;/a&gt;"
> >>          },
> >>      ],
> >>      ...
>
> >> }
>
> >> in both of these, the location attribute appears and is populated
> >> because i used the geocode operator onsearch.  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 geotaggingAPI(its not a geotweet).  the second, however,
> >> has its location set to that latitude and longitude from the
> >> geotaggingAPI, and thegeoattribute is populated -- that one is a
> >> geotweet.
>
> >> there is no current way to filtersearchresults so that you only get
> >> geotweets.
>
> >> does this help?
>
> >>> Hi everyone, I have a question regarding thesearchAPI.
>
> >>> Take a look at these two tweets return from theAPI.
> >>> {
>
> >>>    * 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 withgeofiled  
> >>> included(I
> >>> go through more than 20 pages). Is this normal? Is that possible to
> >>> get only tweet withgeoincluded?
>
> >>> 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
>
> --
> Raffi Krikorian
> Twitter Platform Team
> ra...@twitter.com | @raffi- Hide quoted text -
>
> - Show quoted text -

Reply via email to