Currently, using places doesn't modify the 'geo' field. This makes
sense for neighborhoods or cities, because picking a centroid is a
little arbitrary and those users might get freaked out if we place
them at a specific point on a map. However, I would argue that this
behavior is counterintuitive when we get to the 'poi' level. When I
pick the building I'm in on twitter.com, I'm assuming I'm geocoding my
location (and providing some additional semantic information beyond
lat/lng). However, this doesn't seem to be the case. Would we consider
changing this?

Furthermore, will any place-annotated tweets show up in the streaming
API when using the locations query parameters? Or is that only limited
to explicitly geotagged tweets?


Reply via email to