{
  "fetched_at": "2026-10-20T08:14:12Z",
  "source_url": "https://www.kaggle.com/competitions/alta-geoloc-reprise/data",
  "pages": [
    {
      "name": "data-description",
      "content": "<p>You have available the list of tweet IDs and a script that you can use to download the tweets. The script downloads the raw HTML data, you will still need to extract the tweet information from the downloaded data.</p>\r\n<p>Copyright restrictions from Twitter does not allow us to distribute the contents of the tweets, that's why we are providing the IDs and a script to download the tweets. The script incorporates a \"sleep\" instruction to avoid sending all requests at once, so allow several hours to download the tweets. Alternatively you may want to register to Twitter Developers and use their API to download the tweets.</p>\r\n<p>There is a training set and a test set. The training set contains 2000 tweets sorted in time, together with the location mentions. The format of this file is exactly the same as the format of the submission file. The test set contains just over 1000 tweets sorted in time, this time without the location mentions. Your task is to find the location mentions of this test set and submit the results to Kaggle in Class. The timestamp of the tweets of the test set are after those of the training set, to model a realistic scenario where we train on known tweets and we want to predict the location mentions in future tweets.</p>\r\n<p>File descriptions</p>\r\n<ul>\r\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">tweetstrain.csv - the training set</span></li>\r\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">tweetstestids.csv - the test set with the LocationMentions column empty</span></li>\r\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">tweetsetsids.txt - the list of tweets IDs for use with getTweettById.sh</span></li>\r\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">getTweetById.sh - a simple bash script that downloads the tweets</span></li>\r\n</ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "<p>Please read the task description at the <a href=\"http://www.alta.asn.au/events/sharedtask2014/description.html\" target=\"_blank\">ALTA 2014 shared task website</a>.</p>\r\n<p>This task is a reprise of the original ALTA 2014 shared task, but made open to the public on an ongoing basis.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>The evaluation metric for this competition is <a href=\"https://www.kaggle.com/wiki/MeanFScore\"> Mean F1-Score</a>. The F1 score, commonly used in information retrieval, measures accuracy using the statistics precision p and recall r. Precision is the ratio of true positives (tp) to all predicted positives (tp + fp). Recall is the ratio of true positives to all actual positives (tp + fn). The F1 score is given by:</p>\r\n<p>\\[ F1 = 2\\frac{p \\cdot r}{p+r}\\ \\ \\mathrm{where}\\ \\ p = \\frac{tp}{tp+fp},\\ \\ r = \\frac{tp}{tp+fn} \\]</p>\r\n<p>The F1 metric weights recall and precision equally, and a good retrieval algorithm will maximize both precision and recall simultaneously. Thus, moderately good performance on both will be favored over extremely good performance on one and poor performance on the other.</p>\r\n<h2>Submission Format</h2>\r\n<p><strong>For every tweet in the dataset</strong>, submission files should contain two columns: TweetId and LocationMentions. LocationMentions should be a space-delimited list. If a location mention is repeated, number each repeated location. If a location has multiple words, separate them with blank space so that, in effect, it does not matter whether it is one location expression with two words or two different location expressions. Thus, if a tweet with ID \"1234\" has two location expressions \"London\" and \"United States\" the following are valid and equivalent descriptions:</p>\r\n<pre>1234,london united states<br />1234,united london states</pre>\r\n<p>The file should contain a header and have the following format:</p>\r\n<pre>TweetId,LocationMentions<br />235423423559754,uk australia1 london australia2<br />493450763931512832,france germany us uk libya<br />etc.</pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "rules",
      "content": "\r\n\t<!-- Begin Base Rules -->\r\n    <h3>One account per participant</h3>\r\n    <p>You cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.</p>\r\n    <h3>No private sharing outside teams</h3>\r\n    <p>\r\n        Privately sharing code or data outside of teams is not permitted.\r\n        It's okay to share code if made available to all participants on the forums.\r\n    </p>\r\n    <h3>Team Mergers</h3>\r\n    <p>Team mergers are not allowed in this competition.</p>\r\n\r\n    <h3>Team Limits</h3>\r\n    <p>There is no maximum team size.</p>\r\n    <h3>Submission Limits</h3>\r\n    <p>You may submit a maximum of 2 entries per day.</p>\r\n    <p>You may select up to 2 final submissions for judging.</p>\r\n    <h3>Competition Timeline</h3>\r\n    <p>Start Date: <strong>7/7/2015 1:03 PM UTC</strong></p>\r\n    <p>Merger Deadline: <strong>None</strong></p>\r\n    <p>Entry Deadline: <strong>None</strong></p>\r\n    <p>End Date: <strong>12/31/2017 11:59 PM UTC</strong></p>\r\n\t<!-- End Base Rules -->\r\n<p>Please be aware that you must not redistribute Tweets, per the Twitter usage agreement.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}