User talk:Svc135bsoe

Future Bus Services from Woodleigh Int

Service	Destination
81	Tampines Int
82	Punggol Temp Int
104	Punggol Coast Int
146	Hougang St 21 / Kovan MRT (Loop)
506	Jurong East Int

Future Bus Services from Punggol Coast Int

Service	Destination
34/e	Changi Airport (Loop)
104	Woodleigh Int
117/M	Sembawang Int
383	Punggol Central / Punggol MRT (Loop)

Predictions for Bus Services from Beauty World Int

Service	Destination
41	Jurong East Int
66	Jurong East Int
92	Science Park Dr (Loop)
100	Serangoon Int
111	Temasek Ave (Loop)
170	Larkin Ter (Johor Bahru)
871	Tengah Int

Predictions for Bus Services from Kallang Int

Service	Destination
11	Rhu Cross (Loop)
62	Punggol Temp Int
64	Mei Ling St (Loop)
134	Marine Terrace (Loop)
137	Upp East Coast Ter
140	St Wilfred Road (Loop)
141	Toa Payoh Int
175	Clementi Int
853	Yishun Int
961/M	Woodlands Temp Int
980	Sembawang Int
985	Choa Chu Kang Int

Random Ideas and Stuff

135	I've always liked Service 135 since it gets me from home to important places such as school. There's Woodleigh on the way and Marine Parade is not too far down. Aside from that, there's a full fleet of MB Citaros, which are personally my favourite bus model. That's my opinion, but what do you think? More information at Bus Service 135, created by me.
Seletar Bus Package	Seletar somehow gets all those lush greenies. LG Citaros, LG B9TLs, LG A22s... I feel that there are the least variety of batches and liveries in Seletar. But what do you think?
Buona Vista Bus Interchange	I always thought a bus interchange (whether ITH or normal) should be built at Buona Vista, which would merge and operate services from the existing Buona Vista Ter and perhaps some from Ghim Moh Ter. Another option would be one closer to Holland Village. But what do you think?

Undo of your edits

Hi,

I had undo your edit on Bus Deployments by Service, as I do not want to be flamed by critics for implementing disorientation into this page for the following:

1. Trunk Service:

• 130 - 134, 136, 137, 139
• Template:Bus/135 Template:Bus/138

Now, it will be very confusing at a glance and reader will think that Service 135 and 138 had discontinued due to lack of continuous numbering. If we split it up like this:

• 130 - 134
• Template:Bus/135
• 136, 137
• Template:Bus/138
• 139

Then it will be too long and weird. That was why there are quite a few service - despite having a separated pages, didn't have its listing indicated here but rather required a double click action.

2. Feeder service

• Choa Chu Kang: Template:Bus/300 Template:Bus/301
• Feeder Service 302 & 307 (Choa Chu Kang)

This make it looks like there is two seperate town called "Choa Chu Kang". That is the reason why it will only be reflected when ALL pages is converted in it.

I hope you understand the rationale behind my undo.

Regards

RE: Undo of your edits

Hi supernutocrazy,

I understand the rationale behind this and will not make any of such edits again. Thank you.

Regards svc135bsoe

Opinion

Hi,

I would like to seek your opinion on the following proposed changes:

1. Launch of sgWiki Bus Spotting Page A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.

The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.

2. Use of Subpages for Bus Model Deployment I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:

Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:

1. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
2. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
3. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
4. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)

A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:

Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment

This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.

Alternative Table Layouts:

1. Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
2. Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
3. Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)

Please let me know your thoughts on these proposals. Thank you for your time and feedback.

Regards, Supernutorcrazy