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

TSA doesn't show from DateTime - uses UTC #399

Closed
neilh10 opened this issue Jun 13, 2019 · 6 comments
Closed

TSA doesn't show from DateTime - uses UTC #399

neilh10 opened this issue Jun 13, 2019 · 6 comments

Comments

@neilh10
Copy link

neilh10 commented Jun 13, 2019

The TimeSeriesAnalysis (TSA)graph window appears to display in TimeZone (TZ) "DateTimeUTC". This makes it difficult to discuss and display it to other interested parties.

The intial "72hrs Charts" display with the recorded TZ. https://data.envirodiy.org/sites/LCC45a3/
The downloaded data uses the recorded TZ, and specifies the offset from UTC.

I start the TSA graph from the "72hrs Chart" by pressing the button"open in Time Series Analysis"

It would expect the TSA graph to use the recorded zone. Alternatively if the TZ=UTC is required, it would be nice if that was an option, rather than the default.

The attached graph shows a snapshot of the TSA graph with some anomolies in it. Hovering over the rightmost anomolies shows its time as using "DateTimeUTC", instead of the local "DateTime"

from the .csv download
DateTime | TimeOffset | DateTimeUTC
6/12/2019 7:15 | -8:00 | 6/12/2019 15:15 | 0.97

EnvirDIY_TSA_190613_0943

@neilh10 neilh10 changed the title TSA doesn't show TZ are allow change to local TZ TSA doesn't show from DateTime - uses UTC Jun 13, 2019
@aufdenkampe
Copy link
Member

Agreed. This would be a nice feature that was suggested but not prioritized in #236 (comment) and #293.

I've added it to a future feature milestone, but we might not get to it soon due to limited funding and priority to our bug fix milestone for release 0.10.

@neilh10
Copy link
Author

neilh10 commented Jun 13, 2019

Ok thanks, whenever. I looked through the open issues and didn't see it, so thought I should enter it for reference.

@aufdenkampe
Copy link
Member

@neilh10, I really appreciate you posting this issue, especially with the level of detail that you provide on what you would see as helpful and why. Do so is a very helpful contribution to our long-term development, and I think it also helps us generate more funding to do the work. Many thanks!

I also appreciate that you looked through the open issues. Indeed, there was nothing that was open that was related to this topic. Thanks.

@neilh10
Copy link
Author

neilh10 commented Jun 14, 2019

hey you're welcome. I've been through a number of software development projects, and been on the fixing end of issues. :)

@dbressler75
Copy link
Collaborator

dbressler75 commented Jul 18, 2019

@aufdenkampe, to follow up on what @neilh10 said: The TSA display in UTC is fine for general data consistency; however, in terms of actual data usage in the here and now and in the citizen science context displaying it this way is probably going to be problematic. Ideally, maybe there would be an option to display data in the current time where a station is located (or possibly a standard time for a region - e.g., for eastern time zone maybe always displaying in EST, as opposed to switching between EST and EDT). Main point being that displaying data in UTC is going to make it a lot harder for users to connect the dots.

@aufdenkampe
Copy link
Member

We have decided to replace TSA with a Time Series Visualization (TSV) page, starting with:

Check out the screenshots I just posted with #512 (comment).
We think our new TSV addresses this issue.

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

No branches or pull requests

4 participants