You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can under the properties timeZoneID and timeZoneRawOffset for a TimeSeriesContainer. I was more thinking about two issues:
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.
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.
No description provided.
The text was updated successfully, but these errors were encountered: