Queensland UTC +10
Terms of use Privacy About us Media Contact

Links

Author Topic: New stop -not communicated or documented in timetable  (Read 1173 times)

Offline pangwen

  • Member
  • *****
  • Posts: 58
New stop -not communicated or documented in timetable
« on: October 04, 2016, 07:28:57 AM »
On the 130 this morning and the driver randomly picked up somebody from the stop at Pinelands Rd/Barney St. Didn't think much of it (it wasn't an express stop but I thought the driver was just being nice to someone who didn't know that). However, I just heard over the driver radio that this is actually a new express stop and that all services that drive past (inc P129, 131, P137, P141 and 151) must now stop there.

 Not sure why there was little/no communication (it's still not on the tl website and there didn't appear to be A frames advertising the stop)  and the go card readers are still not programmed to include the stop. Seems like a bit Of a rushed implementation.

Offline CQRail

  • Member
  • *
  • Posts: 13
Re: New stop -not communicated or documented in timetable
« Reply #1 on: October 04, 2016, 03:44:44 PM »
Seems like a pointless addition considering the Pinelands stop is 500-650m away outbound/inbound and Hellawell is 550-750m inbound/outbound in the other direction. Even though it may only add an extra minute or two, the 130 is a long enough route without additional stops.

The Translink website upon searching for the stop ID shows all those sevices stopping there.

http://jp.translink.com.au/travel-information/network-information/stops-and-stations/stop/010201

EDIT: It came into effect today.

http://translink.com.au/service-updates/95061
« Last Edit: October 04, 2016, 03:52:18 PM by CQRail »

Offline City Designer

  • Member
  • *****
  • Posts: 107
Re: New stop -not communicated or documented in timetable
« Reply #2 on: October 05, 2016, 01:35:32 PM »
TransLink announced it a few weeks ago taking effect today.

Seem redundant as Barney Street does not have a safe crossing point within proximity to the stops.

Offline City Designer

  • Member
  • *****
  • Posts: 107
Re: New stop -not communicated or documented in timetable
« Reply #3 on: October 05, 2016, 05:00:07 PM »
The same thing has happened with route 350, which now services Glenrosa Road RED HILL. No change to the pdf timetable and no upgrading to 'express top' status.

Offline SurfRail

  • Global Moderator
  • Member
  • *****
  • Posts: 7312
Re: New stop -not communicated or documented in timetable
« Reply #4 on: October 05, 2016, 05:12:35 PM »
As an interesting parallel, you wouldn't even know the 310 was an express service reading the timetable.  Bit of an aberration now as the only BT timetable in the "everybody else" format.

http://translink.com.au/sites/default/files/assets/timetables/161004-310,N310.pdf
Ride the G:

Offline City Designer

  • Member
  • *****
  • Posts: 107
Re: New stop -not communicated or documented in timetable
« Reply #5 on: October 05, 2016, 05:57:22 PM »
The 310, N310 timetable is in private operator format due to the N310 being a private operator route.

The N310 is also the only NightLink route that uses an express stopping pattern.

Offline SurfRail

  • Global Moderator
  • Member
  • *****
  • Posts: 7312
Re: New stop -not communicated or documented in timetable
« Reply #6 on: October 05, 2016, 07:05:22 PM »
I think it's ridiculous there is more than one format period.

Who actually produces the timetables?
Ride the G:

Offline City Designer

  • Member
  • *****
  • Posts: 107
Re: New stop -not communicated or documented in timetable
« Reply #7 on: October 05, 2016, 11:47:09 PM »
The private operator timetables are produced by Transit Graphics.

I don't know who produces the Brisbane Transport timetables but I much prefer the older style format.

 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 


“You can't understand a city without using its public transportation system.” -- Erol Ozan