Hi Diego,

If you want to geotag your tweets from a web browser you can use the
service we developed in my company: http://www.kirigo.com
It's still in beta and not so many people are using it, but if you
find it useful please spread the news

I do welcome any feedback

Luca

dbasch ha scritto:
> Many people use UberTwitter from their phone and also tweet from the
> web or a desktop client. UT updates the profile location with GPS data
> but the browser doesn't. If the source of the tweet is UT chances are
> the location is accurate, otherwise it's probably old. If you
> desperately need to pin as many tweets on the map as possible you may
> want to use this information for the time being.
>
> Diego
>
> On Dec 14, 8:33 pm, redders <redders6...@googlemail.com> wrote:
> > Hi Raffi,
> >
> > I'll be interested to hear when the API adds functionality that'll
> > allow us to retrieve *only* tweets with a geopoint! Any hints?
> >
> > In the meantime; copyied from the first post, what is going on with
> > tweets like this? :
> > {
> >     * location: "iPhone: 37.313690,-122.022911"
> >     * geo: null
> >
> > }
> >
> > {
> >     * location: "ÜT: 37.293106,-121.969004"
> >     * geo: null
> >
> > }
> >
> > Presumably this is some developer-implemented work around from a
> > client that geotagged tweets before the geotagging API was available,
> > by setting the profile location (where it normally says London, UK
> > etc.) to co-ords?
> > If so, I will just ignore it, as these should in theory become less
> > and less common as developers update their apps to use the official
> > geotagging method, but I want to be sure that I'm not missing some
> > crucially geotagged tweets!

Reply via email to