Re: [twitter-dev] Geo-caching Without Lat/Long

2010-06-11 Thread Matt Harris
Hey Bryan,

Status updates only accept lat/long or place_id. There isn't a way of
providing plain text locations for these fields. If you wish to display a
textual representation of where someone is on your app you would need to
carry out a reverse geocode first.

I don't know the method you are using to obtain the location but generally
we see developers use the lat/long returned by the browser or device.

One thing that might be useful to know is that we perform a reverse lookup
on the lat/long when we display the tweet, converting it to some textual
description like "SoMa, San Francisco", or "from here" as appropriate.

Hope that answers your question,
Matt

On Fri, Jun 11, 2010 at 6:41 AM, Bryan  wrote:

> Hey everyone, is there a way to geo-tweet with the API without knowing
> the Lat/Long? In other words, can I say "San Francisco, CA" or search
> for valid place_id's with this name? I'm trying to make my user
> interface as user-friendly as possible, and asking for lat/long for my
> userbase won't work. I also want to rely on as few as API's as
> possible, so I'd prefer not to run my name through Google's Map API
> and then through the reverse geocode API on twitters. Thanks.
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris


[twitter-dev] Geo-caching Without Lat/Long

2010-06-11 Thread Bryan
Hey everyone, is there a way to geo-tweet with the API without knowing
the Lat/Long? In other words, can I say "San Francisco, CA" or search
for valid place_id's with this name? I'm trying to make my user
interface as user-friendly as possible, and asking for lat/long for my
userbase won't work. I also want to rely on as few as API's as
possible, so I'd prefer not to run my name through Google's Map API
and then through the reverse geocode API on twitters. Thanks.