02-07-2017, 11:15 PM
Ahahaha, great video 
Yeah, there's certainly a lot of variables. The way I have it set up is to insert all times as a GMT timestamp. GMT never changes for daylight savings, so that provides a solid base to perform all of the local conversions on. Then it's just a matter of keeping up to date with all of the changes, like which countries decide to observe DST, if countries decide to switch time zones, etc. Those will, unfortunately, have to be manually updated. But as long as that data is correct there shouldn't be any problems. And with an application like this I'm not concerned with leap seconds, or getting extremely precise times. I don't even use seconds in the calculations, arrival/departure times are only accurate down to the minute.
Yeah, there's certainly a lot of variables. The way I have it set up is to insert all times as a GMT timestamp. GMT never changes for daylight savings, so that provides a solid base to perform all of the local conversions on. Then it's just a matter of keeping up to date with all of the changes, like which countries decide to observe DST, if countries decide to switch time zones, etc. Those will, unfortunately, have to be manually updated. But as long as that data is correct there shouldn't be any problems. And with an application like this I'm not concerned with leap seconds, or getting extremely precise times. I don't even use seconds in the calculations, arrival/departure times are only accurate down to the minute.