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.retweeted.place.* targets are unpopulated for that Tweet.
Typically, a shortened version of twitter.retweeted.place.full_name. For example:
|If twitter.retweeted.place.full_name is this:||twitter.retweeted.place.name might be this:|
|Division No. 11, Alberta||Division No. 11|
Note that there is a one-to-one mapping from twitter.place.full_name to twitter.place.name but a one-to-many mapping in the reverse direction.
In other words, this filter:
twitter.retweeted.place.full_name == "London, England"
always produces objects with twitter.place.name set to "London".
But this filter:
twitter.retweeted.place.name == "London"
produces objects with twitter.retweeted.place.full_name set to "London, England" or "London, Ohio" or other values.
1. Filter for Retweets of Tweets for which the user-supplied location information is London. There are several cities called London, and this filter delivers results from them all: