Skip to content
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

Seems like the timezone is off. #2

Open
kun-zhou opened this issue Apr 2, 2017 · 1 comment
Open

Seems like the timezone is off. #2

kun-zhou opened this issue Apr 2, 2017 · 1 comment

Comments

@kun-zhou
Copy link

kun-zhou commented Apr 2, 2017

When I request directly to Darksky with a NYC location using Time Machine request, hourly data starts at 00:00:00 EST on the day I requested, but this package keeps giving me 03:00:00 EDT?

@davidski
Copy link
Contributor

davidski commented Jul 4, 2017

@kun-zhou I've not been able to reproduce this behavior. Would you give the full call and system info you're using? Note that if you pass the add_json = TRUE parameter to get_forecast_for you'll get the full JSON as returned from darksky. That may be helpful for debugging.

This package just does a straight as.POSIXct conversion on the timestamps, so double check that your system timezone is as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants