User talk:Svc135bsoe - Revision history

Svc135bsoe: do not randomly put up deletion notices.

2025-07-07T00:41:46Z

do not randomly put up deletion notices.

← Older revision		Revision as of 08:41, 7 July 2025
Line 1:		Line 1:
	~~{{Deletion\|[[Special:Contributions/Svc135bsoe\|Svc135bsoe]] (talk) is the last day of operation}}~~

Jade at 16:08, 6 July 2025

2025-07-06T16:08:37Z

← Older revision	Revision as of 00:08, 7 July 2025
Line 1:	Line 1:
		{{Deletion\|[[Special:Contributions/Svc135bsoe\|Svc135bsoe]] (talk) is the last day of operation}}

Svc135bsoe: byesgwiki

2025-07-06T15:22:18Z

byesgwiki

Show changes

Svc135bsoe: /* Future Bus Services from Woodleigh Int */

2025-04-28T06:47:28Z

Future Bus Services from Woodleigh Int

← Older revision		Revision as of 14:47, 28 April 2025
Line 16:		Line 16:
	!style="{{CSS/SBST\|xfc=\|xbc=}}"\|146		!style="{{CSS/SBST\|xfc=\|xbc=}}"\|146
	\|Hougang St 21 / Kovan MRT (Loop)		\|Hougang St 21 / Kovan MRT (Loop)
			\|-
			!style="{{CSS/SBST\|xfc=\|xbc=}}"\|148
			\|Potong Pasir Ave 1 (Loop)
	\|-		\|-
	!style="{{CSS/SBST\|xfc=\|xbc=}}"\|506		!style="{{CSS/SBST\|xfc=\|xbc=}}"\|506

Supernutorcrazy: /* RE: Undo of your edits */

2025-02-20T23:52:31Z

RE: Undo of your edits

← Older revision		Revision as of 07:52, 21 February 2025
Line 153:		Line 153:
	Regards		Regards

	== RE: ~~Undo of your edits~~ ==		== RE: History Page for Defunct Services ==
			Hi,

	~~Hi supernutocrazy,~~		Sounds good. I was thinking what if we merged all (including those at respective bus pages) into the year page?
			*[[2019]]
	~~I understand the rationale behind this and will not make any of such edits again. Thank you.~~		*[[2021]]
			*[[2023]]
			*[[2024]]
			*[[2025]]

	Regards		Regards
	~~svc135bsoe~~

			Supernutorcrazy

	==Opinion==		==Opinion==

Supernutorcrazy: /* English Usage */

2025-02-06T23:37:43Z

English Usage

← Older revision		Revision as of 07:37, 7 February 2025
Line 202:		Line 202:

	I look forward to your suggestion on the term and structure.		I look forward to your suggestion on the term and structure.

			==Merging of Euro Emission & Batches==
			Hi,

			Do you think we should merge the Euro Emission and Batches as we moves to subpage. This make it easier to link from Deployment by service pages back to model, and bus community will find it easier to find/track a bus rather than remembering the batches.

			So it will be like this:

			{\|class='wikitable sortable'
			!style='{{CSS/BUS\|xfc=\|xbc=\|bgop=a0}}' width=10%\|Registration no.
			!style='{{CSS/BUS\|xfc=\|xbc=\|bgop=a0}}' width=10%\|Deployment
			!style='{{CSS/BUS\|xfc=\|xbc=\|bgop=a0}}' width=10%\|Batches (Optional Column)
			!class=unsortable style='{{CSS/BUS\|xfc=\|xbc=\|bgop=a0}}text-align:center' width=40%\|Advertisement
			!class=unsortable style='{{CSS/BUS\|xfc=\|xbc=\|bgop=a0}}text-align:center' width=40%\|Former Deployments
			\|}

			Bodywork differences such as Volvo B9TL CDGE/WEG/Gemilang will not be affected, similiarily to 2D/3D variants.

Supernutorcrazy at 09:18, 27 January 2025

2025-01-27T09:18:20Z

← Older revision		Revision as of 17:18, 27 January 2025
Line 181:		Line 181:

	Regards, Supernutorcrazy		Regards, Supernutorcrazy

			== English Usage==
			Hi, saw your edits to help improve the language usage, but there is this part there is something that need to be adjusted:

			* 41: It was the 34th bus service that benefits under the Land Transport Authority’s (LTA) [[Bus Service Enhancement Programme]] (BSEP).
			* 651: It was the 14th bus service that benefits under the Land Transport Authority’s (LTA) [[Bus Service Enhancement Programme]] (BSEP), and the 1st peak-hour unidirectional city direct bus service introduced.
			* 951E: It was the 12th bus service that benefits under the Land Transport Authority’s (LTA) [[Bus Service Enhancement Programme]] (BSEP), and the 4th peak-hour unidirectional express bus service introduced.
			* 230: It is the 16th bus service that benefited under the Land Transport Authority’s (LTA) [[Bus Connectivity Enhancement Programme]] (BCEP).
			* 967: It was the 15th bus service that benefits under the Land Transport Authority’s (LTA) [[Bus Connectivity Enhancement Programme]] (BCEP).

			Over here I used benefit(s/ed) instead of introduced or extended because - the count actually tally into it. For example, if we take 230 as an example, it is the 1st bus service that '''extended''', because all the previous one is '''introduced''', but on paper, they say it is the 16th bus service under BCEP.

			If we look at bus service 41, it is not 34th bus service to be introduced, because the 34th didn't include - peak period bus services before it being introduced (9 of them), supplementary route, or operating hours extension. But on paper, it stated 34th bus service.

			As for the term residential estates or residents, let's make it simpler - if it is road - use residents, if it is town name based on URA, then use residential estates.
			* Residential estates - Town-centric, Building-centric
			* Residents - People-centric

			Using this method, I feel is clearer because a road can have industrial on one side, and residential on the other side, which means, residentials estates only means cater to one side of the road. But residents, we didn't say xxx's residents, so I guess it can inferred as Singapore residents (anyone) regardless of whether they live there or not.

			I look forward to your suggestion on the term and structure.

Supernutorcrazy: /* Opinion */

2025-01-25T06:41:58Z

Opinion

← Older revision		Revision as of 14:41, 25 January 2025
Line 166:		Line 166:
	Hi,		Hi,

	~~I would like to seek~~ your ~~opinion~~ on the ~~following~~ proposed changes:		Thank you for sharing your feedback on the proposed changes earlier. I am pleased to inform you that the bus spotting page has been launched, which I believe will assist editors in verifying deployment accuracy and enhancing the reliability of current deployment information.

	~~1. Launch~~ of ~~sgWiki Bus Spotting Page~~		To address concerns regarding potential false entries on the spotting page, I trust in the integrity of our editors to avoid posting hypothetical or inaccurate information. Additionally, I have implemented features such as Date/Time stamps and Editor attribution to reinforce accountability.
	~~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~~.		Regarding the subpages, I have launched the following: [[Scania K230UB (Euro IV) (Batch 2)]]. Deployment details have been transferred to the respective subpages.

	~~2. Use of Subpages for Bus Model Deployment~~		As a trial, I finalised the layout for the first subpage: [[Scania K230UB (Euro IV) (Batch 2)/1]], incorporating your valuable feedback.
	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:~~		Please confirm if the following criteria are met:
	~~# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)~~		# Clear visibility and usability on mobile devices.
	~~# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)~~		# Ease of information references.
	# ~~Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)~~
	# ~~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:~~		If you have additional suggestions for improving the subpage layout, please do not hesitate to share your input. Thank you for your time and constructive feedback.

	~~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:~~
	~~# Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Maintain status quo)~~
	~~# Batch \| Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Merging of Batches, numerical order, maintain status quo)~~
	~~# 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		Regards, Supernutorcrazy

Supernutorcrazy at 08:03, 18 January 2025

2025-01-18T08:03:27Z

← Older revision		Revision as of 16:03, 18 January 2025
Line 161:		Line 161:
	Regards		Regards
	svc135bsoe		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:
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
			# 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:
			# Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Maintain status quo)
			# Batch \| Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Merging of Batches, numerical order, maintain status quo)
			# 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

Svc135bsoe at 08:57, 15 January 2025

2025-01-15T08:57:05Z

@@ Line 40: / Line 40: @@
 |}
-== Predictions for Bus Services From Beauty World Int ==
+== Predictions for Bus Services from Beauty World Int ==
 {| class='wikitable'
 !Service
@@ Line 65: / Line 65: @@
 !style="{{CSS/TTS|xfc=|xbc=}}"|871
 |Tengah Int
 |}
 == Random Ideas and Stuff ==
 {| class='wikitable'
 |-