Difference between revisions of "User talk:Wekelwrady"

From SgWiki
Jump to navigation Jump to search
m
 
(35 intermediate revisions by 7 users not shown)
Line 1: Line 1:
Just discuss below.
Just discuss below.
===Written explanation on BS07379: Improving Commuter Logic===
I will write my take solely focusing on the case of Lavender and its nearby CBD areas without taking any other example.
Lavender is an area that can be confusing for new/first-time commuters who are attempting wayfinding, because wayfinding is largely affected by the presence of two main roads: North Bridge Rd and Victoria Street. '''Commuters who may not be familiar usually have an incorrect impression that because 000 service stops at Victoria Street eastbound, 000 service would also serve Victoria Street westbound.''' However, we all know that only selected services serve Victoria Street westbound while the rest ply North Bridge Road. This is a huge flaw when the difference could not be told, and this case is not isolated to Lavender alone.
Thus, the routings of services 61, 107, 133, 145 and 961 has to be distinctively differentiated from the moment they depart BS07379 (Aperia) bus stop. A bus driver may not understand if the commuter asks whether North Bridge Rd services go to EW11 Lavender station. But if you ask a Service 2, 12, 33, 107, 133 bus driver, they will confirm that these go to EW11 Lavender station. This is also the reason why I did not label EW11 Lavender on BS01339 Bef Crawford Bridge as commuters need to know that North Bridge Road and Victoria Street bring them to different destinations.
This is in line with how the City Hall bus stops are listed. While Services 147 and 190 turn right into Victoria Street, they do not serve City Hall MRT as the station is not within the sight of CHIJMEs bus stop. Whereas Services 124 and 174 serve directly outside City Hall MRT along North Bridge Rd.
Why is BS07371 labelled with EW11 Lavender instead? Because the reason is simple: it is heading away from North Bridge Rd & Victoria Street. And as per explanation, there is a guided sheltered walkway connecting EW11 Lavender station. Therefore, the question is entirely reasonable and I feel that can be explained and broken down into detail with.
===Heads Up===
After I complete some of my work I will start to upgrade the rest of the existing bus stop templates. I aiming to complete it by end of February although it's thousands of bus stops. Cheers.


===User's Stance: Uploading of non-watermarked images===
===User's Stance: Uploading of non-watermarked images===
Line 36: Line 22:


I am supposed to be helping out at the trains page, but if editors can be more attentive, I hope I can continue my supposed schedule at the trains page.
I am supposed to be helping out at the trains page, but if editors can be more attentive, I hope I can continue my supposed schedule at the trains page.
===Feedback from social media===
 
Special trip departures and Short-Trip departures are too clustered - not spaced apart.
To correct with appropriate line spacing and more neat presentation of departures
==Re: Alternate Travel Option Wording==
* NS11: 962 Remarks: You can take the NSLFBB due to the long walking distance to Blk 680.
>> The walking distance may be on par with Opp Admiralty Stn bus stop as one need to turn left twice to Admiralty Stn bus stop, turn left again and walk down, cross the overhead bridge and further walk to Opp Admiralty Stn, whereas the walking path to Blk 680 bus stop is straightforward & direct (turn right and walk to road, turn left again to bus stop).
* NS12: 962->117/M 883/M Remarks: You can take the NSLFBB due to the long travelling journey to the station.
>> What do you mean long travelling time? Alternatively how about 965->Darul Mosque->Overhead bridge->169/117/883 to Canberra, will it be faster?


== RE: Alternate Travel Options==
== RE: Alternate Travel Options==
Line 65: Line 36:


As for the station layout map, I trying to figure out a way to translate 2D diagram to isometric view (Mathematics involved) for better clarity, so once that done I will slowly progressive roll out on most of the NSL and the eastern EWL. Didn't really have the accurate network layout for most station.
As for the station layout map, I trying to figure out a way to translate 2D diagram to isometric view (Mathematics involved) for better clarity, so once that done I will slowly progressive roll out on most of the NSL and the eastern EWL. Didn't really have the accurate network layout for most station.
===Improvements to counting buses by op===
Automatic calculator that monitors the deployment table(?)
== Fixing 184 Weekday Last Bus timings ==
42119 - 23:39<br>
42089 - 23:40   42071 - 23:37<br>
42149 - 23:41<br>
12099 - 23:43      12091 - 23:34<br>
12089 - 23:28   12081 - 23:34<br>
12079 - 23:45   17111 - 23:32<br>
17229 - 23:45<br>


== Re: Travel Time==
== Re: Travel Time==
I am planning to overhaul it, after considering how disruption take place.
I had updated the new travel time to reflect Hume, Punggol Coast and Teck Lee Station.
 
First of all, if a line is down, most of the time is section based, and this means, we can use a common template to syncronised the route based on the sector.
 
Regarding if there is a need for example Pasir Ris to Jurong East etc. I think should such breakdown incident happen FBB is a better option rather than using alternative bus service.
 
As for sectors, I havent analyse it.
 
With the implementation of Bus Service Pages, this make it easier as viewer can click on the bus service to see the other station it served and no need for a full list. :)


For the new upgrade template on bus service page, yes is correct. There isn't any much changes to the new templates.
*Bus Fleet - <code><nowiki>{{Col|xxx}}</nowiki></code>
*Bus Fleet - <code><nowiki>{{Fleet|fleet=xxx|model=xxx}}</nowiki></code>
*Special Departure/SWT - <code><nowiki>{{Col/1|xxx}}</nowiki></code> ← This was used because it didn't use the same format due to vertical alignment issue
*First/Last Bus - <code><nowiki>{{Bus/FBLB}}</nowiki></code>
**<code><nowiki>wd=/fr=/sa=/su=</nowiki></code> → stands for no weekday/friday/saturday/sunday columns
**<code><nowiki>fwd=/ffr=/fsa=/fsu=</nowiki></code> → first bus column for weekday/friday/saturday/sunday columns (used for skipping)
**<code><nowiki>lwd=/lfr=/lsa=/lsu=</nowiki></code> → last bus column for weekday/friday/saturday/sunday columns (used for skipping)
**order : weekdays →  saturdays → sundays → fridays


===Re:===
[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 08:02, 8 March 2025 (+08)
Yes, agree and thanks for the email to LTA regarding first/last bus timing. In fact, I also had to do it for MRT. The first southbound train at Yishun is not even Marina South Pier train (Marina Bay). I havent had time to compile for other lines if there is such inaccuracies because of work commitments and bus pages overhual to bring sgWiki to its best for public. but I faced backlashed on social media for my overhaul. ㅜㅜ.
 
Moving forwards, I also do not have much time left, as you can see I starting to take a step back (the last week), but nevertheless will continue to do what I can as and when.


==Re: Template standardisation==
==Re: Template standardisation==
Line 161: Line 117:
After analysing, the activation of FBB is normally between these sectors or consective sectors depending on the scale.
After analysing, the activation of FBB is normally between these sectors or consective sectors depending on the scale.


== Re: Images with destinations has to be shown ==
==Reply==
Noted on your Tampines Alternate Travel and 107/M.
 
(1) 107/107M. I had remove the "Revised Timing will be announced by operater" for Service 6, given that only GAS announced it only. SMRT also didn't announced the revised timing when 964 did not operates on Sundays either for New Year/CNY/Christmas.
 
(2) Alternative Travel
 
Looks ok. When I was doing Yishun Alternative Travel, I noticed most of it involve travelling to - Lentor/Springleaf/Pending for transfer to continue on to let's say JUR/ORC/MRB/CTH/RFP. This bring me the question - do we really need to keep those route when we can easily use Others - Lentor/Springleaf/Pending (Refer to Alternative Travel - Admiralty where I included Woodlands South).
 
For EWL, yesterday disruption show us the segment: Queenstown - Jurong East, Jurong East - Boon Lay, but given the bad luck where the track fault lies between Jurong East and Clementi (highly believe is UPDEP track fault), this result in Queenstown - Boon Lay facing disruption.
 
In the meantime, I was reorganising and arranging Yishun Station layout display, which I think I am going to revamp and include "Travel Time" in the route diagram so is easier to reference, and hopefully progressively rolled out to all stations. I had rolled out the partial new route diagram at Changi Airport & Nicoll Highway to follow more "TEL" like diagram, with interchange are clearly marked out now.
 
I look forward to your reply.
 
[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 17:26, 5 April 2025 (+08)


Hi, I understand what you said to me now. Ok, I will be careful when looking for images.
== Combine Service xxG/xxW into one single page ==
 
Hi Wekelwrady, good suggestion if I can see your table put onto your userpage, for Bus Service 84. Maybe we can use that? Leave message to the admin, so that the admin will allow.


Thanks
Thanks


[[User:Alphabetlorefan1|Alphabetlorefan1]] ([[User talk:Alphabetlorefan1|talk]]) 27 February 2025, 23:16
[[User:Alphabetlorefan1|Alphabetlorefan1]] ([[User talk:Alphabetlorefan1|talk]]) 7 April 2025, 11:32
 
==Re: Point about G/W directional==
Hi,
 
Noted on your reply regarding the appearance of 170X, 410G/W, 225G/W, 243G/W on the bus stop pole around Q3 2019 and the usage of "#" for 853/925/961.
 
The reason why I raised the issue up, is because there is no standardisation for Sundays/Holidays variant, in which the same route number was used. As for the bus stop information panels (the pole doesn't reflect "#" if I remember correctly), but the stops details panel reflect "#"), and if we are going to refer to LTA/official, is just without "#" and use "(Sunday/Holiday). I believe the "#" was used as a storage/electronic means to reflect alternate. So that is why I am asking should we based on official Renumber from (with/without #) for actual clarity.
 
Secondly, I noticed the issue regarding G/W plate (desto) era where the service are classified as single service i.e. 225 Direction 1 is 225G and Direction 2 is 225W, but was "renumbered" to 225G and 225W today without any news. Like you mention, it happened some times back in Q3 2019. Similarly for 170X was original 170 (Blue Plate), thanks for the info. The EDS uses * which I believe is SBS Transit way to denote alternate routing just as SMRT uses "#".
 
Some notes I wish to highlight:
 
* 12 August 2018 (or the next available operating day if the service didn't operate of 12 Aug):
** Standardisation of Express service
*** E → e for all service with parent service (854E → 854e)
*** e/(empty) → E for all service without parent service (868 → 868E)
** Standardisation of Terminating Trip Feeder service
*** E → T for SMRT Intra-Town/SBS Transit Townlink (811E → 811T)
*** T plate → T suffix for SBS Transit Townlink (293 → 293T)
*** No change for Go-Ahead Townlink (358T) due to them using this method since takeover
** Rebranding of Express Service
*** Fast Forward → Express
** Rebranding of Feeder Service
*** Townlink/Intra-Town → Feeder
 
* 5 April 2021 (or the next available operating day if the service didn't operate of 5 Apr):
** Standardisation of Late Night SWT/Terminating Trip
*** Classification as mid-route ending service as "new SWT" for last bus (63 → 63A)
*** Usage of "T" suffix for mid-route ending service at interchange/terminal for last bus (73 → 73T)
 
And if we look at how the previous standardisation occurs:
 
* 8 September 2019 (or the next available operating day if the service didn't operate of 8 Sep):
** Clarity of Bus Service for Weekend/Holiday variants or those with "multiple directions" (853 (Sunday/Holiday) → 853M)
 
Based on this, would it be plausible that the renumbering for 170 (Blue plate) → 170X, 225 D1 → 225G, 225 D2 → 225W etc was done together with the renumbering of 853# → 853M?
 
[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 14:44, 7 April 2025 (+08)
 
===Re:===
Noted on your point.
 
After reviewing the bus guide for 170X, it was clear that despite in 2014 when K230UB do cross-border, it was marked with a small "*" or "x". But the gallery guide still reflect it as 170 (Blue Plate) and after in 2018 with the 7th gen bus guide it was then mark with "170X". Also seen a photo at Woodlands CIQ, where it was indicated with "170x" (smaller case x instead of upper case) which was recently place in 2022/2023.
 
Like you mention, there is no clear indication on when such changes are mention. I had been searching through archives, for 410G/W, back in the days before 2010 (or so) it uses the route diagram to denote G/W. For 243G/W, at Boon Lay Temp Int, it uses the white/green signage plate with the W/G suffix in 2006. For 225G/225W at old Bedok Int (before moving to Bedok Temp Int), it once uses 225 (Green), 225 (White) before shifting over to 225G/225W in tandem with the WAB.
 
But sadly, there is no record of it appearing on physical bus guide (6th gen or earlier), so it's hard to determine, and it true that these service are gradually replaced by the current notation we are used now.
 
Regarding merging of the pages, there is a concern here - 859A/859B. It acts the same as 84G/84W, and all the feeders G/W. Then 859A/B is marked as SWT by SMRT, and Variant by LTA. And if we are to merge all these G/W plate, and proceed with A/B for 859, then it will bring the problem above like 853/925/961 - 859 is Sembawang ↺ Yishun, or Sembawang ↺ Admiralty Link? Luckily, Tower Transit remains using 859A and 859B and not lump them into a single service.
 
[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 17:42, 7 April 2025 (+08)

Latest revision as of 17:42, 7 April 2025

Just discuss below.

User's Stance: Uploading of non-watermarked images[edit]

I would like to answer some questions regarding why I choose to upload other types of images instead of using Land Transport Guru's.

My answer is simple. First of all, images with watermarks in the middle affect the overall aesthetics of the infobox. Secondly, exploring other image options out of the comfort zone is a good thing, and it captures the eyes of internet users in a more pleasant manner, rather than a heavily watermarked image. The images involved in Sgwiki's bus service pages are in Google Images right now as I speak.

Lastly and most importantly, the goal in the manifest is to build a comparative platform.

I hope that more users are able to understand where I am coming from and able to assist in contributing more of your OWN images. It is really appreciated with gratitude.

Clarification![edit]

My words seem to have been put out of context. I think I didn't make it clear what I meant by the watermarked images. What I was referring to was to address allegations that "sgwiki is plagarising LTG", which I think we should take a unique and exclusive step in the editorial direction of sgwiki. Presenting my own images is part of reducing that negative perception that readers initially had on the new bus service page rollout.

But please don't rush!! The content still has to come first, pictures come last!!

Secondly, I would like to point out self-sustainability for sgwiki as a goal, thus these images I uploaded are meant for sgwiki use, and meant to remove any layer of copyright issues that arise (TLDR: just use them directly for bus service pages). Images that are already on model pages are not to be largely untouched as these are not a priority.

User's Stance: Regarding recent Maintenance Work[edit]

I would like to be realistic here. The reasons other transport pages have been successful have always been attributed to regular maintenance. Therefore, for an encyclopedia to be relevant, the MOST IMPORTANT CORE OF CONTENTS MUST BE THERE. I know that I am getting frustrated, but stacking incomplete work on top of incomplete work can stress out people. Checks and corrections are an important investment and can never be excluded. I hope relevant editors can understand why I need to emphasise this.

I am supposed to be helping out at the trains page, but if editors can be more attentive, I hope I can continue my supposed schedule at the trains page.

RE: Alternate Travel Options[edit]

Hi,

Thanks for your progress. I had updated the Schematic route for Woodlands station, by including coloured lines at the bottom of the icon for quick reference on the icons group, so that it would be more easier to reference the icon-pairing when viewing 2 images side by side.

I will update the travelling time for TEL4 asap once I timed the whole trip from Woodlands North to Bayshore and analyze first as the current Opening House could not be fully gauge (as it was sector by sector) so actual dwell time may differ.

Thanks and Regards

Re: Disruption dropdown box idea[edit]

Yes, is fine to do it, I not really sure what you meant by main page, perhaps you can trial first for it? The main page is not locked (I believe)

As for the station layout map, I trying to figure out a way to translate 2D diagram to isometric view (Mathematics involved) for better clarity, so once that done I will slowly progressive roll out on most of the NSL and the eastern EWL. Didn't really have the accurate network layout for most station.

Re: Travel Time[edit]

I had updated the new travel time to reflect Hume, Punggol Coast and Teck Lee Station.

For the new upgrade template on bus service page, yes is correct. There isn't any much changes to the new templates.

  • Bus Fleet - {{Col|xxx}}
  • Bus Fleet - {{Fleet|fleet=xxx|model=xxx}}
  • Special Departure/SWT - {{Col/1|xxx}} ← This was used because it didn't use the same format due to vertical alignment issue
  • First/Last Bus - {{Bus/FBLB}}
    • wd=/fr=/sa=/su= → stands for no weekday/friday/saturday/sunday columns
    • fwd=/ffr=/fsa=/fsu= → first bus column for weekday/friday/saturday/sunday columns (used for skipping)
    • lwd=/lfr=/lsa=/lsu= → last bus column for weekday/friday/saturday/sunday columns (used for skipping)
    • order : weekdays → saturdays → sundays → fridays

Supernutorcrazy (talk) 08:02, 8 March 2025 (+08)

Re: Template standardisation[edit]

Hi,

I had trial on Template:BS65009 regarding the feedbacks, and special thanks to Shaun for highlighting the problem. You can refer to

For the effect.

Key notes:

  • {{BS65009}} - Shows bus stop and nearby ammenities columns.
  • {{BS65009|landmark=}} - Shows bus stop only
  • {{BS65009|swt={{BS/SWT|xxx}}}} - Shows bus stop, swt and nearby ammenities columns. The template 'SWT' has no change, just append "BS/" to its prefix will do.

Regarding Alternate Travel Option, I am thinking of consodilate and merge into a single sector page, i.e. 1 page for Pasir Ris to Tanah Merah (sector as train normally turnaround at Tanah Merah if breakdown between this sector), showing a spider network on traveling between the four station.

But I saw your work at Tampines, which is quite good, so can just use yours.

Regarding the major stops connections, I use NSL for example:

  • Jurong East
  • Bukit Batok (Between JE to CCK, Bt Batok serves as intermediate stop, with more options heading to CCK/Wdl, and Bt Gomak connections)
  • Choa Chu Kang (For Yew Tee connections)
  • Woodlands (For Kranji, Marsiling, Admiralty, Sembawang connections)
  • Yishun (For Sembawang, Canberra, Khatib connections)
  • Ang Mo Kio (For Yio Chu Kang connections)
  • Bishan
  • Toa Payoh (For Braddell connections)
  • Newton
  • Orchard (For Somerset/Dhoby Ghaut connections)
  • City Hall / Raffles Place
  • Marina Bay
  • Marina South Pier

I omit Sembawang and Yio Chu Kang because there is adequte bus service from other station to those station, and almost all bus service do passes those station first before reaching Sembawang/Yio Chu Kang.

As for Novena, the way moving forward is via Newton or Marymount/Upper Thomson connections.

As for sector, NSL:

  • Jurong East - Choa Chu Kang
  • Choa Chu Kang - Woodlands
  • Woodlands - Yishun
  • Yishun - Ang Mo Kio
  • Ang Mo Kio - Newton
  • Newton - Marina South Pier

EWL:

  • Pasir Ris - Tanah Merah
  • Tanah Merah - Paya Lebar
  • Paya Lebar - Outram Park
  • Outram Park - Buona Vista
  • Buona Vista - Jurong East
  • Jurong East - Boon Lay
  • Boon Lay - Joo Koon
  • Joo Koon - Tuas Link
  • Tanah Merah - Changi Airport

NEL:

  • HarbourFront - Serangoon
  • Serangoon - Punggol Coast

After analysing, the activation of FBB is normally between these sectors or consective sectors depending on the scale.

Reply[edit]

Noted on your Tampines Alternate Travel and 107/M.

(1) 107/107M. I had remove the "Revised Timing will be announced by operater" for Service 6, given that only GAS announced it only. SMRT also didn't announced the revised timing when 964 did not operates on Sundays either for New Year/CNY/Christmas.

(2) Alternative Travel

Looks ok. When I was doing Yishun Alternative Travel, I noticed most of it involve travelling to - Lentor/Springleaf/Pending for transfer to continue on to let's say JUR/ORC/MRB/CTH/RFP. This bring me the question - do we really need to keep those route when we can easily use Others - Lentor/Springleaf/Pending (Refer to Alternative Travel - Admiralty where I included Woodlands South).

For EWL, yesterday disruption show us the segment: Queenstown - Jurong East, Jurong East - Boon Lay, but given the bad luck where the track fault lies between Jurong East and Clementi (highly believe is UPDEP track fault), this result in Queenstown - Boon Lay facing disruption.

In the meantime, I was reorganising and arranging Yishun Station layout display, which I think I am going to revamp and include "Travel Time" in the route diagram so is easier to reference, and hopefully progressively rolled out to all stations. I had rolled out the partial new route diagram at Changi Airport & Nicoll Highway to follow more "TEL" like diagram, with interchange are clearly marked out now.

I look forward to your reply.

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

Combine Service xxG/xxW into one single page[edit]

Hi Wekelwrady, good suggestion if I can see your table put onto your userpage, for Bus Service 84. Maybe we can use that? Leave message to the admin, so that the admin will allow.

Thanks

Alphabetlorefan1 (talk) 7 April 2025, 11:32

Re: Point about G/W directional[edit]

Hi,

Noted on your reply regarding the appearance of 170X, 410G/W, 225G/W, 243G/W on the bus stop pole around Q3 2019 and the usage of "#" for 853/925/961.

The reason why I raised the issue up, is because there is no standardisation for Sundays/Holidays variant, in which the same route number was used. As for the bus stop information panels (the pole doesn't reflect "#" if I remember correctly), but the stops details panel reflect "#"), and if we are going to refer to LTA/official, is just without "#" and use "(Sunday/Holiday). I believe the "#" was used as a storage/electronic means to reflect alternate. So that is why I am asking should we based on official Renumber from (with/without #) for actual clarity.

Secondly, I noticed the issue regarding G/W plate (desto) era where the service are classified as single service i.e. 225 Direction 1 is 225G and Direction 2 is 225W, but was "renumbered" to 225G and 225W today without any news. Like you mention, it happened some times back in Q3 2019. Similarly for 170X was original 170 (Blue Plate), thanks for the info. The EDS uses * which I believe is SBS Transit way to denote alternate routing just as SMRT uses "#".

Some notes I wish to highlight:

  • 12 August 2018 (or the next available operating day if the service didn't operate of 12 Aug):
    • Standardisation of Express service
      • E → e for all service with parent service (854E → 854e)
      • e/(empty) → E for all service without parent service (868 → 868E)
    • Standardisation of Terminating Trip Feeder service
      • E → T for SMRT Intra-Town/SBS Transit Townlink (811E → 811T)
      • T plate → T suffix for SBS Transit Townlink (293 → 293T)
      • No change for Go-Ahead Townlink (358T) due to them using this method since takeover
    • Rebranding of Express Service
      • Fast Forward → Express
    • Rebranding of Feeder Service
      • Townlink/Intra-Town → Feeder
  • 5 April 2021 (or the next available operating day if the service didn't operate of 5 Apr):
    • Standardisation of Late Night SWT/Terminating Trip
      • Classification as mid-route ending service as "new SWT" for last bus (63 → 63A)
      • Usage of "T" suffix for mid-route ending service at interchange/terminal for last bus (73 → 73T)

And if we look at how the previous standardisation occurs:

  • 8 September 2019 (or the next available operating day if the service didn't operate of 8 Sep):
    • Clarity of Bus Service for Weekend/Holiday variants or those with "multiple directions" (853 (Sunday/Holiday) → 853M)

Based on this, would it be plausible that the renumbering for 170 (Blue plate) → 170X, 225 D1 → 225G, 225 D2 → 225W etc was done together with the renumbering of 853# → 853M?

Supernutorcrazy (talk) 14:44, 7 April 2025 (+08)

Re:[edit]

Noted on your point.

After reviewing the bus guide for 170X, it was clear that despite in 2014 when K230UB do cross-border, it was marked with a small "*" or "x". But the gallery guide still reflect it as 170 (Blue Plate) and after in 2018 with the 7th gen bus guide it was then mark with "170X". Also seen a photo at Woodlands CIQ, where it was indicated with "170x" (smaller case x instead of upper case) which was recently place in 2022/2023.

Like you mention, there is no clear indication on when such changes are mention. I had been searching through archives, for 410G/W, back in the days before 2010 (or so) it uses the route diagram to denote G/W. For 243G/W, at Boon Lay Temp Int, it uses the white/green signage plate with the W/G suffix in 2006. For 225G/225W at old Bedok Int (before moving to Bedok Temp Int), it once uses 225 (Green), 225 (White) before shifting over to 225G/225W in tandem with the WAB.

But sadly, there is no record of it appearing on physical bus guide (6th gen or earlier), so it's hard to determine, and it true that these service are gradually replaced by the current notation we are used now.

Regarding merging of the pages, there is a concern here - 859A/859B. It acts the same as 84G/84W, and all the feeders G/W. Then 859A/B is marked as SWT by SMRT, and Variant by LTA. And if we are to merge all these G/W plate, and proceed with A/B for 859, then it will bring the problem above like 853/925/961 - 859 is Sembawang ↺ Yishun, or Sembawang ↺ Admiralty Link? Luckily, Tower Transit remains using 859A and 859B and not lump them into a single service.

Supernutorcrazy (talk) 17:42, 7 April 2025 (+08)