Furthermore, here is a tweet that shows what's going on:
http://twitter.com/#!/TaimMobile/status/35349967103209472
Tweeted from 51st Street (btw 6/7th ave), yet the map shows 34th
street.
Obviously the map on the website shows the same incorrect data:
http://www.taimmobile.com
Is this the
Hi David,
We use the lat/lon sent to us when the Tweet is created. How that lat/lon is
retrieved depends on the device being used to send the Tweet. The content of
the Tweet is not used to populate the lat/lon coordinates.
A couple of reasons for why it could be reported like this:
* The user is
Thanks for the tips Matt.
The people using this system definitely send the tweet when they reach their
final destination (they're run a food truck), and don't use wifi. They are
using both iPhone and Android phones to send these tweets, so the only answer
is that their devices must be sending
OK, thanks for the confirmation about how the data is being retrieved. From
an API perspective we receive two parameters, lat and lon. Whatever the
client sets those to is what the Tweet gets attributed to.
Looking at that Tweet I see the Geo Point of reference for the Tweet you
mentioned is:
On Wed, 9 Feb 2011 14:35:06 -0500, David Terranova
da...@davidterranova.com wrote:
Thanks for the tips Matt.
The people using this system definitely send the tweet when they
reach their final destination (they're run a food truck), and don't
use wifi. They are using both iPhone and Android
