View source for User talk:Sgbusntrain

==Re:==
We shall fine tune the service page first before creating more and bring the rest to new format. With regards to whether to include bus rego or not is still TBC. Best is don't include.

Secondly, I noticed that certain trips of the day is always operated by certain capacity bus type/model regardless of operators. Maybe we can include that in as a general if that was the case? This also include crossover remarks, jumpbus remarks, or CLOWBus remarks. I also noticed that SWT and parent service fleet are usually interchangable (that why I proposed to be same page). This include additional bus stop enroute affecting parent service = SWT also affected.

Thirdly, I was thinking of First/Last Bus at key stops such as MRT stations or landmark.

With regards to service code for travel advisory:
*S1XXE = Express service which start with 1xx
*S22XF = Feeder service which start with 22x
*S95x = Basic service which start with 95x

So for Feeder 222 will just be S22XF



All those special buses can also have their own ''Additional Information'' table like in the old format of bus deployments just add everything special there.

First bus and last bus at Train stations are difficult to find out but it is informative, so i guess it can have its own section.

== Re: Bus Service Pages ==

Dear Sgbusntrain,

Maybe we should try adding the perms for non flexi-deployment bus services. Anyway, I understand why we cannot add links to different bus model pages. Also, maybe we can consider bus service duty allocation similar to bus service 296.

Yours Faithfully,<br>
[[User Talk:SBS5251K]]

==Roads Page==
===List of roads in Tampines===
Hi,

Can you help me with the bus stops on this page?

Regards,<br>
[[User Talk: SBS5251K]]

===Merging of pages===
Hi,

Just a curiosity, are you going to create 10000 plus page for each and every roads in Singapore that just state some unnecessary information such as a list of bus stop and some connecting roads with no real meaningful like histories etc especially for minor roads. If so, I would encourage you to condenses and merge multiple pages into one for the sake of it to be more meaningful.

Regards

In reply

I appreciate your perspective but it is just a passion of mine to create these. I’ll try to add more relevant and important information to major roads, and dig out as much information as possible for minor ones. I’ll try to consider merging pages.

Thanks

== Non-revenue buses ==

Hi Sgbustrain,

If you want to list the bus as non-revenue, you must include what happened to the bus in the edit summary for example an accident with another vehicle. So what really happened to SG1756J???? Reply if you know!

Alphabetlorefan1

In reply 

Hi,

SG1756J got into an accident with a white BMW yesterday. Thats all the info I know as of then and i hoped it answers your question. I will make sure the add a brief description next time.

Sgbusntrain

To anyone who wants the reason since i forgotten to put it.

there was an incident involving SMB304J


== SBS6623P damage ==

Hi, do you have any proof that this bus got damaged? The SGRV video showed that it didnt get rear ended or it might be unknown. Or you claiming it was from another website. 

Thanks, 
[[User:Alphabetlorefan1|Alphabetlorefan1]] ([[User talk:Alphabetlorefan1|talk]]) 21:07, 6 July 2024

In reply, SBS6623P accident happened near lorong 106 changi, that bus in the SGRV video is '''NOT''' SBS6623P and there was damage to the rear of the bus, the bus is currently in the workshop according to my friend's BCF.

==Non-revenue buses==

Hi could you please take note that a bus that has broken down is not considered non-revenue, and only more major happenings such as bus accidents, where the bus has to go through excessive repair works, are considered non-revenue. Thanks.

Edit: I just realised that you have clarified that you felt that non-revenue means any bus that is out of service. However, by this definition, tons of buses would have to be put on the list (as can be seen from these 2 days. As such, I would suggest that you do not continue to put buses that breakdown (bus breakdowns are way too frequent) on the list, if not it would make it much harder to track. 

Regards,
LTA Bus Irrationalisation

Just to let you know those buses that brokedown were from a list past 5 days so thats why there is so many buses all of a sudden. Let those be for now.

Re: I understand you want to put bus breakdowns on the list. However, ever since that page existed, only scrapped or damaged (not breakdown) buses has been formally put on the page. Please stop placing these breakdown buses on there. That is also why non-revenue buses has to be given a proper reason, if not it will also get reverted. Plus non-revenue buses means gone for quite a while, unlike 5035E which was repaired in just a day. Thanks.

==Bus Service Page==
Hi,

Regarding the history section, it is better or confusing for a trial at [[Bus Service 222]] and [[Bus Service 911]], where I had included the previous history (prior to renumbering)?

Do let me know your take, and also how should we proceed for the old history services.

Thanks

==Travel Advisory==
Hi, for the travel advisory, keep in chronical order from date of changes with MRT/LRT first followed by Bus as the impact of the changes affects more to trains (1000 (MRT)/200 (LRT) passengers per train every 3 mins) as compared to bus (80 passengers per bus every 10 mins)

==Warning Points==
{{Warning Point|13 September 2023|Excessive Editing on a page.

Please refrain from excessive a single page multiple time as this will hinder the abilities of Administrator to patrol or monitor for rouge editor. You may use the "Preview" button to preview your change before clicking on the "Save" to avoid mistake.

In the event of suspected session lost error encounter, just scroll down and press "save" one more time and the latest change will be reflected.

Thank you for your understanding.}}
{{Warning Point|19 March 2024|Creating unnecessary template.

For Varients/Supplementry/Express Services, please use the parent template. Eg. '''<nowiki>{{Bus/963e}}</nowiki>''' can be written as '''<nowiki>{{Bus/963|a=e}}</nowiki>'''}}
{{Warning Point|19 March 2024|Excessive Template creation (Revoke rejection by user: Asking the admin to go through and deleting

Template for bus stops should not be created unless such bus stop may served as important transport nodes (major bus stop for transfering between services or rail). For other bus stop, please use the template BS00000 instead and manual populate the entries.}}

== Adding Bus Service Page Links to the “Bus Deployments By Package” Page ==

Hi, is it ok if I add links to the “Bus Deployments By Package” page? 

I find it annoying that to go to any Bus Service page from the “Bus Deployments By Package” page, you would have to click off, go to the “Bus Deployments By Service” page, click on the page that you wish to go, then click on the respective page you want to go to go there. It would be more convenient if the links to the Bus Service pages was right at the “Bus Deployments By Package” page. 

That way, people could go to their respective Bus Service pages from the “Bus Deployments By Package” List and not have to click off as I said earlier. Thanks.

Best regards, <br>
[[User:Gjxl1303|Gjxl1303]]

== Finding a way to add buses that do downroute trips from a bus stop to its terminal with its plate if the bus service page has been made ==

Hi, if someone knows the bus (for example SBS0000X, SMB0000X or SG0000X) that does downroute trips from a stop to an interchange, how do they add that bus?

Before bus service pages were made, the “Notes” section would have “'''X Service XXX ([bus type]) buses/ SXX0000X (Service XXX)''' will perform X down-route trip(s) as Service XXX from [road name] (Bus Stop XXXXX - [Bus Stop Name]) towards [terminating point] before/during [time period down route happens], departing at XXXX hours.”

Now, with bus service pages, if people know the bus that does downrouting from a stop to a bus interchange/terminal, how do they add it so that the public still knows what bus and it’s duty does the downroute? I’m curious to find out how you would solve this problem.

If you find out a way, please let me know, thank you.

Best regards, <br>
[[User Talk: Gjxl1303]]

I think what the user meant is if there are 2 downroute trips, and 1 bus is perm for one of the departing timing, how to label that bus in and not the table format.

== Bus Deployments by Package ==

Hi Sgbustrain,

I was wondering why you completely reformatted this page. The main problem I have with this page is that there is no link to the page of each individual bus package, i.e. {{Bulim}} or {{Loyang}}. I did think of putting it like this where the title is clickable
{|class="wikitable" style="width:100%"
!colspan=3 style="{{CSS/TTS|s=|t=}}border-right:none;height:20px;"|{{Icon|Bus|W|20px|d=inline}} {{Bulim}} Bus Package
!style="border-left:none" width=75|<small><small>[ [[Template:Bulim Bus Package|V]] • [[Template talk:Bulim Bus Package|T]] • <span class="plainlinks">[//sgwiki.com/index.php?title=Template:Bulim_Bus_Package&action=edit E]</span> ]
|-
|width=100 colspan=4 style="text-align:center"|{{TTS}}
|}
but even if there somehow was a way to make the whole line clickable, it would still look downright ugly in blue. I will now undo this edit so that the page continues to have these links. I feel that the UI is easier to use in the previous version as the different services can all be found within each bus package page, and things such as "Clementi feeders" or "Bukit Batok feeders" can also be found in the bus deployments by service page, and these templates also make this page uneccessarily long. That being said, if you do find an effective way to solve the main problem I mentioned earlier, feel free to reformat the bus deployments by package page.
Thanks.

Regards,
LTA Bus Irrationalisation


Re: Jumping straight to the point, I really dislike the new format which you have put in as it makes the page very very long. Why I do not like this new format is because:
1. Most of the information found in the template can be found in each specific bus package. This includes bus models and type of service for each bus number.

2. The only information that can really be considered extra would be which neighbourhood each feeder serves, such as bishan feeders being 410, toa payoh feeders being 230, 231, etc. This information can already be derived from [[Bus Deployments by Service]], or even derived from each bus package page, as all feeders start/loop at a place with the neighbourhood name (i.e. amk feeder 265 starting at amk depot looping at amk ave 10). Hence, this is just uneccessary information for [[Bus Deployments by Package]] page which is meant to give an overview of the bus packages and not delve into the specifics.

3. People may not realise that the title is clickable, leading to specific information about each bus package being so called “inaccessible”. (yes I know I may be contradicting my earlier message but I didnt forsee this unintended consequence) Some people like me sometimes do not use laptops so there isn't a mouse to hover over the title to realise its clickable, compared with the previous format where the blue font makes it obvious that it is clickable.

I am not saying that this your ideas are worthless as there are still certain ideas which can be used to improve each individual bus package page. This include the sorting of services, where a class="wikitable sortable" can be added to the table of services to be able to sort them based on service (colour coding works too if need be). Links to each bus model in each bus package can also be placed to make it easier to go between the pages. In conclusion, I will change back the format and edit each bus package page accordingly with the edits I have suggested here unless you are able to show me what this new format does better than the old format. 


Thanks for reading this and apologies for being so critical here, and I hope that you wont take offence because of this message.

== Bus History Page ==

Hi can the History page be kept untouched? I nearly missed out on Sv 78's amendment to Jurong Town Hall Int when doing a complication of the bus history for today (26 November)