{
  "id": 367991,
  "title": "The time zone in Germany is UTC+2 in August",
  "url": "/competitions/otto-recommender-system/discussion/367991",
  "author_name": "",
  "post_date": "2022-11-22T21:51:28.126956500Z",
  "votes": 18,
  "comment_count": 5,
  "views": 0,
  "content": "<p>Hi,</p>\n<p>The time zone in Germany is UTC+2 in summer. <br>\nMaybe that's why min <strong>ts</strong> is 2022-07-31 22:00:00 in train, and max <strong>ts</strong> is 2022-08-28 21:59:59.<br>\nAnd maybe we should add 2 hours to <strong>ts</strong> to be at german time.</p>\n<p>Do you agree ?</p>",
  "messages": [
    {
      "id": "2040292",
      "postDate": "11/22/2022 21:51:28",
      "content": "<p>Hi,</p>\n<p>The time zone in Germany is UTC+2 in summer. <br>\nMaybe that's why min <strong>ts</strong> is 2022-07-31 22:00:00 in train, and max <strong>ts</strong> is 2022-08-28 21:59:59.<br>\nAnd maybe we should add 2 hours to <strong>ts</strong> to be at german time.</p>\n<p>Do you agree ?</p>",
      "rawMarkdown": "Hi,\n\nThe time zone in Germany is UTC+2 in summer. \nMaybe that's why min **ts** is 2022-07-31 22:00:00 in train, and max **ts** is 2022-08-28 21:59:59.\nAnd maybe we should add 2 hours to **ts** to be at german time.\n\nDo you agree ?",
      "votes": null
    },
    {
      "id": "2040379",
      "postDate": "11/23/2022 01:31:40",
      "content": "<p>Great point. (Or just convert the timestamps from milliseconds into local German time). It would make more sense that the dataset starts on 12am start of day first day. And ends 11:59pm on the last day.</p>",
      "rawMarkdown": "Great point. (Or just convert the timestamps from milliseconds into local German time). It would make more sense that the dataset starts on 12am start of day first day. And ends 11:59pm on the last day.",
      "votes": null
    },
    {
      "id": "2053554",
      "postDate": "12/03/2022 11:48:34",
      "content": "<p>It makes sense but do we know all of the events are from Germany? They could be done from different time zones and normalized to UTC+0. Can we have a clarification regarding this? <a href=\"https://www.kaggle.com/pnormann\" target=\"_blank\">@pnormann</a> </p>",
      "rawMarkdown": "It makes sense but do we know all of the events are from Germany? They could be done from different time zones and normalized to UTC+0. Can we have a clarification regarding this? @pnormann",
      "votes": null
    },
    {
      "id": "2065485",
      "postDate": "12/14/2022 17:47:07",
      "content": "<p>Hi <a href=\"https://www.kaggle.com/adaubas\" target=\"_blank\">@adaubas</a>, sorry for not getting back to you sooner. I can confirm your assumption. All timestamps are UNIX timestamps and therefore represent UTC, whereas <strong>the local time zone of our german customers in the dataset is UTC+2 (CEST)</strong>. So you can recover the local time by adding 2 hours to all the <code>ts</code> values.</p>",
      "rawMarkdown": "Hi @adaubas, sorry for not getting back to you sooner. I can confirm your assumption. All timestamps are UNIX timestamps and therefore represent UTC, whereas **the local time zone of our german customers in the dataset is UTC+2 (CEST)**. So you can recover the local time by adding 2 hours to all the `ts` values.",
      "votes": null
    },
    {
      "id": "2065490",
      "postDate": "12/14/2022 17:53:03",
      "content": "<p><a href=\"https://www.kaggle.com/gunesevitan\" target=\"_blank\">@gunesevitan</a> we only deliver to Germany. So you can also assume that all events were produced by customers living in CEST.</p>",
      "rawMarkdown": "gunesevitan we only deliver to Germany. So you can also assume that all events were produced by customers living in CEST.",
      "votes": null
    },
    {
      "id": "2065514",
      "postDate": "12/14/2022 18:47:22",
      "content": "<p>Thank you for confirming !</p>",
      "rawMarkdown": "Thank you for confirming !",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 2040379,
      "author_name": "cdeotte",
      "author_url": "",
      "post_date": "11/23/2022 01:31:40",
      "content": "<p>Great point. (Or just convert the timestamps from milliseconds into local German time). It would make more sense that the dataset starts on 12am start of day first day. And ends 11:59pm on the last day.</p>",
      "votes": null,
      "replies": [
        {
          "id": 2053554,
          "author_name": "gunesevitan",
          "author_url": "",
          "post_date": "12/03/2022 11:48:34",
          "content": "<p>It makes sense but do we know all of the events are from Germany? They could be done from different time zones and normalized to UTC+0. Can we have a clarification regarding this? <a href=\"https://www.kaggle.com/pnormann\" target=\"_blank\">@pnormann</a> </p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 2065490,
          "author_name": "pnormann",
          "author_url": "",
          "post_date": "12/14/2022 17:53:03",
          "content": "<p><a href=\"https://www.kaggle.com/gunesevitan\" target=\"_blank\">@gunesevitan</a> we only deliver to Germany. So you can also assume that all events were produced by customers living in CEST.</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 2065485,
      "author_name": "pnormann",
      "author_url": "",
      "post_date": "12/14/2022 17:47:07",
      "content": "<p>Hi <a href=\"https://www.kaggle.com/adaubas\" target=\"_blank\">@adaubas</a>, sorry for not getting back to you sooner. I can confirm your assumption. All timestamps are UNIX timestamps and therefore represent UTC, whereas <strong>the local time zone of our german customers in the dataset is UTC+2 (CEST)</strong>. So you can recover the local time by adding 2 hours to all the <code>ts</code> values.</p>",
      "votes": null,
      "replies": [
        {
          "id": 2065514,
          "author_name": "adaubas",
          "author_url": "",
          "post_date": "12/14/2022 18:47:22",
          "content": "<p>Thank you for confirming !</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "2040292": "Hi,\n\nThe time zone in Germany is UTC+2 in summer. \nMaybe that's why min **ts** is 2022-07-31 22:00:00 in train, and max **ts** is 2022-08-28 21:59:59.\nAnd maybe we should add 2 hours to **ts** to be at german time.\n\nDo you agree ?",
    "2040379": "Great point. (Or just convert the timestamps from milliseconds into local German time). It would make more sense that the dataset starts on 12am start of day first day. And ends 11:59pm on the last day.",
    "2053554": "It makes sense but do we know all of the events are from Germany? They could be done from different time zones and normalized to UTC+0. Can we have a clarification regarding this? @pnormann",
    "2065485": "Hi @adaubas, sorry for not getting back to you sooner. I can confirm your assumption. All timestamps are UNIX timestamps and therefore represent UTC, whereas **the local time zone of our german customers in the dataset is UTC+2 (CEST)**. So you can recover the local time by adding 2 hours to all the `ts` values.",
    "2065490": "gunesevitan we only deliver to Germany. So you can also assume that all events were produced by customers living in CEST.",
    "2065514": "Thank you for confirming !"
  },
  "source": "meta"
}