# Impact on Route and Matrix Calculations

In some cases, the user receives an error - “Path could not be calculated.” This error is caused by restricted closest arcs. The improved snapping logic helps in reducing such errors by avoiding restricted arcs.

The improved logic takes the closest arc into consideration and attempts to ignore such arcs thus reducing errors. For example, if there is any restricted road near the start or end point, the new snapping logic ignores the restricted path and finds another way to calculate the route matrix.

With the reduced errors caused by restricted arcs, the performance of route and matrix calculations increases as the routing algorithm has less number of path complexities to handle.

startpoint: -73.5661, 45.5077 endPoint: -73.576048, 45.496936
Table 1. Comparing Boundaries
Before After
“Path could not be calculated” error
startPoint: -80.146276, 26.707754 endPoint: -81.483591, 28.583825
Table 2. Comparing Boundaries
Before After
“Path could not be calculated” error