Additional clang reformating

Additional reformating of the proto files.

Author: carsten-kuebler

osi_detectedlane.proto

@@ -70,12 +70,13 @@ message DetectedLaneBoundary
     // attribute has to be set for each instance. All other values will be
     // reused from the previous \c BoundaryPoint in the sequence or set to
     // default values if there is none or it was never set. For dashed lines,
-    // one \c LaneBoundary::BoundaryPoint has to be at the start and another at the end
-    // of each dashed line segment. For Botts' dots lines, one
-    // \c LaneBoundary::BoundaryPoint position has to define each Botts' dot.
+    // one \c LaneBoundary::BoundaryPoint has to be at the start and another at
+    // the end of each dashed line segment. For Botts' dots lines, one \c
+    // LaneBoundary::BoundaryPoint position has to define each Botts' dot.
     //
-    // \attention For \c LaneBoundary::BoundaryPoint the same rules regarding maximum
-    // distance and approximation error apply as for \c Lane::Classification::centerline.
+    // \attention For \c LaneBoundary::BoundaryPoint the same rules regarding
+    // maximum distance and approximation error apply as for \c
+    // Lane::Classification::centerline.
     //
     repeated LaneBoundary.BoundaryPoint boundary_line = 3;
 

osi_detectedtrafficsign.proto

@@ -31,8 +31,8 @@ message DetectedTrafficSign
 
     //
     // \brief Candidates for a detected main sign as estimated by the sensor.
-	//
-	// \image html OSI_DetectedMainTrafficSign.jpg
+    //
+    // \image html OSI_DetectedMainTrafficSign.jpg
     //
     message DetectedMainSign
     {
@@ -159,8 +159,8 @@ message DetectedTrafficSign
     //
     // \brief Candidates for all detected supplementary signs of one traffic
     // sign as estimated by the sensor.
-	//
-	// \image html OSI_DetectedSuppSign.jpg
+    //
+    // \image html OSI_DetectedSuppSign.jpg
     //
     message DetectedSupplementarySign
     {

osi_environment.proto

@@ -109,9 +109,12 @@ message EnvironmentalConditions
     // contrast of a distant object against its background.
     //
     // \par References:
-    // - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway. Transportation Research Board, 1996.
-    // - [3] [StVO 17 chapter 3](https://www.stvo.de/strassenverkehrsordnung/101-17-beleuchtung)
-    // - [4] [Homepage of the Meteorological Office](http://www.metoffice.gov.uk/guide/weather/observations-guide/how-we-measure-visibility)
+    // - [2] SHEPARD, Frank D. Reduced visibility due to fog on the highway.
+    // Transportation Research Board, 1996.
+    // - [3] [StVO 17 chapter
+    // 3](https://www.stvo.de/strassenverkehrsordnung/101-17-beleuchtung)
+    // - [4] [Homepage of the Meteorological
+    // Office](http://www.metoffice.gov.uk/guide/weather/observations-guide/how-we-measure-visibility)
     //
     enum Fog
     {
@@ -175,11 +178,17 @@ message EnvironmentalConditions
     // [6] and standards for required lighting levels on roads [6, 7, 8, 9].
     //
     // \par References:
-    // - [5] [The NIST Reference on Constants, Units, and Uncertainty](https://physics.nist.gov/cuu/Units/units.html)
-    // - [6] [National Optical Astronomy Observatory](https://www.noao.edu/education/QLTkit/ACTIVITY_Documents/Safety/LightLevels_outdoor+indoor.pdf)
-    // - [7] [Standards for required street lighting in the USA](http://www.wsdot.wa.gov/research/reports/fullreports/847.1.pdf)
-    // - [8] [Canadian IES-RP-8 standards for road lighting - municipality of Saint-Gedeon-de-. Beauce](http://sslnet.ca/wp-content/uploads/2011/10/LTE-RT-2011-0076-Anglais.pdf)
-    // - [9] [European standards for road lighting](http://courtneystrong.com/wp-content/uploads/2017/07/css-sl1-class-and-quality-of-street-lighting.pdf)
+    // - [5] [The NIST Reference on Constants, Units, and
+    // Uncertainty](https://physics.nist.gov/cuu/Units/units.html)
+    // - [6] [National Optical Astronomy
+    // Observatory](https://www.noao.edu/education/QLTkit/ACTIVITY_Documents/Safety/LightLevels_outdoor+indoor.pdf)
+    // - [7] [Standards for required street lighting in the
+    // USA](http://www.wsdot.wa.gov/research/reports/fullreports/847.1.pdf)
+    // - [8] [Canadian IES-RP-8 standards for road lighting - municipality of
+    // Saint-Gedeon-de-.
+    // Beauce](http://sslnet.ca/wp-content/uploads/2011/10/LTE-RT-2011-0076-Anglais.pdf)
+    // - [9] [European standards for road
+    // lighting](http://courtneystrong.com/wp-content/uploads/2017/07/css-sl1-class-and-quality-of-street-lighting.pdf)
     //
     enum AmbientIllumination
     {
@@ -194,8 +203,8 @@ message EnvironmentalConditions
         // Level 1 illumination in ]0.001, 0.01[ [lx]
         // E.g. Night with no artificial light.
         //
-        // \note Use \c #AMBIENT_ILLUMINATION_LEVEL1 if illumination is less than
-        // 0.001 [lx]
+        // \note Use \c #AMBIENT_ILLUMINATION_LEVEL1 if illumination is less
+        // than 0.001 [lx]
         //
         AMBIENT_ILLUMINATION_LEVEL1 = 2;
 
@@ -242,8 +251,8 @@ message EnvironmentalConditions
         // Level 9 illumination in [10000, 120000[ [lx]
         // E.g. Full daylight to intense sunlight.
         //
-        // \note Use \c #AMBIENT_ILLUMINATION_LEVEL9 if illumination is more than
-        // 120000 [lx]
+        // \note Use \c #AMBIENT_ILLUMINATION_LEVEL9 if illumination is more
+        // than 120000 [lx]
         //
         AMBIENT_ILLUMINATION_LEVEL9 = 10;
     }

osi_groundtruth.proto

@@ -125,7 +125,9 @@ message GroundTruth
     // Unit: []
     //
     // \par References:
-    // - [1] [International Standard ISO 3166-1: Codes for the representation of names of countries and their subdivisions - Part 1: Country codes, third ed., 2013] (https://www.iso.org/obp/ui/)
+    // - [1] [International Standard ISO 3166-1: Codes for the representation of
+    // names of countries and their subdivisions - Part 1: Country codes, third
+    // ed., 2013] (https://www.iso.org/obp/ui/)
     // - [2] [Wikipedia ISO 3166/1] (https://en.wikipedia.org/wiki/ISO_3166-1)
     //
     optional uint32 country_code = 13;

osi_lane.proto

@@ -45,7 +45,7 @@ message Lane
         // Example: \c #type = \c #TYPE_DRIVING (see reference picture)
         //
         optional Type type = 1;
-        
+
         // Indicates that the host vehicle travels on this particular lane.
         // The host vehicle may travel on more than one lane at once. This does
         // also apply for the \c CanditateLane in the \c DetectedLane .
@@ -54,21 +54,22 @@ message Lane
 
         // The lane's center line (as a list of segments).
         //
-        // This is the line, that a typical vehicle is supposed to follow. Thus, if
-        // the road narrows (e.g. at a construction site) this line is supposed to
-        // describe the trajectory that the vehicle should follow. The intended
-        // direction of travel on the lane is given by the direction defined by the
-        // sequence of points forming the center line.
+        // This is the line, that a typical vehicle is supposed to follow. Thus,
+        // if the road narrows (e.g. at a construction site) this line is
+        // supposed to describe the trajectory that the vehicle should follow.
+        // The intended direction of travel on the lane is given by the
+        // direction defined by the sequence of points forming the center line.
         //
         // \image html highway_exit.png "Center lines as yellow dotted lines."
         //
         // \attention The points describing the center line might be set at
-        // arbitrary distances. When the points are pairwise linearly connected, the
-        // lateral distance to the real ideal line (as used by the simulation
-        // environment internally) must not exceed 5cm. As shown in the following
-        // image:
+        // arbitrary distances. When the points are pairwise linearly connected,
+        // the lateral distance to the real ideal line (as used by the
+        // simulation environment internally) must not exceed 5cm. As shown in
+        // the following image:
         //
-        // \image html line_approximation_error.png "Approximation error as green line."
+        // \image html line_approximation_error.png "Approximation error as
+        // green line."
         //
         // \note The \c #centerline is defined only for \c #type =
         // \c #TYPE_DRIVING and one \c #lane_pairing pair.
@@ -78,23 +79,23 @@ message Lane
         // Definition of the intended driving direction.
         //
         // Defined and used for driving lanes.
-        // true means driving direction is according to ascending storage order of
-        // center line points.
-        // false means driving direction is according to descending storage order of
-        // center line points.
+        // true means driving direction is according to ascending storage order
+        // of center line points. false means driving direction is according to
+        // descending storage order of center line points.
         //
-        // \note The \c #centerline_is_driving_direction is defined for \c #type =
-        // \c #TYPE_DRIVING .
+        // \note The \c #centerline_is_driving_direction is defined for \c #type
+        // = \c #TYPE_DRIVING .
         //
         optional bool centerline_is_driving_direction = 4;
 
-        // List of IDs of all lane segments that are directly adjacent to the lane
-        // on the left side (w.r.t. intended driving direction). Note that lengths
-        // of lane segments are not synchronized and therefore there are multiple
-        // adjacent segments if there is a split/merge point in the adjacent lane.
+        // List of IDs of all lane segments that are directly adjacent to the
+        // lane on the left side (w.r.t. intended driving direction). Note that
+        // lengths of lane segments are not synchronized and therefore there are
+        // multiple adjacent segments if there is a split/merge point in the
+        // adjacent lane.
         //
-        // Example: The lane ID 2 is the only left adjacent lane for lane ID 3 in
-        // the reference picture.
+        // Example: The lane ID 2 is the only left adjacent lane for lane ID 3
+        // in the reference picture.
         //
         // \note The \c #left_adjacent_lane_id is undefined for \c #type =
         // \c #TYPE_INTERSECTION .
@@ -103,14 +104,14 @@ message Lane
         //
         repeated Identifier left_adjacent_lane_id = 5;
 
-        // List of IDs of all lane segments that are directly adjacent to the lane
-        // on the right side (w.r.t. intended driving direction). Note that lengths
-        // of lane segments are not synchronized and therefore there are multiple
-        // adjacent segments if there is a split/merge point in the adjacent lane.
-        // Example: The lane IDs 4 and 7 are the right adjacent lane segments for
-        // lane ID 3 in the reference picture due to the lane split. Lane ID 6 is
-        // not a right adjacent lane to lane ID 3 as they are separated by lane ID
-        // 7.
+        // List of IDs of all lane segments that are directly adjacent to the
+        // lane on the right side (w.r.t. intended driving direction). Note that
+        // lengths of lane segments are not synchronized and therefore there are
+        // multiple adjacent segments if there is a split/merge point in the
+        // adjacent lane. Example: The lane IDs 4 and 7 are the right adjacent
+        // lane segments for lane ID 3 in the reference picture due to the lane
+        // split. Lane ID 6 is not a right adjacent lane to lane ID 3 as they
+        // are separated by lane ID 7.
         //
         // \note The \c #right_adjacent_lane_id is undefined for \c #type =
         // \c #TYPE_INTERSECTION .
@@ -120,20 +121,19 @@ message Lane
         repeated Identifier right_adjacent_lane_id = 6;
 
         // The antecessor/successor lane pairings of this lane. There can be
-        // multiple pairings with the same antecessor and different successor lanes
-        // and vice versa.
-        // The antecessor lanes end in the same point that this lane starts from.
-        // The successor lanes start in the same point that this lane ends in.
-        // Example:
+        // multiple pairings with the same antecessor and different successor
+        // lanes and vice versa. The antecessor lanes end in the same point that
+        // this lane starts from. The successor lanes start in the same point
+        // that this lane ends in. Example:
         //
         // \note OSI uses singular instead of plural for repeated field names.
         //
         repeated LanePairing lane_pairing = 7;
 
-        // The right adjacent lane boundaries \c #right_lane_boundary_id may only be
-        // shared with/as the left adjacent lane boundaries
-        // \c #left_lane_boundary_id of the nearest right adjacent lane
-        // \c #right_adjacent_lane_id.
+        // The right adjacent lane boundaries \c #right_lane_boundary_id may
+        // only be shared with/as the left adjacent lane boundaries \c
+        // #left_lane_boundary_id of the nearest right adjacent lane \c
+        // #right_adjacent_lane_id.
         //
         // \note Empty for intersections.
         //
@@ -144,10 +144,10 @@ message Lane
         //
         repeated Identifier right_lane_boundary_id = 8;
 
-        // The left adjacent lane boundaries \c #left_lane_boundary_id may only be
-        // shared with/as the right adjacent lane boundaries
-        // \c #right_lane_boundary_id of the nearest left adjacent lane
-        // \c #left_adjacent_lane_id.
+        // The left adjacent lane boundaries \c #left_lane_boundary_id may only
+        // be shared with/as the right adjacent lane boundaries \c
+        // #right_lane_boundary_id of the nearest left adjacent lane \c
+        // #left_adjacent_lane_id.
         //
         // \note Empty for intersections.
         //
@@ -184,7 +184,8 @@ message Lane
             TYPE_OTHER = 1;
 
             // A normal lane.
-            // Example: lanes with IDs 1, 2, 3, 4 and 7 of the highway_exit image.
+            // Example: lanes with IDs 1, 2, 3, 4 and 7 of the highway_exit
+            // image.
             //
             TYPE_DRIVING = 2;
 
@@ -227,10 +228,10 @@ message Lane
             //
             optional double surface_ice = 4;
 
-            // The coefficient representing the roughness or unevenness of the road.
-            // International Roughness Index (IRI) [1] values range from 0 = smooth
-            // ground (equivalent to driving on a plate of glass) up to > 20 mm/m
-            // (a very rough road).
+            // The coefficient representing the roughness or unevenness of the
+            // road. International Roughness Index (IRI) [1] values range from 0
+            // = smooth ground (equivalent to driving on a plate of glass) up to
+            // > 20 mm/m (a very rough road).
             //
             // Estimated value ranges (IRI):
             //        0.0 [mm/m] absolutely perfect evenness
@@ -265,9 +266,10 @@ message Lane
             // The surface texture or fine roughness
             //
             // Whereas the IRI-based roughness or unevenness measure only takes
-            // into account road wavelengths around 0.5m - 100m, the surface texture
-            // or fine roughness [2] measures only wavelengths below 0.5m.
-            // It is given as the standard height deviation of fine roughness
+            // into account road wavelengths around 0.5m - 100m, the surface
+            // texture or fine roughness [2] measures only wavelengths below
+            // 0.5m. It is given as the standard height deviation of fine
+            // roughness
             //
             // Unit: [m]
             //
@@ -315,13 +317,13 @@ message LaneBoundary
     // Since a \c BoundaryPoint is part of a sequence, only the position
     // attribute has to be set for each instance. All other values will be
     // reused from the previous \c BoundaryPoint in the sequence or set to
-    // default values if there is none or it was never set. 
+    // default values if there is none or it was never set.
     //
     // \note For dashed lines, one \c BoundaryPoint has to be at the start and
-    // another at the end of each dashed line segment. The first 
+    // another at the end of each dashed line segment. The first
     // \c BoundaryPoint defines the beginning of the first dashed lane marking.
-    // The last \c BoundaryPoint defines the end of the last dashed lane 
-    // marking. For example, the area between the second and third 
+    // The last \c BoundaryPoint defines the end of the last dashed lane
+    // marking. For example, the area between the second and third
     // \c BoundaryPoint has no lane marking, and so on.
     // \note For Botts' dots lines, one \c BoundaryPoint position has to define
     // each Botts' dot.
@@ -383,9 +385,9 @@ message LaneBoundary
         repeated Identifier limiting_structure_id = 3;
 
         // The lane boundary type.
-        // There is no special representation for double lines, e.g. solid / solid
-        // or dashed / solid. In such cases, each lane will define its own side of
-        // the lane boundary.
+        // There is no special representation for double lines, e.g. solid /
+        // solid or dashed / solid. In such cases, each lane will define its own
+        // side of the lane boundary.
         //
         enum Type
         {
@@ -451,21 +453,22 @@ message LaneBoundary
         }
 
         // The color of the lane boundary in case of a lane markings.
-        // Lane markings that alternate in color must be represented by individual
-        // \c LaneBoundary segments.
+        // Lane markings that alternate in color must be represented by
+        // individual \c LaneBoundary segments.
         //
         enum Color
         {
-            // Color of marking is unknown. Value must not be used in ground truth.
+            // Color of marking is unknown. Value must not be used in ground
+            // truth.
             //
             COLOR_UNKNOWN = 0;
 
             // Other (unspecified but known) color.
             //
             COLOR_OTHER = 1;
 
-            // Marking without color. Used to represent logical boundaries without
-            // actual physical markings at the respective position.
+            // Marking without color. Used to represent logical boundaries
+            // without actual physical markings at the respective position.
             // Value may be used in ground truth only.
             //
             COLOR_NONE = 2;

osi_occupant.proto

@@ -106,11 +106,11 @@ message Occupant
             //
             STEERING_CONTROL_NO_HAND = 2;
 
-            // One hand is on the steering wheel. Whether it is the left or right
-            // hand is unspecified or unknown.
+            // One hand is on the steering wheel. Whether it is the left or
+            // right hand is unspecified or unknown.
             //
-            // \note If there is no differentiation between one or both hands on the
-            // steering wheel, this value should be used.
+            // \note If there is no differentiation between one or both hands on
+            // the steering wheel, this value should be used.
             //
             STEERING_CONTROL_ONE_HAND = 3;