Struct TrafficSign::SupplementarySign¶

Defined in File osi_trafficsign.proto

Nested Relationships¶

This struct is a nested type of Struct TrafficSign.

Nested Types¶

Struct Documentation¶

struct SupplementarySign

Additional supplementary sign modifying the main sign.

../_images/OSI_SupplementarySign.svg

Public Members

optional BaseStationary osi3::TrafficSign::SupplementarySign::base = 1

The base parameters of the supplementary traffic sign.

The orientation of the bounding box SupplementarySign::base ( BaseStationary::orientation ) is defined as follows: The z-axis of the given BaseStationary::orientation is the vector from the bottom to the top of the supplementary traffic sign’s 2D image plate. (Normally it is equal to the ground truth z-axis.) The x-axis of the given BaseStationary::orientation is view normal of the supplementary traffic sign’s image. This x-axis points from the supplementary traffic sign’s image in the direction from where a ‘viewer’ could see the supplementary traffic sign image.

optional Classification osi3::TrafficSign::SupplementarySign::classification = 2: The classification of the supplementary traffic sign.

struct Classification

Classification data for a supplementary traffic sign.

When constructing a SupplementarySign, consider the use of the following members:

In order to include numerical values indicated in the sign, use TrafficSignValue::value. Accompany this value with an indication of its unit of measure given by TrafficSignValue::value_unit.
In order to include strings of text indicated in the sign, use TrafficSignValue::text. The interpretation of this text is left to a user-defined procedure.

Note: The definition of the sign types is thought to be independent of the country, even if the images used in this documentation are based on the German Road Traffic Regulations (StVO).

Public Types

enum Type¶

Definition of supplementary sign types.

For general supplementary signs use TYPE_TEXT. Supplementary signs with general space restrictions use TYPE_SPACE. Supplementary signs with general time restrictions use TYPE_TIME. Supplementary signs with displayed arrow directions use TYPE_ARROW. Supplementary signs constraint to one type of actors use TYPE_CONSTRAINED_TO. Supplementary signs that will exclude one type of actors use TYPE_EXCEPT. If supplementary signs combine contraints, restrictions, or plain text, Type is used in descending order in the following sequence: TYPE_EXCEPT, TYPE_CONSTRAINED_TO, TYPE_ARROW, TYPE_TIME, TYPE_SPACE, TYPE_TEXT.

Values:

TYPE_UNKNOWN = 0¶: Type of supplementary sign is unknown (must not be used in ground truth).

TYPE_OTHER = 1¶: Other (unspecified but known) type of supplementary sign.

TYPE_NO_SIGN = 2¶: There is no supplementary sign (must not be used in ground truth).

TYPE_TEXT = 41¶

Text sign.

Use it as a canvas for text-only signs:

Use TrafficSignValue::value to indicate a numerical value indicated on the sign. Accompany this value with an indication of its unit of measure given by TrafficSignValue::value_unit.
Use TrafficSignValue::text to indicate a string of text indicated on the sign.

The following table summarizes possible configurations for this kind of supplementary signs:

TYPE_SPACE = 39¶

Text sign with distance indication.

Use it as a canvas for text signs that make reference to a point or area in space:

Use TrafficSignValue::value to include the distance indicated in the sign. Accompany this value with an indication of its unit of measure given by TrafficSignValue::value_unit (e.g. [m]),
Use TrafficSignValue::text to indicate the sign’s specific text,

The following table summarizes possible configurations for this kind of supplementary signs:

TYPE_TIME = 26¶

Text sign with time indication.

Use it as a canvas for text signs that make: reference to a point in time or a time range.

Use one or more TrafficSignValue messages to include the times indicated in the sign. Accompany each value with an indication of its unit of measure given by TrafficSignValue::value_unit, e.g. [h].
For each TrafficSignValue, TrafficSignValue::value indicates the time elapsed since midnight every day.
Use the TrafficSignValue::text member of the first TrafficSignValue message to indicate the sign’s specific text.

The following table summarizes possible configurations for this kind of supplementary signs:

Note

Time interval need two TrafficSignValue messages, one to indicate their start and one to indicate their end.
In case more than one time range is required, the TrafficSignValue::value member of the first TrafficSignValue message is interpreted as the beginning of the first interval, the TrafficSignValue::value member of the second TrafficSignValue message is interpreted as the end of the first interval, and so on.

TYPE_ARROW = 30¶

A supplementary sign showing a direction alone.

Use together with the message

Classification::arrow. The following signs can be built:

TYPE_CONSTRAINED_TO = 46¶

The list of traffic actors to which the main sign’s regulation is constrained to.

Use as many members of the

Actor enumerator as needed to denote the related traffic actors.

The following tables summarize possible configurations for this kind of supplementary signs:

Also, some of the German StVO traffic signs denoting traffic actors for which the main sign’s regulation applies exclusively can be constructed.

Note: In the German StVO, these signs typically include the word “Nur”.

In addition, some of the German StVO supplementary signs with actors that receive an explicit allowance to use the street or the shoulder can be constructed:

Finally, the signs

can be incorporated.

TYPE_EXCEPT = 45¶

The list of traffic actors for which the main sign’s regulation does not apply or have a special driving allowance.

Use as many members of the

Actor enumerator as needed to denote the excepted traffic actors:

The following table summarizes possible configurations for this kind of supplementary signs:

Note: In the German StVO, these signs include the word “frei”.

TYPE_VALID_FOR_DISTANCE = 3¶

Traffic sign is valid for a certain distance.

Use TrafficSignValue::value and TrafficSignValue::value_unit (e.g. [m]) to indicate the distance.

TYPE_PRIORITY_ROAD_BOTTOM_LEFT_FOUR_WAY = 27¶: Priority road from bottom to left in the intersection.

TYPE_PRIORITY_ROAD_TOP_LEFT_FOUR_WAY = 28¶: Priority road from top to left in the intersection.

TYPE_PRIORITY_ROAD_BOTTOM_LEFT_THREE_WAY_STRAIGHT = 32¶: Priority road from bottom to left, junction from above.

TYPE_PRIORITY_ROAD_BOTTOM_LEFT_THREE_WAY_SIDEWAYS = 33¶: Priority road from bottom to left, junction from the right.

TYPE_PRIORITY_ROAD_TOP_LEFT_THREE_WAY_STRAIGHT = 34¶: Priority road from top to left, junction from below.

TYPE_PRIORITY_ROAD_BOTTOM_RIGHT_FOUR_WAY = 29¶: Priority road from bottom to right in the intersection.

TYPE_PRIORITY_ROAD_TOP_RIGHT_FOUR_WAY = 31¶: Priority road from top to right in the intersection.

TYPE_PRIORITY_ROAD_BOTTOM_RIGHT_THREE_WAY_STRAIGHT = 35¶: Priority road from bottom to right, junction from above.

TYPE_PRIORITY_ROAD_BOTTOM_RIGHT_THREE_WAY_SIDEWAY = 36¶: Priority road from bottom to right, junction from the left.

TYPE_PRIORITY_ROAD_TOP_RIGHT_THREE_WAY_STRAIGHT = 37¶: Priority road from top to right, junction from below.

TYPE_VALID_IN_DISTANCE = 4¶

Distance to the start of validity of the traffic sign.

Use TrafficSignValue::value and TrafficSignValue::value_unit (e.g. [m]) to indicate the distance.

Note: For OSI 4.0 compatibility use TYPE_SPACE instead.

TYPE_STOP_IN = 25¶

Stop in e.g. .. [m].

Use TrafficSignValue::value and TrafficSignValue::value_unit (e.g. [m]) to indicate the distance.

Note: For OSI 4.0 compatibility use TYPE_SPACE instead.

TYPE_LEFT_ARROW = 11¶

Direction, left-pointing.

Note: For OSI 4.0 compatibility use TYPE_ARROW instead.

TYPE_LEFT_BEND_ARROW = 13¶

Direction of potential danger, left-pointing.

Note: For OSI 4.0 compatibility use TYPE_ARROW instead.

TYPE_RIGHT_ARROW = 12¶

Direction, right-pointing.

Note: For OSI 4.0 compatibility use TYPE_ARROW instead.

TYPE_RIGHT_BEND_ARROW = 14¶

Direction of potential danger, right-pointing.

Note: For OSI 4.0 compatibility use TYPE_ARROW instead.

TYPE_ACCIDENT = 40¶

Accident hazard.