Imagery © Esri World Imagery · roads © OpenStreetMap contributors
Work zone seen on 2+ days (bigger = more days)
Pedestrian in our car's path, under 3 s away
Cyclist or scooter rider in our car's path, under 3 s away
★ A downloadable real scenario
At a glance
Real crossing conflicts, ready to simulate
Each download has a local OpenDRIVE map, an OpenSCENARIO file with our car and the pedestrian or cyclist moving as they really did, and the dashcam clip. The OpenSCENARIO 1.2 file is checked against the official schema.
Work zones found
| Street | Days seen | Most cones | First → last |
|---|
What you get
- Crossing scenarios from your operating area: OpenSCENARIO + OpenDRIVE + real video, with the road user's real path.
- Work-zone layer: cones placed on the map and dated, per day (GeoJSON, WZDx).
- Curb activity layer (in development): where vehicles stand, double-park and block crossings, by block and hour.
- Road video of your streets at any hour, for robots and vehicles that ride on streets and in bike lanes.
Limits
- Seen from a car's windshield, not a sidewalk robot's camera: sold as map layers, scenarios and road-side behaviour, not as sidewalk training images.
- Positions come from the dashcam with nominal lens values: road users and cones are typically within 1–2 m.
- "Conflict" means a pedestrian or cyclist in our car's path less than 3 s away at its speed, a screening measure, not a judged near-miss. Every one shown was found by our road model and confirmed by a second, independent detector (YOLOv8x).
- Daylight and twilight only for detections. Street map © OpenStreetMap contributors (ODbL). Faces in the clips are blurred.