Skip to content

Commit

Permalink
fix typo
Browse files Browse the repository at this point in the history
Signed-off-by: Mamoru Sobue <[email protected]>
  • Loading branch information
soblin committed Aug 19, 2024
1 parent 00825dd commit 38903c9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Although `bicycle_lane` subtype is already defined in the original [Lanelet2 doc

- refers: `road` lanelet adjacent to the objective `bicycle_lane` should share the same boundary LineString
- specification:
- A `bicyle_lane` is connected to/from only `bicycle_lane` lanelets and is adjacent to a `road` lanelet. Namely in Left(Right) hand side traffic rules, it is on the left(right) side of `road` lanelet.
- A `bicycle_lane` is connected to/from only `bicycle_lane` lanelets and is adjacent to a `road` lanelet. Namely in Left(Right) hand side traffic rules, it is on the left(right) side of `road` lanelet.
- A `road_shoulder` lanelet must not be adjacent to a `bicycle_lane` because pullover on `bicycle_lane` is prohibited. For simplifying planning/prediction component, at format_version 2, a `bicycle_lane` should cover the adjacent area corresponding to `road_shoulder` or `pedestrian_lane`.
- The treatment of _navigation mark_, or the shift-arrow shaped painting on the side of the road without explicit separating line, is open to discussion. We can either identity them as part of the vehicle road or separate them as distinct bicycle lanes.

Expand Down

0 comments on commit 38903c9

Please sign in to comment.