You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is an issue with the original data source or in the version stored here, but the weather datatime_hour column appears to be using a UTC offset (+8 for the pacific time zone).
Weather data
year
month
hour
time_hour
2022
1
0
2022-01-01 08:00:00
2022
1
1
2022-01-01 09:00:00
2022
1
2
2022-01-01 10:00:00
2022
1
3
2022-01-01 11:00:00
2022
1
4
2022-01-01 12:00:00
2022
1
5
2022-01-01 13:00:00
2022
1
6
2022-01-01 14:00:00
2022
1
7
2022-01-01 15:00:00
2022
1
8
2022-01-01 16:00:00
2022
1
9
2022-01-01 17:00:00
Where the flights data is using local.
Flights data
year
month
hour
time_hour
2022
1
23
2022-01-01 23:00:00
2022
1
22
2022-01-01 22:00:00
2022
1
23
2022-01-01 23:00:00
2022
1
23
2022-01-01 23:00:00
2022
1
23
2022-01-01 23:00:00
2022
1
23
2022-01-01 23:00:00
2022
1
0
2022-01-01 00:00:00
2022
1
22
2022-01-01 22:00:00
2022
1
23
2022-01-01 23:00:00
2022
1
23
2022-01-01 23:00:00
If you attempt to use the time_hour column to merge data between these two sources, you'd end up with some potentially misleading data.
Based on what I could find on the Bureau of Transportation website all time values are local.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is an issue with the original data source or in the version stored here, but the weather data
time_hour
column appears to be using a UTC offset (+8 for the pacific time zone).Weather data
Where the flights data is using local.
Flights data
If you attempt to use the
time_hour
column to merge data between these two sources, you'd end up with some potentially misleading data.Based on what I could find on the Bureau of Transportation website all time values are local.
The text was updated successfully, but these errors were encountered: