AirQo Low-Cost Air Quality Monitor Calibration Challenge
Helping Uganda
$1 000 USD
Challenge completed over 4 years ago
Prediction
311 joined
161 active
Start
Apr 30, 21
Close
Jun 06, 21
Reveal
Jun 06, 21
'%3e%3cg id='b'%3e%3cpath id='a' d='M0-8v8h4z' transform='rotate(18 0 -8)'/%3e%3cuse xlink:href='%23a' transform='scale(-1 1)'/%3e%3c/g%3e%3cuse xlink:href='%23b' transform='rotate(72)'/%3e%3cuse xlink:href='%23b' transform='rotate(144)'/%3e%3cuse xlink:href='%23b' transform='rotate(216)'/%3e%3cuse xlink:href='%23b' transform='rotate(288)'/%3e%3c/g%3e%3c/svg%3e){kind=small}
Column created_at
Help · 11 May 2021, 09:22 · 5
Hi Zindians,
What should I do to handle UTC + 3 in the created_at column: do +3 hours everywhere !? or leave the time as it is !?
Thank you!
Hi!
Does it matter?
I don't know. To know it, I would have to make one submission and I don't have one submission to lose.
The time given is local time in Uganda. THe +3 does not actually mean you have to add 3 hours to it, it is just telling you that the local time is given at UTC+3. So defintiel do not add 3 to it. You should be able to do most of what you need to do without needing to change this. The submissions are the prediction against the index not against the time so it wont affect your submission. If you are worried you could explore tz_localize and tz_convert but really dont think you need to go there.
Does it matter? I think not
The data is a time-series(time-dependent) type of data, the +03:00 just indicates the GMT zone, you can convert this column to a timestamp
Okay. Thank you.