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

Handle data with timestamps #135

Open
dschristianson opened this issue Jun 3, 2022 · 0 comments
Open

Handle data with timestamps #135

dschristianson opened this issue Jun 3, 2022 · 0 comments
Labels

Comments

@dschristianson
Copy link
Contributor

With the addition of instantaneous values from USGS, we need a strategy for handling data with timestamps, especially regarding synthesis.

Notes:

  • Timestamps can be reported in many formats (i.e., from the various data sources) with or without timezone.
  • Local time vs UTC
  • Daylight savings time. Some data follow it some do not. When converting data with daylight savings to without can cause duplicate / missing hour.
  • There are many cases in which the data are not collected at local time, purposefully and also by mistake. E.g., the data logger was setup with a computer in another timezone.

Ideas so far:

  • Assume local time if time zone is not reported.
  • Strip timezone
  • Plugins handle time conversions and/or basin3d can deal with a set of standard time formats (especially if not explicitly reported)
  • Convert time to UTC for basin3d core. In the "views" repo have different options for time synthesis representation, e.g. synthesize by UTC or by local time (with or without daylight savings)

Considerations:

  • transparency from the data source. can / should we report original time format?
  • Time frequencies higher than daily may need some different handling than the pandas dataframe approach for synthesis.
    -- (re-)consider having the date/timestamp for the index
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants