Skip to content

Commit c9651c3

Browse files
author
Habedank Clemens
committed
sharpened definition of distance in LongitudinalDistanceAction and LateralDistanceAction, noted current limitations, fixed sentence in PathAction
1 parent 25271a5 commit c9651c3

File tree

1 file changed

+19
-9
lines changed

1 file changed

+19
-9
lines changed

osi_trafficcommand.proto

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -229,8 +229,8 @@ message FollowTrajectoryAction
229229
//
230230
// \brief Follow path action.
231231
//
232-
// Controls a traffic participant to follow a trajectory using vertices
233-
// with timings. It specifies the motion in space independent of time.
232+
// Controls a traffic participant to follow a path using vertices. It
233+
// specifies the motion in space independent of time.
234234
//
235235
// \note The StatePoint messages in path_point only requires a specified
236236
// position field. The orientation can be set optionally. Any
@@ -482,13 +482,18 @@ message SpeedAction
482482

483483
// \brief Longitudinal Distance Action
484484
//
485-
// The action tells the traffic participant to reach a longitudinal distance to
486-
// another traffic participant. The longitudinal distance is defined as the distance
487-
// along the lane.
485+
// The action tells the (host) traffic participant to reach a certain longitudinal distance
486+
// relative to a target traffic participant. The longitudinal distance is defined as the distance
487+
// along the centerline of the lane, on which the (host) traffic participant is currently located.
488+
// The interpolation strategy between centerline points for calculating
489+
// that distance along the centerline is open to the traffic participant modeller.
488490
//
489491
// \note This action is aligned with LongitudinalDistanceAction of OpenSCENARIO 1.0
490492
// defining the reference traffic participant and the distance.
491493
//
494+
// \note Limitation: This concept currently only works for lanes with a centerline, i.e. for lanes
495+
// of TYPE_DRIVING, not for lanes of TYPE_NONDRIVING or TYPE_INTERSECTION.
496+
//
492497

493498
message LongitudinalDistanceAction
494499
{
@@ -532,13 +537,18 @@ message LongitudinalDistanceAction
532537

533538
// \brief Lateral Distance Action
534539
//
535-
// The action tells the traffic participant to reach a lateral distance to
536-
// another traffic participant. The lateral distance is defined as the perpendicular to the current lane
537-
// along the lane.
540+
// The action tells the (host) traffic participant to reach a certain lateral distance relative to
541+
// a target traffic participant. The lateral distance is defined along an imaginative perpendicular line
542+
// with respect to the centerline of the current (host) traffic participant's lane.
543+
// The interpolation strategy between centerline points for calculating that distance along the imaginative
544+
// perpendicular line is open to the traffic participant modeller.
538545
//
539546
// \note This action is aligned with LateralDistanceAction of OpenSCENARIO 1.0
540547
// defining the reference traffic participant and the distance.
541548
//
549+
// \note Limitation: This concept currently only works for lanes with a centerline, i.e. for lanes
550+
// of TYPE_DRIVING, not for lanes of TYPE_NONDRIVING or TYPE_INTERSECTION.
551+
//
542552

543553
message LateralDistanceAction
544554
{
@@ -595,7 +605,7 @@ message LaneOffsetAction
595605
optional ActionHeader action_header = 1;
596606

597607
// Targeted lane offset in meters relative to the centerline of the
598-
// current lane. Positive values mean left of the centerline,
608+
// current traffic participant's lane. Positive values mean left of the centerline,
599609
// negative values mean right of the centerline.
600610
//
601611
// Unit: m

0 commit comments

Comments
 (0)