-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tunnel description in OSI #311
Comments
Hi @haoyuanying , could you elaborate on the concrete requirements you have towards tunnel descriptions? I guess you need more details for the sensor model effects for radars in tunnels? I actually had the same thought just some days ago! :) |
Requirement to model tunnels came up again in #537 . As also ghost wrote, it would be good to have a more specific description about the requirement. Plan is to discuss it in the next Harmonization Group meeting. |
This topic was in discussion in Harmonisation group at 03.08.2021: For harmonization with OpenDRIVE, there is only very simple description of tunnels. Before integrating new information to the model, further reconcilation needs to be done:
|
From the sensor model point of view a few tunnel attributes would support dealing w/ the challenge of how to model radar/lidar behaviour inside a tunnel (just to get a rough idea, what might happen there, take a look into into dataset #110 from the radar scenes collection https://radar-scenes.com). E.g.
|
Requirements would need to come from sensor modellers, therefore deleting RoadModel label. |
@LukasElster as you are investigating tunnel effects in sensor data, do you have any comments on this? |
In the latest version, the lane is hardly to be described as a part of a tunnel, even through lane boundary TYPE_STRUCTURE, e.g. tunnel height, tunnel shape and so forth. Would it be something to think about here? Since sensors are sensitive to tunnels in any case... @CarloVanDriestenBMW
The text was updated successfully, but these errors were encountered: