Looping supports circular routes that can have fixed exact schedules or ad-hoc schedules. To configure a Schedule for a circular route follow the steps below:
Create a Route with the stops already created.
Enter the Start DateEnd Date (optional)
Select the days of the week the Route Service runs
Click the “Looping” checkbox
Enter the Start Time and End Time, hours the Circular Route is in the service
- Click “Add Ride”. Note: Only one Ride needs to be added for each vehicle servicing the Circular Route
There are two types of looping rides, those that are on a schedule "exact schedule loops" and those that are not "non-exact loops". Loops on a schedule have a published time at which a vehicle will arrive and depart, just like non-looping rides. Looping rides not on a schedule are on an estimated schedule in which there is no expectation the vehicle will be at a stop at a particular time, but the round trip time can be approximated.
Looping rides are configured in the Route editor. Clicking on the “Loop” checkbox shows 4 fields : start time, end time, exact schedule, and round trip time (see below).
Looping rides are expected to run only between the start and end time for each day the route service is active.
In both types of loops- at least one scheduled ride will always need to be configured for a looping service. For exact scheduled loops, the scheduled departure times are extrapolated based on the round trip time.
Consider an exact schedule loop example:
Start Time: 8:00AM
End Time: 5:00PM
Exact Schedule: Checked
Round Trip Time: 20 minutes
This creates a service for two vehicles driving the loop, each 10 minutes apart. The Admin will assign an individual Ride to a shift which is tied to a Driver and vehicle- each loop will show the expanded list of individual stop statuses in dispatch tab and dashboard.
For Exact-schedule, rider tallies, alerts, arrival detection and arrival estimates are all supported.
Non-exact loops are similarly configured but are more limited. They do not support alerts or arrival estimates but do support arrival detection and rider tallies. Stops are not expanded initially as with exact schedule rides. Instead admins see the initial set of stops plus a new awaiting stop after the last departed stop. Hence the list of stop status information grows automatically as the vehicle drives the loop.