# Bus stops on cycle lane

**URL:** <https://forum.irap.org/t/bus-stops-on-cycle-lane/1082>\
**Category:** CycleRAP\
**Created:** [February 12, 2025, 3:07pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082 "2025-02-12T15:07:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![RoxyTacq](https://forum.irap.org/user_avatar/forum.irap.org/roxytacq/32/19_2.png) [@RoxyTacq](https://forum.irap.org/u/RoxyTacq)\
**Post date:** [February 12, 2025, 3:07pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/1 "2025-02-12T15:07:07Z")

</div>

Should we code additional attributes to capture the risk of a bus stop on a cycling lane?

Example:  
[https://maps.app.goo.gl/tA96v9N7MgwN1ybq7](https://maps.app.goo.gl/tA96v9N7MgwN1ybq7)

 ![Foto 12-02-2025 om 16.03](https://forum.irap.org/uploads/default/original/1X/c810fb7ba25cc9ad73d5b7036add920e80f2f3ac.jpeg)

There is a difference in high, but the design is comfortable to cycle on.  
Advantages are a good view between the cyclist and pedestrians.

Maybe code the following to capture the additional risk:

- pedestrian flow: medium/high
- pedestrian crossing: present
- width restriction: present  
or
- surface deformation: present

---

<div class="post-metadata">

**Author:** ![shanna.lucchesi](https://forum.irap.org/user_avatar/forum.irap.org/shanna.lucchesi/32/386_2.png) [@shanna.lucchesi](https://forum.irap.org/u/shanna.lucchesi)\
**Post date:** [February 13, 2025, 5:23pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/2 "2025-02-13T17:23:31Z")

</div>

Hi Roxy,

I agree with all your suggestions, except for the width restrictions. I believe the pedestrian flow already captures the effect you’re aiming for. If the number of pedestrians waiting for the bus blocks the facility, we can code the facility access as inadequate. In such cases, cyclists will prefer to ride in the traffic lane, and the model will assume cyclists are in mixed traffic for that section. Additionally, the presence of heavy vehicles and parking are attributes that need to be considered.

---

<div class="post-metadata">

**Author:** ![RoxyTacq](https://forum.irap.org/user_avatar/forum.irap.org/roxytacq/32/19_2.png) [@RoxyTacq](https://forum.irap.org/u/RoxyTacq)\
**Post date:** [February 13, 2025, 5:56pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/3 "2025-02-13T17:56:22Z")

</div>

Hi Shanna,

All right. Ok we can add parking as well.  
And yes off course we won’t forget the heavy vehicle flow along the whole on-road lane.

---

<div class="post-metadata">

**Author:** ![RoxyTacq](https://forum.irap.org/user_avatar/forum.irap.org/roxytacq/32/19_2.png) [@RoxyTacq](https://forum.irap.org/u/RoxyTacq)\
**Post date:** [December 4, 2025, 10:40am UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/4 "2025-12-04T10:40:06Z")

</div>

What would be the best practice to code the risk of bus stops that are on/interrupting an on-road bike lane?

 ![](https://forum.irap.org/uploads/default/original/1X/a2f42e062f4ad0025a8d8624ef65a0d3c8ec4b85.jpeg)

Facility type: mixed traffic lane

OR

Facility type: on-road lane + facility access inadequate ??

Plus:

- pedestrian flow medium/high
- pedestrian crossing
- adjacent vehicle parking 0-1m

(HVF medium/high)

---

<div class="post-metadata">

**Author:** ![RoxyTacq](https://forum.irap.org/user_avatar/forum.irap.org/roxytacq/32/19_2.png) [@RoxyTacq](https://forum.irap.org/u/RoxyTacq)\
**Post date:** [December 4, 2025, 1:11pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/5 "2025-12-04T13:11:02Z")

</div>

> [@RoxyTacq](#):
>
> - pedestrian crossing
> - adjacent vehicle parking 0-1m

The manual states that we should code a non-fixed obstacle.

So it’s both a non-fixed obstacle and vehicle parking?

---

<div class="post-metadata">

**Author:** ![shanna.lucchesi](https://forum.irap.org/user_avatar/forum.irap.org/shanna.lucchesi/32/386_2.png) [@shanna.lucchesi](https://forum.irap.org/u/shanna.lucchesi)\
**Post date:** [December 4, 2025, 3:12pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/6 "2025-12-04T15:12:10Z")

</div>

Hi Roxy, I suggest code as a vehicle parking, because the associated treatment will be remove/reconfigure parking, what seems to be a possibility. While the non-fixed obstacles will trigger the recommendation of removing the obstacle, what will not solve the issue.

---

<div class="post-metadata">

**Author:** ![shanna.lucchesi](https://forum.irap.org/user_avatar/forum.irap.org/shanna.lucchesi/32/386_2.png) [@shanna.lucchesi](https://forum.irap.org/u/shanna.lucchesi)\
**Post date:** [December 4, 2025, 9:45pm UTC](https://forum.irap.org/t/bus-stops-on-cycle-lane/1082/7 "2025-12-04T21:45:18Z")

</div>

I recommend code as on-road bicycle lane with inadequate access because the model will assume for this session that bicyclists will ride along with cars. The model will generate a slightly grater risk if coded as a mixed-traffic road lane, but the effect is minor.
