User talk:Sgeditransport5929: Difference between revisions

From SgWiki
Jump to navigation Jump to search
← Older editNewer edit →
Supernutorcrazy (talk | contribs)
37,676 edits
mNo edit summary
Supernutorcrazy (talk | contribs)
37,676 edits
mNo edit summary
Line 1: Line 1:
== New Bus Service Pages ==
==Opinion==
Hi,
Hi,


Is it possible to add in the bus route details when creating those pages too. I noticed that you always leave those empty with provision and expecting other editors to take in the effort to add it in for you.
I would like to seek your opinion on the following proposed changes:


Thanks & Regards
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.


==Sgeditransport5929 reply==
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.
Hi,
 
I am always unsure in what bus stop I should put in. Because I observed you have put in bus stops in the list that do not connect to MRT/LRT stations, so I therefore do not know what to do. Therefore, I leave the bus route details blank to ensure there is no controversy when creating the page.
 
Thank you!
 
== Reply==
I meant the list of all calling stops, in stopping order. If you have noticed when expanding, it tallies to the first stop to the last stop. So for example, for Service 333, it will be "28009, 28059, 28659, 28649, 28639, 28321, 28331, 28451, 28461, 28471, 28481, 28459, 28339, 28329, 28631, 28641, 28651, 28051, 28199, 28009" in this order.
 
If you are unsure of which one to use:
 
*<nowiki>|-</nowiki><br><nowiki>|{{BSxxxxx}}</nowiki> → Use this for the following bus stops.
** First/Last Stop of all service/SWT
** Connecting MRT/LRT station
** First stop of special departure if the first bus departs earlier then the first bus from first stop.
** Notable tourist/community attractions or high activity stops (Ignore this condition is ok if unsure)
*<nowiki>|- class='ex'</nowiki><br><nowiki>|{{BSxxxxx}}</nowiki> → Use this for all other calling stops, or if you are unsure.


==lack of stops==
2. Use of Subpages for Bus Model Deployment
Hi,
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:


Your recent edits regarding Service 354 and Service 358 stating that they serve only 3 and 5 stops, respectively, contain inaccurate information. These services have more extensive routes that should be fully represented.
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)


To ensure complete route coverage on all service pages, please follow these steps:
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:
# Click on the "[Show/Hide Full Route Details]" button at the top left-hand corner of the route page.
# This toggle button reveals the entire list of stops, as some stops are hidden by default using the <code><nowiki>class='ex'</nowiki></code> code.


When creating or editing service pages, please make sure to include the full route details to maintain accuracy and consistency.
Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment
 
- Supernutorcrazy
 
== New Deployment Format ==
Hi,


I would appreciate it if you could take some time to review the proposed table format for [[Bus Service 168]]'s fleet.
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.


Your genuine feedback is highly valued, particularly regarding whether this new format effectively addresses concerns related to the "counting" of buses for users with dyslexia, compared to the existing table structure. Your input will help ensure accessibility and clarity for all users.
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)


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


- Supernutorcrazy
Regards, Supernutorcrazy

Revision as of 16:02, 18 January 2025

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

Retrieved from "https://sgwiki.com/index.php?title=User_talk:Sgeditransport5929&oldid=652819"