{"action":"closed","issue":{"url":"https://api.github.com/repos/Esri/public-information-map-template-js/issues/36","labels_url":"https://api.github.com/repos/Esri/public-information-map-template-js/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/Esri/public-information-map-template-js/issues/36/comments","events_url":"https://api.github.com/repos/Esri/public-information-map-template-js/issues/36/events","html_url":"https://github.com/Esri/public-information-map-template-js/issues/36","id":65483732,"number":36,"title":"Twitter API places","user":{"login":"driskull","id":1231455,"avatar_url":"https://avatars.githubusercontent.com/u/1231455?v=3","gravatar_id":"","url":"https://api.github.com/users/driskull","html_url":"https://github.com/driskull","followers_url":"https://api.github.com/users/driskull/followers","following_url":"https://api.github.com/users/driskull/following{/other_user}","gists_url":"https://api.github.com/users/driskull/gists{/gist_id}","starred_url":"https://api.github.com/users/driskull/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/driskull/subscriptions","organizations_url":"https://api.github.com/users/driskull/orgs","repos_url":"https://api.github.com/users/driskull/repos","events_url":"https://api.github.com/users/driskull/events{/privacy}","received_events_url":"https://api.github.com/users/driskull/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Esri/public-information-map-template-js/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":{"login":"driskull","id":1231455,"avatar_url":"https://avatars.githubusercontent.com/u/1231455?v=3","gravatar_id":"","url":"https://api.github.com/users/driskull","html_url":"https://github.com/driskull","followers_url":"https://api.github.com/users/driskull/followers","following_url":"https://api.github.com/users/driskull/following{/other_user}","gists_url":"https://api.github.com/users/driskull/gists{/gist_id}","starred_url":"https://api.github.com/users/driskull/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/driskull/subscriptions","organizations_url":"https://api.github.com/users/driskull/orgs","repos_url":"https://api.github.com/users/driskull/repos","events_url":"https://api.github.com/users/driskull/events{/privacy}","received_events_url":"https://api.github.com/users/driskull/received_events","type":"User","site_admin":false},"milestone":null,"comments":6,"created_at":"2015-03-31T15:54:41Z","updated_at":"2015-04-30T17:33:10Z","closed_at":"2015-04-30T17:33:10Z","body":"Hey ESRI team,\r\n \r\nWe’re writing to inform you of some changes we are implementing over the next few months in order to improve the user experience when Tweets are created with location data. Some of these changes should be visible in the Twitter UI and have an effect on the Tweet payload starting today.\r\n \r\nYou may have noticed recent changes to the Twitter UI allowing a user to geotag their Tweet using venue data powered by Foursquare. If a user selects the Foursquare powered venue when Tweeting, the “place” section of the Tweet data payload will include the venueID, place name, and lat/long coordinates of the venue. This has significant benefits for data consumers. Place data can now be used to associate individual Tweets with specific venues. In addition, the lat/long coordinates of these venues are much more specific than the lat/long bounding boxes provided with the previous place types--neighborhood, city, or country. These non-venue places will still be available for selection in the UI and the resulting place data in the payload will be unchanged.\r\n \r\nWe are working on other improvements to the user experience when Tweeting with location to keep that experience consistent with our users’ expectations. As a part of these changes, the number of Tweets with the “coordinates” payload element, which is a lat/long associated with a Tweet and not a place, is expected to decrease significantly. This specific change will begin to roll out in late April. We don’t expect this change to cause any decrease in the overall number of Tweets with \"place\" data, including the lat/long coordinates defining the place bounding box.\r\n \r\nAll of these payload changes are backward compatible and will not result in any changes to the structure of the Tweet payload. You can view a sample payload of a Tweet associated with a venue to better understand these changes.\r\n\r\nPlease let me know if you have any questions regarding these changes."}}