Get the path, distance in BC Route Planner
A documented BC Route Planner operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Get the path, distance and travel time between a series of geographic points
- POSTChanges data · route
router.api.gov.bc.ca/route.{outputFormat}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which BC Route Planner operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other BC Route Planner operations
- Get distance and travel time between two geographic pointsPOST · changes data
- Get the directions, pathPOST · changes data
- Get the path, distance and travel time between a start pointPOST · changes data
- Get the directions, optimal pathPOST · changes data
- Get the path, distancePOST · changes data
- Get distance and travel time between two geographic pointsPOST · changes data
- Get the directions, pathPOST · changes data
- Get the path, distance and travel time between a start pointPOST · changes data
Questions
- Can HumDay get the path, distance in BC Route Planner?
- Yes. This operation is published in BC Route Planner's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my BC Route Planner data?
- Yes — this is a POST operation, so it changes something in BC Route Planner. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your BC Route Planner account.
Where this came from
Read from a published API description for BC Route Planner at raw.githubusercontent.com/bcgov/api-specs/master/router/router.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.