We have extended our geofencing capabilities around the arrival at stops.
So far admins already had the ability to set an optional maximum_driver_distance_meters
on stops when
creating bookings, inserting custom stops into bookings or tours, or by updating them. When set a driver
is prohibited to mark a stop as arrived when outside of the specified aerial distance from the stop location.
We have extended these functionalities with additional features:
Automatic arrival at stop
In addition to the maximum_driver_distance_meters
we now also allow defining an auto_arrival_distance_meters
on the same endpoints. When set the driver app will automatically mark the stop as arrived when the driver enters
the given radius from the stop location.
Defaults from booking and tour services
Additionally to the manual passing or setting of these values via the API we now also allow defining defaults
for both maximum_driver_distance_meters
as well as auto_arrival_distance_meters
on the booking and tour services
for each stop type.
When configured stops where the corresponding service applies will automatically be created with these defaults applied.