SUBWAY - Random Thoughts Topic

[Fresh Pond]

Is that green LED circle really f&$king necessary?! A red diamond would have been enough.

It's been like that for years going back to when the 62As dominated the line

 

Green circle = local

Red diamond = express

[Train92]

Are there any R62/A/142A's on the or the ?

Edited July 1, 2017 by 4 Train Man

[Daniel The Cool]

Are there any R62/A/142A's on the or the ?

There's a few R62As on the . None on the

[YankeesPwnMets]

Do the R42s have the orange sign installed or are they just planning to use the old 

[paulrivera]

They've finally fixed the and glitch on SubwayTime:

[Train92]

There's a few R62As on the . None on the

Oh. Any R142A's on the then?

[trainfan22]

Do the R42s have the orange sign installed or are they just planning to use the old

they don't have orange m signs, they would most likely use the shuttle or special roll signs up front.

[LegoBrickBreaker101]

Oh. Any R142A's on the then?

Nope, the is all R142s, and the is R62A, R142, and R142A.

[Daniel The Cool]

They've finally fixed the and glitch on SubwayTime:

I wouldn't say that yet. The Trains crews that start in the Bronx are actually running as Trains due to the Train G.O

[Deucey]

They've finally fixed the and glitch on SubwayTime:

What was the glitch?

[IAlam]

Would anyone happen to know why the GTFS data in the Transit app is showing via Broadway/West End and via 8th Avenue/Culver from 2AM July 4th to 1AM July 5th?

Transit is known for predicting Weekend and holiday service changes

 

Taken from their blog:

 

Well, it turns out that Google’s developers (and Apple’s, ours, and everyone else’s) don’t actually have access to any of the MTA’s service disruption data. Literally all we have to work off of is the text on the The Weekender website.

 

...

 

Thankfully, one of those rare transit geniuses works for Transit. His name is Leo. Every week, Leo reads The Weekender with his morning coffee, and with a combination of automated tools and human oversight turns The Weekender’s text into data that our trip planner can use ✅

 

Source: https://medium.com/transit-app/how-were-bringing-real-time-countdowns-to-nyc-s-lettered-lines-482d3b8f9899

Edited July 1, 2017 by IAlam

[Calvin]

I wonder how many cars was the Shuttle around the Rockaways was when it was R32 class cars

[R32 3838]

I wonder how many cars was the Shuttle around the Rockaways was when it was R32 class cars

4 cars

[MetroTransitTee]

When the 4th Avenue line is pulling a Hillside...

[Around the Horn]

When the 4th Avenue line is pulling a Hillside...

 

Oh dear... what happened now?

[MetroTransitTee]

Oh dear... what happened now?

R trains are being stored on the express tracks and are "short-turning" at 9th Ave, N trains are running on the local track between 59th and 36th.

[Around the Horn]

R trains are being stored on the express tracks and are "short-turning" at 9th Ave, N trains are running on the local track between 59th and 36th.

 

Yeah that's the GO this weekend. Here i was thinking something unplanned happened...

[MysteriousBtrain]

Few notes on the new codes for the codes (from 86 St):

At 59 St, the R142s announce a transfer to the and train (in that exact order).

At Fulton St, the and are omitted and Pellet announces the and . Same case for Court St.

Between Brooklyn Bridge and Bowling Green, the calls itself a Brooklyn bound local train.

At Bowling Green, Pellet announces a (not free) transfer to and train.

South of and including Bowling Green, the announces itself as an Eastchester bound local train.

At Franklin Ave, Pellet announces a transfer to the and Franklin Av .

 

Separate note, there is at least one set with a code to 86 St, but most are signed up as s to 149 St, Wakefield, Eastchester, etc.

Edited July 2, 2017 by ShadeJay

[CTK246]

Few notes on the new codes for the codes (from 86 St):

At 59 St, the R142s announce a transfer to the and train (in that exact order).

At Fulton St, the and are omitted and Pellet announces the and . Same case for Court St.

Between Brooklyn Bridge and Bowling Green, the calls itself a Brooklyn bound local train.

At Bowling Green, Pellet announces a (not free) transfer to and train.

South of and including Bowling Green, the announces itself as an Eastchester bound local train.

At Franklin Ave, Pellet announces a transfer to the and Franklin Av .

 

Separate note, there is at least one set with a code to 86 St, but most are signed up as s to 149 St, Wakefield, Eastchester, etc.

This is for the Clark St tube G/O, I assume. The Eastchester announcement is probably a glitch.

[LegoBrickBreaker101]

My Woodlawn bound train today kept announcing itself as a "Manhattan bound local train" while it was running in the Bronx. I'm not surprised that the MTA keeps making these trivial mistakes, but can't they at least ask someone to listen to these faulty announcements BEFORE they are played out loud in service?...

[CTK246]

My Woodlawn bound train today kept announcing itself as a "Manhattan bound local train" while it was running in the Bronx. I'm not surprised that the MTA keeps making these trivial mistakes, but can't they at least ask someone to listen to these faulty announcements BEFORE they are played out loud in service?...

Actually, it's a pretty common glitch that happens quite a bit on the R142s. Sometimes the announcements get stuck in the previous borough. For some reason, it's more prevalent on the Lex lines than 7th Av.

[Lawrence St]

I think it's because Lex has a more complex routing program code then 7th Avenues. At times the announcements will not cycle through and glitch, and remain on that same announcements unless there's a trigger code to change it again (I.e entering Brooklyn.)

 

But, for that glitch where Flatbush Avenue bound trains will announce themselves as Eastchester bound 5 trains, that's a result of faulty programming. To me it looks like the wrong file is used to play the bound announcement.

[Calvin]

Is there a free transfer from Bowling Green to South Ferry station just like the at Lexington Av-63 to the 59 St station?

[Union Tpke]

Yes.

[Lance]

Few notes on the new codes for the codes (from 86 St):

At 59 St, the R142s announce a transfer to the and train (in that exact order).

At Fulton St, the and are omitted and Pellet announces the and . Same case for Court St.

Between Brooklyn Bridge and Bowling Green, the calls itself a Brooklyn bound local train.

At Bowling Green, Pellet announces a (not free) transfer to and train.

South of and including Bowling Green, the announces itself as an Eastchester bound local train.

At Franklin Ave, Pellet announces a transfer to the and Franklin Av .

 

Separate note, there is at least one set with a code to 86 St, but most are signed up as s to 149 St, Wakefield, Eastchester, etc.

One of these days, they will get the correct transfer at 59 Street. I have faith in them.  Seriously though, I'm actually impressed they have updated all of the transfer announcements to reflect the Clark St weekend closures. Usually it takes them a while to get these things updated.

 

My Woodlawn bound train today kept announcing itself as a "Manhattan bound local train" while it was running in the Bronx. I'm not surprised that the MTA keeps making these trivial mistakes, but can't they at least ask someone to listen to these faulty announcements BEFORE they are played out loud in service?...

It's a persistent glitch in the code, which has actually been there since the 142s entered revenue service in 2000. For whatever reason, the code will sometimes not cycle to the next destination file as programmed. It isn't a matter of the increased number of destination-related files to call as this has been prevalent through the cars' AAS since inception. This was a common glitch to encounter on the train, which only cycled through two destination files for southbound routes.