Re: [twitter-dev] Re: Twitter Places Follow Up
Only tweets from the place, or a place within the place. David On Thu, Jun 24, 2010 at 12:44 PM, ELB ebrit...@gmail.com wrote: Currently we call the exact same endpoint to get the Tweets from a given place, but we pass the latitude and longitude, rather than the Place ID. The Latitude/Longitude method forces a 1 km radius around the endpoint. So, when we get the tweets via the Place ID method at the same endpoint - will it only show tweets from the actual place or will it show us Tweets from the place and the surroinding 1km radius? On Jun 23, 11:59 am, David Helder da...@twitter.com wrote: Sure, do this: 1) Find the place ID of the Staples Center:http://api.twitter.com/1/geo/search.json?query=Staples%20Centerlat=3... = The place ID is 7893eab4ca4c1efb (second result) 2) Get all tweets from that ID:http://search.twitter.com/search.json?q=place:7893eab4ca4c1efb If you only have 100 places, you could probably do 100 searches and find the best result by hand when there are multiple results. David On Tue, Jun 22, 2010 at 9:35 AM, ELB ebrit...@gmail.com wrote: The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update orhttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0u...) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Twitter Places Follow Up
Sure, do this: 1) Find the place ID of the Staples Center: http://api.twitter.com/1/geo/search.json?query=Staples%20Centerlat=34.04lon=-118.27granularity=poi = The place ID is 7893eab4ca4c1efb (second result) 2) Get all tweets from that ID: http://search.twitter.com/search.json?q=place:7893eab4ca4c1efb If you only have 100 places, you could probably do 100 searches and find the best result by hand when there are multiple results. David On Tue, Jun 22, 2010 at 9:35 AM, ELB ebrit...@gmail.com wrote: The statuses/update API linked to (http://dev.twitter.com/doc/post/ statuses/update or http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update) is the method that is used for an authenticated Twitter user to add his/her own new Tweet. (It's not a method of returning Tweets already created by other users.) We don't want to create Tweets from a given place - instead we want to use the Twitter API to publish Tweets from a given place. So, here is our page about the Staples Center in Los Angeles. http://sency.com/los-angeles/STAPLES-Center-4165 our goal is to publish the most recent Tweets, made from the Staples Center - on this page... would this be possible based on the current Twitter API?
Re: [twitter-dev] Twitter Places
Sure, you can use the search method to find the place ID: http://dev.twitter.com/doc/get/geo/search Then set the place_id argument to /statuses/update to tweet from that place: http://dev.twitter.com/doc/post/statuses/update David On Sun, Jun 20, 2010 at 9:01 PM, ELB ebrit...@gmail.com wrote: Hello, I read on the Twitter blog that: (http://blog.twitter.com/2010/06/ twitter-places-more-context-for-your.html) We are releasing API functionality that lets developers integrate Twitter Places into their applications.“ I wanted to check in to see where we could learn about what functionality has been released. We have 100 places, ie: Staples Center, LAX Airport, Grand Central Terminal, etc that we want to publish Tweets from. Are we able to use the Twitter API to publish the current Tweets from a given place? if so, where in the API is the documentation to do this? ELB
Re: [twitter-dev] Re: Recent Places-related API enhancements more to come...
The geo field is the user's (or tweet's) exact location. The place field, whether a POI, neighborhood, city, or admin, contains the place's location. Today POIs are always points, but in the future there may be some polygons (e.g. stadiums, malls, amusement parks). In this case the exact location would matter. A place-annotated tweet will show up in the streaming API, even if it doesn't have an exact location. David Twitter Geo Team On Thu, Jun 17, 2010 at 3:28 PM, harrisj harrisj.h...@gmail.com wrote: Hello, Currently, using places doesn't modify the 'geo' field. This makes sense for neighborhoods or cities, because picking a centroid is a little arbitrary and those users might get freaked out if we place them at a specific point on a map. However, I would argue that this behavior is counterintuitive when we get to the 'poi' level. When I pick the building I'm in on twitter.com, I'm assuming I'm geocoding my location (and providing some additional semantic information beyond lat/lng). However, this doesn't seem to be the case. Would we consider changing this? Furthermore, will any place-annotated tweets show up in the streaming API when using the locations query parameters? Or is that only limited to explicitly geotagged tweets? Thanks, Jacob
Re: [twitter-dev] Granularity for geo/search is strange/unknown
That query will search for java java places of type neighborhood or higher granularity (including city, admin, and country). If you want POI (or higher), set granularity to poi. We do return results that are far away. This may be controllable in the future. The autocomplete parameter is flag that's a hint that search is being used for autocompletion. It will favor results with matching prefixes. An admin place is an administrative area, such as a state or province. David Twitter Geo Team On Wed, Jun 16, 2010 at 7:54 AM, MeltingIce meltingice8...@gmail.com wrote: Hey everyone, I am trying to search for locations using the new geo/search API call, but the granularity of the locations returned is nearby cities at best even though the granularity is set to neighborhood. I would like to pass in simply a lat/long, but even when I pass in a search query as well, I either get extremely broad results or no results at all. Heres an example that I've been trying which is returning cities as far away as Virginia although the lat/long is really in Charleston, SC. http://api.twitter.com/1/geo/search.json?query=java+javaaccuracy=761.9884176autocomplete=falselong=-80.1489lat=32.6058granularity=neighborhood The autocomplete param is undocumented, although switching it from false to true doesn't seem to have an effect anyways. Is there something I'm missing here? Thanks in advance for the help!
Re: [twitter-dev] Geotagging Bug: Anything North of London, UK is mapped to Alaska, USA :-)
We're working on this.
David
Twitter Geo Developer
On Tue, Mar 30, 2010 at 10:42 AM, janole s...@mobileways.de wrote:
I've been getting some bug reports of users of my Twitter client
Gravity since yesterday evening.
The mapping of places for coordinates North of London seems to be
buggy.
Geotagging a tweet with latitude 52.41 and longitude -1.90 (somewhere
near Birmingham, UK) claims that this is a place in Alaska, US!
{place:{place_type:admin,country_code:US,bounding_box:
{type:Polygon,coordinates:[[[-179.231086,51.175092],
[179.859681,51.175092],[179.859681,71.441059],
[-179.231086,71.441059]]]},full_name:Alaska,
US,name:Alaska,id:07179f4fe0500a32,country:The United
States of America,url:http://api.twitter.com/1/geo/id/
07179f4fe0500a32.json}
The coordinates in the tweet are still correct, though:
coordinates:{type:Point,coordinates:[-1.9,52.41]}
Unfortunately, the website seems to use the wrong place instead of the
correct coordinates.
ole @ mobileways.de
http://twitter.com/janole
To unsubscribe from this group, send email to twitter-development-talk+
unsubscribegooglegroups.com or reply to this email with the words REMOVE
ME as the subject.
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words REMOVE ME as the subject.
Re: [twitter-dev] Geotagging Bug: Anything North of London, UK is mapped to Alaska, USA :-)
This should work now. Let us know if you see any further problems.
David
On Tue, Mar 30, 2010 at 12:32 PM, David Helder da...@twitter.com wrote:
We're working on this.
David
Twitter Geo Developer
On Tue, Mar 30, 2010 at 10:42 AM, janole s...@mobileways.de wrote:
I've been getting some bug reports of users of my Twitter client
Gravity since yesterday evening.
The mapping of places for coordinates North of London seems to be
buggy.
Geotagging a tweet with latitude 52.41 and longitude -1.90 (somewhere
near Birmingham, UK) claims that this is a place in Alaska, US!
{place:{place_type:admin,country_code:US,bounding_box:
{type:Polygon,coordinates:[[[-179.231086,51.175092],
[179.859681,51.175092],[179.859681,71.441059],
[-179.231086,71.441059]]]},full_name:Alaska,
US,name:Alaska,id:07179f4fe0500a32,country:The United
States of America,url:http://api.twitter.com/1/geo/id/
07179f4fe0500a32.json}
The coordinates in the tweet are still correct, though:
coordinates:{type:Point,coordinates:[-1.9,52.41]}
Unfortunately, the website seems to use the wrong place instead of the
correct coordinates.
ole @ mobileways.de
http://twitter.com/janole
To unsubscribe from this group, send email to twitter-development-talk+
unsubscribegooglegroups.com or reply to this email with the words REMOVE
ME as the subject.
--
To unsubscribe, reply using remove me as the subject.
