User talk:Hearmeout

Re: Service 912

Hi, I noted on your reply. Let's me clarify the statement regarding 912A/B. First and foremost, the official reason why 912E was discontinued was due to frequent congestions at Woodlands Centre Road (Custom Jam) which provided the irregular headway and frequency. Ask LTA for it. On top of that Service 913 was later amended away from Woodlands Centre Road as a justification of better serving the needs (removing the popular connectivity between Woodlands Checkpoint and Woodlands Int, leaving commuters cramming on Service 911). But this is just an attempt to mask the congestion at Woodlands Centre Road.

Regarding of the Bunching and Headway between 912 and 912A/B, (which I get the replied from LTA), 912A and 912B timetable is independent of 912. Meaning, when trip departing at WITH as 912, by right, 912A/912B shouldn't depart, but they had to depart. This is controversial and unlike the 912E format. I know, you know, everybody know, but apparently, fare transfer between 912, 912A, and 912B only at Woodlands Interchange is transferable (no new ride penalty imposed), but metric treat all three as separate service.

Next, WLDEP do deploy BD on weekends on feeder services (not part of negotiated contracts) when it at WTBI. After shifting to WITH, such deployment does not exists. There is weekends where 858 does not have bendy, which result in Woodlands Feeder having bendy cameo. This is thus the statement on why I said bendy lots had reduced or allocated (it's either-or situation).

Next, at WRI, all parking lots are Bendy accommodated. But with the upgrading, WITH only features one row of bendy (or half row only). This is the reason why WLDEP deploy Bendy on shift schedule with no/little break in between legs for most trip for services other than 912.

Due to the parking lot shortages - 912 layover at Alighting Berth for 5 minutes, 911 layover between Berth B5 and B6 (outside the TEL entrance), 913 layover outer lane at Berth B2 (if unable to filter and stop there, it will then proceed to Berth B9).

Regarding to depax - All ITH are configured only to allow depax at Alighting Berth. WITH is the exception where Boarding Berth B1, and B8 are configured to do dual role. At WTBI, 912A and 912B sometimes do depax away at Alighting Berth, at any random Boarding Berth. Similarly for 911/913 at WTBI, sometime they do depax and board at Boarding Berth at the same time. But after shifting to WITH, this had been strictly not allowed, because passenger cannot enter from outside at boarding berth (it's risky if no commuter wants to board).

I hope there is a better way to represent such information.

Supernutorcrazy (talk) 11:51, 4 April 2025 (+08)

History for Woodlands Service

Hi,

Notice that you had add in for routing "Temp Int" for all Woodlands Service between 2016 to 2021.

Given that most route history dropped "Temp Int" due to it still being the main interchange (even CCK Int is no longer called Temp Int" etc, which LTA had dropped too, the problem lies in Woodlands.

From 2016 to 2021 during the WRI → WITH upgrading, the current temporary int uses the bus stop code "46009", which makes sense for us to continue to use "Woodlands - xxx" for the routing. It is only on 13 June 2021, when WITH opened, WTBI uses the code "47009" which means, even through 925/M, 950, 961/M, and 965 didn't physically shifted, it was official amended to Woodlands Temp Int, and vice-versa, the rest of the service that shift to WITH was physically shifted, but officially not amended (bus stop code remains).

Omit the fact of these four bus stop code 46008/59008/75008/77008 (which is used for dual loop feeder - and to enable "transfer" between the variants/terminating trip).

So the question is should the route be stated as (1) "Woodlands - xxx" regardless of operating from WTBI/WITH (2) "Woodlands - xxx" for all, with "Woodlands Temp Int - xxx" only after 13 June 2021

Supernutorcrazy (talk) 17:15, 5 April 2025 (+08)

Re:

Noted on your reply regarding History Route for Woodlands services.

Regarding these services: 853#, 925#, 961#. These historical service are uniquely presented whereby the destination signs on buses are reflected as 853, 925, and 961 on Sundays/PH. But on eguide/Datamall, these services are denotes with the "#" suffix. Definately they are renumbered, but is it renumber from without the "#" or with the "#". I.e. 853 to 853M or 853# to 853M?

For 170X, the historical bus are denote by the plate (can't remember the colour use) with just "170", then follow by 170* (on EDS) and finally today uses 170X. Throughout, they use 170X on eguide. Do they renumbered? Furthermore 170X routing is unique. It seems like it originate from Kranji Stn and not Opp Kranji Stn since when I dont know, but it definately not even publish or updated.

For 225/410, the historical bus are denote by the green/white plate with just "225" and "410" which when using EDS, then denote by G/W suffix, with the plate exists. No official news/poster mention on renumbered. So did they consider renumbered from 225 to 225G/225W or do they not?

Supernutorcrazy (talk) 12:49, 6 April 2025 (+08)

135

Issok. What section are u up till?