Jump to content

Ashland Extension to new northern terminal?


Tcmetro

Recommended Posts

5 minutes ago, Busjack said:

The Advance Timetable link was for all changed routes.  The 9 webpage was and still is correct. What's on street corners, I don't know.

If you mean the bus stops signs, they’re still the same & haven’t been changed yet to reflect the new routing.

  • Thanks 1
Link to comment
Share on other sites

17 hours ago, Busjack said:

The Advance Timetable link was for all changed routes.  The 9 webpage was and still is correct. What's on street corners, I don't know.

The bus stop I waited this afternoon is still one that says to Clark/Belle Plaine. So they're good on that front for now. Don't know if actual destination signs are updated yet since the one northbound bus I saw, bus 8051, had a broken sign that's stuck on 11 Lincoln to Foster and a paper sign on the windshield with 9 Ashland on it.

Link to comment
Share on other sites

42 minutes ago, jajuan said:

The bus stop I waited this afternoon is still one that says to Clark/Belle Plaine. So they're good on that front for now. Don't know if actual destination signs are updated yet since the one northbound bus I saw, bus 8051, had a broken sign that's stuck on 11 Lincoln to Foster and a paper sign on the windshield with 9 Ashland on it.

They are. The destination signs as well as the route/destination announcements say “To Ravenswood Metra Station”.

Link to comment
Share on other sites

10 minutes ago, TaylorTank1229 said:

They are. The destination signs as well as the route/destination announcements say “To Ravenswood Metra Station”.

As I suspected. Of course that couldn't be helped given that the original plan was to implement the extension yesterday along with the other Fall pick updates. So obviously the update in signs and announcements had to come with other fall run updates.

Link to comment
Share on other sites

On 8/15/2024 at 8:21 PM, TaylorTank1229 said:

According to Alderman Martin (via email), the service date for the #9 Ashland bus extension  has been delayed an additional week to Tuesday, September 3th in order for the CDOT to conduct road work in some areas along the extension route.

IMG_4391.jpeg

I saw some folks grumbling about this; it might've also been helpful to mention that concrete bus pads are apparently also going in.

Slightly related, the city & CTA should probably consider some sort of informational campaign about why this kind of work is necessary (although I can understand being annoyed that it wasn't completed prior to the start date), especially since I'm sure folks often think the city = CTA and vice versa

Link to comment
Share on other sites

So apparently CTA has recycled old destination codes for the extension. For the second day in a row I'm seeing northbound buses flashing "11 to Foster" signs. Matter of fact, they're signs for the 11 Lincoln/Sedgwick from when CTA experimented with running the 11 south of the Western Brown Line again.

  • Haha 1
Link to comment
Share on other sites

17 hours ago, NewFlyerMCI said:

I saw some folks grumbling about this; it might've also been helpful to mention that concrete bus pads are apparently also going in.

Slightly related, the city & CTA should probably consider some sort of informational campaign about why this kind of work is necessary (although I can understand being annoyed that it wasn't completed prior to the start date), especially since I'm sure folks often think the city = CTA and vice versa

Seem like the concrete pads and well as the road work is something they could’ve take care of weeks beforehand, if you ask me, instead of waiting this late.

  • Upvote 1
Link to comment
Share on other sites

On 8/27/2024 at 2:43 PM, jajuan said:

So apparently CTA has recycled old destination codes for the extension. For the second day in a row I'm seeing northbound buses flashing "11 to Foster" signs. Matter of fact, they're signs for the 11 Lincoln/Sedgwick from when CTA experimented with running the 11 south of the Western Brown Line again.

It was a sight to see yesterday morning that's for sure. 😅 

DSC_7628 copy.png

DSC_76254 copy.png

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

On 8/27/2024 at 3:35 PM, TaylorTank1229 said:

Seem like the concrete pads and well as the road work is something they could’ve take care of weeks beforehand, if you ask me, instead of waiting this late.

 

1 hour ago, YoungBusLover said:

It was a sight to see yesterday morning that's for sure. 😅 

DSC_7628 copy.png

DSC_76254 copy.png

You'd think by now they'd learn to clear old codes knowing they tend to reuse them by now 🥴🥴

  • Upvote 2
  • Haha 1
Link to comment
Share on other sites

46 minutes ago, Sam92 said:

 

You'd think by now they'd learn to clear old codes knowing they tend to reuse them by now 🥴🥴

Besides, it's a new bus that should have never had that reading.

Link to comment
Share on other sites

3 hours ago, YoungBusLover said:

It was a sight to see yesterday morning that's for sure. 😅 

DSC_7628 copy.png

DSC_76254 copy.png

Not surprised, that happened last year when the 84 started going to Thorndale. Some of them would say “145 - MICHIGAN EXP; to WILSON”. 😅

 

Also there was a woman today who was waiting at SW corner of Lawrence and Ashland waiting for the bus. The bus driver for the EB #81 there asked “What bus are you waiting for?” and she said “the #9 Ashland”. And crazy enough, this old married couple waiting at future #9 layover spot at Ravenswood Metra, and it doesn’t seem like the CDOT hasn’t started it road work there. This is why putting a few notices at bus stops along Ashland and it new upcoming stops to inform themselves of the start date is probably is important & why waiting till the last minute to get preparations done is not advised.

Link to comment
Share on other sites

11 hours ago, Busjack said:

Besides, it's a new bus that should have never had that reading.

Crazy part is that the glitch up when I've seen it here and there has mainly been with Nova buses, both 7900s and 8350s. I haven't yet see any 1000s with that reading.

10 hours ago, TaylorTank1229 said:

Not surprised, that happened last year when the 84 started going to Thorndale. Some of them would say “145 - MICHIGAN EXP; to WILSON”. 😅

 

Also there was a woman today who was waiting at SW corner of Lawrence and Ashland waiting for the bus. The bus driver for the EB #81 there asked “What bus are you waiting for?” and she said “the #9 Ashland”. And crazy enough, this old married couple waiting at future #9 layover spot at Ravenswood Metra, and it doesn’t seem like the CDOT hasn’t started it road work there. This is why putting a few notices at bus stops along Ashland and it new upcoming stops to inform themselves of the start date is probably is important & why waiting till the last minute to get preparations done is not advised.

Yes notices on bus stops would have helped. Not everyone is familiar with the option CTA provides to get direct updates on specific routes. Nor are there as many who get information from Block Club Chicago, where a lot of us in the forum first heard about the extension. The local alderman of the area has been touting it with constituents, but the only traditional local media outlet I saw mention it was the Chicago Sun-Times. 

On the road work front, the way I understood it the vast majority of the work had to do with Ashland itself along the extension and entailed creating bulbouts at intersections to place the new bus stops so that buses wouldn't need to maneuver out of and back into the travel lane to meet the curb. At the layover spot, it seemed the major concern there was removal of enough parking spaces to make room for the buses to have their layovers.

Link to comment
Share on other sites

1 hour ago, jajuan said:

Crazy part is that the glitch up when I've seen it here and there has mainly been with Nova buses, both 7900s and 8350s. I haven't yet see any 1000s with that reading.

Would depend, though, whether they are the original Novas with Luminator signs (which 1000s also have), or the newer ones with Hanover signs (as pictured). IIRC, the first buses with Hanover signs were 700s, and it seems like #11 Lincoln Sedgwick was canceled at the same time (2012). Why CTA would load a 12-year old file is beyond me.

Link to comment
Share on other sites

14 hours ago, Busjack said:

Besides, it's a new bus that should have never had that reading.

 

1 hour ago, Busjack said:

Would depend, though, whether they are the original Novas with Luminator signs (which 1000s also have), or the newer ones with Hanover signs (as pictured). IIRC, the first buses with Hanover signs were 700s, and it seems like #11 Lincoln Sedgwick was canceled at the same time (2012). Why CTA would load a 12-year old file is beyond me.

If the code isn't erased any bus could pull it up. I've seen 4300s with 145 readings lol

Link to comment
Share on other sites

2 hours ago, Busjack said:

Would depend, though, whether they are the original Novas with Luminator signs (which 1000s also have), or the newer ones with Hanover signs (as pictured). IIRC, the first buses with Hanover signs were 700s, and it seems like #11 Lincoln Sedgwick was canceled at the same time (2012). Why CTA would load a 12-year old file is beyond me.

It's been both Nova sets, the original 7900s set with Luminators and the 8350s set with the Hanovers. 8051 is a main culprit which was the first I visually spotted earlier this week. There were a couple of others out of 74th's original Novas that I spotted but couldn't get a clear view because each time I was spotting them in traffic from another vehicle traveling the opposite direction, and an SUV or commercial truck was always blocking the fleet number. @YoungBusLover's picture shows that at least one 8350 has this glitch. It seems it's like in prior times. It's a random glitch that makes certain individual buses, regardless of model or type of destination signs, show readings from the past. The vast majority of buses show '9 TO RAVENSWOOD METRA STATION'. 

Link to comment
Share on other sites

2 hours ago, Sam92 said:

 

If the code isn't erased any bus could pull it up. I've seen 4300s with 145 readings lol

But if it is a fresh file, it should have pulled up to Ravenswood, as  @jajuan says others do.

Link to comment
Share on other sites

As far as codes are concerned the CTA updates the signage every 6 - 12 months and very often they will reuse old codes from discontinued routes so in theory any bus can pull up the code if it is indeed available. You'd be surprised with how much old stuff hasn't been replaced yet.

20231209_192504.jpg

20231209_192342.jpg

20231209_193216.jpg

20240104_195917.jpg

20220704_235003.jpg

20240225_113724.jpg

  • Like 1
Link to comment
Share on other sites

37 minutes ago, YoungBusLover said:

As far as codes are concerned the CTA updates the signage every 6 - 12 months and very often they will reuse old codes from discontinued routes so in theory any bus can pull up the code if it is indeed available. You'd be surprised with how much old stuff hasn't been replaced yet.

20231209_192504.jpg

20231209_192342.jpg

20231209_193216.jpg

20240104_195917.jpg

20220704_235003.jpg

20240225_113724.jpg

So are the updates supposed to be downloaded on every individual bus?  

Link to comment
Share on other sites

23 minutes ago, artthouwill said:

So are the updates supposed to be downloaded on every individual bus?  

They used to go in every bus and plug in a card. Now every bus revives updates wirelessly when parked for the day. 

Link to comment
Share on other sites

On 8/29/2024 at 7:45 AM, jajuan said:

Crazy part is that the glitch up when I've seen it here and there has mainly been with Nova buses, both 7900s and 8350s. I haven't yet see any 1000s with that reading.

Yes notices on bus stops would have helped. Not everyone is familiar with the option CTA provides to get direct updates on specific routes. Nor are there as many who get information from Block Club Chicago, where a lot of us in the forum first heard about the extension. The local alderman of the area has been touting it with constituents, but the only traditional local media outlet I saw mention it was the Chicago Sun-Times. 

On the road work front, the way I understood it the vast majority of the work had to do with Ashland itself along the extension and entailed creating bulbouts at intersections to place the new bus stops so that buses wouldn't need to maneuver out of and back into the travel lane to meet the curb. At the layover spot, it seemed the major concern there was removal of enough parking spaces to make room for the buses to have their layovers.

Well as far I’ve seen currently, people are still parking in the upcoming layover spot. Just think the city would’ve put a notice by there saying that cars will not be permitted to park here at said effective date, or something like that. Unless they planning to do so the upcoming holiday weekend, you think when the extension starts people will still be putting their cars there?

1 hour ago, YoungBusLover said:

As far as codes are concerned the CTA updates the signage every 6 - 12 months and very often they will reuse old codes from discontinued routes so in theory any bus can pull up the code if it is indeed available. You'd be surprised with how much old stuff hasn't been replaced yet.

20231209_192504.jpg

20231209_192342.jpg

20231209_193216.jpg

20240104_195917.jpg

20220704_235003.jpg

20240225_113724.jpg

Wow, they still have the codes for routes like #25 & #27? Codes that old!? And the #169… I assume it used to terminate at the Halsted Green Line station at one point before going to 69th Red Line?

Link to comment
Share on other sites

10 minutes ago, TaylorTank1229 said:

Well as far I’ve seen currently, people are still parking in the upcoming layover spot. Just think the city would’ve put a notice by there saying that cars will not be permitted to park here at said effective date, or something like that. Unless they planning to do so the upcoming holiday weekend, you think when the extension starts people will still be putting their cars there?

Wow, they still have the codes for routes like #25 & #27? Codes that old!? And the #169… I assume it used to terminate at the Halsted Green Line station at one point before going to 69th Red Line?

169 to 63rd/Halsted was a detour from the Dan Ryan shutdown to still connect with the red line same with 8A

Link to comment
Share on other sites

7 minutes ago, Sam92 said:

169 to 63rd/Halsted was a detour from the Dan Ryan shutdown to still connect with the red line same with 8A

On yeah, that’s right. When the Red Line Southbound Construction project was happening and Red Trains were ending at Ashland/63rd.

Link to comment
Share on other sites

2 hours ago, artthouwill said:

So are the updates supposed to be downloaded on every individual bus?  

Yes, the software update takes a while for every singal bus to receive depending on the garage they're at. Hence why alot of 103rd's #8350s still display the old centered signage. Any bus that has been oos for let's say anytime before the left aligned update will also take a while to recieve it.

 

2 hours ago, Sam92 said:

They used to go in every bus and plug in a card. Now every bus revives updates wirelessly when parked for the day. 

That is correct.

Link to comment
Share on other sites

11 minutes ago, Sam92 said:

New Novas on J14 show up as J14 Jeffery Express 🤣🤣

That's very inconsistent, historically speaking. Either it was 14 Jeffrey Express or J14 Jeffery Jump.

Only thing I conclude is that CTA doesn't have proofreaders.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...