These use cases will still require some level of interaction between the road network description and the test case or the ODD characteristics. One example is traffic simulations with intelligent traffic agents, which interact directly with the road network without strictly needing a scenario. Various use cases leverage road network descriptions without necessarily requiring a scenario. Insights into how this standard might evolve The latest version of OpenDRIVE is V1.7.1, released in June 2021. The main purpose of OpenDRIVE is to provide a road network description that can be fed into simulations for development and validation purposes of AD and ADAS features. The road networks that are described in the OpenDRIVE file can either be synthetic or based on real data. The data that is stored in an OpenDRIVE file describes the geometry of roads, lanes, and objects, such as markings on the road, as well as features along the roads, for example signals. You can find a detailed description in chapter 5.4.1 of the CarMaker 9.x User’s Guide.The OpenDRIVE format provides a common base for describing road networks with Extensible Markup Language (XML) syntax, using the file extension. Because of the differences between the internal structures of IPGRoad and OpenDRIVE, there are certain limitations to the export from IPGRoad to OpenDRIVE. Since CarMaker 9.0, there is also a OpenDRIVE Export available. Open the OpenDRIVE file in a text editor and check it for any discrepancies to the mentioned points above. This is currently not supported in CarMaker Possibly existing information on geo-references in OpenDRIVE refer to an open source project for the conversion of geo-references.as well as all other objects which are not part of the official OpenDRIVE documentation revision 1.4 or 1.5.stop lines, due to missing parameters required by the road markings in IPGRoad (lane, length, width, etc.).lateral elevation of a driving lane, e.g.lanes being defined with reference to the road border instead of the lane width.lateral profiles of type superelevation, crossfall and shape.The following items in OpenDRIVE road descriptions are not supported in CarMaker 8.x and 9.x or only limited support is provided due to missing counterparts in IPGRoad: several small junctions combined to one huge and complex junction with many odr-roads in one.standard junctions with a connection of two parallel links.
Contact opendrive manual#
The following scenarios might require a manual adaption after the import: segments with a length of zero are ignored.lane width profiles which lead to self-overlapping sections at the given curvature.The following common errors in OpenDRIVE road description files are not automatically corrected by the import: One possible problem might be an error in the OpenDrive file. the OpenDRIVE specification is not entirely explicit and in some cases interpretations of the specification are possible.OpenDRIVE and IPGRoad have different internal structures.
Contact opendrive how to#
How to import an OpenDRIVE file to CarMaker is described in the FAQ In this FAQ article some information and advice shall be given for the import of OpenDRIVE road descriptions.
0 kommentar(er)
