Coordinates
Public road geometry is read as ordered coordinate points.
This page explains the public-facing formula chain. It does not change the live app model; it explains how road geometry, speed, friction, and comparative-output interpretation are connected.
Public road geometry is read as ordered coordinate points.
Direction changes across the selected segment are measured.
Segment length and heading change are converted into bend severity.
Centripetal demand, safe speed, slip ratio, and stopping distance are estimated.
Weather, visibility, driver, surface, vehicle, and context assumptions are applied.
The output is compared against sampled roads under the same assumptions.
Some values are derived directly from geometry. Some are physical checks based on standard motion relationships. Some are scenario modifiers or interpretive conversions that help the output make sense to users.
The important discipline is to keep those categories separate. A formula can be physically valid while the final risk interpretation still depends on assumptions, data quality, and calibration limits.
Physical meaning: the model estimates directional change before deriving curvature and radius.
Appears in: curvature, radius, selected-road geometry, maths output.
Road Risk uses this to translate map geometry into a physical bend radius.
Appears in: Safe Speed, curvature score, Annualised Comparative Model Output.
A tighter bend or higher speed increases the lateral acceleration required to follow the curve.
Appears in: slip ratio, safe-speed interpretation, curvature-related risk context.
Road Risk uses this as a readable physical check against the active scenario speed.
Appears in: Safe Speed.
A higher value means the scenario is closer to the assumed grip limit.
Appears in: Annualised Comparative Model Output and maths diagnostics.
Road Risk uses this to explain how speed, friction, and scenario assumptions affect stopping demand. The velocity-squared term is why speed changes can dominate braking distance.
Appears in: Stopping Distance.
The daily view helps users read a small annual value without changing the primary comparison basis.
Appears in: Daily Interpretive View.
Model use: scenario assumptions adjust the comparative output so sensitivity to conditions can be examined.
Appears in: Annualised Comparative Model Output, Daily Interpretive View, scenario summary.
If the selected geometry has a short segment length and a noticeable heading change, the calculated radius becomes smaller. At the same scenario speed, smaller radius increases centripetal acceleration, which can reduce safe-speed margin and raise the comparative model output.
This example explains the formula chain. It is not an exported real-road result and should not be interpreted as observed crash evidence.
Selected road coordinates are converted into segment length, heading change, radius, and curvature.
Speed, radius, friction, reaction time, safe speed, and stopping distance are evaluated.
Weather, visibility, traffic, road context, driver behaviour, and vehicle profile affect interpretation.
The app displays risk card values, maths, graph data, route analysis, and exports from the current context.
This page explains the public method at a readable level. The live app contains additional implementation detail for fallback assumptions, route sampling, percentile context, exports, and UI state.
The app turns these relationships into selected-road outputs, scenario controls, graphs, route analysis, and exports.