SUBWAY - Random Thoughts Topic

[checkmatechamp13]

I've heard of this "metro card" hack (basically bending your card in a certain spot) then can get you in the the system for free. Is this even real?

 

It was true at some point, but I think the MTA fixed that glitch.

[SevenEleven]

The retro bullets have been uploaded for the time being. They are located at the very end (or bottom) of the emoticon list. There are different variations to the formatting used to insert these bullets. That is as follows:
 
For the numbered and single lettered routes that exist today (E, J, whatever): Wrap colons around the route. For example:
 
 

 ; 

becomes ;
 
For the most recent iteration of double lettered and diamond routes: Wrap parenthesis [diamonds] around the route. For example:
 
 

 ; 

becomes ;

For earlier iterations of routes, wrap those in colons as well. For example, to get the green CC bullet:
 

becomes

The retro bullets will disappear and reappear over the next couple of minutes, as I totally forgot to save them in .PNG format.

 

All re-uploaded!!

[Javier]

 Alright thanks Seven!
  You even added the RR awesome!

Edited June 3, 2016 by Seven

[Jcb]

Edited June 3, 2016 by Jcb

[MysteriousBtrain]

Let's see, we got , , , (mm), , (aa), , , (8) , :s:, ,

 

Just to test out some of the new codes.

Looks like some are either not real routes or not programmed yet. Either way, thanks admins.

[Lance]

Basically, every route from 1967 to '79 must be wrapped in colons. Routes from 1979 to the present must be wrapped in parenthesis or angled brackets to display correctly. I included what should be every route from the '67 color explosion to the present. Enjoy.

 

Also, thanks for adding them to the system Seven.

 

One final thing: please do not abuse the smiley privilege with posts filled with nothing but route bullets. Thank you.

Edited June 3, 2016 by Lance

[BDNQ2345]

Let me try it out

Edited June 4, 2016 by BDNQ2345

[BDNQ2345]

(QT) COOL

[Wallyhorse]

     

   

Just testing.

[CenSin]

     

 

   

 

Just testing.

I predict generous use of these bullets in the near future.

 

to 96 Street. to Forest Hills–71 Avenue. to Broad Street. <M> to Bay Parkway.

 

It’s conceivable that in some far off future, there will be more routes than letters and numbers, and the MTA will be forced to distinguish them by shape (circle versus diamond) and/or by a second letter. Similar routes might share a letter and become distinguished by shape: ⟶ <A> . The freed-up letters would go to newly minted routes like 168 Street–Washington Heights to Voorhies Avenue–Sheepshead Bay via 8 Avenue/Worth Street/Utica Avenue.

Edited June 4, 2016 by CenSin

[GojiMet86]

The I, K, O, P, U, V, X, and Y are still free (not counting H). But could you imagine the outrage if they had to use numbers on the B Division? I could see either 10 and up, or 20 and up being used.

Edited June 4, 2016 by GojiMet86

[CenSin]

The I, K, O, P, U, V, X, and Y are still free (not counting H).

Assuming an eventual two routes per line built (since double-tracked construction will be the norm, and any line built would be justified by high ridership, which in turn would mean 15 T.P.H.), 4 more lines could be built and they’d still have enough letters to go around. I assume I and O will never be used, but H is still up in the air.

 

But could you imagine the outrage if they had to use numbers on the B Division?

0 outrage predicted, except from hardcore subway fans.

[GojiMet86]

The OCD will shoot through the roof.

[paulrivera]

I wonder if there were multiple complaints made to the about weekend Lex service that they have restored weekend service from 20 minute headways back to the as-originally assigned 12 minute headways...

 

Whenever there was insufficient service the would have these insane gaps in service since it would practically be running by itself on the weekends (we all know the tourists dont really take the ...)

[trainfan22]

The I, K, O, P, U, V, X, and Y are still free (not counting H). But could you imagine the outrage if they had to use numbers on the B Division? I could see either 10 and up, or 20 and up being used.

They used numbers on the B div before..

 

http://nycsubway.org/perl/show?2603

 

Seeing numbers on the B Div again would be nostalgia. 

[Porter]

Thank you very much, Seven! This update has really brightened my week!

 

I can only think of adding the following bullets to cover all post-1979/1985-reform lines:

 

（Ｂ）（Ｄ）（Ｓ）（Ｓ）

〈Ａ〉〈Ｂ〉〈Ｍ〉〈Ｒ〉

 

I also can't tell whether the is supposed to be black, grey, or something purposely and cleverly in between.

[Lance]

I predict generous use of these bullets in the near future.

 

to 96 Street. to Forest Hills–71 Avenue. to Broad Street. <M> to Bay Parkway.

 

It’s conceivable that in some far off future, there will be more routes than letters and numbers, and the MTA will be forced to distinguish them by shape (circle versus diamond) and/or by a second letter. Similar routes might share a letter and become distinguished by shape: ⟶ <A> . The freed-up letters would go to newly minted routes like 168 Street–Washington Heights to Voorhies Avenue–Sheepshead Bay via 8 Avenue/Worth Street/Utica Avenue.

They could always go back to double-letters for full local routes like the , and .

 

I wonder if there were multiple complaints made to the about weekend Lex service that they have restored weekend service from 20 minute headways back to the as-originally assigned 12 minute headways...

 

Whenever there was insufficient service the would have these insane gaps in service since it would practically be running by itself on the weekends (we all know the tourists dont really take the ...)

Who knows. The lack of any construction work on the Lexington Ave and White Plains Rd lines should allow trains to run normally.

 

Thank you very much, Seven! This update has really brightened my week!

 

I can only think of adding the following bullets to cover all post-1979/1985-reform lines:

 

（Ｂ）（Ｄ）（Ｓ）（Ｓ）

〈Ａ〉〈Ｂ〉〈Ｍ〉〈Ｒ〉

 

I also can't tell whether the is supposed to be black, grey, or something purposely and cleverly in between.

The normal shuttle is colored dark slate gray, while the Canarsie line is colored light slate gray. The bullet may be slightly darker here than it is in reality, but that's not really a pressing issue.

 

As for the remaining diamond bullets, they will be added in another update.

[Porter]

The normal shuttle is colored dark slate gray, while the Canarsie line is colored light slate gray. The bullet may be slightly darker here than it is in reality, but that's not really a pressing issue.

 

 

As for the remaining diamond bullets, they will be added in another update.

 

I suppose it's not worth distinguishing the dark and light grey bullets on this site?

 

I look forward to the new update!

[CenSin]

As for the remaining diamond bullets, they will be added in another update.

The sizes are currently inconsistent, and should probably be worked on as well:

 

Ideally, these bullets would be SVG (since support for it is nearly universal now with the death of Internet Explorer 6, 7, 8, and soon 9 and 10). The CSS style for the diamond bullets could be…

max-height: 1em;

…so that it matches the size of the text it is inlined with. Circular bullets should be smaller, so that their weight is visually similar to the diamonds. The are good as they are right now.

 

Formulas for sizes (width and height) based on scaling factor S:

Diamond: S√2

Circle: 2√(S÷π)

 

For example, a circle that has a height of 1.12837917 (S=1) would have a corresponding diamond with the height of 1.41421356. The area of the circle would be equal to the area of the diamond giving them both equal weight.

 

Or if you wanted to, you could start out with a diamond and create a slightly smaller circle based on this formula:

Circle: ∜8÷√π×S ≈ 0.94885000×S

 

In CSS, the circle bullets would be:

max-height: 0.94885em;

The way the looks compared to the is downright anorexic currently.

 

 

EDIT: If not using SVG, pixel-aligned designs should have the circle be 1 pixel less on each side compared to the diamond. A 20-pixel high diamond would have a corresponding 18-pixel high circle. It doesn’t obey the formulas above, but makes for crisper graphics on displays with large pixels. (Font designers have to deal with this crap all the time.) On an Apple Retina display, the math starts working out a little better as we have higher pixel density to work with, and we can obey the formula again. A 39-pixel high diamond would have a corresponding 37-pixel high circle. An 80-pixel high diamond would have a corresponding 76-pixel high circle (for the day when 8K displays become commonplace). The overriding rule is, however, to always shrink by the same number of pixels on each side. size_of_diamond−size_of_circle should be divisible by 2.

Edited June 4, 2016 by CenSin

[P3F]

They could do a combo of numbers and letters, like (A1) and (A2).

[Calvin]

Was there a G/O on the today? I was at Canal St and the to Broad went to Chambers St instead

[MHV9218]

Bad C/R on the I just had. Won't name car numbers or anything but not a good job. Made no announcements from Jay St through West 4th St. despite the leaving the FIND on the 8th Ave program. York St. was announced as High St., etc., and then when he shut the FIND off, it booted back up to 23rd St. on the IND while we pulled into 2nd Avenue. Still no announcements or clarification. People had no idea where the train was going or what stop they were at. I heard one person at West 4th say "what? We were just at 23rd St!" Not great information. 

[Daniel The Cool]

Was there a G/O on the today? I was at Canal St and the to Broad went to Chambers St instead

Stalled train at Broad

[Lance]

Bad C/R on the I just had. Won't name car numbers or anything but not a good job. Made no announcements from Jay St through West 4th St. despite the leaving the FIND on the 8th Ave program. York St. was announced as High St., etc., and then when he shut the FIND off, it booted back up to 23rd St. on the IND while we pulled into 2nd Avenue. Still no announcements or clarification. People had no idea where the train was going or what stop they were at. I heard one person at West 4th say "what? We were just at 23rd St!" Not great information. 

Not that this an excuse, but I don't believe there is a - Euclid Av to 145 Street via Delancey St option in the 160s. Even then, (s)he could've used the 168 Street via Delancey option and reset the system at W 4 Street. They could've also used the usual "will not stop" setting for the normal Cranberry stations. Either way, there is no reason why this conductor neglected to make any kind of announcement regarding the service change.

[Around the Horn]

Not that this an excuse, but I don't believe there is a - Euclid Av to 145 Street via Delancey St option in the 160s. Even then, (s)he could've used the 168 Street via Delancey option and reset the system at W 4 Street. They could've also used the usual "will not stop" setting for the normal Cranberry stations. Either way, there is no reason why this conductor neglected to make any kind of announcement regarding the service change.

Yup. Conductors will put either the 145 St via Cranberry or the 168 St via Delancey option up.

 

When I rode the Saturday to get to SummerStage in Central Park, the conductor had the 168 St program and was manually making announcements. I wonder if it is possible to manually announce 145 St "over" the automated announcements without disabling them?

 

Also I wonder how hard it is to code new automated announcements in the FIND system. You'd think they would have made a 145 Street via Delancey program before the G/O started. (I guess this could be a use for the new WiFi)