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 non-time-series data #18

Open
rileyhales opened this issue Nov 9, 2021 · 1 comment
Open

Handle non-time-series data #18

rileyhales opened this issue Nov 9, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@rileyhales
Copy link
Owner

make multiple classes?

  • grids.Query.point, .multipoint, etc for queries which will produce a single value rather than a series
  • other coordinate variables used instead of time?
  • make a general Series class with an attribute indicating name of coordinate variable for the series?
  • grids.TimeSeries returns grids.Series with the series coordinate variable attribute set to time (or the best guess for time)
  • change the way the time steps are handled to be create the coordinate value index with one of the options being when the coordinate variable is time
@rileyhales rileyhales added the enhancement New feature or request label Nov 9, 2021
@rileyhales rileyhales self-assigned this Nov 9, 2021
@rileyhales
Copy link
Owner Author

This may require converting some of the query functions to static methods which get mixed-in to multiple other classes. Or make series the general class and TimeSeries and Query inherit from Series with specializations. Using classes is necessary to keep the code reasonably readable and maintainable rather than converting all of these to a series of functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant