[ENH] - QuickCapture ignore tracklog points when device does not move for a long time. #327
Labels
Dewberry Task
Task for the Dewberry Team
Enhancement
New feature or request
QuickCapture
Pertains to the QuickCapture app config or schema
v10
Enhancements and changes for the next version of the SARCOP data model.
Milestone
Which app?
QuickCapture
Describe requirements
We want to reduce the amount of unwanted tracklog data, in particular when users are stationary and not searching OR forgot to turn their tracklogs off. The QuickCapture Team has created a solution for this using the device accelerometer and eventually an "activity recognition API". See more details below. Let's ensure this makes it into the v10 Deployment.
Alternatives
None
Other Relevant Info
From QC Team on1/14/25
"For your information, if you set the excludeLocationsWhenStationary property to true the feature will be enabled with default values. This means that if the device is stationary for 10 minutes, you will see a little red icon on the button bar of the project page. If you see the red dot, it means that the device is stationary and any collected vertices (from GPS drift) will not be added to the line.
If the device picks up any movement via the accelerometer within a set time (10 minutes), the dot will disappear, and the line vertices will start to be captured again.
The store version (1.21.20) only uses the accelerometer of the device for this process, the March update will also use the activity recognition capability API of the device. This accounts for the situation where the device is put down/mounted on a vehicle on a very smooth road (or on a boat), where it is possible that no events are registered by the accelerometer even when the device is moving. This is fairly unlikely, but not impossible.
For testing you can set the timeThreshold to 10 or 30 seconds. This means that the dot will appear sooner. Essentially, if no movements are felt for 10 or 30 seconds the app will assume that the device is stationary, and stop capturing vertices. In testing you can configure the project to capture streaming points to make a comparison with the track. The points will not be filtered by this setting.
We are also looking at the ignoring network locations, and will be able to share a beta version with you shortly."
Priority impact
p0 - not time sensitive
Impact
This should improve data quality, improve performance, and potentially help prompt the end user to turn off their tracklogs when not searching.
The text was updated successfully, but these errors were encountered: