Road Selection and Context
Click a road, retrieve nearby public map data, preserve relevant OSM tags, and identify the selected road segment. Supports: selected-road context and export evidence.
Road Risk is not just a map demo. It is a live analytical workspace for selecting roads, inspecting geometry, changing assumptions, comparing distributions, analysing routes, and exporting evidence.
Each feature supports the same public-data to risk-output chain. The app should be used as an exploratory model, not as a black-box verdict.
Click a road, retrieve nearby public map data, preserve relevant OSM tags, and identify the selected road segment. Supports: selected-road context and export evidence.
Estimate segment length, heading change, bearing, curvature, radius, and related values from selected road geometry. Supports: safe speed, curvature risk, and maths output.
Translate speed, friction, curvature, reaction time, and stopping assumptions into readable physical outputs. Limitation: this is simplified physics, not full vehicle simulation.
Change vehicle class, weather, lighting, behaviour, BAC, fatigue, distraction, speed, and road-context assumptions. Supports: sensitivity testing.
Use highway class, speed tags, surface, smoothness, lanes, lighting, traffic proxies, and missing-data flags to keep context visible. Limitation: absent public tags do not prove absent infrastructure.
Sample the visible network and compare selected-road output against percentile, density, and tail views. Supports: context beyond a raw model output.
Calculate routes, draw route lines, sample route risk, inspect hotspots, and explore isochrone-style reachability contexts. Supports: route mean and peak segment interpretation.
Export CSV, GeoJSON, JSON summaries, distribution data, and visual outputs so the result can be reviewed outside the app. Supports: reproducibility and audit.
Use the app as a teaching and research surface where assumptions, formulas, and limitations are visible rather than hidden.
| Feature group | Scientific purpose | Outputs supported | Caution |
|---|---|---|---|
| Road data and selection | Build the selected-road context from public geometry and tags. | Road info, selected segment, exports. | Parallel roads and missing tags require careful interpretation. |
| Geometry extraction | Convert road shape into measurable length, bearing, heading change, radius, and curvature. | Curvature, safe speed, maths panel. | Sparse or noisy road nodes can reduce confidence. |
| Scenario testing | Show how assumptions change model output direction and magnitude. | Annual output, daily view, safe speed, stopping distance. | Assumptions should be changed deliberately, not treated as observed facts. |
| Infrastructure context | Separate retrieved OSM tags from derived values and fallback assumptions. | Infrastructure rating, confidence notes, exported metadata. | Missing public tags should not be interpreted as proof that infrastructure is absent. |
| Statistics and graphs | Place one road inside a sampled comparison set. | Percentile, density, tail, distribution exports. | The comparison depends on the sampled area and available road data. |
| Route, isochrone, and export tools | Extend selected-segment reasoning to routes, reachable areas, hotspots, and review files. | Route mean, highest segment, isochrone overlays, CSV, GeoJSON, JSON, PNG outputs. | Route and isochrone outputs remain sampled model interpretations, not official assessments. |
Use the map to select a real road segment and verify that the highlighted geometry matches the intended road.
Review missing tags, fallback assumptions, vehicle profile, speed, weather, lighting, and traffic context.
Compare Annualised Comparative Model Output, daily view, safe speed, stopping distance, infrastructure rating, and maths notes.
Open graph views or route analysis to understand whether the road is typical, elevated, or unusual in context.
Use export formats to preserve geometry, tags, scenario assumptions, model values, and graph data for review.
Risk card, maths, graph data, route overlay, and export state update from the active road context.
Vehicle, weather, visibility, behaviour, traffic, surface, and speed assumptions.
Coordinate geometry supports segment length, heading change, radius, and curvature. Sparse or noisy geometry lowers confidence.
Speed, radius, friction, reaction time, and vehicle assumptions create interpretable physical checks.
Rain, fog, ice/snow, heat, fatigue, distraction, BAC, overspeed, and surface quality can change interpretation.
OSM tags and fallback assumptions help describe context without pretending missing data is proof of absence.
Sampled-network comparison, P95/P99 style thresholds, and distribution spread make outputs easier to interpret.
Route overlays, sampled segments, CSV, GeoJSON, JSON, distribution data, and PNG outputs support review.
The maths page and modal explain how physical quantities connect to displayed values.
Distribution views show where one selected road sits relative to sampled roads.
Export formats make it possible to audit values, geometry, and scenario assumptions.
Fallbacks and missing public data are part of the interpretation, not hidden from the user.
The public site explains the system. The live app is where the map, model, graphs, routes, and exports run.