Know what a route crosses
Routed results report the tollways and access-restricted ways they cross, directions can route around them on request, and suggestions never propose one at all.
Routed results now report the tollways and access-restricted ways they cross. Every GeometryAnalysis carries advisories, naming whether the line crosses a way that charges a toll or one restricted to owners, customers, deliveries, permit holders, or destination traffic, and where, as coordinate ranges. Permissive ways, where the owner tolerates passage, are reported but are not treated as a restriction.
directions accepts avoid: [TOLLWAY, RESTRICTED_ACCESS] to route around those ways. It costs a second routing pass only when the first route actually crosses one. Avoidance is best-effort, so each route reports an avoidance outcome: NOT_NEEDED, APPLIED, or NO_ROUTE when the hazard could not be routed around, which usually means a waypoint sits on the way itself.
suggestions never proposes a route through a tollway or an access-restricted way. There is no opt-out: when no hazard-free candidate can be generated from the given points the query fails rather than returning one that crosses something. Use directions when a route should go through such a way deliberately.
Placing a point that routes a segment through a tollway or an access-restricted way now asks first. Confirm and the point is placed; decline and the route returns to its last accepted shape. Opening a saved segment that already crosses one does not prompt; only a change you make does.