Hi Damon.
Yup - we've started updating the docs.
Generally, there will always be a <geo> in the <status> (it may just
be empty, however, if there is no geolocated information attached),
and there will always be a <geo_enabled> on every <user> which is a
boolean representing whether the user has enabled geolocation on his
or her account.
On Aug 21, 2009, at 6:46 PM, Damon Clinkscales <[email protected]> wrote:
On Aug 20, 3:46 pm, Ryan Sarver <[email protected]> wrote:
We wanted to give you all a heads up on a cool new feature that is
coming
soon - Geolocation.
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%A0u...http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve
...
Ryan,
Very cool stuff. Looking forward to it.
I'm assuming that you'll update the wiki (and API when it launches)
such that
everywhere a <status> element is returned, it will contain a <geo>
element?
Thanks,
-damon
