-
Notifications
You must be signed in to change notification settings - Fork 11
Error handling for optimalRoute - Route not found #376
Copy link
Copy link
Open
Labels
Milestone
Description
Issue description:
Within the BC Route Planner test environment (v 2.2.1), the following example generate a 500 error when a route is not found based on the snapDistance parameter value when using /optimalRoute. This behaviour also occurs in production for /optimalRoute, but not for /route.
To reproduce:
Append an API key to the following URL and run the tests.
Expected behavior:
Response - HTTP 200
"routeFound": false,
"distance": -1,
"time": -1,
"timeText": "-1 seconds",
Test URL:
A route will only be found when snapDistance=2100 or higher
Reactions are currently unavailable