![]() This subset extraction is a common case because such huge datasets are seldom used in whole for a limited simulation use case. ![]() It becomes even more challenging when - according to changing requirements during project runtime - varying snippets of these datasets are to be extracted dynamically. Due to OpenDRIVE's complex data structure the plain management of such big datasets is already cumbersome. Various German and international test bed activities acquire extensive amounts of highly detailed road network data covering hundreds and thousands of kilometres of motorways, extra-urban and urban roads. In addition to prototyping of small-scale road segments for special driving simulation use cases the depiction of real-world road network datasets in OpenDRIVE becomes increasingly prominent. By bringing both domains closer together we hope to stimulate promising development of scenario generation and synthesis of reality-based road networks for driving simulator applications. This paper describes an extension of the free and open-source Geospatial Data Abstraction Library (GDAL) with OpenDRIVE as missing link between the domains of driving simulation and geographic information systems. The GIS domain provides well-established and convenient tools for spatial data processing, but does not yet offer support for OpenDRIVE data. makes generation, processing and validation of OpenDRIVE cumbersome. Such road networks, as used in driving/traffic simulation and test vehicles, are provided in specialised description formats - one of which being OpenDRIVE. their elevation profiles are all attached to the reference line.Extensive and highly detailed real-world road networks obtained through mobile mapping and spatial data processing build a basis for development and evaluation of advanced driver assistant and automation systems nowadays. The ASAM OpenDRIVE road network is modelled along the reference line, which is the core piece of every road. This facilitates a high degree of specialization for individual applications (usually simulations) while maintaining the interoperability that is required for the exchange of data between different applications. The format is organized in nodes that can be extended with user defined data. Road data may be manually created from road network editors, conversion of map data, or originate from converted scans of real-world roads. Providing a standardized format for road descriptions also enables the industry to reduce the cost of creating and converting these files for their development and testing purposes. With the help of ASAM OpenDRIVE, these road network descriptions can be exchanged between different simulators. The main purpose of ASAM OpenDRIVE is to provide a road network description that can be fed into simulations to develop and validate ADAS and AD features. The road networks that are described in the ASAM OpenDRIVE file can either be synthetic or based on real data. ![]() The data that is stored in an ASAM OpenDRIVE file describes the geometry of roads, lanes and objects, such as roadmarks on the road, as well as features along the roads, like signals. The ASAM OpenDRIVE format provides a common base for describing road networks with extensible markup language (XML) syntax, using the file extension xodr. ![]() ![]() (The download of the standard ASAM OpenDRIVE is free of charge) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |