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

Resampling over large gaps in data #265

Closed
TorSy opened this issue Oct 13, 2022 · 3 comments
Closed

Resampling over large gaps in data #265

TorSy opened this issue Oct 13, 2022 · 3 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request future This issue is in a backlog of ideas to possibly be done in the future

Comments

@TorSy
Copy link

TorSy commented Oct 13, 2022

Question:
I have a large dataset (1000 GB + ) worth of JSON data that is IoT sensor data. In order to regularize time-series to a set sampling frequency I use tempo.
One issue I experience is that the sensor data can have gaps in it. Sometimes months worth of missing data. The interpolate function fills all this in, which is really not what I want, as this interpolated data is not based on anything substantial. It should be left as Null or NA.

Could a parameter "interpolation limit" or similar be implemented? Currently I have a very computationally expensive workaround to this problem.

@tnixon tnixon added enhancement New feature or request future This issue is in a backlog of ideas to possibly be done in the future labels Oct 17, 2022
@tnixon
Copy link
Contributor

tnixon commented Oct 17, 2022

Hi @TorSy - thanks for your feedback. We plan to separate out the interpolation and resampling functions in a future update so that you should be able to upsample and just fill with "default" values (nulls, zeros or empty strings). The interpolation function would be separate and could be chained together with resampling if that's the desired effect, but not necessary if not. Would this solve your issue?

@epa095
Copy link

epa095 commented Nov 15, 2023

@TorSy Sounds like #147 no?

@tnixon
Copy link
Contributor

tnixon commented Nov 16, 2023

Agreed @epa095 - I think this is a duplicate of #147.

@tnixon tnixon closed this as not planned Won't fix, can't repro, duplicate, stale Nov 16, 2023
@tnixon tnixon added the duplicate This issue or pull request already exists label Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request future This issue is in a backlog of ideas to possibly be done in the future
Projects
None yet
Development

No branches or pull requests

3 participants