Florida toll rates

How a bot finds the toll (read this first)

1. Get your route as roads and points. From the route planner take (a) the line of lat/lon points and (b) the OSM way id of every road piece the route drives (Valhalla: trace_attributes on the route shape, attribute edge.way_id).
2. Find the toll points you pass. Every row of the table “Booths” below is one booth standing on one OSM way. You pass that booth when both hold: your route drives that OSM way, and your line passes within 10 m of the booth’s lat/lon. Note the row’s point_id. A ramp booth is on the ramp’s way, so driving past on the main road is not a hit; a main-road booth is on the main road’s way, so a ramp beside it is not a hit. Rows marked “position only” have no OSM road: there, passing within the stated radius counts.
3. Note your direction at that booth (the compass direction your route is heading there: northbound, southbound, eastbound, westbound).
4. Read the price. Open the point’s facility page (the point_id links there). Under the point_id is one row per direction, vehicle and payment: take the row whose direction is yours or “both”, your vehicle (axles) and how you pay. A point with no row for your direction does not charge you.
5. Roads priced per trip (marked “per trip”): their booths are the road’s exits. The first one your route passes is where you got on, the last one where you got off; read that pair in the facility page’s “Trip prices” table for your direction.
6. Add up the amounts of every point (and trip) passed.
7. Check for untied tolls. The table “OSM toll nodes not tied to a toll point” lists toll gantries/booths mapped in OpenStreetMap on these roads that no published point claims. If your route passes one (same way + distance rule), say so: the published rates do not price it.

No route line? Fall back to names: each facility page has the road in driving order with exit numbers and the names the route planner uses. Names cannot tell which ramp you took at an exit with several ramps; the way id can.