Skip to content

Commit 4d4812e

Browse files
tbleherStefan Cyliax
authored andcommitted
Clarify merging of lanes
Signed-off-by: Thomas Bleher <thomas.tb.bleher@bmw.de>
1 parent 31c1f93 commit 4d4812e

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

osi_logicallane.proto

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,6 @@ message LogicalLaneBoundary
238238
// left).
239239
//
240240
PASSING_RULE_BOTH_ALLOWED = 5;
241-
242241
}
243242
}
244243

@@ -261,11 +260,11 @@ message LogicalLaneBoundary
261260
//
262261
// If OSI is generated from OpenDRIVE, then \link LogicalLane
263262
// LogicalLanes\endlink map directly to OpenDRIVE lanes. However, it is allowed
264-
// to merge multiple consecutive OpenDRIVE lanes with the same type into one
265-
// OSI LogicalLane: if an OpenDRIVE lane has a single successor, which has the
266-
// same lane type, and this successor has only one predecessor (so no lane
267-
// merging or splitting) then the two lanes may be presented as one continuous
268-
// LogicalLane. This may be done recursively.
263+
// to merge multiple consecutive (in S direction) OpenDRIVE lanes with the same
264+
// type into one OSI LogicalLane: if an OpenDRIVE lane has a single successor,
265+
// which has the same lane type, and this successor has only one predecessor
266+
// (so no lane merging or splitting) then the two lanes may be presented as one
267+
// continuous LogicalLane. This may be done recursively.
269268
//
270269
// The \link ReferenceLine reference line\endlink pointed to by
271270
// #reference_line_id defines an ST coordinate system for the lane. This ST

0 commit comments

Comments
 (0)