Impact on Route and Matrix Calculations - Spectrum_Routing_for_Big_Data - 3.0

Global Routing SDK Developer Guide

Product type
Software
Portfolio
Locate
Product family
Spectrum™ software
Product
Spatial Big Data > Routing for Big Data
Version
3.0
ft:locale
en-US
Product name
Routing for Big Data
ft:title
Global Routing SDK Developer Guide
Copyright
2024
First publish date
2007
ft:lastEdition
2024-10-15
ft:lastPublication
2024-10-15T10:39:39.482000

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