Worked like a charm. Thanks so much!
On May 21, 2:29 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Ken, > > Few things I would check: > > #1 - is the account that you are using "geo-enabled" ? You can configure > this option on the account settings page:http://twitter.com/settings/account > #2 - I noticed that in your query here, you've specified > "display_coordinates=true" with a question mark ahead of it. Since you > already had a query parameter, you should be joining it by an ampersand > (same with long) > #3 - The lat, long, and display_coordinates are all more appropriately > passed as POST parameters (like you are doing for status > > Your request, given that the user is geo-enabled, might be better executed > as: > > curl -u username:password -d status="status_text" -d lat="32.6626" -d > long="-115.8471" -d > display_coordinates="true"http://api.twitter.com/1/statuses/update.json > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Fri, May 21, 2010 at 12:26 PM, Ken Hoff <telefrag...@gmail.com> wrote: > > Hey there – I've been trying to get geolocation in my tweets and it's > > not taking. It posts the tweet to the correct account just fine, but > > the tweet doesn't contain any location data. The account is geo > > enabled. Here's an example of my curl call: > > > curl -u username:password -d status="status_text" > > >http://api.twitter.com/1/statuses/update.json?lat=32.6626?long=-115.8... > > > I'm not sure what's wrong with it. Any chance anyone knows what's up?