[twitter-dev] location track error!
I tried thousands of times, and it's always like this: Location track items must be given as pairs of comma separated lat/ longs: [Ljava.lang.String;@4e08cd9c my query is: curl -d locations http://stream.twitter.com/1/statuses/filter.json -u zhangle871024:*** where *** is my password, I will not show it here. :) the locations file is just the following: locations=-122.75,36.8,-121.75,37.8,-74,40,-73,41 And this locations is the example on Twitter Streaming API doc. See: -- Example: Create a file called ‘locations’ that contains, excluding the quotation marks, the phrase: “locations=-122.75,36.8,-121.75,37.8,-74,40,-73,41” then execute: curl -d @locations http://stream.twitter.com/1/statuses/filter.json - uAnyTwitterUser:Password. You will receive all geo tagged tweets from the San Francisco and New York City area. -- What wrong with it?? Can anyone give some hint? I am really, really appreciating your help. 3ks! -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] location operator for the Search API
Any idea? -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On Jan 24, 2011, at 00:23 , Yusuke Yamamoto wrote: Hi, What is location operator? The doc for the search API addresses location operator in Operator Limits paragraph. http://dev.twitter.com/doc/get/search - location operator: • results are limited to 7 days - But the operator is not listed in the following page: http://search.twitter.com/operators Is the operator really existing? Thanks in advance, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] location operator for the Search API
Hi, What is location operator? The doc for the search API addresses location operator in Operator Limits paragraph. http://dev.twitter.com/doc/get/search - location operator: • results are limited to 7 days - But the operator is not listed in the following page: http://search.twitter.com/operators Is the operator really existing? Thanks in advance, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Location-based search is returning tweets that should not be included (again)
In response to this query: http://search.twitter.com/search.atom?rpp=100geocode=38.627522%2C-90.19841%2C30misince_id=28525950136229890 I get tweets like this: http://api.twitter.com/1/statuses/show/28525953676218368.json We're talking about a location search for St. Louis MO, radius of 30 miles. We're getting a guy from Jeffersonian, but timezone is Madrid. Any ideas where this wire got crossed, when we can get it uncrossed, or what the long-term viability of location based searches are? Marc Brooks http://stltweets.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Location-based search is returning tweets that should not be included (again)
On Fri, 21 Jan 2011 12:37:18 -0800 (PST), @IDisposable idisposa...@gmail.com wrote: In response to this query: http://search.twitter.com/search.atom?rpp=100geocode=38.627522%2C-90.19841%2C30misince_id=28525950136229890 I get tweets like this: http://api.twitter.com/1/statuses/show/28525953676218368.json We're talking about a location search for St. Louis MO, radius of 30 miles. We're getting a guy from Jeffersonian, but timezone is Madrid. Any ideas where this wire got crossed, when we can get it uncrossed, or what the long-term viability of location based searches are? Marc Brooks http://stltweets.com I filed an issue last year and it was closed as fixed on January 8, 2011: http://code.google.com/p/twitter-api/issues/detail?id=1348 I have a Perl script that will grab tweets in a 25 mile radius of Portland, Oregon and dump them to CSV. I haven't run it in a while, though, so I don't know if the results are better now than when I filed it. If you have something to reproduce this, maybe you should re-open issue 1348. I guess given the low percentage of people who enter their actual location in the profile, as opposed to being from Botland or Earth or Hilbert Space, maybe the Search API should only return geotagged tweets when a geocode radius is specified, like the Streaming filter API does. It's that or somehow crowdsource locations, which is going to violate peoples' privacy if done without permission. To me it seems like a tradeoff between clean but very sparse data or messy but copious data that can be imputed or cleaned via crowdsourcing provided permissions can be obtained. I can't put a business case forward for either option from Twitter's perspective, but I think I'd prefer as a researcher to have Search adopt the Streaming model and only return geotagged tweets when a geocode parameter is specified. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Location returning no results
I use Abraham Williams's Twitteroauth https://github.com/abraham/twitteroauth to search for Tweets near a location (for http://twitter.com/#!/birminghamuk) but in the last few days it has started returning no results. Similarly search.Twitter.com is returning no results for any search near a location Is anyone else having these issues? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] location based search and user location field
Hi, Search API with location restriction (geocode parameter) used to search through tweets that were geotagged and also tweets that were tweeted by user who had set her location in profile settings. Seems that currently search API, when both geocode and and q parameters are set, only goes through the geotagged tweets. Although seems that when only geocode is set, tweets are included by user' location field as well. I was told (by @twitterapi) that this is temporary situation to be fixed soon. 1) Can anyone suggest when will it probably be fixed? is there alternative solution until then? 2) I would like to try out Streams API' filter method, but it is states that this only goes through geotagged tweets. Is there any workaround to make frequent location specific searches through geotagged tweets and also the ones that are not geotagged? Thank you in advance, siim -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Location information only delivered on geocoded searches?
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 +,
from_user:geo_rube,
metadata:{result_type:recent},
to_user_id:1203277,text:@wonderchook You need to write a book
quot;Adventures in #Geoglobaldominationquot; or quot;Bangin
BPquot;,
id:17997780478,from_user_id:100089794,
to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
Note no location info. However, if I do
http://search.twitter.com/search.json?q=%23geoglobaldominationgeocode=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 +,from_user:geo_rube,metadata:
{result_type:recent},to_user_id:1203277,text:@wonderchook
You need to write a book quot;Adventures in
#Geoglobaldominationquot; or quot;Bangin BPquot;,id:
17997780478,from_user_id:
100089794,to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
Re: [twitter-dev] Location information only delivered on geocoded searches?
Hi James,
I'm not sure why the location field is missing from those search results so
I'll need to follow that up. Can you file it as a defect in the API Issues
List: http://code.google.com/p/twitter-api/issues/list
and i'll look into it.
Just to clarify though, the location field is the location you see under a
users name on their Twitter profile page. It is a free-text field in which
the user can put anything they want. If Twitter Search can reverse geocode
the text in that field it will use it as the geo for the Tweet only when the
Tweet itself doesn't have any geo co-ordinates. This means when you perform
a Geocoded Twitter Search you may see results you wouldn't expect. For
example somebody who says their location is San Francisco but is on holiday
in New York may not geocode their Tweets and so their Tweets will be indexed
as being in San Francisco.
Hope that explains how this works.
Thanks,
Matt
On Thu, Jul 8, 2010 at 6:16 AM, James tedr...@gmail.com wrote:
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 +,
from_user:geo_rube,
metadata:{result_type:recent},
to_user_id:1203277,text:@wonderchook You need to write a book
quot;Adventures in #Geoglobaldominationquot; or quot;Bangin
BPquot;,
id:17997780478,from_user_id:100089794,
to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
Note no location info. However, if I do
http://search.twitter.com/search.json?q=%23geoglobaldominationgeocode=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 +,from_user:geo_rube,metadata:
{result_type:recent},to_user_id:1203277,text:@wonderchook
You need to write a book quot;Adventures in
#Geoglobaldominationquot; or quot;Bangin BPquot;,id:
17997780478,from_user_id:
100089794,to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
Re: [twitter-dev] Location information only delivered on geocoded searches?
Quoting Matt Harris thematthar...@twitter.com:
Hi James,
I'm not sure why the location field is missing from those search results so
I'll need to follow that up. Can you file it as a defect in the API Issues
List: http://code.google.com/p/twitter-api/issues/list
and i'll look into it.
Just to clarify though, the location field is the location you see under a
users name on their Twitter profile page. It is a free-text field in which
the user can put anything they want. If Twitter Search can reverse geocode
the text in that field it will use it as the geo for the Tweet only when the
Tweet itself doesn't have any geo co-ordinates. This means when you perform
a Geocoded Twitter Search you may see results you wouldn't expect. For
example somebody who says their location is San Francisco but is on holiday
in New York may not geocode their Tweets and so their Tweets will be indexed
as being in San Francisco.
Hope that explains how this works.
Thanks,
Matt
If your search query does *not* include a 'geocode=' parameter, the
tweets returned will *not* have *any* location information! I don't
recall if this is a bug or a feature, or whether I filed an issue
report. ;-)
On Thu, Jul 8, 2010 at 6:16 AM, James tedr...@gmail.com wrote:
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 +,
from_user:geo_rube,
metadata:{result_type:recent},
to_user_id:1203277,text:@wonderchook You need to write a book
quot;Adventures in #Geoglobaldominationquot; or quot;Bangin
BPquot;,
id:17997780478,from_user_id:100089794,
to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
Note no location info. However, if I do
http://search.twitter.com/search.json?q=%23geoglobaldominationgeocode=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 +,from_user:geo_rube,metadata:
{result_type:recent},to_user_id:1203277,text:@wonderchook
You need to write a book quot;Adventures in
#Geoglobaldominationquot; or quot;Bangin BPquot;,id:
17997780478,from_user_id:
100089794,to_user:wonderchook,geo:null,iso_language_code:en,source:lt;a
href=quot;http://www.tweetdeck.comquot;
rel=quot;nofollowquot;gt;TweetDecklt;/agt;}
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
[twitter-dev] Location glitches
I've got openSUSE 11.2 64-bit, connected to the Internet via wireless. I'm running both Firefox 3.6.3 and Chrome 6.0.427.0 dev. Chrome seems to be picking up my location correctly. When I go into the menu to set my location, I am seeing a list of businesses nearby, including the place where I'm working. But Firefox has a completely different list of businesses, a couple miles away in a totally different neighborhood! Apparently Mozilla is somehow garbling the location information it's getting from Google, or Google is favoring its own browser. Anybody else seeing this? One other note: *both* browsers are resetting the location after I post a tweet! It drops back to a neighborhood or city. I don't see much point in filing a ticket at this time - the fail whales are probably a tad more interesting to Twitter at the moment.
[twitter-dev] Location finding practices
I've taken a look at recent posts on locations and geo-tagging. My read of all of this is that we can associate tweets with locations in ~3 ways.. 1. Geo-tags (user opt-in) 2. Location (user provided, pretty um.. low quality) 3. Some kind of behind the scenes magic that Twitter is doing For case 3, that means that when we specify geo-boxes we're getting something more than just 1. Is there anything available publicly about how this is done? i.e. is it parsing of User.location, some kind of IP thing, spy satellites..? ;) As someone posted a while back, it seems that we can get all tweets within a geo-box, but we can't get the inverse, i.e. an (approximate) lat lon for an arbitrary tweet. So suppose: Tg[] = all tweets within box g. Tg[k] = some tweet in that bounding box, *without* a geo-location U[l].tweets.contains(Tg[k]) From which I know that Tg[k] is in g. Now, is that based solely on info from U[l] or does it take into account anything about Tg[k]? And, is my understanding correct that if I discovered Tg[k] from somewhere outside of that location search, I *can't* determine g (unless of course it is geo-tagged or I do some kind of bone-headed exhaustive search..) ? Finally, has anyone else in API-consumer land come up with a good set of heuristics for determining location from the user.location alone? I mean, there are some obvious steps, but I don't want to re-invent the wheel and given the uncertainty about the data available (TeaPartyVille,USA, Beer City In Flavor Country (sounds like a nice place to visit)) I'm not certain it's worth it. Are people having pretty good results about just parsing place names? Code? :) And of course, does anyone want to tell us/speculate about what TrendsMaps is doing here? My assumption is that they are just doing searches based on the twitter geo-boxing, but perhaps there is more magic here that might be sharable. enquiring minds... Miles
[twitter-dev] Location Data From Stream API
OK my app basically provides a way for users to come to the site, and look at local tweets by city/state combo (I have to include state because a lot of states have identical city names). I WAS using the search API feature with geocodes to get local tweets and it worked PERFECTLY minus of course the limited data set problem -- but I obviously can't do that due to API call limits and having (hopefully :)) thousands of users per day searching for local tweets repeatedly. Now according to Raffi Krikorian 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. Well, not having knowledge of those other signals... leaves me with pretty much nothing but the Location field to parse for location information. Right now I'm working on a DB search scheme to match likely city, state combos but other than that do you guys see any other methodology I may be overlooking?? The location field, unless it contains lon/lat coordinates, is a mess of garbage, nonsense, mispelled names, and a host of other useless noise. The ones that have lon/lat information in the tweet location field are perfect because then I can do my own radius calculations locally. But, for example, out of a 1.5 million tweet sample only 100,200 of those had lon/lat coordinates :(
Re: [twitter-dev] Location Data From Stream API
Parsing the location field is probably your best bet, but I'd say you have a challenging road ahead. It is indeed a mess, but there are geocoding solutions available to try and sort this stuff out. ---Mark http://twitter.com/mccv On Fri, Mar 5, 2010 at 1:04 PM, GeorgeMedia georgeme...@gmail.com wrote: OK my app basically provides a way for users to come to the site, and look at local tweets by city/state combo (I have to include state because a lot of states have identical city names). I WAS using the search API feature with geocodes to get local tweets and it worked PERFECTLY minus of course the limited data set problem -- but I obviously can't do that due to API call limits and having (hopefully :)) thousands of users per day searching for local tweets repeatedly. Now according to Raffi Krikorian 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. Well, not having knowledge of those other signals... leaves me with pretty much nothing but the Location field to parse for location information. Right now I'm working on a DB search scheme to match likely city, state combos but other than that do you guys see any other methodology I may be overlooking?? The location field, unless it contains lon/lat coordinates, is a mess of garbage, nonsense, mispelled names, and a host of other useless noise. The ones that have lon/lat information in the tweet location field are perfect because then I can do my own radius calculations locally. But, for example, out of a 1.5 million tweet sample only 100,200 of those had lon/lat coordinates :(
Re: [twitter-dev] Location Data From Stream API
Quoting Mark McBride mmcbr...@twitter.com: Parsing the location field is probably your best bet, but I'd say you have a challenging road ahead. It is indeed a mess, but there are geocoding solutions available to try and sort this stuff out. Be *very* careful with geocoding solutions, especially taking note of the terms of service and licensing constraints. Google, Yahoo and Microsoft all have restrictions on what you can do with their tools. There are some open source / free as in freedom tools too, but they may be more limited. I've spent a number of hours recently working with various open source projects associated with mapping earthquake and other disaster zones, and this is a constant source of frustration. I'm guessing it would be even more a source of frustration if you're building marketing / sales tools rather than non-profit ones. People trapped in the rubble of a collapsed build usually *want* to be found; people sitting in a restaurant having a glass of wine with some friends might not. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos
[twitter-dev] Location of a Tweet
I am new to java and I was wondering if anybody knew how to get the location of a tweet (not the geolocation) using the twitter4j Library when you do a query class search. Thanks
[twitter-dev] Location Specific Public Timeline
Hi, I'm trying to build an application around trending topics based on a specific location through the public timeline, but would rather not filter the timeline on location afterwards. I did notice the Local Trends Methods, but I would like to set my own parameters and therefore depend on the public timeline to get the recent posts for the specific country. Is there a way to request the http://twitter.com/statuses/public_timeline.xml for specific countries and/or locations? I need the most recent status posts from a specific location, but I don't want to waste requests by deleting most of the data afterwards. Any help would be great! Arthur
Re: [twitter-dev] Location Specific Public Timeline
not right now, unfortunately. On Fri, Dec 11, 2009 at 5:16 AM, ArtJulian art.jul...@gmail.com wrote: Hi, I'm trying to build an application around trending topics based on a specific location through the public timeline, but would rather not filter the timeline on location afterwards. I did notice the Local Trends Methods, but I would like to set my own parameters and therefore depend on the public timeline to get the recent posts for the specific country. Is there a way to request the http://twitter.com/statuses/public_timeline.xml for specific countries and/or locations? I need the most recent status posts from a specific location, but I don't want to waste requests by deleting most of the data afterwards. Any help would be great! Arthur -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] location data for searched tweets
Hi, is it not possible to get the location data as a return value after a search request? For example, if I get the tweets for the query swine flue, it won´t be possible to get location data fot them? So I need a method to get users details. But it cost a lot api calls for every user. Is there any clever way to solve this? Thanks.
