Newark, Delaware Extension - SEPTA Connection

Discussion related to DC area passenger rail services from Northern Virginia to Baltimore, MD. Includes Light Rail and Baltimore Subway.

Moderators: mtuandrew, Robert Paniagua, therock

Posts: 571
Joined: Mon Mar 30, 2009 4:51 pm
Location: Wayne, NJ NJTR-MP (20.8)

Re: Newark, Delaware Extension - SEPTA Connection

Post by CentralValleyRail » Sun Oct 29, 2017 1:48 am

Arlington wrote:WILMAPCO approved its study results in September:" onclick=";return false;
Link seems to be dead for me.

User avatar
Posts: 1303
Joined: Sat Oct 24, 2015 5:18 pm
Location: Baltimore, MD

Re: Newark, Delaware Extension - SEPTA Connection

Post by STrRedWolf » Sun Oct 29, 2017 10:51 am

Try again, it works for me.
"The last and final stop is BALTIMORE PENN STATION." I can has MARC V?

Posts: 3994
Joined: Wed Jun 02, 2004 7:51 am
Location: Medford MA (was Arlington MA and Arlington VA)

Re: Newark, Delaware Extension - SEPTA Connection

Post by Arlington » Sun Oct 29, 2017 12:10 pm

Big PDF takes a while for its dowload and opening to get negotiated, is my guess.
"Trying to solve congestion by making roadways wider is like trying to solve obesity by buying bigger pants."--Charles Marohn

Posts: 267
Joined: Mon Oct 09, 2017 7:13 pm
Location: HFD

Re: Newark, Delaware Extension - SEPTA Connection

Post by daybeers » Wed Nov 28, 2018 2:02 am

Any updates on this? That PDF was a little difficult to understand.

Posts: 404
Joined: Mon Jan 09, 2017 11:48 am

Re: Newark, Delaware Extension - SEPTA Connection

Post by andrewjw » Wed Nov 28, 2018 2:24 pm

Build Scenario 1, 2 & 3

In addition to the 2040 no-build scenario, three build scenarios were evaluated. The first build scenario is based on information provided by MTA which assumed doubling the frequencies of the Penn Line during peak hours for testing purpose only. This scenario was used to determine an upper limit for the potential demand for the corridor, although operating at this increased frequency would be infeasible based on current capacity restrictions. Comparing the transit headways coded in the MWCOG, BMC, and DVRPC models, the proposed schedule reduces the headway by 50% and off peak headways are unchanged. Standard practice is to assume wait time is to be half of headways. Thewait time was reduced by half between TAZ pairs served by the extension for peak periods. This build scenario assumes the rail route is connected but does not account for the speed differences between MARC and SEPTA.

The second build scenario differs by assuming transfers at Newark for both peak period and off peak period. The transfer time is added by identifying the arrival and departure times for MARC and SEPTA service. Additional boarding time was added to TAZ pairs that are served by the extensions that use the Newark station.

The third build scenario is based on the new schedule “MARC Exercise #1a – schedule with express service.xlsx” provided by WILMAPCO. The new schedule was compared with the first build scenario and additional wait time was added to the TAZ pairs crossing through the Newark station. The seven- to eight-minute transfer time at Newark in the daily last run for both northbound and southbound was not accounted for due to model limitations. The detailed headways for all scenarios can be found in Table 4.
From the above (pages 6-7)

Post Reply

Return to “DC - Maryland - Virginia Area Passenger Rail: MTA(MARC), VRE, WMATA(Metro)”