Why is there a difference between the added time and mileage shown in Google Maps compared to those shown in Dispatch Science?

Dispatch Science leverages both OSRM and Mapbox to perform routing and distance calculations. OSRM (Open Source Routing Machine) is primarily used for route optimization, including the calculation of the total route distance and the overall driver workload across multiple stops. In contrast, Mapbox is used to calculate the distance for individual orders, such as the straight-line or point-to-point distance between pickup and delivery locations.

This dual-system approach allows Dispatch Science to optimize routes efficiently while also providing accurate order-level distance estimates for pricing, reporting, or service level analysis.

What Tool is Used to Calculate Mileage?
OSRM is used for route optimization, meaning the total route distance and driver workload are calculated using OSRM. However, the distance for individual orders is calculated using Mapbox.

What backend technology is used to calculate route distances in Dispatch Science, and how is route optimization determined (e.g., by time, distance, or eco-friendly settings)? Does Dispatch Science take traffic into account when planning future routes?
Dispatch Science utilizes OSRM for our initial calculations of route distances. OSRM, built on the OpenStreetMap platform, relies on community contributions and open data, providing a more adaptable and customizable option for developers. For ORSM, we employ a car-based optimization model with a feature to exclude ferries. You can view the base model at https://map.project-osrm.org/?z=7&center=50.000000%2C12.000000&hl=en&alt=0&srv=0. However, traffic is not considered during the optimization process. 

How does the Route Pickup Warehouse affect the routes optimization mileage?

The Route module in Dispatch Science is based on a distribution model, where the driver begins their route from a known starting location. This location typically defaults to a designated warehouse, but each route can also have a customized starting point. It's important to note that this starting location is not considered an actual stop—rather, it's similar to a driver picking up their vehicle, clocking in, or officially beginning their shift before proceeding to their assigned deliveries.

If the first stop on the route is not the default or specified warehouse, the distance from the starting location to that first stop—commonly referred to as deadhead mileage—is included in the total mileage of the route.

Similarly, the route can be configured to end at a warehouse. If this return leg is not explicitly defined, the total mileage calculation will stop at the final delivery point. To capture the complete route distance (including the return to the warehouse), the end-of-route location must also be established.

Does Dispatch Science use live traffic data when calculating route times and distances? 

Short answer: No, live traffic data is not used in the route calculations.

Dispatch Science does not rely on real-time (live) traffic conditions when calculating travel time or distance. Instead, the system calls out to a mapping service (such as HERE Maps or Mapbox), which uses periodically updated datasets. These datasets incorporate road network changes, speed profiles, historical driving times, and known road closures.

This means that while general traffic patterns (based on historical data) and road availability are considered, real-time congestion, incidents, or temporary construction delays are not reflected in the calculations.

For example, similar to how Google Maps provides estimated travel times based on typical conditions for a given time of day—rather than what’s happening live—Dispatch Science works with a comparable model that emphasizes reliability and consistency for future-dated route planning.

This approach ensures more stable and predictable route optimization, especially when routes are planned days or weeks in advance. However, it also means that sudden traffic disruptions won’t be factored into the system’s estimated times or mileage.

Why does the mileage in the Driver App differ from Google Maps? 

The mileage shown in the Driver App is an estimated straight-line distance (often referred to as "as the crow flies") from the driver’s current location to the geofence boundary of the next stop. This estimate does not follow actual roads and may not measure precisely to the stop's physical address—only to the outer edge of its geofenced area.

In contrast, Google Maps provides the actual driving distance using the road network, which naturally results in a higher mileage. It accounts for roads, turns, traffic patterns, and restrictions, offering a more realistic travel distance.

Why Do Estimated Times and Distances Differ Between Dispatch Science and Google Maps?

The estimated travel times and distances shown in Dispatch Science may not always match those displayed in Google Maps. This is expected and can be attributed to several key differences in how each system calculates routes.

1. Estimates Are for Guidance Only

The travel times shown in the Driver App are based on the distance to the outer boundary of a stop’s geofence, not the exact address. These are approximate estimates, and drivers may arrive sooner or later depending on actual road conditions and stop locations.

2. Route Optimization and Traffic Data

Google Maps calculates routes using real-time traffic, road closures, and historical traffic patterns to determine the fastest current route.
In contrast, Dispatch Science uses predefined speed profiles and does not account for live traffic, making it better suited for pre-planned or future-dated routes.

3. Stop Times and Service Buffers

Dispatch Science includes extra time at each stop to account for loading, unloading, or administrative tasks—typically 10 to 15 minutes per stop.
Google Maps does not include these service times in its travel estimates.

4. Impact on Entire Route

In Dispatch Science, adding or changing a stop can affect the sequence of all other stops in the route.
This means any added time reflects the impact on the entire route, not just the point-to-point distance or time between two locations. Even a nearby stop can introduce indirect delays due to rerouting.

Differences between Dispatch Science and Google Maps are normal due to how each system handles route planning, traffic, stop times, and distance measurements. Dispatch Science is designed to support efficient multi-stop routing and driver workload management, which may lead to different—but more operationally accurate—estimates.