Having access to the complete road description empowers the scenario designer to easily control any actor within the scene. If your scenario involves following a lead car, you want to be able to simply set the lead car to “keep its lane”, without having to manually describe the curve it has to follow. When you’re building your experiment, you create some situations which involve other actors, such as cars or pedestrians. However, roads are never uniform and straight, so we need to have access to the actual geometry of them to compute those values.Īnother reason is scenario creation. If the road is perfectly uniform and straight, computing those is simple. Some of that data includeĪll of those values have one thing in common: they rely on the road geometry. As such, we’re interested in data that will be generated when subjects are driving. One answer lies in the reason why we use driving simulators: to run experiments. Any road network in the world can be described in the OpenDRIVE format. This includes road geometries, marking, lanes, borders, etc.
Initially developped through the PEGASUS project, OpenDRIVE was then transfered to ASAM, where its development continues.Īn OpenDRIVE file follows the XML standard and contains all relevant information describing a road network. But in driving simulators, we need much, much more information than that. Google Maps, OpenStreetMap), you might notice that you don’t get much description beyond “there’s a road here”. If you’re familiar with traditional mapping tools (e.g. OpenDRIVE defines a file format for the precise description of road networks
0 kommentar(er)
