The geo field is the user's (or tweet's) exact location.  The place
field, whether a POI, neighborhood, city, or admin, contains the
place's location.  Today POIs are always points, but in the future
there may be some polygons (e.g. stadiums, malls, amusement parks).
In this case the exact location would matter.

A place-annotated tweet will show up in the streaming API, even if
it doesn't have an exact location.

Twitter Geo Team

On Thu, Jun 17, 2010 at 3:28 PM, harrisj <> wrote:
> Hello,
> 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, 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?
> Thanks,
> Jacob

Reply via email to