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
Hello, I am receiving unexpected behavior from detection.stay_locations.
When a stay ends, leaving_datetime is the datetime value of the first point outside of the spatial radius, not the final point within the spatial radius.
In this example, there is one stay at the lat/lng coordinates (1, 1) for datetime 2018-01-01 00:00 to 2018-01-01 00:06. I would expect the leaving_datetime of this visit to be 2018-01-01 00:06, however, in this example it is actually the datetime of the following point in the sequence: 2018-01-01 00:23.
Using the datetime of the first point outside the spatial radius may not introduce much difference in the duration of visits for a regularly sampled time series, but for an irregular time series it can produce an inaccurate duration.
Is this a bug or an intentional design choice?
Thank you for your assistance.
The text was updated successfully, but these errors were encountered:
Hello, I am receiving unexpected behavior from
detection.stay_locations
.When a stay ends,
leaving_datetime
is the datetime value of the first point outside of the spatial radius, not the final point within the spatial radius.A toy example is available here.
In this example, there is one stay at the lat/lng coordinates
(1, 1)
for datetime2018-01-01 00:00
to2018-01-01 00:06
. I would expect theleaving_datetime
of this visit to be2018-01-01 00:06
, however, in this example it is actually the datetime of the following point in the sequence:2018-01-01 00:23
.Using the datetime of the first point outside the spatial radius may not introduce much difference in the duration of visits for a regularly sampled time series, but for an irregular time series it can produce an inaccurate duration.
Is this a bug or an intentional design choice?
Thank you for your assistance.
The text was updated successfully, but these errors were encountered: