viewof gpsAccuracy = Inputs.range([3, 20], {
value: 10,
step: 1,
label: "GPS Accuracy (meters):"
})
viewof fenceRadius = Inputs.range([20, 200], {
value: 120,
step: 10,
label: "Geofence Radius (meters):"
})
viewof dwellTime = Inputs.range([0, 120], {
value: 30,
step: 10,
label: "Dwell Time (seconds):"
})
// Ratio of stated accuracy to chosen radius; this is not a trigger probability.
accuracyRadiusRatio = gpsAccuracy / fenceRadius
html`<div style="background: #f8f9fa; padding: 15px; border-radius: 8px; border-left: 4px solid #2C3E50; margin-top: 15px;">
<h4 style="color: #2C3E50; margin-top: 0;">Selected geofence settings</h4>
<p>Accuracy-to-radius ratio: <strong>${accuracyRadiusRatio.toFixed(3)}</strong></p>
<p>Selected dwell time: <strong>${dwellTime} seconds</strong></p>
<p>The ratio describes the two input lengths. Trigger probability also depends on distance from the boundary and the location-error distribution.</p>
</div>`Geofence Settings Explorer
Geofence Settings Explorer
animation
location
ux-design
Try Change Geofence Radius (meters): from 120 to 20.
Observe Watch Accuracy-to-radius ratio with GPS Accuracy (meters): at 10.
Explain Explain why changing Dwell Time (seconds): from 30 does not change Accuracy-to-radius ratio.
Technical boundaries. The ratio describes the two input lengths, not trigger probability. Trigger probability also depends on distance from the boundary and the location-error distribution.
Geofence Settings Explorer
The listed UWB anchor and tag costs, accuracy, battery life, and annual savings are hypothetical procurement inputs requiring vendor quotes and workload-specific measurements.
The next design question is whether the chosen accuracy tier is worth its installation and operating cost.