[twitter-dev] Geotagging
Hello,
firstable, i need to get the location of a tweet not tweets of
location !!
ok this time i'll explain things in details.., i'm using the hammock
library..t this is an example to get statuses:
var request = new RestRequest
{
Credentials = _credentials,
Path = /statuses/update.xml,
Method = WebMethod.Post
};
request.AddParameter(status, tweetText);
i just need to add other parameters like place_id or lon and lat ! but
i can't figure out !! :( since this function called from hammock take
only 2 parameters!
PS: i'm working on wp7
Thanks.
--
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
[twitter-dev] Geotagging
Hello, i'm a student engineer and i'm developping a twetter Client for WP7...In fact, i almost finnished and i just want to add a geotagging service to localizate any tweet a user want! i realized my map by calling this service from bing...but it still static positions but i want to make that dynamic using twitter APIs so help plz because the time is killing me to validate my project. Thanks! -- 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] geotagging
Hello, I'm building a twitter client with windows phone 7 and i want to localizate a tweet .. does anyone has ideas and help! Thanks Nassr Zied -- 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] Geotagging broken when user is using a foreign language
Please see bug report 1725 - http://bit.ly/anxAiC Apparently, you cannot geotag tweets anymore when a user's account is configured to any non-English language. My client users started to report this error a couple of days ago. When they switch back to English (lang = en), everything's fine again and they can geo-tag their tweets. ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client #Gravity
Re: [twitter-dev] Geotagging broken when user is using a foreign language
Oh dear, thanks a lot for this info. I was trying for two days to get this working! Thanks! Daniel Am 06.07.2010 um 13:24 schrieb janole: Please see bug report 1725 - http://bit.ly/anxAiC Apparently, you cannot geotag tweets anymore when a user's account is configured to any non-English language. My client users started to report this error a couple of days ago. When they switch back to English (lang = en), everything's fine again and they can geo-tag their tweets. ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client #Gravity
Re: [twitter-dev] Geotagging broken when user is using a foreign language
can you all please provide a concrete example? i just geotagged a tweet from my test account, switched my test account to spanish, then successfully geotagged another tweet, switched to japanese, and then geotagged yet another tweet. On Tue, Jul 6, 2010 at 4:43 AM, Daniel Schroeder deeme...@googlemail.comwrote: Oh dear, thanks a lot for this info. I was trying for two days to get this working! Thanks! Daniel Am 06.07.2010 um 13:24 schrieb janole: Please see bug report 1725 - http://bit.ly/anxAiC Apparently, you cannot geotag tweets anymore when a user's account is configured to any non-English language. My client users started to report this error a couple of days ago. When they switch back to English (lang = en), everything's fine again and they can geo-tag their tweets. ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client #Gravity -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Geotagging Bug: Anything North of London, UK is mapped to Alaska, USA :-)
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.
Re: [twitter-dev] Geotagging Bug: Anything North of London, UK is mapped to Alaska, USA :-)
Has Sarah Palin joined Twitter? :P Aral On Tue, Mar 30, 2010 at 6:42 PM, 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! snip 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 :-)
On 03/30/2010 11:18 AM, Aral Balkan wrote: Has Sarah Palin joined Twitter? :P Aral On Tue, Mar 30, 2010 at 6:42 PM, 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! snip 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. IIRC only USA locations are in Twitter's database. So there's definitely a bug if a geotag in the UK is being accepted as defining a place. 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 :-)
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.
Re: [twitter-dev] Geotagging API
Raffi / list - thanks again for confirming things with re: to GeoJSON.
It will be interesting to see the adoption of the Geo tagging across
the numerous hashtags we are tracking at TwapperKeeper.
map - http://twapperkeeper.com/geoall.php
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
http://www.linkedin.com/in/jobrieniii
On Nov 21, 2009, at 5:53 PM, Raffi Krikorian wrote:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
right now we only support point types -- you'll see georss for XML
and geojson for JSON.
does that help?
Raffi,
Thanks again for this. Is there anywhere in the wiki that explains
the various types (Point, etc) and if the object model is
different?
[I didn't see anything offhand...]
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian wrote:
here is something i just ran against the search API (i formatted
the JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from
%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's
APIs. Specific geotagging methods have been added and existing
formats expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our
Geotagging Best Practices page [5] where we have UX mock-ups,
hints on how to best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
Raffi - thanks for confirming that only type Point is being leveraged
at this time... made my update to TwapperKeeper much easier this
morning.
Of course, I created a little technical baggage depending on when
other types are leveraged.. but will cross that bridge when the time
comes.
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 21, 2009, at 5:53 PM, Raffi Krikorian wrote:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
right now we only support point types -- you'll see georss for XML
and geojson for JSON.
does that help?
Raffi,
Thanks again for this. Is there anywhere in the wiki that explains
the various types (Point, etc) and if the object model is
different?
[I didn't see anything offhand...]
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian wrote:
here is something i just ran against the search API (i formatted
the JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from
%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's
APIs. Specific geotagging methods have been added and existing
formats expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our
Geotagging Best Practices page [5] where we have UX mock-ups,
hints on how to best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
Raffi,
Thanks again for this. Is there anywhere in the wiki that explains
the various types (Point, etc) and if the object model is different?
[I didn't see anything offhand...]
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian wrote:
here is something i just ran against the search API (i formatted the
JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Best Practices page [5] where we have UX mock-ups, hints on how to
best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-
locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
Wait - I did a little reading and figured out you are aligned with
http://geojson.org/
Thanks,
John
@jobrieniii
http://twapperkeeper.com
On Nov 21, 2009, at 5:17 PM, JOHN OBRIEN wrote:
Raffi,
Thanks again for this. Is there anywhere in the wiki that explains
the various types (Point, etc) and if the object model is different?
[I didn't see anything offhand...]
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian wrote:
here is something i just ran against the search API (i formatted
the JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Best Practices page [5] where we have UX mock-ups, hints on how
to best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
right now we only support point types -- you'll see georss for XML and
geojson for JSON.
does that help?
Raffi,
Thanks again for this. Is there anywhere in the wiki that explains
the various types (Point, etc) and if the object model is different?
[I didn't see anything offhand...]
Thanks again,
John
@jobrieniii
http://twapperkeeper.com
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian wrote:
here is something i just ran against the search API (i formatted
the JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Best Practices page [5] where we have UX mock-ups, hints on how
to best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
here is something i just ran against the search API (i formatted the
JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/
NUNGf,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I can't
find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever they
appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their settings
page [2]. From that page, a user can turn this feature on by
checking the Enable geotagging checkbox. Alternatively, we're
also providing a mobile optimized geotagging settings page [3] that
you can send them too as well. As a developer, you can determine
whether a user has enabled geotagging by calling the users/show
method [4] or in any other user element returned by the REST API
where a user object shows up -- just look for the geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Best Practices page [5] where we have UX mock-ups, hints on how to
best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
Re: [twitter-dev] Geotagging API
Sent from my iPhone
On Nov 20, 2009, at 5:40 PM, Raffi Krikorian ra...@twitter.com wrote:
here is something i just ran against the search API (i formatted the
JSON for readability).
[ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl http://search.twitter.com/search.json?q=ands=twitter+FTWfrom=raffi
{
results:
[
{
profile_image_url:http://a1.twimg.com/profile_images/364041028/raffi-headshot-casual_normal.png
,
created_at:Fri,
20 Nov 2009 15:40:40 +,
from_user:raffi,
to_user_id:null,
text:Soy milk, FTW (@ Twitter in SF) http://bit.ly/NUNGf
,
id:5892191934,
from_user_id:278432,
geo:
{
type:Point,
coordinates:
[
37.7824,
-122.4009
]
},
iso_language_code:en,
source:lt;a href=quot;http://foursquare.comquot;
rel=quot;nofollowquot;gt;foursquarelt;/agt;
}
],
max_id:5900232920,
since_id:0,
refresh_url:?since_id=5900232920q=+twitter+FTW+from%3Araffi,
results_per_page:15,
page:1,
completed_in:0.01934,
query:+twitter+FTW+from%3Araffi
}
On Nov 20, 2009, at 2:21 PM, JOHN OBRIEN wrote:
Quick question...
What format will [geo] be from the /search api?
just the lat long, something like...
[geo] = 37.78029 -122.39697
I am watching a bunch of tweets coming into our service, but I
can't find one that is populated, so just thought I would ask.
(And I can't see anything from my account just yet... )
Thanks,
John
http://twapperkeeper.com
On Nov 19, 2009, at 4:51 PM, Raffi Krikorian wrote:
As you may have seen on the Twitter blog [1], geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
check out
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Geotweets now carry the geotag whenever available and whenever
they appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their
settings page [2]. From that page, a user can turn this feature
on by checking the Enable geotagging checkbox. Alternatively,
we're also providing a mobile optimized geotagging settings page
[3] that you can send them too as well. As a developer, you can
determine whether a user has enabled geotagging by calling the
users/show method [4] or in any other user element returned by
the REST API where a user object shows up -- just look for the
geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Best Practices page [5] where we have UX mock-ups, hints on how to
best support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
[1] http://blog.twitter.com/2009/11/think-globally-tweet-
locally.html
[2] http://twitter.com/account/settings
[3] http://m.twitter.com/account/settings/geo
[4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
[5] http://help.twitter.com/forums/26810/entries/78525
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi
[twitter-dev] Geotagging API
As you may have seen on the Twitter blog [1], geotagging is now available for all users and developers throughout Twitter's APIs. Specific geotagging methods have been added and existing formats expanded to accommodate this rich new information. To get started developing with this API and sending geotweets, check out http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update Geotweets now carry the geotag whenever available and whenever they appear in our REST, Search, and Streaming APIs. Remember, geotagging is disabled by default on users' accounts. Encourage your users to enable it by sending them to their settings page [2]. From that page, a user can turn this feature on by checking the Enable geotagging checkbox. Alternatively, we're also providing a mobile optimized geotagging settings page [3] that you can send them too as well. As a developer, you can determine whether a user has enabled geotagging by calling the users/show method [4] or in any other user element returned by the REST API where a user object shows up -- just look for the geo_enabled flag. For more hints on how to use geotagging, check out our Geotagging Best Practices page [5] where we have UX mock-ups, hints on how to best support user privacy, and more. We're really excited about this feature! And more is coming. Go get lost. We'll send help. [1] http://blog.twitter.com/2009/11/think-globally-tweet-locally.html [2] http://twitter.com/account/settings [3] http://m.twitter.com/account/settings/geo [4] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show [5] http://help.twitter.com/forums/26810/entries/78525 -- Raffi Krikorian Twitter Platform Team ra...@twitter.com | @raffi
