{
  "fetched_at": "2026-10-19T14:24:32Z",
  "source_url": "https://www.kaggle.com/competitions/dsbootcamp10/data",
  "pages": [
    {
      "name": "rules",
      "content": "This is a page where you can include rules that participants must accept before joining. You may wish to include rules like:\n\n - Don't cheat!\n - Apply yourself!\n - Have fun!",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "<h2>Brief Description</h2>\n\n<p>You are provided with an anonymized dataset of drivers PING signals containing numeric feature variables, the binary target column, and a string order_id column.</p>\n<p>The task is to predict the value of the label column in the test set.</p>\n\n<h2>File descriptions</h2>\n<ul>\n<li><strong>train.csv</strong> - the training set</li>\n<li><strong>test.csv</strong> - the test set</li>\n<li><strong>sampleSubmission.csv</strong> - a sample submission file in the correct format</li>\n</ul>\n<h2>Data fields</h2>\n<ul>\n<li><strong>order_id</strong> - an anonymous id unique to a given order number</li>\n<li><strong>service_type</strong> - service type, can be GORIDE or GOFOOD</li>\n<li><strong>driver_status</strong> - status of the driver PING, can be AVAILABLE, UNAVAILABLE, OTW_PICKUP, OTW_DROPOFF</li>\n<li><strong>hour</strong> - hour</li>\n<li><strong>seconds</strong> - seconds in linux format</li>\n<li><strong>latitude</strong> - GPS latitude</li>\n<li><strong>longitude</strong> - GPS longitude</li>\n<li><strong>altitude_in_meters</strong> - GPS Altitude</li>\n<li><strong>accuracy_in_meters</strong> - GPS Accuracy, the smaller the more accurate</li>\n</ul>\n\n",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F642531%2F58f5580d54da253277f3b9060cd6ecc8%2FScreen%20Shot%202019-10-11%20at%2006.03.45.png?generation=1570754068153991&alt=media)\n\n\n<p>Among our drivers, there are drivers who use Fake GPS application to mock their location.\nThis FGPS usage is unfair for other GOJEK drivers who work honestly. \nHence, we would like to apply a machine learning model to classify whether a trip is being done using fake GPS or not based on their PING behavior.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>The evaluation pages describes how submissions will be scored and how students should format their submissions. You don't need a sub-title at the top (the page title appears above). For an example of a high quality evaluation page, see the 2013 KDD Cup page, which we have copied here:</p>\r\n<hr />\r\n<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 author in the dataset</strong>, submission files should contain two columns: AuthorId and DuplicateAuthorIds. DuplicateAuthorIds should be a space-delimited list. Every AuthorId counts as his/her own duplicate, and every duplicate should be listed under each of its respective ids. For example, if you suspect author A, B, and C are the same, you should list (A,A B C), (B,B A C), (C,C A B).</p>\r\n<p>The file should contain a header and have the following format:</p>\r\n<pre>AuthorId,DuplicateAuthorIds<br />1,1<br /><span style=\"font-size: 14px; line-height: 1.4em;\">8,8<br />9,9 10<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">10,10 9<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">etc.</span></pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}