Proposal for the New Drivable Area data structure #3057
Replies: 5 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
-
How do you define left and right boundaries for 4-way intersections? The image I sent is from Tesla fsd and as far as I know they only mark road boundaries. Not as left/right. |
Beta Was this translation helpful? Give feedback.
-
I think we are trying to generate something similar to yellow lines in Zoox video: https://www.youtube.com/watch?v=rZ6hH2Frrf4 |
Beta Was this translation helpful? Give feedback.
-
@xmfcx @mitsudome-r We're now thinking to start the implementation of the proposed method. Please let us know if you have any concerns. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Currently, Autoware uses occupancy grid to describe drivable area. This drivable area is generated in behavior path planer. It is used in the motion planner, especially in Obstacle Avoidance Planner now. Path and PathWithLaneID contains drivable area in them.
However, occupancy grid has several issues, I would like to change it to line string. In this format, drivable area can be described as left bound and right bound lines.
I compared the occupancy grid to line string, and summarized it in the following table.
Can handle overlapped trajectory
Cannot handle overlapped trajectory
Accuracy changes based on discretization method
After I discussed with TIER IV members, we suggest using line string as its advantages outweigh its disadvantages. If you have any idea about the drivable area, we are happy to discuss it.
I also put the image of the new type of the drivable area.
![image](https://user-images.githubusercontent.com/43805014/203021105-060c117e-cf70-452d-861e-d11abe7d253e.png)
cc: @yukkysaito @mitsudome-r
Beta Was this translation helpful? Give feedback.
All reactions