The time it takes for the Mobile app to capture an image needs reducing without reducing quality of the GPS-based location data coming from the app.
We need you - a data analyst - to study and solve the problem...
OUTCOME:
Data-driven decision on convergence time-out strategy
Find ways to speed up a positive convergence on certain phones.
Faster app on the ground and more impact.
Suggestions for more detailed track info
Open an ADR discussing strategies and consequences for adjusting the time-out on GPS convergence.
BACKGROUND:
The Android App is being used to track millions of trees.
Planters and organizations use the app to take repetitive photos of the trees as they grow.
TIME TO TRACK
The largest barrier to using the system is the TIME TO TRACK per tree (planters are tracking several hundred trees a day, for organizations with millions of trees, the seconds and costs add up quickly.
The fastest the app has ever been at a pre-tree level is ~3 seconds and current times are ~20 seconds.
The app can be tested by taking as many photos as possible in a short amount of time, for example, 7:20 seconds / 50 photos.
GPS LOCATION ACCURACY
The primary increase in TIME TO TRACK has come from major advances in location accuracy. The 3-second app has been notorious for sending useless location data making it nearly impossible to match tree captures over time.
The latest version of the app is slow, however, it is producing high-quality data. It relies on GPS convergence to pinpoint its location before allowing the user to make a capture of the tree. Relaxing GPS accuracy requirements are directly in conflict with data needs for capture matching.
RESEARCH STATMENTS:
We have data to study to ascertain:
(1) Are we spending too much time converging on good devices (we are already converged, but still waiting)
(2) Are we wasting time trying to converge on devices that just don't converge (wait for the timeout)
SUGGESTED STARTING POINT:
Find device info for all the tracking sessions.
Find data sets related to the problem.
Look at data sets, tracking time varies from 18 to 7 seconds between photos on different devices
PROBLEM/OPPORTUNITY
The time it takes for the Mobile app to capture an image needs reducing without reducing quality of the GPS-based location data coming from the app.
We need you - a data analyst - to study and solve the problem...
OUTCOME:
BACKGROUND:
The Android App is being used to track millions of trees.
Planters and organizations use the app to take repetitive photos of the trees as they grow.
TIME TO TRACK
The largest barrier to using the system is the TIME TO TRACK per tree (planters are tracking several hundred trees a day, for organizations with millions of trees, the seconds and costs add up quickly.
The fastest the app has ever been at a pre-tree level is ~3 seconds and current times are ~20 seconds.
The app can be tested by taking as many photos as possible in a short amount of time, for example, 7:20 seconds / 50 photos.
GPS LOCATION ACCURACY
The primary increase in TIME TO TRACK has come from major advances in location accuracy. The 3-second app has been notorious for sending useless location data making it nearly impossible to match tree captures over time.
The latest version of the app is slow, however, it is producing high-quality data. It relies on GPS convergence to pinpoint its location before allowing the user to make a capture of the tree. Relaxing GPS accuracy requirements are directly in conflict with data needs for capture matching.
RESEARCH STATMENTS:
We have data to study to ascertain: (1) Are we spending too much time converging on good devices (we are already converged, but still waiting) (2) Are we wasting time trying to converge on devices that just don't converge (wait for the timeout)
SUGGESTED STARTING POINT:
Find device info for all the tracking sessions. Find data sets related to the problem. Look at data sets, tracking time varies from 18 to 7 seconds between photos on different devices