From 38903c94cc73f0571f25c076049d5eb7ba493d38 Mon Sep 17 00:00:00 2001 From: Mamoru Sobue Date: Mon, 19 Aug 2024 21:27:28 +0900 Subject: [PATCH] fix typo Signed-off-by: Mamoru Sobue --- autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md b/autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md index 0376bba..d5e8cab 100644 --- a/autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md +++ b/autoware_lanelet2_extension/docs/extra_lanelet_subtypes.md @@ -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.