so an opted-in user will have latLong data automatically attached to
her/his updates, taken from the browser/client W3c geolocation
capabilities or is it necessary to explicitly include them in the
message content?
On Aug 21, 6:44 pm, Ryan Sarver wrote:
> Ben,
>
> Currently we geocode your user.
ok ok...
so I guess the Search API json response will include a:
'geo': {
"type":"Point",
"coordinates":[37.78029, -122.39697]
}
block for each of element of the 'results' array
BTW: I believe
'geo': null
would be formally more correct than
'geo': {}
for tweets missing geoLocation metadata.
ok ok...
so i guess that in the search API json response we will see an extra:
"geo":
{
"type":"Point",
"coordinates":[37.78029, -122.39697]
}
for each element of the 'results' array.
BTW: I believe "geo": null,
would be more manageable and formally correct then:
"geo":{}, when geolocation me
wondering... how does the language of a tweet actually get set ?!
is it taken from the profile settings (location?), http headers set
from the user OS or from actually analyzing the text content and
assigning to a language with a dedicated algorithm?!
On Aug 17, 4:59 pm, Ben Eliott wrote:
> H
I tried this with the search API, json version (
http://search.twitter.com/search.atom?lang=en&q=devo)
but did not see get any geo sub-object... is it on only for atom
output or ..?!?
™hanks,ciao
On Oct 1, 9:52 pm, Raffi Krikorian wrote:
> as some of you may have already noticed, we've starte
