Jump to content

dkupf

Veteran Member
  • Posts

    231
  • Joined

  • Last visited

Posts posted by dkupf

  1. What are your opinions regarding a Bx7/Bx9 switch north of 225 Street?

     

    Yes, local bus service would duplicate the subway between 215 and 231 Streets.  But local buses have short-haul riders, and may reflect actual ridership patterns and trends.

     

    It all depends on the amount of people who currently transfer between 225 St and 231 St.  Would it increase or decrease?

     

    Also, would such a change increase or decrease ridership?  How would it affect ridership on the 1 and A Trains?  Or would it simply shift riders around for better or worse?

     

    These are things the service planners, at the lower levels of NYCT, must examine.  But they have do it objectively.  In other words, they have to ask as to what must be done in order to implement the best strategy that MAXIMIZES OPERATING EFFICIENCY.  Not to fear their supervisors, and give lame excuses as to why the status quo should be maintained.

  2. An NYCT Staff Summary dated February 27, 2008, titled "Request for Public Hearings for New Bus and Subway Service Proposals" discussed the current B32, originally designated as the B62. (Bear in mind that the current B62 didn't exist at the time.)

     

    The proposed span was weekdays 5am-1am, weekends 8am-10pm.

     

    It followed the current routing of the B32 south of Newtown Creek (except that it would have served the Bedford Ave L-Train Station in BOTH DIRECTIONS). North of Newtown Creek, however, it would have served Grand Central Terminal via the folowing routeing:

     

    To Grand Central: Pulaski Bridge, 11 St, 48 Ave, Center Blvd, 50 Ave, Queens Midtown Tunnel, E 37 St, and Park Ave.

    From Grand Central: E 42 St, 2 Ave, Queens Midtown Tunnel, 11 St, Borden Ave, 2 St, 50 Ave, Center Blvd, 48 Ave, Vernon Blvd, 50 Ave, Jackson Ave, 11 St, Pulaski Bridge.

     

    Proposed Implementation: Fall 2008.

     

    There were 10 other proposals throughout the NYCT network. All eleven would have cost $29.4 million annually.

     

    Then came the Great Recession. 'Nuff said.

  3. Of course you do - It's your proposal !

    See here..... The point is, you can believe whatever you want....

    But when you come on here boasting about how superior your proposal is, that's a different story..... One is an opinion, one is (stated like it's) fact..... 

     

    As far as the rest of what you say here.... Well, 90% of the B18's ridership isn't really saying much, compared to how much ridership the B13 had (before the B13/B18 combination)...... You believe service should be put back on Cypress, that's fine for you, but I don't - I'm not gonna waste too much energy making a counter-argument already made (by Q23).... 

     

    The gap b/w 61st & 64th is negligible, and IMO, isn't worth arguing....

    Furthermore, you say too many Q59 riders would be severely impacted & inconvenienced (lol)..... My question is a simple one, because I happen to know how riders tend to utilize the Q59 -  and that is:

     

    What Q59 riders would be severely impacted & inconvenienced? 

    It's not the Williamsburg folks, because these aren't the people that make up for "too many riders" on the route riding to Queens Blvd/Grand.... and it isn't the Maspeth folks, because they'd still have the Q58/LTD along Grand.... There aren't near as many Q59 riders from the west that use the Q59 along Grand (b/w 64th & QB, not inclusive)..... Most of the patrons along Grand itself (within Queens) either seek the 59 b/c it is simply just another bus that takes them to QB, or seek Q58's to QB [or past QB, towards Flushing].....

     

    The Q59 is supplemental along Grand av in Queens.... I do not believe ridership would be discouraged, b/c buses would still head out to QB (albeit not along Grand).... The masses that get off at Grand/QB on the 58/59 either take the subway, or walk due east towards the mall(s)....

     

    Await your response....

     

    I'm talking about ALL of the CURRENT Q59 riders.  How many do you think would have their travel time increase?  I believe it would be between 25% and 50 %!  That's much too many for a service change like this.

     

    And how many do you think would be forced to transfer?  I think that it would be between 10% and 25%!  That's much too many for a service change like this.

     

    Based on the aforementioned, the service planners would soundly and logically reject this idea.

     

    My proposal leaves the Q59 intact, except for the short extension via 62 Dr/63 Rd due to the breakup of the Q38.

  4. 1- That's all well & good, but I wouldn't keep the 38 as is....

     

    2- I don't see what you're saying here....

    I have a (split) 38 running along Eliot, to QCM..... It makes no difference whether the 59 or the 38 runs along Eliot, to QCM - Unless you're arguing Williamsburg/Brooklyn necessarily needs direct access to QCM via a Q59 on Eliot (which I can't say I agree with)..... Personally, I think Ridgewood can/would benefit from direct access to QCM, moreso than Williamsburg (I'd say most those folks are concerned with getting to Union Sq & Manhattan (in general) than anywhere around that part of Queens).....

     

    What I'd aim to do with the Q59 is to (try) to make it less supplemental (because again, I think the Q58/LTD is all that is needed along Grand (Queens side))..... Granted, the 59 I have on the map is indirect, but the only other real alternative is to keep buses on Metropolitan all the way from Brooklyn/Queens border to 69th st, and run via the Q38 Penelope branch that way - but that would be worse (as far as supplemental-ness is concerned), because the 54 doesn't need a supplement for that much of the route [service on the 54 is another issue I won't get into right this second])..... Well that, and skipping industrial Maspeth (along Grand av; around by the depot, etc.)....

     

    I wouldn't do anything to the Q58/LTD, so yeah, they'd stay on Grand....

     

     

    Because it leaves the Q59 alone, because it restores Cypress av service, Oh, so what....

    How superior is your plan really when you have very weak reasons as to why you say it's supposedly so (and the fact that you even have to reiterate it).....

     

    All this is, is a *my proposal is better than anyone else's because I say so*, and nothing more...

    Which is a lazy way of discussing & defending your proposal.....

     

    But shifting the Q59 would create a service gap on Grand Ave between 61 St and 64 St, discouraging ridership. Besides, too many current Q59 riders would be severely impacted and inconvenienced.

     

    Believe it or not, Cypress Ave represented 90% of the old B18's ridership, when the service planners originally claimed 25%. They later admitted to this deception. My proposal corrects this injustice.

     

    The B13 costs more now to operate than before its extension. Sending it via Cypress Ave and would make the B13 less expensive to operate and would be significantly faster, encouraging ridership.

     

    So, yes, I do believe my proposal is superior.

  5. Then, it's settled.

     

    When it comes to Boston Road, the Bx30, and the Bee-Line 52, the routings should be maintained.

     

    Probably the best thing I said in this thread, eh?

     

    LOL.

     

    But I continue to insist that the Bx16 should operate via E 233 St between Webster and Baychester Avenues, with a Bx29 extension as a replacement for Bx16 Baychester/Nereid Avenues service.

  6. It's okay that the M5 could operate from the GWB Bus Terminal all the way to South Ferry, but not okay to extend the B7 to Fresh Pond?  Sorry, but that logic doesn't fly with me.

     

    The B26 would still operate to Ridgewood Terminal.  Just every other trip during most hours, except the Weekday AM Peak, would operate to/from Bway-Halsey St.  In fact, with the addition of the B7 extension, there would actually be the same or more bus service on Halsey St east of Bway during most hours.

     

    And, as that the B7 extension would serve as a partial replacement of B20 Fresh Pond service, it would be, overall, less expensive to operate.  A win-win situation!

  7. Brooklynbus and Nyctransitman floated this idea, but I'm willing to see it through.

     

    As most of you know, the service planners have been wanting to discontinue B20 Fresh Pond service for years but couldn't think of alternatives to mitigate the expected burden on riders.

     

    Here's what the two suggested:

     

    B20 - Cut back northern terminus to Broadway-Van Sinderen Ave.

    B7 - Extend via Halsey St, Wyckoff Ave, and the current B20 routing to 67 Ave-Forest Ave.

    B26 - Operate every other bus during most hours, but not the Weekday AM Peak, to Broadway-Halsey St.

     

    Bus requirements would be less than today, e.g. 4 less during the Weekday AM Peak and weekday midday, while increasing the mobility for central Brooklyn riders.  A win-win situation for both parties.

     

    Yes, there will be some losers, but many more would benefit.

  8. I have been always curious about ridership levels along Boston Rd within the NYC city limits.  How is it?  Is service just right?  Should there be additional service and/or span within the city limits?

     

    I would change the Bee-Line 60, 61, and 62 to boarding only northbound, alighting only southbound.

     

    Should this be done, the Bx30 would have to be restructured to operate between Fordham Plaza and Ropes Ave-Boston Rd.

     

    I would also extend the Bee-Line 52 to operate via the current Bx30 within Co-Op City to Erskine Place with unlimited boarding and alighting privileges, but MUST have similar frequencies and span within the NYC city limits as the current Bx30, with reimbursement.  (In this case, I think that it would be less expensive for the MTA to pay Bee-Line than operating a separate route.)

     

    However, if riderhip levels along Boston Rd are relatively poor, then I would prefer to maintain the status quo.

  9. As I said, I also hate SEPTA's schedulers.

     

    But I do think that SEPTA's service planners are relatively better than the NYCT.  At least SEPTA's planners are willing to try different things in order to get service to their standards.  BTW, I don't like their cost recovery ratio "standards" either, because there will always be a bus route that doesn't meet them.  But I digress.

     

    NYCT and MTA Bus have "guidelines", but they refuse to publish them.  But what I do know is that if ridership doesn't meet all or part of certain minimums at the maximum load point (MLP), the point where a certain route has the most riders on board, NYCT and MTA Bus would simply eliminate span and/or discontinue the route.  A major change in span (more than plus-or-minus 59 minutes) and/or route discontinuation is subject to a "public hearing".

     

    But NYCT and MTA Bus can get around this by incrementally adding or eliminating span 59 minutes at a time.

  10. But the service planners here don't want to try anything.  They refuse to look at the system holistically.  For example, the northern terminus of the Bx46 is 1/2 mile from The Hub.  They claim that there wasn't enough money, which is far from the truth.

     

    The service planners only do comprehensive studies when they are told to do so by the Brass, which is rare.  And when comprehensive studies are done, the service planners present their results on a take-it-or-leave-it basis, resulting in no changes being made.

     

    In fact, the changes that occurred in the eastern Bronx in June 2010 was the result of a comprehensive study, and we all know what happened when it was implemented.

     

    This is why the service planners prefer to do incremental changes that affect one or two routes, while ignoring major service gaps, especially in the Bronx.

  11. I would rather be in favor of the Q59 along Eliot for two reasons

     

    1. Helps out the Q38, which has it's problems

    2. Maintains service to QCM (one of a few major destinations)

    The Q58 LTD can stay on Grand

     

    As for Penelope Avenue, just let the Q38 run between FP Road and Forest Hills, and that's it.

     

    Try telling that to the people of Maspeth, who would lose Q59 service.  And try telling that to current Q59 riders, who would be forced to transfer to the Q58.

     

    This would also create a service gap on Grand Ave between 61 St and 64 St, as that Fresh Pond Rd goes as far north as Flushing Ave.  (This is why the Q39 uses 61 St.)

     

    My proposal is superior, because it leaves the Q59 alone (except for the short Q59 extension via 63 Rd/110 St/62 Dr).

  12. I think that Maspeth residents will be in an uproar if the Q59 is taken off of Grand Ave.

     

    Here's what I would do:

     

    Q59 - Extend via 63 Rd, returning via 62 Dr.

     

    Q72 - Takes over the Penelope Ave-Juniper Valley Rd portion of the Q38.  Southern terminus at Fresh Pond Rd-Metropolitan Ave.

     

    Q38 - Extend Eliot Ave portion via Metropolitan Ave, Forest Ave, and the current Q39 routing to Cooper Ave-60 Lane.

     

    Q39 - Operate via Fresh Pond Rd and the current B13 routing to the Cypress Hills station.

     

    B13 - Operate via Cypress Ave between Cypress Hills St and the Ridgewood Terminal.

     

    B52 - Extend via Gates Ave and the current B13 routing to Fresh Pond Rd station.

     

    This would keep the Q59 on Grand Ave as well as restore Cypress Ave service, which was taken away over 10 years ago when the B18 was eliminated, something which noone at the public hearing supported.

     

    BTW, NYCT later admitted that Cypress Ave represented 90% of the B18's ridership.

     

    Currently, the B13 costs more now to operate than before the B18's elimination.

  13. And maybe extend the route [the Q19] to 2nd Street.

     

    That's a great idea.  But it should operate bidirectional via Hoyt Ave and 21 St.  This would give the people who live in the Astoria Houses access to Astoria Park and their large swimming pool for the first time, especially during the summer months.

     

    Another great idea to boost ridership and revenue, making the borough more accessible by mass transit.

    what do you have to say about this and elimnating 1 branch of the q16 for extending the q34

    http://www.timesledger.com/stories/2013/47/busrouteflushing_bt_2013_11_22_q.html

     

    It's a good idea, but I would operate the Q34 between Flushing and Fort Totten ONLY, and operate daily, in order to maintain good service reliablility.  Additional Q25 service would be added south of Flushing to compensate for the loss of the Q34.

     

    The Q16 could then have is Francis Lewis Blvd branch eliminated, and the Utopia Pkwy branch rerouted from Fort Totten to Beechhurst.

  14. Do you know where most people take the Q67 from Middle Village to?

    Do you know there's industrial workers that still utilize the Q67 on weekends?

    Do you know why it runs on weekends?

    Do you know how much worse youre making the situation?

     

    I will admit, Q67 Ridership is low, but you are making the situation worse by eliminating the Q67, making everyone's commute either impossible or worse.

     

    I know, but try telling that to the service planners. They just care about the numbers.

  15. HELL NO.

     

    You'd be forcing 3 types of riders problems.

     

    Riders in the industrial portions seeking the (M) at Middle Village would need to take the Q67 to the Q18 to the (M) (Do not even bring up making a three legged transfer. 

     

    People in Middle Village seeking the train to the city would have to make their way through a circuitous Q18 to have a longer trip on the train (7) .

     

    Late Night Industrial Shift workers and Weekend shift workers would be left without service.

     

    You have no where to layover the Q67 in the Grand Avenue vicinty.

     

    The MTA service planners can eliminate Q67 weekend service tomorrow due to its low ridership. I'm just trying to make the best of a bad situation.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.