-
Notifications
You must be signed in to change notification settings - Fork 37
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
Why is trim_missing=True
the default method read_ts
?
#40
Comments
Hello,
The trim missing won't (or at least shouldn't) remove values of 0 as they
aren't considered missing in DSS files. Missing values are specifically
indicated by -901 and -902 in DSS (1). I believe it will also work based on
a quality flag which it would then remove regardless of value (our SQL
database works that way at least I but I don't think I've tested that in
DSS.) If you're having "0"s removed it could be worth checking that there
aren't any quality flags that got erroneously added.
The primary purpose is to reduce data transfer amounts. If you're
transferring data and there's a lot missing past either extent, and the
given purpose would already deal with all the date/time pairs correctly
it's convenient.
That said, I agree it should be false by default to always return
everything in the window so you know what regular interval data is actually
present vs supposed to be there. And an application should assert otherwise.
Mike
(1) Yes, that will cause problems storing differences that get that large.
…On Tue, May 10, 2022 at 3:25 PM Daniel Hamill ***@***.***> wrote:
Having been caught up on this in several projects, what is the rational
for having trim_missing=True in the read_ts method as the default
behavior?
In my mind, zero is a valid measurement.
—
Reply to this email directly, view it on GitHub
<#40>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB44KCCXKQN4L7TQ34IFE2LVJLO6VANCNFSM5VTAIC2A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I will have to work out an example to show the unexpected behavior, but I am seeing zeros (not noData or -901.0) being dropped from the beginning or end of a time series with the default If a user goes through the effort to provide and exact window to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having been caught up on this in several projects, what is the rational for having
trim_missing=True
in theread_ts
method as the default behavior?In my mind, zero is a valid measurement.
The text was updated successfully, but these errors were encountered: