Clarifications on curbs and other boundaries with a height#608
Clarifications on curbs and other boundaries with a height#608clemenshabedank wants to merge 3 commits intomasterfrom
Conversation
…having a 'height' Signed-off-by: Habedank Clemens <qxs2704@europe.bmw.corp>
…n line with curb definitions in other standards Signed-off-by: Habedank Clemens <qxs2704@europe.bmw.corp>
|
With the latest change in 6526e0a this PR is seen more as a bugfix to the current definition, because modelling curbs with only one laneboundary of type curb and a height field makes the height of adjacent lanes ambiguous. This PR makes it clearer that a curb must be modelled with two laneboundary's while deprecation of TYPE_CURB can of course be done in v4.0 earliest. |
|
The basic issue is now resolved by #634. This PR can be closed by future Road Model work if not seen helpful. |
2 similar comments
|
The basic issue is now resolved by #634. This PR can be closed by future Road Model work if not seen helpful. |
|
The basic issue is now resolved by #634. This PR can be closed by future Road Model work if not seen helpful. |
|
We will close this PR due to a lack of interest in the topic. |
modifications and clarifications for curbs and other lane boundaries having a 'height'
Signed-off-by: Habedank Clemens qxs2704@europe.bmw.corp
#### Reference to a related issue in the repository
Add a reference to a related issue in the repository.
Add a description
This PR is a suggestion which was preceded by discussion in the Road Model WP. It is basically reasoned by certain unclarities in the current definition of curbs:
This definition tries to fix those unclarities and needs to be seen in combination with #600
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!