It is important to note that the feature is going to be
strictly opt-in. It will be disabled until a user chooses to switch it on. We will provide a read-only attribute <geo_enabled> on the user object so an app can detect if the user has it disabled and let them know if they need to turn it on before using a geolocation feature.
While we can't provide an exact date for launch, you should plan on having a few weeks of development time before the new API is officially launched. With that being said, lets get to it...
Example: Geotagging a Tweet
-----------------------
curl -d "lat=37.780467&long=-122.396762&status=I have arrived" -u user:pass "
http://twitter.com/statuses/update.xml"
<?xml version="1.0" encoding="UTF-8"?>
<status>
<created_at>Tue Apr 07 22:52:51 +0000 2009</created_at>
...
<geo xmlns:georss="http://www.georss.org/georss">
<georss:point>37.780467 -122.396762</georss:point>
</geo>
<user>
<id>1401881</id>
<name>Doug Williams</name>
...
<geo_enabled>true</geo_enabled>
...
</user>
</status>
We have also updated the wiki to reflect what the API will look like when it launches, so check it out and let us know if you have any questions:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
We'll also be in our recently announced IRC channel (#twitterapi on
irc.freenode.net) if you want to discuss the announcement with the team.
Ryan