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

Verify translation between timestamps between DSS and R's POSIXt class #5

Open
eheisman opened this issue Oct 8, 2013 · 2 comments

Comments

@eheisman
Copy link
Owner

eheisman commented Oct 8, 2013

No description provided.

@cameronbracken
Copy link
Collaborator

Does DSS even specify time zone?

@eheisman
Copy link
Owner Author

eheisman commented Oct 8, 2013

It can under the properties timeZoneID and timeZoneRawOffset for a TimeSeriesContainer. I was more thinking about two issues:

  1. DST isn't accounted for in either POSIXt or HecTime timestamps, but PST != PDT on an hourly model. Also, I believe I've run into problems with POSIXt on R on Windows saying PDT isn't a valid timezone, but R's Sys.timezone() returning "PDT". It would be nice to check if the DSS data has a timezone assigned, and use it, if not assigned, default to the system's timezone.

  2. How does POSIXt handle 00:00 vs 24:00 hrs on a given day? If I recall correctly, for a HecTime object, it handles them as start of day and end of day respectively, 24 hours apart. - Not really an issue given the current method of translation, but I had a slower function that translated it through a string.

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