-
Notifications
You must be signed in to change notification settings - Fork 72
fix(lanelet2_extension): improve traffic regulatory element id visualization #225
fix(lanelet2_extension): improve traffic regulatory element id visualization #225
Conversation
…ization Signed-off-by: satoshi-ota <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #225 +/- ##
==========================================
- Coverage 11.26% 11.11% -0.16%
==========================================
Files 37 37
Lines 2671 2709 +38
Branches 1370 1387 +17
==========================================
Hits 301 301
- Misses 1950 1987 +37
- Partials 420 421 +1
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Could you explain a bit more detail on why you want to move the text to stopline? In general, if you want to know the link between lanelet, stopline, and the traffic light, then using vector map builder would be a better option. Are there any particular reasons why you want to see it on RVIZ? Also, even if you can get the id of the traffic light regulatory element at the stopline, you can't really know which traffic light is linked to the road anyways. Here are some alternative ideas that I can think of depending on your use case.
|
@mitsudome-r Thanks for your comment.
Yes. Sometimes we developper use this rviz plugin in order to check the behavior for traffic signals, and I think it is convenient for us to show the related traffic light regualtory element ID on rviz.
I see. Then, I'll fix the logic so that it can show exact relation between road lanelet and traffic light regulatory elements. |
Signed-off-by: satoshi-ota <[email protected]>
@mitsudome-r I fixed implementation to show exact related traffic reg elem ID in cebfe7b. And, please check autowarefoundation/autoware.universe#6028. |
@satoshi-ota Thanks for the reply. I am okay with the change then. |
@mitsudome-r Thank you. I'll merge this PR with autowarefoundation/autoware.universe#6028. |
Signed-off-by: satoshi-ota <[email protected]>
Signed-off-by: satoshi-ota <[email protected]>
Signed-off-by: satoshi-ota <[email protected]>
…ization (autowarefoundation#225) * fix(lanelet2_extension): improve traffic regulatory element id visualization Signed-off-by: satoshi-ota <[email protected]> * fix(lanelet2_extension): show exact relation Signed-off-by: satoshi-ota <[email protected]> * feat(lanelet2_extension): show traffic light id Signed-off-by: satoshi-ota <[email protected]> * fix: typo Signed-off-by: satoshi-ota <[email protected]> * fix(lanelet2_extension): remove whitespace Signed-off-by: satoshi-ota <[email protected]> --------- Signed-off-by: satoshi-ota <[email protected]>
Description
It was difficult to understand relationship between regulatry element id and road lanelet. In this PR, I fixed id visualization to show the id on stop line which is reffered by traffic regulatory element in order to make it easier to know related regulatory elements.
Tests performed
Psim
Effects on system behavior
Nothing.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.