ADAS Road Geometry Creation Using Link Chains and Bezier Curves
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing geographic databases designed for navigation systems do not meet the specific data needs and accuracy requirements of advanced driver assistance systems (ADAS), leading to inefficiencies and inaccuracies in providing road geometry and other critical information.
Innovation Solution
A method and system for creating geometry in ADAS using link chains, 2D and 3D B-splines, and Bezier curves, which are optimized to minimize storage requirements and improve data accuracy, by selecting road segments, fitting splines, and correcting for GPS inaccuracies, ultimately converting these into Bezier curves for efficient ADAS functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If navigation system geographic database is used for ADAS, then data availability is improved, but data accuracy and suitability for ADAS functions deteriorates
Solution Approach 1:
The geographic database is segmented into two distinct versions: a navigation version containing comprehensive data for general navigation purposes, and an ADAS version containing only the specific road geometry data (nodes, shapes, altitudes) required for advanced driver assistance functions. This segmentation allows each version to be optimized for its specific purpose without compromise.
Solution Approach 2:
The ADAS geographic database extracts only the essential road geometry elements (nodes with latitude/longitude/altitude and shapes with curve definitions) from the comprehensive navigation database, removing all unnecessary navigation-specific data. This extraction process creates a streamlined database that is both smaller in size and precisely tailored for ADAS computational requirements.
2Loss of information
If comprehensive navigation database is used, then information completeness is improved, but storage requirements increase
Solution Approach 1:
The ADAS database extracts only the essential road geometry elements (nodes with latitude/longitude/altitude and shapes with curve definitions) from the comprehensive navigation database, removing all unnecessary navigation-specific data. This extraction process creates a streamlined database that is both smaller in size and precisely tailored for ADAS computational requirements.
Solution Approach 2:
The database structure uses local quality by defining shapes with specific curve types (Bezier curves, B-splines, circular arcs) appropriate for different road geometry characteristics. Each road segment's shape is represented with the most efficient and accurate curve type for that specific geometry, optimizing both storage and computational efficiency for local road features.
3Manufacturing precision
If road geometry is represented with complex curves, then manufacturing precision is improved, but device complexity increases
Solution Approach 1:
The patent transforms road geometry representation by changing the parameters from discrete coordinate points to continuous mathematical curve definitions (Bezier curves and B-splines). This parameter change allows precise representation of complex road geometries using a small number of control points and curve parameters, significantly reducing data complexity while maintaining high geometric precision for ADAS calculations.
Data Source
AI summary
A method and system for creating geometry for ADAS are described. Link chains, which are a sequence of segments, are created. The link chains are used to create 2D splines. The link chains, the 2D splines, and height data are used to create 3D splines. The 3D splines and possibly the 2D splines are converted to Bezier curves, which can be used to create a 2D polyline. ADAS applications can use the Bezier curves and the 2D polylines to provide ADAS functions.