My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
4.5. SR 10-19-1998
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
1993 - 1999
>
1998
>
10/19/1998
>
4.5. SR 10-19-1998
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:33:23 AM
Creation date
2/5/2004 7:56:36 PM
Metadata
Fields
Template:
City Government
type
SR
date
10/19/1998
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
22
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
This technical memorandum documents an illustrative response to comments made by members <br />of the Northstar Corridor Development Authority Board at their meeting of Septmber 3. <br /> <br />Passenger Rail Service "Concept B" incorporates most of the features of the original concept (to <br />be designated "Concept A"), but also reflects changes made to accommodate the Board's <br />comments. The principal adjustments made to the first service plan are: <br /> <br />Operation of two southbound moming trips from St. Cloud to Minneapolis, <br />arriving at peak commute times, and two northbound evening trips from <br />Minneapolis to St. Cloud, departing at peak commute times. This feature <br />augments the previous concept of only one through trip to and from St. Cloud <br />during peak periods. <br /> <br />Operation of one through peak period trip between Minneapolis and St. Cloud in <br />the "reverse peak" direction. This feature makes possible an arrival at St. Cloud <br />during typical work start hours, and a departure from St. Cloud during the <br />evening peak. <br /> <br />Possible location of the central maintenance facility at St. Cloud rather than at. Elk <br />River. <br /> <br />Additional comments received from the Board referred to the desirability of evening service, <br />primarily on Fridays and Saturdays, for various kinds of events, such as large gatherings for <br />sports events. That particular aspect is not addressed in the example schedules provided here <br />since large-scale public events can begin and end at widely varying times. It is assumed that <br />extra trains will be operated for these events on a schedule that meets the needs of these events. <br />While they are not presented on the regular weekday schedule, an allowance will be made for <br />them in the operating cost estimates when they are prepared. <br /> <br />Absent Board comment, a revised weekend and holiday timetable has not been prepared at this <br />time. It is assumed that the previous concept of three daily scheduld round trips (morning, <br />midday, late afternoon) will be sufficient for the study's purposes at this point. <br /> <br />Departure and arrival times have been adjusted to reflect a "memory" timetable concept, based <br />on a half-hour module. For example, all trains departing St. Cloud leave at either 5 or 35 <br />minutes after the hour. All trains arriving at Minneapolis arrive either on the hour or at half-past. <br />The same is true at intermediate stations. For example, all Northbound trains at Anoka are on <br />the hour or half hour. This concept permits easier memory of train times by the public, and, very <br />importantly, makes coordination with local bus services easier, provided they also use memory <br />scheduling on a compatible headway. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.