Automate BC Route Planner
HumDay reads BC Route Planner’s own published API description and derives 24 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What BC Route Planner is
Finds shortest/fastest route between a start point and one or more stop points on British Columbia's public road network. The BC Route planner [webpage](https://www2.gov.bc.ca/gov/content?id=9D99E684CCD042CD88FADC51E079B4B5) provides additional information. Here are some geocoded addresses to play with: 18 Douglas St,Victoria -123.36962,48.40892 1002 Johnson St, Victoria -123.355745,48.42620
API host: router.api.gov.bc.ca
What HumDay can do in BC Route Planner
12 documented operations change something in BC Route Planner.
- POSTGet the path, distance and travel time between a series of geographic points
/route.{outputFormat} - POSTGet distance and travel time between two geographic points
/distance.{outputFormat} - POSTGet the directions, path, distance and travel time between a series of geographic points
/directions.{outputFormat} - POSTGet the path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time.
/optimalRoute.{outputFormat} - POSTGet the directions, optimal path, distance and travel time between a start point and one or more end points which are reordered to minimize total distance or time.
/optimalDirections.{outputFormat} - POSTGet the path, distance and travel time between a series of geographic points
/truck/route.{outputFormat} - POSTGet distance and travel time between two geographic points
/truck/distance.{outputFormat} - POSTGet the directions, path, distance and travel time between a series of geographic points
/truck/directions.{outputFormat} - POSTGet the path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time.
/truck/optimalRoute.{outputFormat} - POSTGet distance and travel time between each pair of geographic points
/distance/betweenPairs.{outputFormat} - POSTGet the directions, optimal path, distance and travel time between a start point and one or more end points which are reordered to minimize total distance or time.
/truck/optimalDirections.{outputFormat} - POSTGet distance and travel time between each pair of geographic points
/truck/distance/betweenPairs.{outputFormat}
What HumDay can read from BC Route Planner
These are the operations a schedule or a trigger can watch.
- GETGet the path, distance and travel time between a series of geographic points
/route.{outputFormat} - GETGet distance and travel time between two geographic points
/distance.{outputFormat} - GETGet the directions, path, distance and travel time between a series of geographic points
/directions.{outputFormat} - GETGet the optimal path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time.
/optimalRoute.{outputFormat} - GETGet the directions, optimal path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time.
/optimalDirections.{outputFormat} - GETGet the path, distance and travel time between a series of geographic points for a commercial vehicle
/truck/route.{outputFormat} - GETGet distance and travel time between two geographic points for a commercial vehicle
/truck/distance.{outputFormat} - GETGet the directions, path, distance and travel time between a series of geographic points for a commercial vehicle
/truck/directions.{outputFormat} - GETGet the optimal path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time for a commercial vehicle
/truck/optimalRoute.{outputFormat} - GETGet distance and travel time between each pair of geographic points
/distance/betweenPairs.{outputFormat} - GETGet the directions, optimal path, distance and travel time between a start point and a series of end points which are reordered to minimize total distance or time for a commercial…
/truck/optimalDirections.{outputFormat} - GETGet distance and travel time between each pair of geographic points for a commercial vehicle
/truck/distance/betweenPairs.{outputFormat}
How automating BC Route Planner works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live BC Route Planner account.
- Grant access, then go live. You approve the specific BC Route Planner operations it may use — and only those.
Automate BC Route Planner with these
- BC Data Catalogue22 operations
- BC Geocoder16 operations
- BC Geographical Names14 operations
- BC GeoMark7 operations
- BC Gov News 1.027 operations
- BC Groundwater Wells, Aquifers and Registry24 operations
- DriveBC's Open5114 operations
- WorkBC Job Posting5 operations
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
- OSF APIv2 Documentation156 operations
- IllumiDesk143 operations
Categories
Questions about BC Route Planner automation
- Can HumDay connect to BC Route Planner?
- Yes. HumDay reads BC Route Planner's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 24 operations are documented.
- Do I need to write code to automate BC Route Planner?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your BC Route Planner account.
- What can HumDay do in BC Route Planner?
- 12 of the 24 documented operations change something in BC Route Planner, and 12 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my BC Route Planner account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to BC Route Planner is held behind that approval.
Where this came from
The operations above are read from a published API description for BC Route Planner at raw.githubusercontent.com/bcgov/api-specs/master/router/router.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.