plexus-python-pulse-common 1.1.75__py3-none-any.whl

plexus/pulse/common/resources/tags/universal-1.0.0.tagset.yaml

@@ -0,0 +1,1390 @@
+$namespace: "universal"
+$version: "1.0.0"
+# language=markdown
+$desc: !markdown |
+  **Universal Tagset**
+  
+  Universal tags applicable across various scenarios, environments, and data types. This tagset provides a common
+  vocabulary for describing key attributes of roadway scenes, traffic conditions, environmental factors, and data
+  quality issues relevant to autonomous driving and advanced driver-assistance systems (ADAS). The tags are organized
+  into categories such as environment, roadway, traffic, and data fidelity, with detailed subcategories to capture
+  specific conditions and characteristics. Each tag includes a description to clarify its meaning and intended use,
+  supporting consistent annotation, analysis, and communication across datasets and applications.
+$def:
+  camera_views:
+    &camera_views
+    unified:
+      # language=markdown
+      $desc: !markdown |
+        **Unified Camera View**
+        
+        A camera view that combines the fields of view from multiple cameras into a single, cohesive perspective. This
+        view is often used in perception systems to provide a comprehensive understanding of the environment by
+        integrating data from front, side, and rear cameras. The unified camera view can enhance object detection,
+        tracking, and scene understanding by providing a more complete visual representation of the surroundings.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_center:
+      # language=markdown
+      $desc: !markdown |
+        **Front Center Camera View**
+        
+        A camera view that captures the area directly in front of the vehicle, typically aligned with the center of the
+        front bumper. This view is crucial for detecting and tracking objects such as vehicles, pedestrians, and
+        traffic signs in the path of travel. The front center camera provides critical information for lane keeping,
+        adaptive cruise control, and collision avoidance systems.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_left:
+      # language=markdown
+      $desc: !markdown |
+        **Front Left Camera View**
+        
+        A camera view that captures the area to the front left of the vehicle, typically covering the left lane and
+        adjacent areas. This view is important for monitoring traffic in the left lane, detecting pedestrians or
+        cyclists approaching from the left, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_right:
+      # language=markdown
+      $desc: !markdown |
+        **Front Right Camera View**
+        
+        A camera view that captures the area to the front right of the vehicle, typically covering the right lane and
+        adjacent areas. This view is important for monitoring traffic in the right lane, detecting pedestrians or
+        cyclists approaching from the right, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    side_left:
+      # language=markdown
+      $desc: !markdown |
+        **Side Left Camera View**
+        
+        A camera view that captures the area directly to the left of the vehicle, typically covering the left side of
+        the roadway and adjacent areas. This view is important for monitoring traffic in the left lane, detecting
+        pedestrians or cyclists approaching from the left, and providing situational awareness for lane changes and
+        turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    side_right:
+      # language=markdown
+      $desc: !markdown |
+        **Side Right Camera View**
+        
+        A camera view that captures the area directly to the right of the vehicle, typically covering the right side
+        of the roadway and adjacent areas. This view is important for monitoring traffic in the right lane, detecting
+        pedestrians or cyclists approaching from the right, and providing situational awareness for lane changes and
+        turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    rear_left:
+      # language=markdown
+      $desc: !markdown |
+        **Rear Left Camera View**
+        
+        A camera view that captures the area to the rear left of the vehicle, typically covering the left rear lane
+        and adjacent areas. This view is important for monitoring traffic behind the vehicle, detecting pedestrians or
+        cyclists approaching from the rear left, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    rear_right:
+      # language=markdown
+      $desc: !markdown |
+        **Rear Right Camera View**
+        
+        A camera view that captures the area to the rear right of the vehicle, typically covering the right rear lane
+        and adjacent areas. This view is important for monitoring traffic behind the vehicle, detecting pedestrians or
+        cyclists approaching from the rear right, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+  radar_views:
+    &radar_views
+    unified:
+      # language=markdown
+      $desc: !markdown |
+        **Unified Radar View**
+        
+        A radar view that combines the data from multiple radar sensors into a single, cohesive perspective. This view
+        is often used in perception systems to provide a comprehensive understanding of the environment by integrating
+        data from front, side, and rear radars. The unified radar view can enhance object detection, tracking, and
+        scene understanding by providing a more complete representation of the surroundings, especially in adverse
+        weather conditions where cameras may be less effective.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    bumper_center:
+      # language=markdown
+      $desc: !markdown |
+        **Bumper Center Radar View**
+        
+        A radar view that captures the area directly in front of the vehicle, typically aligned with the center of the
+        front bumper. This view is crucial for detecting and tracking objects such as vehicles, pedestrians, and
+        traffic signs in the path of travel. The bumper center radar provides critical information for adaptive cruise
+        control, collision avoidance systems, and low-speed maneuvering.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    bumper_left:
+      # language=markdown
+      $desc: !markdown |
+        **Bumper Left Radar View**
+        
+        A radar view that captures the area to the front left of the vehicle, typically covering the left lane and
+        adjacent areas. This view is important for monitoring traffic in the left lane, detecting pedestrians or
+        cyclists approaching from the left, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    bumper_right:
+      # language=markdown
+      $desc: !markdown |
+        **Bumper Right Radar View**
+        
+        A radar view that captures the area to the front right of the vehicle, typically covering the right lane and
+        adjacent areas. This view is important for monitoring traffic in the right lane, detecting pedestrians or
+        cyclists approaching from the right, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+  lidar_views:
+    &lidar_views
+    unified:
+      # language=markdown
+      $desc: !markdown |
+        **Unified LiDAR View**
+        
+        A LiDAR view that combines the point cloud data from multiple LiDAR sensors into a single, cohesive
+        perspective. This view is often used in perception systems to provide a comprehensive understanding of the
+        environment by integrating data from front, side, and rear LiDAR sensors. The unified LiDAR view can enhance
+        object detection, tracking, and scene understanding by providing a more complete representation of the
+        surroundings, especially in low-light or adverse weather conditions where cameras may be less effective.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_center:
+      # language=markdown
+      $desc: !markdown |
+        **Front Center LiDAR View**
+        
+        A LiDAR view that captures the area directly in front of the vehicle, typically aligned with the center of the
+        front bumper. This view is crucial for detecting and tracking objects such as vehicles, pedestrians, and
+        traffic signs in the path of travel. The front center LiDAR provides critical information for lane keeping,
+        adaptive cruise control, and collision avoidance systems.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_left:
+      # language=markdown
+      $desc: !markdown |
+        **Front Left LiDAR View**
+        
+        A LiDAR view that captures the area to the front left of the vehicle, typically covering the left lane and
+        adjacent areas. This view is important for monitoring traffic in the left lane, detecting pedestrians or
+        cyclists approaching from the left, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    front_right:
+      # language=markdown
+      $desc: !markdown |
+        **Front Right LiDAR View**
+        
+        A LiDAR view that captures the area to the front right of the vehicle, typically covering the right lane and
+        adjacent areas. This view is important for monitoring traffic in the right lane, detecting pedestrians or
+        cyclists approaching from the right, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    side_left:
+      # language=markdown
+      $desc: !markdown |
+        **Side Left LiDAR View**
+        
+        A LiDAR view that captures the area directly to the left of the vehicle, typically covering the left side of
+        the roadway and adjacent areas. This view is important for monitoring traffic in the left lane, detecting
+        pedestrians or cyclists approaching from the left, and providing situational awareness for lane changes and
+        turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    side_right:
+      # language=markdown
+      $desc: !markdown |
+        **Side Right LiDAR View**
+        
+        A LiDAR view that captures the area directly to the right of the vehicle, typically covering the right side of
+        the roadway and adjacent areas. This view is important for monitoring traffic in the right lane, detecting
+        pedestrians or cyclists approaching from the right, and providing situational awareness for lane changes and
+        turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    rear_left:
+      # language=markdown
+      $desc: !markdown |
+        **Rear Left LiDAR View**
+        
+        A LiDAR view that captures the area to the rear left of the vehicle, typically covering the left rear lane
+        and adjacent areas. This view is important for monitoring traffic behind the vehicle, detecting pedestrians or
+        cyclists approaching from the rear left, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+    rear_right:
+      # language=markdown
+      $desc: !markdown |
+        **Rear Right LiDAR View**
+        
+        A LiDAR view that captures the area to the rear right of the vehicle, typically covering the right rear lane
+        and adjacent areas. This view is important for monitoring traffic behind the vehicle, detecting pedestrians or
+        cyclists approaching from the rear right, and providing situational awareness for lane changes and turns.
+        
+        Examples:
+        
+        - [Case 1](https://image-search.plexus.ai/particular_case_image)
+        - [Case 2](https://image-search.plexus.ai/particular_case_image)
+$tags:
+  environment:
+    # language=markdown
+    $desc: !markdown |
+      Environmental conditions that affect the roadway scene, traffic behavior, and sensor performance. This category
+      includes factors such as time of day, weather, visibility, obstructions, lighting conditions, and road surface
+      state. Each tag captures specific conditions that can impact vehicle perception, decision-making, and control,
+      providing critical context for data annotation and scenario analysis.
+    tod:
+      # language=markdown
+      $desc: !markdown |
+        Time of day categories that describe the lighting conditions and typical traffic patterns associated with
+        different periods. These tags help capture the temporal context of a scene, which can influence visibility,
+        driver behavior, and sensor performance. For example, dawn and dusk often present unique challenges due to
+        low-angle sunlight and changing light conditions, while nighttime typically involves reduced visibility and
+        increased reliance on artificial lighting.
+      dawn: { $desc: "dawn" }
+      daytime: { $desc: "daytime" }
+      dusk: { $desc: "dusk" }
+      nighttime: { $desc: "nighttime" }
+      unknown: { $desc: "unknown" }
+    weather:
+      # language=markdown
+      $desc: !markdown |
+        Weather conditions that can affect driving safety, vehicle dynamics, and sensor performance. These tags capture
+        specific weather phenomena that may be present in a scene, such as precipitation, fog, or cloud cover. Each
+        condition has unique implications for visibility, road surface state, and driver behavior, making them important
+        for scenario analysis and data annotation. For example, rain can reduce tire traction and cause glare, while fog
+        can significantly impair visibility.
+      cloudy: { $desc: "cloudy" }
+      foggy: { $desc: "foggy" }
+      rainy: { $desc: "rainy" }
+      snowy: { $desc: "snowy" }
+      unknown: { $desc: "unknown" }
+    visibility:
+      # language=markdown
+      $desc: !markdown |
+        Visibility conditions that describe the clarity of the environment and the distance at which objects can be
+        detected. These tags capture the level of visibility, which can be affected by weather conditions, lighting,
+        and obstructions. High visibility allows for better perception and safer driving conditions, while low
+        visibility can increase the risk of accidents and require more cautious behavior.
+      high: { $desc: "high" }
+      moderate: { $desc: "moderate" }
+      low: { $desc: "low" }
+      unknown: { $desc: "unknown" }
+    obstructions:
+      # language=markdown
+      $desc: !markdown |
+        Environmental obstructions that can block or obscure the view of the roadway, traffic, or surroundings. These
+        tags capture specific types of obstructions that may be present in a scene, such as fog, smoke, dust, or
+        precipitation. Each type of obstruction has unique implications for visibility and sensor performance, making
+        them important for scenario analysis and data annotation.
+      fog:
+        # language=markdown
+        $desc: !markdown |
+          **Fog**
+          
+          A weather condition characterized by a thick cloud of tiny water droplets suspended in the air near the
+          ground, significantly reducing visibility. Fog can create hazardous driving conditions by obscuring the view
+          of the road, other vehicles, pedestrians, and traffic signs. Drivers may need to use fog lights, reduce
+          speed, and increase following distance to navigate safely in foggy conditions. Sensor performance may also be
+          affected, requiring adjustments to maintain detection and tracking capabilities.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      smoke:
+        # language=markdown
+        $desc: !markdown |
+          **Smoke**
+          
+          A visible suspension of carbon or other particles in the air, typically produced by fire, industrial
+          processes, or vehicle emissions. Smoke can significantly reduce visibility and create hazardous driving
+          conditions by obscuring the view of the road, other vehicles, pedestrians, and traffic signs. Drivers may need
+          to reduce speed, increase following distance, and use headlights to navigate safely in smoky conditions.
+          Sensor performance may also be affected, requiring adjustments to maintain detection and tracking
+          capabilities.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      dust:
+        # language=markdown
+        $desc: !markdown |
+          **Dust**
+          
+          Fine particles of matter suspended in the air, often generated by dry conditions, construction activities,
+          or unpaved roads. Dust can reduce visibility and create hazardous driving conditions by obscuring the view of
+          the road, other vehicles, pedestrians, and traffic signs. Drivers may need to reduce speed, increase
+          following distance, and use headlights to navigate safely in dusty conditions. Sensor performance may also be
+          affected, requiring adjustments to maintain detection and tracking capabilities.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      snowfall:
+        # language=markdown
+        $desc: !markdown |
+          **Snowfall**
+          
+          A weather condition characterized by the falling of snowflakes from the sky, which can accumulate on the
+          ground and create hazardous driving conditions. Snowfall can reduce visibility, obscure road markings, and
+          create slippery surfaces, increasing the risk of accidents. Drivers may need to use headlights, reduce speed,
+          and increase following distance to navigate safely in snowy conditions. Sensor performance may also be
+          affected, requiring adjustments to maintain detection and tracking capabilities.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      rainfall:
+        # language=markdown
+        $desc: !markdown |
+          **Rainfall**
+          
+          A weather condition characterized by the falling of water droplets from the sky, which can create hazardous
+          driving conditions. Rainfall can reduce visibility, create slippery surfaces, and cause glare, increasing the
+          risk of accidents. Drivers may need to use headlights, reduce speed, and increase following distance to
+          navigate safely in rainy conditions. Sensor performance may also be affected, requiring adjustments to
+          maintain detection and tracking capabilities.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    lighting:
+      # language=markdown
+      $desc: !markdown |
+        Lighting conditions that describe the level and quality of ambient light in the environment. These tags
+        capture specific lighting conditions that can affect visibility, perception, and driver behavior. For example,
+        glare from the sun or artificial sources can create temporary blindness, while shadows can obscure objects on
+        the roadway. Understanding lighting conditions is crucial for accurate data annotation and scenario analysis.
+      normal: { $desc: "normal ambient lighting" }
+      low_light:
+        # language=markdown
+        $desc: !markdown |
+          **Low Light**
+          
+          Ambient lighting conditions that are significantly dimmer than normal, often occurring during dawn, dusk, or
+          nighttime. Low light conditions can reduce visibility and make it more difficult for drivers and sensors to
+          detect objects, read signs, and navigate safely. Drivers may need to use headlights and exercise increased
+          caution, while sensors may require adjustments to maintain performance.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      glare:
+        # language=markdown
+        $desc: !markdown |
+          Glare conditions caused by direct sunlight or bright artificial light sources that can impair visibility and
+          create temporary blindness for drivers. Glare can occur when the sun is low on the horizon during dawn or
+          dusk, or when headlights from oncoming traffic are particularly bright. Drivers may need to use sun visors,
+          adjust their position, or slow down to mitigate the effects of glare, while sensors may require adjustments to
+          maintain performance.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      shadows:
+        # language=markdown
+        $desc: !markdown |
+          Shadow conditions caused by objects such as buildings, trees, or other vehicles that can create areas of
+          reduced visibility on the roadway. Shadows can obscure objects, pedestrians, or road markings, making it more
+          difficult for drivers and sensors to detect and navigate safely. Drivers may need to exercise increased
+          caution when driving through areas with significant shadows, while sensors may require adjustments to maintain
+          performance.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    road_surface:
+      # language=markdown
+      $desc: !markdown |
+        Road surface conditions that affect vehicle dynamics, traction, and safety. These tags capture specific states
+        of the roadway surface, such as being dry, wet, icy, or covered in snow or slush. Each condition has unique
+        implications for driving behavior and sensor performance, making them important for scenario analysis and data
+        annotation. For example, icy conditions can significantly reduce traction and increase stopping distances, while
+        wet surfaces can lead to hydroplaning.
+      dry: { $desc: "dry" }
+      wet: { $desc: "wet" }
+      standing_water:
+        # language=markdown
+        $desc: !markdown |
+          **Standing Water**
+          
+          A condition where water has accumulated on the roadway surface, creating a hazard for vehicles. Standing water
+          can lead to hydroplaning, where tires lose contact with the road and skid uncontrollably. Drivers may need to
+          reduce speed and avoid sudden maneuvers when driving through standing water, while sensors may require
+          adjustments to maintain performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      icy:
+        # language=markdown
+        $desc: !markdown |
+          **Icy**
+          
+          A condition where the roadway surface is covered with a layer of ice, significantly reducing traction and
+          increasing the risk of accidents. Icy conditions can occur due to freezing rain, melting snow refreezing,
+          or cold temperatures causing moisture to freeze on the road. Drivers may need to reduce speed, increase
+          following distance, and avoid sudden maneuvers when driving on icy roads, while sensors may require
+          adjustments to maintain performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      snow_covered:
+        # language=markdown
+        $desc: !markdown |
+          **Snow Covered**
+          
+          A condition where the roadway surface is covered with a layer of snow, which can reduce traction, obscure road
+          markings, and create hazardous driving conditions. Snow-covered roads can lead to increased stopping
+          distances and a higher risk of accidents. Drivers may need to use headlights, reduce speed, and increase
+          following distance when driving on snow-covered roads, while sensors may require adjustments to maintain
+          performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      slush:
+        # language=markdown
+        $desc: !markdown |
+          **Slush**
+          
+          A condition where the roadway surface is covered with a mixture of snow and water, creating a slippery and
+          hazardous driving environment. Slushy conditions can occur during melting snow or when rain falls on snow,
+          leading to reduced traction and increased stopping distances. Drivers may need to use headlights, reduce
+          speed, and increase following distance when driving on slushy roads, while sensors may require adjustments to
+          maintain performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      gravel:
+        # language=markdown
+        $desc: !markdown |
+          **Gravel**
+          
+          A condition where the roadway surface is covered with loose gravel, which can reduce traction and create
+          hazardous driving conditions. Gravel roads can lead to increased stopping distances and a higher risk of
+          accidents, especially at higher speeds. Drivers may need to reduce speed and exercise caution when driving on
+          gravel roads, while sensors may require adjustments to maintain performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      contaminated:
+        # language=markdown
+        $desc: !markdown |
+          **Contaminated**
+          
+          A condition where the roadway surface is covered with substances such as oil, mud, or debris that can reduce
+          traction and create hazardous driving conditions. Contaminated roads can lead to increased stopping distances
+          and a higher risk of accidents. Drivers may need to reduce speed and exercise caution when driving on
+          contaminated roads, while sensors may require adjustments to maintain performance in these conditions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+  roadway:
+    # language=markdown
+    $desc: !markdown |
+      Roadway characteristics that describe the physical and functional attributes of the road environment. This
+      category includes factors such as road type/classification, layout, lane configuration, shoulder type, junction
+      type, infrastructure features, and geometric characteristics. Each tag captures specific attributes of the roadway
+      that can influence driving behavior, vehicle dynamics, and sensor performance, making them important for scenario
+      analysis and data annotation. For example, an expressway typically has high speeds and limited access points,
+      while a residential street may have low speeds and frequent pedestrian activity.
+    classification:
+      # language=markdown
+      $desc: !markdown |
+        Roadway classifications that describe the functional category of the road based on its design, purpose, and
+        typical traffic patterns. These tags capture specific types of roadways, such as expressways, highways,
+        arterials, collectors, residential streets, rural roads, unpaved roads, service roads, and parking lots. Each
+        classification has unique characteristics that influence driving behavior, vehicle dynamics, and sensor
+        performance, making them important for scenario analysis and data annotation. For example, expressways are
+        designed for high-speed, long-distance travel with limited access points, while residential streets are designed
+        for low-speed local traffic with frequent pedestrian activity.
+      expressway:
+        # language=markdown
+        $desc: !markdown |
+          **Expressway**
+          
+          A high-capacity, controlled-access roadway designed primarily for through traffic, typically features multiple
+          lanes in each direction, no at-grade intersections, grade-separated interchanges, and limited or no direct
+          property access; typical design speeds are high (often 55–75 mph / 90–120 km/h or greater depending on
+          region). Engineering emphasizes high throughput, long sight distances, and safety features such as wide
+          medians, clear zones, and crash barriers. Pedestrian, bicycle, and local-access interactions are minimized;
+          ramps and merge/diverge areas create characteristic conflict zones that matter for routing and sensor
+          coverage. In perception and mapping contexts, expect long straight segments, frequent guardrails, overhead
+          signage, and predictable lane geometry but high relative speeds that can complicate detection and tracking.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      highway:
+        # language=markdown
+        $desc: !markdown |
+          **Highway**
+          
+          A major public road connecting cities and regions; may be partially controlled-access but often includes
+          at-grade intersections and property access in places. Speeds are generally high but lower than expressways in
+          built-up sections; lanes can vary from two to multiple per direction with paved shoulders and marked
+          centers/medians. Design balances mobility with broader connectivity, so you’ll see intersections, ramps, rest
+          areas, and a mix of signage and turn lanes. For sensors and scene understanding this class introduces more
+          interaction points (turns, intersections, merging) and more variable roadside features (businesses, driveways,
+          variable shoulder conditions).
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      arterial:
+        # language=markdown
+        $desc: !markdown |
+          **Arterial**
+          
+          An urban or suburban road intended to carry moderate-to-high volumes of traffic between collectors and
+          highways. Typically signalized at intersections, with multiple lanes, dedicated turn lanes, and frequent
+          access points to commercial and institutional properties. Speeds are moderate (commonly 30–50 mph / 50–80
+          km/h) and the environment includes dense curbside activity (parked vehicles, crosswalks, transit stops).
+          Arterials require handling of frequent stopping/starting, complex intersection geometry, and mixed road users;
+          mapping should capture turn lanes, signal phases, and curb cuts to support routing and behavior prediction.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      collector:
+        # language=markdown
+        $desc: !markdown |
+          **Collector**
+          
+          A roadway class that gathers traffic from local/residential streets and funnels it to arterials or highways.
+          Collectors balance mobility and property access: lower speeds than arterials, fewer lanes, and more direct
+          driveway connections. Typical features include moderate spacing of intersections, parking in some segments,
+          and occasional pedestrian facilities. For data annotation and planning, collectors often exhibit heterogeneous
+          geometry, variable roadside clutter, and transitional traffic patterns (local access trips mixed with through
+          movements).
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      residential:
+        # language=markdown
+        $desc: !markdown |
+          **Residential Street**
+          
+          Low-speed local streets primarily serving housing areas, fronting private driveways, sidewalks, and frequent
+          pedestrian activity. Characteristics include narrow lanes, on-street parking, traffic-calming measures (speed
+          humps, curb bulbs), and many short local trips with turning movements. Sightlines can be limited by parked
+          cars, landscaping, and driveways; expect high pedestrian and cyclist presence, variable lighting, and numerous
+          occlusions—important for fine-grained perception and safety-critical behavior modeling.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      rural:
+        # language=markdown
+        $desc: !markdown |
+          **Rural Road**
+          
+          Roadways located in non-urban areas with low development density; may be two-lane undivided roads with
+          intermittent shoulders and limited lighting. Speeds can be moderate to high, but geometry is frequently
+          constrained (narrow lanes, sharp curves, grade changes) and roadside hazards (ditches, trees, wildlife) are
+          common. Pavement condition and signage vary widely; environmental factors like limited markings, fog, and
+          seasonal surface changes matter for sensor robustness and vehicle control.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unpaved:
+        # language=markdown
+        $desc: !markdown |
+          **Unpaved Road**
+          
+          Non-paved surfaces such as gravel, dirt, or stabilized earth that significantly affect vehicle dynamics and
+          sensing. Characteristics include reduced traction, dust or loose material generation, variable rutting and
+          washboarding, and often narrower or poorly defined lane boundaries. Vehicle speed and maneuverability are
+          constrained; perception systems must handle dust occlusion, sparse lane markings, and variable reflectivity.
+          Maintenance variability leads to frequent geometry changes and atypical object placements (puddles, rocks,
+          vegetation).
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      service_road:
+        # language=markdown
+        $desc: !markdown |
+          **Service Road**
+          
+          A low-speed road providing direct access to properties, businesses, or buildings adjacent to a higher-class
+          roadway (sometimes called a frontage road). Designed to separate local access movements from through traffic
+          on the main corridor, service roads feature frequent driveways, parking access, and conflict points where
+          vehicles enter/exit. They often have complex interactions with pedestrian flow, parked vehicles, and delivery
+          activities—important for close-range perception, low-speed maneuver planning, and understanding localized
+          occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      parking_lot:
+        # language=markdown
+        $desc: !markdown |
+          **Parking Lot**
+          
+          Areas used for vehicle parking, loading/unloading, and short-term staging, including surface lots and
+          multi-level garages. Environment is highly unstructured compared to public roads: irregular lanes, variable
+          markings, numerous static obstacles (curbs, bollards, light poles), and dense pedestrian movement. Speeds are
+          very low but interactions are frequent and unpredictable (reversing, double-parking, pedestrians crossing
+          between aisles). Mapping and perception must capture fine detail (parking stall boundaries, curb ramps,
+          signage) and support tight maneuvering and short-range obstacle detection.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    layout:
+      # language=markdown
+      $desc: !markdown |
+        Roadway layout types that describe the overall configuration of the road and its lanes. These tags capture
+        specific layout types such as single way, undivided two-way, divided two-way, and unknown. Each layout type has
+        unique implications for traffic flow, driver behavior, and sensor coverage, making them important for scenario
+        analysis and data annotation. For example, a single way layout typically involves one lane of traffic in each
+        direction with no physical separation, while a divided two-way layout includes a physical barrier or median
+        separating opposing traffic flows.
+      single_way:
+        # language=markdown
+        $desc: !markdown |
+          **Single Way Layout**
+          
+          A roadway configuration where traffic flows in both directions without any physical separation, such as a
+          centerline or median. This layout typically involves one lane of traffic in each direction, and drivers must
+          exercise caution when passing or making turns due to the potential for head-on collisions. Sensor coverage
+          may be more challenging in single way layouts due to the lack of clear lane boundaries and the presence of
+          oncoming traffic.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      undivided_two_way:
+        # language=markdown
+        $desc: !markdown |
+          **Undivided Two Way Layout**
+          
+          A roadway configuration where traffic flows in both directions with a painted centerline but no physical
+          separation, such as a median or barrier. This layout typically involves one lane of traffic in each direction,
+          and drivers must exercise caution when passing or making turns due to the potential for head-on collisions.
+          Sensor coverage may be more challenging in undivided two-way layouts due to the presence of oncoming traffic
+          and the potential for lane departures.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      divided_two_way:
+        # language=markdown
+        $desc: !markdown |
+          **Divided Two Way Layout**
+          
+          A roadway configuration where traffic flows in both directions with a physical separation, such as a median or
+          barrier. This layout typically involves one or more lanes of traffic in each direction, and the physical
+          separation helps to reduce the risk of head-on collisions. Sensor coverage may be improved in divided two-way
+          layouts due to the presence of clear lane boundaries and reduced interaction with oncoming traffic.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    lane_config:
+      # language=markdown
+      $desc: !markdown |
+        Lane configuration types that describe the number and arrangement of lanes on the roadway. These tags capture
+        specific lane configurations such as single lane, two lane, multi-lane, and unknown. Each configuration has
+        unique implications for traffic flow, driver behavior, and sensor coverage, making them important for scenario
+        analysis and data annotation. For example, a single lane configuration typically involves one lane of traffic in
+        each direction with no passing allowed, while a multi-lane configuration includes multiple lanes in each
+        direction with opportunities for passing and lane changes.
+      single_lane:
+        # language=markdown
+        $desc: !markdown |
+          **Single Lane Configuration**
+          
+          A roadway configuration where there is only one lane of traffic in each direction, with no opportunities for
+          passing or lane changes. This configuration typically involves a centerline to separate opposing traffic
+          flows,
+          and drivers must exercise caution when making turns or navigating around obstacles due to the potential for
+          head-on collisions. Sensor coverage may be more challenging in single lane configurations due to the presence
+          of oncoming traffic and the potential for lane departures.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      two_lane:
+        # language=markdown
+        $desc: !markdown |
+          **Two Lane Configuration**
+          
+          A roadway configuration where there are two lanes of traffic in each direction, allowing for passing and lane
+          changes. This configuration typically involves a centerline to separate opposing traffic flows, and drivers
+          must exercise caution when making turns or navigating around obstacles due to the potential for head-on
+          collisions. Sensor coverage may be improved in two lane configurations due to the presence of clear lane
+          boundaries and reduced interaction with oncoming traffic.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      multi_lane:
+        # language=markdown
+        $desc: !markdown |
+          **Multi Lane Configuration**
+          
+          A roadway configuration where there are multiple lanes of traffic in each direction, allowing for passing,
+          lane changes, and higher traffic volumes. This configuration typically involves a centerline to separate
+          opposing traffic flows, and drivers must exercise caution when making turns or navigating around obstacles due
+          to the potential for head-on collisions. Sensor coverage may be improved in multi-lane configurations due to
+          the presence of clear lane boundaries and reduced interaction with oncoming traffic.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    shoulder:
+      # language=markdown
+      $desc: !markdown |
+        Shoulder types that describe the presence and characteristics of the shoulder area adjacent to the travel lanes.
+        These tags capture specific shoulder types such as none, median, verge, sidewalk, emergency lane, and unknown.
+        Each shoulder type has unique implications for safety, vehicle recovery, and sensor coverage, making them
+        important for scenario analysis and data annotation. For example, a median shoulder typically separates opposing
+        traffic flows and may provide a refuge area for disabled vehicles, while a verge shoulder is located on the
+        outer edge of the roadway and may be used for emergency stops or pedestrian refuge.
+      none:
+        # language=markdown
+        $desc: !markdown |
+          **No Shoulder**
+          
+          The roadway segment does not have a designated shoulder area adjacent to the travel lanes. This condition can
+          increase safety risks as there is no space for vehicles to pull over in case of emergencies, breakdowns, or
+          to avoid obstacles. Drivers may need to stop in the travel lane, which can lead to increased collision risk
+          and traffic disruption. Sensor coverage may also be limited in these areas, making it important for scenario
+          analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      median:
+        # language=markdown
+        $desc: !markdown |
+          **Median Shoulder**
+          
+          A shoulder area located in the median between opposing traffic flows, often separated by a physical barrier or
+          marked with a painted buffer. Median shoulders can provide a refuge area for disabled vehicles and may enhance
+          safety by separating opposing traffic, but they may also have limited width and accessibility. Drivers may use
+          median shoulders for emergency stops or to avoid obstacles, but they should exercise caution due to potential
+          traffic from both directions. Sensor coverage in median shoulders may be limited, making them an important
+          consideration for scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      verge:
+        # language=markdown
+        $desc: !markdown |
+          **Verge Shoulder**
+          
+          A shoulder area located on the outer edge of the roadway, adjacent to the travel lanes. Verge shoulders can
+          provide space for emergency stops, vehicle recovery, and pedestrian refuge, but they may also be narrow and
+          unpaved in some cases. Drivers may use verge shoulders to pull over in case of emergencies or to avoid
+          obstacles, but they should exercise caution due to potential hazards such as soft ground, debris, or limited
+          visibility. Sensor coverage in verge shoulders may be limited, making them an important consideration for
+          scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      sidewalk:
+        # language=markdown
+        $desc: !markdown |
+          **Sidewalk Shoulder**
+          
+          A shoulder area that includes a sidewalk for pedestrian use, typically located on the outer edge of the
+          roadway. Sidewalk shoulders provide a designated space for pedestrians, enhancing safety and accessibility,
+          but they may also be narrow and may not accommodate vehicles in case of emergencies. Drivers should avoid
+          using sidewalk shoulders for stopping or parking, as this can create hazards for pedestrians and may be
+          illegal in some areas. Sensor coverage in sidewalk shoulders may be limited, making them an important
+          consideration for scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      emergency_lane:
+        # language=markdown
+        $desc: !markdown |
+          **Emergency Lane Shoulder**
+          
+          A designated shoulder area specifically intended for use by emergency vehicles, such as police cars, fire
+          trucks, and ambulances. Emergency lane shoulders are typically wider than standard shoulders and may be marked
+          with distinctive signage or pavement markings. They provide a safe space for emergency vehicles to stop or
+          pass through traffic during emergencies, but they should not be used by regular vehicles except in cases of
+          breakdowns or other emergencies. Sensor coverage in emergency lane shoulders may be limited, making them an
+          important consideration for scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    junction:
+      # language=markdown
+      $desc: !markdown |
+        Junction types that describe the configuration of intersections and merging/diverging points on the roadway.
+        These tags capture specific junction types such as cross, tee left/right, y intersection, roundabout, merge,
+        split, other, and unknown. Each junction type has unique implications for traffic flow, driver behavior, and
+        sensor coverage, making them important for scenario analysis and data annotation. For example, a cross
+        intersection typically involves four-way traffic with multiple conflict points, while a roundabout features a
+        circular layout that promotes continuous flow but requires careful navigation.
+      cross:
+        # language=markdown
+        $desc: !markdown |
+          **Cross Intersection**
+          
+          A junction where two or more roads intersect at approximately right angles, typically involving four-way
+          traffic with multiple conflict points. Cross intersections can be signalized or unsignalized and may include
+          features such as turn lanes, pedestrian crosswalks, and traffic islands. Drivers must navigate potential
+          conflicts from all directions, making these intersections complex for perception and behavior prediction.
+          Sensor coverage should capture the full intersection area to support safe navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      tee_left_right:
+        # language=markdown
+        $desc: !markdown |
+          **Tee Intersection (Left/Right)**
+          
+          A junction where one road ends at a perpendicular intersection with another road, forming a "T" shape. In a
+          tee left intersection, the terminating road is on the left side of the through road, while in a tee right
+          intersection, the terminating road is on the right side. Tee intersections can be signalized or unsignalized
+          and may include features such as turn lanes and pedestrian crosswalks. Drivers must navigate potential
+          conflicts from the terminating road and through traffic, making these intersections important for perception
+          and behavior prediction. Sensor coverage should capture the full intersection area to support safe navigation
+          and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      tee_left_only:
+        # language=markdown
+        $desc: !markdown |
+          **Tee Intersection (Left Only)**
+          
+          A junction where one road ends at a perpendicular intersection with another road, forming a "T" shape, with
+          the terminating road on the left side of the through road. Tee left only intersections may be signalized or
+          unsignalized and may include features such as turn lanes and pedestrian crosswalks. Drivers must navigate
+          potential conflicts from the terminating road and through traffic, making these intersections important for
+          perception and behavior prediction. Sensor coverage should capture the full intersection area to support safe
+          navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      tee_right_only:
+        # language=markdown
+        $desc: !markdown |
+          **Tee Intersection (Right Only)**
+          
+          A junction where one road ends at a perpendicular intersection with another road, forming a "T" shape, with
+          the terminating road on the right side of the through road. Tee right only intersections may be signalized or
+          unsignalized and may include features such as turn lanes and pedestrian crosswalks. Drivers must navigate
+          potential conflicts from the terminating road and through traffic, making these intersections important for
+          perception and behavior prediction. Sensor coverage should capture the full intersection area to support safe
+          navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      y_intersection:
+        # language=markdown
+        $desc: !markdown |
+          **Y Intersection**
+          
+          A junction where three roads meet at acute angles, forming a "Y" shape. Y intersections can be signalized or
+          unsignalized and may include features such as turn lanes and pedestrian crosswalks. Drivers must navigate
+          potential conflicts from all directions, making these intersections complex for perception and behavior
+          prediction. Sensor coverage should capture the full intersection area to support safe navigation and
+          decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      roundabout:
+        # language=markdown
+        $desc: !markdown |
+          **Roundabout**
+          
+          A circular junction where traffic flows around a central island, with entering traffic yielding to circulating
+          traffic. Roundabouts can be single-lane or multi-lane and may include features such as pedestrian crosswalks
+          and bicycle lanes. Drivers must navigate the circular flow and yield rules, making roundabouts important for
+          perception and behavior prediction. Sensor coverage should capture the full roundabout area to support safe
+          navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      merge:
+        # language=markdown
+        $desc: !markdown |
+          **Merge Point**
+          
+          A junction where two or more lanes of traffic converge into a single lane, typically involving a merging
+          maneuver. Merge points can occur on highways, expressways, and other multi-lane roads and may be marked with
+          signage and pavement markings. Drivers must navigate potential conflicts from merging traffic, making these
+          points important for perception and behavior prediction. Sensor coverage should capture the full merge area
+          to support safe navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      split:
+        # language=markdown
+        $desc: !markdown |
+          **Split Point**
+          
+          A junction where a single lane of traffic diverges into two or more lanes, typically involving a splitting
+          maneuver. Split points can occur on highways, expressways, and other multi-lane roads and may be marked with
+          signage and pavement markings. Drivers must navigate potential conflicts from diverging traffic, making these
+          points important for perception and behavior prediction. Sensor coverage should capture the full split area
+          to support safe navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      other:
+        # language=markdown
+        $desc: !markdown |
+          **Other Junction Type**
+          
+          A junction that does not fit into the standard categories of cross, tee, y intersection, roundabout, merge, or
+          split. This category captures unique or uncommon junction configurations that may be present in specific
+          locations or under certain conditions. Drivers must navigate potential conflicts from all directions, making
+          these junctions important for perception and behavior prediction. Sensor coverage should capture the full
+          junction area to support safe navigation and decision-making.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    infrastructure:
+      # language=markdown
+      $desc: !markdown |
+        Infrastructure features that describe specific roadway elements and structures. These tags capture features such
+        as tunnels, bridges/overpasses, underpasses, and unknown. Each infrastructure feature has unique implications
+        for driving behavior, vehicle dynamics, and sensor performance, making them important for scenario analysis and
+        data annotation. For example, tunnels can create confined spaces with limited visibility and unique lighting
+        conditions, while bridges/overpasses may involve elevation changes and exposure to wind.
+      tunnel:
+        # language=markdown
+        $desc: !markdown |
+          **Tunnel**
+          
+          A roadway feature that involves a passage through or under a structure, such as a mountain, hill, or urban
+          area. Tunnels can create confined spaces with limited visibility and unique lighting conditions, which can
+          affect driver behavior and sensor performance. Drivers may need to adjust their speed and following distance
+          when entering or exiting tunnels due to changes in visibility and road conditions. Sensor coverage in tunnels
+          may be limited, making them an important consideration for scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      bridge:
+        # language=markdown
+        $desc: !markdown |
+          **Bridge/Overpass**
+          
+          A roadway feature that involves a structure spanning a physical obstacle, such as a river, valley, or another
+          road. Bridges and overpasses may involve elevation changes and exposure to wind, which can affect driver
+          behavior and vehicle dynamics. Drivers may need to adjust their speed and following distance when crossing
+          bridges or overpasses due to changes in road conditions and potential crosswinds. Sensor coverage on bridges
+          and overpasses may be affected by the structure itself, making them an important consideration for scenario
+          analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      underpass:
+        # language=markdown
+        $desc: !markdown |
+          **Underpass**
+          
+          A roadway feature that involves a passage under a structure, such as a bridge, railway, or urban area.
+          Underpasses can create confined spaces with limited visibility and unique lighting conditions, which can
+          affect driver behavior and sensor performance. Drivers may need to adjust their speed and following distance
+          when entering or exiting underpasses due to changes in visibility and road conditions. Sensor coverage in
+          underpasses may be limited, making them an important consideration for scenario analysis and data annotation.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      unknown: { $desc: "unknown" }
+    geometry:
+      # language=markdown
+      $desc: !markdown |
+        Geometric characteristics that describe the shape and profile of the roadway. These tags capture specific
+        geometric features such as straight, curved, incline, decline, hill crest, and sag. Each geometric
+        characteristic has unique implications for vehicle dynamics, driver behavior, and sensor performance, making
+        them important for scenario analysis and data annotation. For example, a straight segment typically allows for
+        higher speeds and better visibility, while a curved segment may require more cautious driving and can create
+        blind spots.
+      curved:
+        # language=markdown
+        $desc: !markdown |
+          **Curved Segment**
+          
+          A roadway segment that features a horizontal curvature, requiring drivers to navigate a bend in the road.
+          Curved segments can vary in radius and degree of curvature, affecting vehicle dynamics and driver behavior.
+          Drivers may need to reduce speed and adjust their steering when navigating curved segments, especially if the
+          curve is sharp or if visibility is limited. Sensor performance may also be affected by curved segments due to
+          changes in the field of view and potential occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+        $schema:
+          type: object
+          properties:
+            curvature_radius:
+              type: number
+              description: "The radius of the curve in meters"
+              minimum: 0
+          required: [ curvature_radius ]
+          additionalProperties: true
+      incline:
+        # language=markdown
+        $desc: !markdown |
+          **Incline Segment**
+          
+          A roadway segment that features a positive vertical grade, requiring drivers to navigate an uphill slope.
+          Incline segments can vary in steepness and length, affecting vehicle dynamics and driver behavior. Drivers may
+          need to reduce speed and adjust their acceleration when navigating incline segments, especially if the incline
+          is steep or if the vehicle is heavily loaded. Sensor performance may also be affected by incline segments due
+          to changes in the field of view and potential occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+        $schema:
+          type: object
+          properties:
+            grade_percentage:
+              type: number
+              description: "The grade of the incline in percentage"
+              minimum: 0
+          required: [ grade_percentage ]
+          additionalProperties: false
+      decline:
+        # language=markdown
+        $desc: !markdown |
+          **Decline Segment**
+          
+          A roadway segment that features a negative vertical grade, requiring drivers to navigate a downhill slope.
+          Decline segments can vary in steepness and length, affecting vehicle dynamics and driver behavior. Drivers may
+          need to reduce speed and adjust their braking when navigating decline segments, especially if the decline is
+          steep or if the vehicle is heavily loaded. Sensor performance may also be affected by decline segments due to
+          changes in the field of view and potential occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+        $schema:
+          type: object
+          properties:
+            grade_percentage:
+              type: number
+              description: "The grade of the decline in percentage"
+              maximum: 0
+          required: [ grade_percentage ]
+          additionalProperties: false
+      hill_crest:
+        # language=markdown
+        $desc: !markdown |
+          **Hill Crest Segment**
+          
+          A roadway segment that features a vertical crest, where the road reaches a high point before descending. Hill
+          crest segments can create blind spots and limited visibility for drivers, affecting driver behavior and sensor
+          performance. Drivers may need to reduce speed and exercise caution when navigating hill crest segments,
+          especially if the crest is sharp or if there are potential obstacles on the other side. Sensor coverage may
+          also be affected by hill crest segments due to changes in the field of view and potential occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+      sag:
+        # language=markdown
+        $desc: !markdown |
+          **Sag Segment**
+          
+          A roadway segment that features a vertical sag, where the road dips down before ascending. Sag segments can
+          create blind spots and limited visibility for drivers, affecting driver behavior and sensor performance.
+          Drivers may need to reduce speed and exercise caution when navigating sag segments, especially if the sag is
+          sharp or if there are potential obstacles in the dip. Sensor coverage may also be affected by sag segments due
+          to changes in the field of view and potential occlusions.
+          
+          Examples:
+          
+          - [Case 1](https://image-search.plexus.ai/particular_case_image)
+          - [Case 2](https://image-search.plexus.ai/particular_case_image)
+  traffic:
+    # language=markdown
+    $desc: !markdown |
+      Traffic conditions that describe the presence and behavior of vehicles, pedestrians, cyclists, and other road
+      users. This category includes factors such as traffic density, pedestrian presence, cyclist presence, construction
+      zones, and accidents. Each tag captures specific conditions that can influence driving behavior, vehicle dynamics,
+      and sensor performance, making them important for scenario analysis and data annotation. For example, dense
+      traffic can lead to stop-and-go conditions and increased risk of collisions, while construction zones may involve
+      lane closures and unexpected obstacles.
+    density:
+      # language=markdown
+      $desc: !markdown |
+        Traffic density levels that describe the amount of vehicular traffic present on the roadway. These tags capture
+        specific density levels such as absent, sparse, light, moderate, dense, jammed, and unknown. Each density level
+        has unique implications for traffic flow, driver behavior, and sensor performance, making them important for
+        scenario analysis and data annotation. For example, absent traffic indicates no vehicles present, while jammed
+        traffic indicates a traffic jam with very slow or stopped vehicles.
+      absent: { $desc: "no traffic" }
+      sparse: { $desc: "sparse traffic" }
+      light: { $desc: "light traffic" }
+      moderate: { $desc: "moderate traffic" }
+      dense: { $desc: "dense traffic" }
+      jammed: { $desc: "traffic jam" }
+      unknown: { $desc: "unknown" }
+    pedestrian_presence:
+      # language=markdown
+      $desc: !markdown |
+        Pedestrian presence levels that describe the amount of pedestrian activity in the scene. These tags capture
+        specific levels of pedestrian presence such as absent, sparse, moderate, dense, and unknown. Each level has
+        unique implications for driver behavior, vehicle dynamics, and sensor performance, making them important for
+        scenario analysis and data annotation. For example, absent pedestrians indicate no pedestrians present, while
+        dense pedestrians indicate a high concentration of pedestrians in the area.
+      absent: { $desc: "no pedestrians" }
+      sparse: { $desc: "sparse pedestrians" }
+      moderate: { $desc: "moderate pedestrians" }
+      dense: { $desc: "dense pedestrians" }
+      unknown: { $desc: "unknown" }
+    cyclist_presence:
+      # language=markdown
+      $desc: !markdown |
+        Cyclist presence levels that describe the amount of cyclist activity in the scene. These tags capture specific
+        levels of cyclist presence such as absent, sparse, moderate, dense, and unknown. Each level has unique
+        implications for driver behavior, vehicle dynamics, and sensor performance, making them important for scenario
+        analysis and data annotation. For example, absent cyclists indicate no cyclists present, while dense cyclists
+        indicate a high concentration of cyclists in the area.
+      absent: { $desc: "no cyclists" }
+      sparse: { $desc: "sparse cyclists" }
+      moderate: { $desc: "moderate cyclists" }
+      dense: { $desc: "dense cyclists" }
+      unknown: { $desc: "unknown" }
+    construction_zone:
+      # language=markdown
+      $desc: !markdown |
+        Construction zone levels that describe the presence and severity of construction activity in the scene. These
+        tags capture specific levels of construction activity such as absent, minor, major, and unknown. Each level
+        has unique implications for traffic flow, driver behavior, and sensor performance, making them important for
+        scenario analysis and data annotation. For example, absent construction indicates no construction activity,
+        while major construction indicates significant construction activity that may involve lane closures and
+        unexpected obstacles.
+      absent: { $desc: "no construction" }
+      minor: { $desc: "minor construction" }
+      major: { $desc: "major construction" }
+      unknown: { $desc: "unknown" }
+    accident:
+      # language=markdown
+      $desc: !markdown |
+        Accident types that describe specific types of accidents or incidents that may be present in the scene. These
+        tags capture specific accident types such as collision, road block, debris on road, animal on road,
+        pedestrian on road, vehicle breakdown, emergency vehicle present, police stop, other, and unknown. Each
+        accident type has unique implications for traffic flow, driver behavior, and sensor performance, making them
+        important for scenario analysis and data annotation. For example, a collision typically involves a crash between
+        two or more vehicles, while a road block may involve an obstruction on the roadway that prevents traffic from
+        passing.
+      road_block: { $desc: "road block" }
+      debris_on_road: { $desc: "debris on road" }
+      animal_on_road: { $desc: "animal on road" }
+      pedestrian_on_road: { $desc: "pedestrian on road" }
+      vehicle_breakdown: { $desc: "vehicle breakdown" }
+      emergency_vehicle_present: { $desc: "emergency vehicle present" }
+      police_stop: { $desc: "police stop" }
+      other: { $desc: "other accident type" }
+  data_fidelity:
+    # language=markdown
+    $desc: !markdown |
+      Data fidelity issues that describe problems or anomalies in the sensor data that may affect its quality and
+      reliability. This category includes factors such as glare, motion blur, lens smear, occlusion, underexposure,
+      overexposure, weather effects, interference, multipath reflections, clutter, motion distortion, range dropout, and
+      reflectivity issues. Each tag captures specific data quality issues that can impact the performance of perception
+      algorithms and the accuracy of scenario analysis, making them important for data annotation and quality control.
+      For example, glare from the sun can create bright spots in camera images that obscure details, while motion blur
+      can occur when the camera or objects in the scene are moving quickly, resulting in blurred images that can be
+      difficult to interpret.
+    camera_issue:
+      # language=markdown
+      $desc: !markdown |
+        Camera data quality issues that describe specific problems or anomalies in camera sensor data. These tags
+        capture specific camera issues such as glare, motion blur, lens smear, occlusion, underexposure, and
+        overexposure. Each camera issue has unique implications for the quality and reliability of camera data, making
+        them important for data annotation and quality control. For example, glare from the sun can create bright spots
+        in camera images that obscure details, while motion blur can occur when the camera or objects in the scene are
+        moving quickly, resulting in blurred images that can be difficult to interpret.
+      glare: { $desc: "glare from sun or artificial source", <<: *camera_views }
+      motion_blur: { $desc: "motion blur", <<: *camera_views }
+      lens_smear: { $desc: "lens smear or dirt", <<: *camera_views }
+      occlusion: { $desc: "occlusion by objects", <<: *camera_views }
+      underexposure: { $desc: "underexposure", <<: *camera_views }
+      overexposure: { $desc: "overexposure", <<: *camera_views }
+    radar_issue:
+      # language=markdown
+      $desc: !markdown |
+        Radar data quality issues that describe specific problems or anomalies in radar sensor data. These tags capture
+        specific radar issues such as weather effects, interference, multipath reflections, and clutter. Each radar
+        issue has unique implications for the quality and reliability of radar data, making them important for data
+        annotation and quality control. For example, weather effects such as rain or snow can cause radar signals to
+        scatter, leading to reduced detection range and increased false positives, while interference from other radar
+        sources can create noise in the radar data that can obscure real targets and lead to false detections. Multipath
+        reflections occur when radar signals bounce off surfaces such as buildings or the ground, creating ghost targets
+        that can confuse perception algorithms, while clutter refers to unwanted radar returns from small objects or
+        environmental features that can create noise in the radar data and reduce the accuracy of target detection and
+        tracking.
+      weather_effects: { $desc: "weather effects", <<: *radar_views }
+      interference: { $desc: "interference", <<: *radar_views }
+      multipath: { $desc: "multipath reflections", <<: *radar_views }
+      clutter: { $desc: "clutter", <<: *radar_views }
+    lidar_issue:
+      # language=markdown
+      $desc: !markdown |
+        LiDAR data quality issues that describe specific problems or anomalies in LiDAR sensor data. These tags capture
+        specific LiDAR issues such as weather effects, occlusion, motion distortion, range dropout, and reflectivity
+        issues. Each LiDAR issue has unique implications for the quality and reliability of LiDAR data, making them
+        important for data annotation and quality control. For example, weather effects such as rain or snow can cause
+        LiDAR signals to scatter, leading to reduced detection range and increased false positives, while occlusion by
+        objects can block the LiDAR's line of sight to certain areas of the scene, resulting in missing data and
+        potential blind spots. Motion distortion occurs when the LiDAR sensor or objects in the scene are moving
+        quickly, causing the point cloud data to be distorted and potentially difficult to interpret. Range dropout
+        refers to situations where the LiDAR fails to return data from certain areas of the scene, which can occur due
+        to factors such as low reflectivity surfaces or long distances. Reflectivity issues arise when certain materials
+        or surfaces do not reflect LiDAR signals well, leading to weak returns that can be difficult to detect and
+        interpret.
+      weather_effects: { $desc: "weather effects", <<: *lidar_views }
+      occlusion: { $desc: "occlusion by objects", <<: *lidar_views }
+      motion_distortion: { $desc: "motion distortion", <<: *lidar_views }
+      range_dropout: { $desc: "range dropout", <<: *lidar_views }
+      reflectivity: { $desc: "reflectivity issues", <<: *lidar_views }