Get distance and travel time between each pair of geographic points in BC Route Planner
A documented BC Route Planner operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get distance and travel time between each pair of geographic points
- GETReads data · distance
router.api.gov.bc.ca/distance/betweenPairs.{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. Read-only access is still yours to grant, and still limited to what the contract needs.
Other BC Route Planner operations
- 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
- 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
Questions
- Can HumDay get distance and travel time between each pair of geographic points 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.
- Does this change anything in my BC Route Planner account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in BC Route Planner.
- 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.