twitter.place.name

note icon

NoteTwitter location data is available only if a Twitter user chooses to activate it. For each individual Tweet, they can choose whether or not to include location data and which location they want to specify, regardless of their real location. For example, a user in New York City could select Edinburgh, Scotland as the purported origin of a Tweet. If they choose not to include location data, all the twitter.place.* targets are unpopulated for that Tweet.

Typically, a shortened version of twitter.place.full_name. For example:

If twitter.place.full_name is this: twitter.place.name might be this:
Charlotte, NC Charlotte
London, England London
Division No. 11, Alberta Division No. 11

Note that a twitter.place.full_name maps to a unique twitter.place.name but, in the reverse direction, one twitter.place.name might correspond to many different twitter.place.full_name values.

In other words, this filter:

twitter.place.full_name == "London, England"

always produces objects with twitter.place.name set to "London".

But this filter:

twitter.place.name == "London"

produces objects with twitter.place.full_name set to "London, England" or "London, KY" and, almost certainly, other values too.

Examples

  1. Filter for Tweets for which the user-supplied location information is London:

    twitter.place.name == "London"

  2. Filter for Tweets from locations called London that are outside the United Kingdom:

    twitter.place.name == "London"
    and twitter.place.country_code != "GB"

Resource information

Target service: Twitter

Target object: Twitter: Place

Type: string

Array: No

Always exists: No