Skip to content

Commit 3b2fa6f

Browse files
Make intersection free lane boundary definition more concrete
Signed-off-by: Fabian Pfeuffer <Fabian.Pfeuffer@bmw.de>
1 parent b00ad2b commit 3b2fa6f

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

osi_lane.proto

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ message Lane
144144
// </tr>
145145
// <tr>
146146
// <td>
147-
// \c #free_lane_boundary_id = lb11
147+
// \c #free_lane_boundary_id = lb11, lb12, lb13, lb14
148148
// </td>
149149
// </tr>
150150
// <tr>
@@ -371,6 +371,14 @@ message Lane
371371
// \note \c Lane with \c #type = \c #TYPE_INTERSECTION use only free
372372
// lane boundaries.
373373
//
374+
// \note Free boundaries should be defined in clockwise direction. The starting
375+
// boundary can be chosen arbitrarily.
376+
// Example: For the intersection lane l7 in image \ref Intersection our
377+
// starting boundary could be lb11. In this case, lb11 must be defined
378+
// from left to right. The next boundary would be lb14, defined from top to
379+
// bottom, then lb13 defined from right to left and finally lb12 defined from
380+
// bottom to top.
381+
//
374382
// \note OSI uses singular instead of plural for repeated field names.
375383
//
376384
// \rules

0 commit comments

Comments
 (0)