RAIL - Back On Track
September 08, 2010, 07:55:40 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
Latest:
MEDIA RELEASES click here!
HOT TOPICS:
Citizens' Public Transport Forum
New Fare Strategy
Go Card & TransLink fares
 
   Home   Help Search Calendar Articles Login Register CPTF TransLink QR My Go Card CRR  
Pages: [1]   Go Down
  Print  
Author Topic: Introduction  (Read 341 times)
ozbob
Administrator
Member
*****
Offline Offline

Posts: 13586



WWW
« on: January 21, 2010, 12:49:58 PM »

Just assuming you had a blank canvas and was asked to put together the timetable for your lines of interest.

How would you do it?  Frequency, timings, patterns.  Things to note, avoid, ensure happen.

Please post your suggestions, constructive comments, discussion and ideas.  

 Study

« Last Edit: January 21, 2010, 01:01:27 PM by ozbob » Logged

Jon Bryant
Guest
« Reply #1 on: January 21, 2010, 04:03:25 PM »

It has to be frequency based pesk, shoulder and off peak
Logged
tramtrain
Member
*****
Offline Offline

Posts: 3062


Intergrated public transport vision for Brisbane


« Reply #2 on: January 21, 2010, 09:04:13 PM »

Does this mean new services or coming? Or is this just a re-arrangement?
Logged

“New ideas pass through three periods: 1) It can’t be done. 2) It probably can be done, but it’s not worth doing. 3) I knew it was a good idea all along!” — Sir Arthur C. Clarke
Posts are my independent commuter view- not RailBOT's or other party.
tramtrain
Member
*****
Offline Offline

Posts: 3062


Intergrated public transport vision for Brisbane


« Reply #3 on: January 21, 2010, 09:18:11 PM »

1. Clock-face or as close to clock face as possible.
2. Increase the frequency on all major lines, aiming for Perth-standard.
3. Two tier timetables across the network, all day.

A rule of thumb. Perhaps people could suggest their own.
I think 30 minutes is a reasonable time to do a journey by commute.

"If a train takes more than 30 minutes, stations after it should be served by an express".
Logged

“New ideas pass through three periods: 1) It can’t be done. 2) It probably can be done, but it’s not worth doing. 3) I knew it was a good idea all along!” — Sir Arthur C. Clarke
Posts are my independent commuter view- not RailBOT's or other party.
ozbob
Administrator
Member
*****
Offline Offline

Posts: 13586



WWW
« Reply #4 on: January 22, 2010, 02:00:12 AM »

Quote
Does this mean new services or coming? Or is this just a re-arrangement?

Blank canvas, complete rewrite, modify the existing, what ever YOU think is the way to go ...
Logged

nikko
Member
*****
Offline Offline

Posts: 465


« Reply #5 on: January 23, 2010, 01:27:14 PM »

I'd aim to create good transfers between all lines (Maximum of 10min wait) without the need to run from one platform to another.

Consistent express stopping patterns and short-working services are also a must.

Logged
dwb
Member
*****
Offline Offline

Posts: 640


« Reply #6 on: March 12, 2010, 12:30:49 PM »

In all my discussions/surveys with people key issues have been value based... meaning they don't care so much on mode or look but the services should be:

 - safe
 - reliable
 - consistent (the icecream shop/ maccas principle - it doesn't have to be THE best, but it does have to be THE SAME each and every time)
 - frequent (dependant on role this might mean every 2-3mins or max up to every 15mins. In my mind 20mins is too long, even on Sundays on district routes)
 - fast enough in comparison to other modes (ie not necessarily faster in all cases but comparable)
 - affordable
Logged
somebody
Member
*****
Offline Offline

Posts: 2407


« Reply #7 on: March 12, 2010, 02:01:16 PM »

1. Clock-face or as close to clock face as possible.
near clock face is pointless.  It should be on the money, without little dithers, such as the 11:06pm Rosewood train ex Central, when trains normally come at :05  (Note, it's not so bad when it's in this direction.  It's when the dither is 1-2mins earlier that it's a real problem)

Also, I'd like it consistent between weekends and weekdays.

Consistent express stopping patterns and short-working services are also a must.
Not too sure about this off peak.  Definitely in the peak though.  And peak Caboolture line services which stop at Albion, Woolloowin, Nundah and Toombul have to become express through those stations.  I think off peak too, once Shorncliffe goes 15 minute frequency.
Logged

Rail should outrun road.
nikko
Member
*****
Offline Offline

Posts: 465


« Reply #8 on: March 13, 2010, 06:31:52 PM »

1. Clock-face or as close to clock face as possible.
near clock face is pointless.  It should be on the money, without little dithers, such as the 11:06pm Rosewood train ex Central, when trains normally come at :05  (Note, it's not so bad when it's in this direction.  It's when the dither is 1-2mins earlier that it's a real problem)

Also, I'd like it consistent between weekends and weekdays.

Consistent express stopping patterns and short-working services are also a must.
Not too sure about this off peak.  Definitely in the peak though.  And peak Caboolture line services which stop at Albion, Woolloowin, Nundah and Toombul have to become express through those stations.  I think off peak too, once Shorncliffe goes 15 minute frequency.

Just to clarify I didn't mean introducing more short-working services, I meant making them consistent (i.e. no more Manly/Thorneside, Redbank/Corinda during peak. One or the other only.)  thumbs_up
Logged
somebody
Member
*****
Offline Offline

Posts: 2407


« Reply #9 on: March 14, 2010, 10:34:17 AM »

Ah Ok.  I'd agree that would be nice, but I'm not sure if it's all that possible on the current infrastructure.  For the Ippy, once Richlands opens I would presume that would become the main (only) short working destination.  But on the Cleveland line, I doubt Manly could handle all the short workings required in peak.
Logged

Rail should outrun road.
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2010, Simple Machines LLC Valid XHTML 1.0! Valid CSS!