Every road starts with one number: how fast drivers will go. Pick a design speed and you've already decided how far ahead a driver must be able to see, how sharp a curve may be, and how gently the road has to round the top of a hill. The rest of the topic works the same way. Traffic operations start from the flow, pavements from the axle loads they'll carry, and safety from how many vehicles had the chance to crash. So the first move on any problem here is to find the governing input. The equation it feeds is usually short. The points get lost in the bookkeeping around it.
Each kind of problem starts from one governing input
Four ideas carry that habit through the topic. Curves get one of their own for the station bookkeeping they bring, and pavements and safety share one.
Design speed sets the geometry. At 60 mph a car covers 88 ft every second, and the driver spends a couple of those seconds just noticing trouble and reaching the brake. The ground covered in those seconds, plus the braking distance, is the stopping sight distance, and much of road geometry exists to provide it: the length of a crest or sag curve, and the clear space inside a horizontal curve. The curve's radius comes from the same speed, through how much banking and tire grip it takes to turn the car. Raise the design speed and all of them grow, most faster than the speed itself. Even a yellow signal is the stopping picture again, timed instead of measured.
Curves are geometry plus station bookkeeping. A horizontal curve is an arc of a circle fitted between two straight roads, and a vertical curve is a parabola fitted between two grades. A little trigonometry or algebra gives a curve's lengths and elevations. Then each answer has to be placed on the road by its station, its distance along the route, and stations follow the road a car actually drives: around the curve, not out to the corner where the straight roads would have met.
Traffic obeys q=kv. Picture a lane as a moving line of cars. The density k is how many cars are in a mile of it, the speed v is how many miles the line moves in an hour, and their product is the flow q, the cars per hour that pass a point. An empty road has all the speed it wants and no cars, and a road jammed solid has all the cars and no speed. Both carry zero flow, so the most traffic moves somewhere in between. Every operations Lesson builds on that product, from the gap between two cars to the letter grade a freeway earns.
Pavements are designed for axle loads, and safety compares rates. In both, the obvious count is the wrong one. A pavement doesn't count vehicles. It counts axle passes, each weighted by how hard the axle presses, and that weight climbs roughly with the fourth power of the load. One loaded truck axle does the damage of thousands of cars, so pavement design converts the traffic into standard axle loads and adds them up over the pavement's life. Crash counts mislead the same way: a busy intersection sees more crashes partly because more cars pass through it. Divide the crashes by the exposure, the vehicles that had the chance to crash, and the crash rate that results is a fair way to compare two sites.
The Lessons below run from geometry through traffic and signals to safety and planning, and finish with pavements. Travel Demand Forecasting, the one Lesson outside the four ideas, follows the same habit: it starts from the trips each zone produces and shares that total among destinations, modes, and routes.
Where the points go
Stations. Station 12+50.00 is 1,250 ft from the start of the route, so adding a 400-ft curve lands at 16+50.00.
Grades. The Handbook's stopping sight distance equation takes a 3% grade as 0.03, and its vertical curve length formulas take a 3% change in grade as 3.
Speeds. The same stopping sight distance equation takes speed in mph, and the Handbook's yellow interval equation takes it in ft/s. 60 mph is 88 ft/s.
Each problem below leans on one of the four ideas. Name it before you reach for an equation.