Spring Bus Stop Relocations

[Vinny]

As reported in CTA Tattler, there were a bunch of stop relocations this week. One of these on the 53 Pulaski moved the SB Lawrence stop from the south side of the intersection to the north side of the intersection.

Now, this stop was just moved from the north side of the intersection to the south side back in September, ostensibly so that the bus wouldn't get stuck at the light. So why move it back less than six months later? I can think of a number of plausible reasons:

- The operating statistics did not support the time-saving theory of avoiding the light in this case

- Customer complaints about the move (there was a bench and shelter under the Walgreens sign on the north side)

- Stop bunching (the SB Leland stop is well to the north of Leland, so the two stops were basically a block apart)

- CTA just wanted to generate busywork

Can anyone shed light on the decision making process for stop relocations? Just wonder if any of my theories hold water.

[cta_44499_FG]

As reported in CTA Tattler, there were a bunch of stop relocations this week. One of these on the 53 Pulaski moved the SB Lawrence stop from the south side of the intersection to the north side of the intersection.

Now, this stop was just moved from the north side of the intersection to the south side back in September, ostensibly so that the bus wouldn't get stuck at the light. So why move it back less than six months later? I can think of a number of plausible reasons:

- The operating statistics did not support the time-saving theory of avoiding the light in this case

- Customer complaints about the move (there was a bench and shelter under the Walgreens sign on the north side)

- Stop bunching (the SB Leland stop is well to the north of Leland, so the two stops were basically a block apart)

- CTA just wanted to generate busywork

Can anyone shed light on the decision making process for stop relocations? Just wonder if any of my theories hold water.

CTA is known to do things like this at any given time for no apparent reason. I live right around the corner from Lawrence/Pulaski...and couldn't help but notice the same thing but also the fact they stuck up about three bus stop relocation signs there....guess they'd make sure the message was loud and clear! LOL...before they move it again! :D

[sht6131]

As reported in CTA Tattler, there were a bunch of stop relocations this week. One of these on the 53 Pulaski moved the SB Lawrence stop from the south side of the intersection to the north side of the intersection.

Now, this stop was just moved from the north side of the intersection to the south side back in September, ostensibly so that the bus wouldn't get stuck at the light. So why move it back less than six months later? I can think of a number of plausible reasons:

- The operating statistics did not support the time-saving theory of avoiding the light in this case

- Customer complaints about the move (there was a bench and shelter under the Walgreens sign on the north side)

- Stop bunching (the SB Leland stop is well to the north of Leland, so the two stops were basically a block apart)

- CTA just wanted to generate busywork

Can anyone shed light on the decision making process for stop relocations? Just wonder if any of my theories hold water.

I was involved in relocation of stops when I was employed at CTA in the Traffic Planning Dept during the 50s and 60s.

Relocation request originate from customer complaints, Bureau of Street Traffic. District Supervisors, Station Managers

Supervisors, and bus drivers. Depending on the necessity as in a busy intersection, correspondence to the BST would be first requesting a meeting at the site. If that is approved a District Supervisor would sometimes be present also depending on who requested the relocation. Side street relocating, adding or eliminating usually involved myself and a district supervisor. They were usually customer complaints (too close to there driveway etc.)