-
Notifications
You must be signed in to change notification settings - Fork 40
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
Allow user to work in timezones besides UTC #3
Comments
Is it possible to only pull the date column from groundwater levels? I'm finding that some sites do not have a time associated with the measurement and it's throwing an error because it can't convert that to a datetime index. |
To update the status of this issue:
At this time there is still no built-in functionality for getting queries back in whatever timezone you want, they do come back with UTC-localized timestamps. |
That's a bug alright. |
On the subject of UTC - Is it expected behavior that the returned datetime index is UTC +0 rather than local UTC? E.g., for a randomly selected GW site with IV service, here is the dataRetrieval result (UTC+0): and here is the NWIS web interface 'view data' (UTC-6): I think can programmatically convert to local UTC using the tz_cd with the site information but perhaps it is preferred to have dataRetrieval handle that conversion? |
Correct, we decided to stick with USGS, unlike the web interface. The reason being what is "local time" when you're working analyzing data from multiple timezones? |
All data is converted to UTC; however, some users might prefer to work in a local timezone.
The text was updated successfully, but these errors were encountered: