Laserfiche WebLink
3. Service Assumptions <br /> <br />As demand forecasts have not yet been run for this service, it is being assumed for purposes of <br />beginning this evaluation that beyohd Elk River, the Northstar Corridor may best be served by an <br />"intercity" pattern of all-day passenger service. "Commuter rail" service, typically, consists of <br />largely peak-period, unidirectional trains oriented to people making work trips to the CBD in the <br />rush hour. <br /> <br />This initial service concept assumption is based on a couple of observations. One is that St. <br />Cloud itself is, at 65+ miles, beyond the distance at which a large number of peak-hour work <br />trips destined to the Minneapolis CBD are likely to be generated. A second is that St. Cloud, <br />while not large, and not apparently a "bedroom community" for the Twin Cities, is a university <br />city and regional service center, generating trips for a variety of purposes. University towns, <br />especially, tend to generate more passenger traffic per capita than other cities their size (examples <br />which come to mind are Davis and San Luis Obispo, California, and Eugene, Oregon). This kind <br />of passenger traffic is not typically oriented primarily to peak travel periods alone. It represents a <br />combination of trip purposes and times, suggesting that a diversity of potential travel times <br />· offered to the traveling public will tend to meet needs better than purely commuter-oriented <br /> scheduling. Accordingly, mornir4g, midday and evening trips, in both directions, are hypothesized <br /> in this concept. The early and late trips, however, are designed to fit into classic "commuter" time <br /> slots. Third, it is interesting to not that some "commuter" rail systems now actually serve a <br /> market which is not predominantly composed of peak hour, peak-directional trips to and from the <br /> regional CBD; San Francisco's Caltrain, Miami's TRI-RA/L, and some lines of the SEPTA <br /> "Regional Rail" system in Philadelphia provide examples of this. <br /> <br />It is recognized that no decision has been made as whether the northern terminal of the Northstar <br />Corridor rail service will be St. Cloud or Rice. In the example service timetables that are <br />presented here, it has been assumed for illustrative purposes that the service will terminate at a <br />station in Downtown St. Cloud. With n'finor adjustments, however, the concept, will work just as <br />readily with a terminal in Rice. <br /> <br />In St. Cloud, the former Northern Pacific station, located on the BNSF mainline, is used by <br />AMTRAK as the passenger station for the single daily Empire Builder in each direction. This <br />station is located on the north/east bank of the Mississippi, across the river from Downtown in a <br />semi-industrial area, in the middle of the wye formed at the junction of the former Great <br />Northern Monticello-St. Cloud line, and the GN/NP joint mainline (also sometimes referred to as <br />the "Elk River" Line). The Great Northern Bridge is still in use, and could be used to take <br />Northstar Corridor trains across the Mississippi directly into Downtown St. Cloud. Here, it <br />would be about a 20-minute walk to the St. Cloud State University campus, and close tO the <br />county courthouse and central business activities of the city. It would also be possible to closely <br />integrate the rail service into the city transit network, in a more intensive way than would be <br />possible across the river. Trains could continue to the GN yard area for layover and servicing, <br />but passengers would be handled downtown. The old station could be retained as an "East St. <br />Cloud" stop for both the Empire B~tilder and the corridor trains, but other than for nostalgic <br /> <br /> <br />