Hi there,

I'm getting started with using the search API; I'm a GIS guy looking
at how to ingest tweets with geo or location info.  I'm seeing an odd
behavior with the location element- it seems the location info is only
displayed when I submit a geocoded search.  As an example:

In the results for 
http://search.twitter.com//search.json?q=%23geoglobaldomination
is the following tweet:
{"Thu, 08 Jul 2010 01:43:02 +0000",
"from_user":"geo_rube",
"metadata":{"result_type":"recent"},
"to_user_id":1203277,"text":"@wonderchook  You need to write a book
"Adventures in #Geoglobaldomination" or "Bangin
BP"",
"id":17997780478,"from_user_id":100089794,
"to_user":"wonderchook","geo":null,"iso_language_code":"en","source":"<a
href="http://www.tweetdeck.com"
rel="nofollow">TweetDeck</a>"}

Note no location info.  However, if I do
http://search.twitter.com/search.json?q=%23geoglobaldomination&geocode=38.895111,-77.036667,100mi
The result is:
{"location":"Springfield, VA","profile_image_url":"http://a1.twimg.com/
profile_images/907787936/shitstorm_normal.jpg","created_at":"Thu, 08
Jul 2010 01:43:02 +0000","from_user":"geo_rube","metadata":
{"result_type":"recent"},"to_user_id":1203277,"text":"@wonderchook
You need to write a book "Adventures in
#Geoglobaldomination" or "Bangin BP"","id":
17997780478,"from_user_id":
100089794,"to_user":"wonderchook","geo":null,"iso_language_code":"en","source":"<a
href="http://www.tweetdeck.com"
rel="nofollow">TweetDeck</a>"}

Reply via email to