-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time_hour discrepancy with weather.rda #1
Comments
Thanks for flagging! I'm investigating this further. |
@dmcmurchy After digging further into this, it does seem that a |
Please reopen and tag me if you see the same issue again. Apologies for the very long delay! |
I had forgotten I submitted this issue, glad it wasn't something I was doing on my end. I had to go back and see what I was doing with this data and it was while I was recreating the CSV data used in the Analyzing Flight Delays and Cancellations project on DataCamp. I used the pyreadr python package and .rda files on your github to do so. Do you know if you'll be updating the related data files you have on Github? If not, I'll just put a note into the related notebook. Thanks |
Ah, good deal! I'll plan to update the data whenever I get a response on my anyflights request. I can reach out to DataCamp on getting things updated there too if needed. |
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: