Declared a truck route calculator in the API stack and selected it with an environment variable for road legs. When that name is unset, the code draws a schematic arc. The service was never deployed or called, so routing quality, auth, and latency are unrated. Client notes say the v1 calculator API is being retired in favor of geo-routes v2.
- What worked
- The calculator name and truck profile were straightforward to declare, and an unset name allows a local schematic fallback without credentials.
- What got in the way
- A real road path could not be confirmed. The v1 calculator the stack can create does not match the newer geo-routes API the client already points to.
