Difference between revisions of "User talk:Sgbusntrain"
Sgbusntrain (talk | contribs) |
m |
||
(62 intermediate revisions by 9 users not shown) | |||
Line 1: | Line 1: | ||
<!-- | |||
Hide this as I don't want to be flamed, but I guess people doesnt learned their mistake. See this critic | |||
*https://www.facebook.com/photo/?fbid=1194794225309886&set=a.148662563256396 | |||
*https://youtu.be/Zn5PsglqTl8?feature=shared | |||
At the YouTube video, how he blast about the issue of colour blindness etc, cannot differtinate colours used in sgWiki, and now in his facebook page on how he claim colours solve everything through colour palatte. Like hellow, three different colour band hold the same meaning, and colour blindness user had to refer to the legend to infer the correct interpretatiom, but with my similiar mimic, at lease the outline can solve this issue without going to the legend area for interpretation. | |||
Next, notice how he use the multirow to denote a single bus, this shows how inexperience or doesnt know how sorting function works. He just aimed for asthetic, simplicity and not underlying wiki/coding functionality. | |||
One thing I noticed is the text readibility, which they also pointed it out. But at least I noticed it before them and use erm, white background over the livery on text to enhanced readibility (remember how I undo your edit on removing white background)? | |||
But thanks to this critic on their mock up rendering, I gain a new idea to fix this. | |||
Face palm. I suspect more editors lurking around here are like them, only know how to critics but never think that the problem are them theyself. Like how they claim I never listen to them, but how entitled they are. E.g. hearmeout, bendermeer. | |||
I like how Shaun challenge my edit, and he consistency bring out innovation or problem faced unlike those critic. Eg. Trial for 65009 template -> challenge the trial by reverting until I realised the problem lies in SWT columns. | |||
So if you are to proceed with your plan and use here as your reference point, you will know the pain. | |||
--> | |||
==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== | ==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=== | ===Merging of pages=== | ||
Hi, | Hi, | ||
Line 43: | Line 86: | ||
Sgbusntrain | 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) | |||
== 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) | |||
==Non-Wheelchair Accessible Bus Stop== | |||
I had verify some bus stop via the LTA Datamall, there are only 76 bus stop that are non-wheelchair accessible as followed: | |||
{| class='wikitable' | |||
|{{BS07231}}||{{BS07249}}||{{BS13101}}||{{BS13169}}||{{BS21099}} | |||
|- | |||
|{{BS21499}}||{{BS22091}}||{{BS23389}}||{{BS23419}}||{{BS24331}} | |||
|- | |||
|{{BS24339}}||{{BS24681}}||{{BS24689}}||{{BS25269}}||{{BS25379}} | |||
|- | |||
|{{BS25389}}||{{BS25469}}||{{BS26241}}||{{BS26251}}||{{BS31071}} | |||
|- | |||
|{{BS31081}}||{{BS31089}}||{{BS31201}}||{{BS31211}}||{{BS32041}} | |||
|- | |||
|{{BS32049}}||{{BS32051}}||{{BS32059}}||{{BS32061}}||{{BS32069}} | |||
|- | |||
|{{BS32071}}||{{BS32079}}||{{BS32101}}||{{BS32109}}||{{BS32111}} | |||
|- | |||
|{{BS32119}}||{{BS33011}}||{{BS33019}}||{{BS33031}}||{{BS33051}} | |||
|- | |||
|{{BS33059}}||{{BS34009}}||{{BS34011}}||{{BS34021}}||{{BS34029}} | |||
|- | |||
|{{BS34031}}||{{BS34039}}||{{BS34041}}||{{BS34049}}||{{BS34051}} | |||
|- | |||
|{{BS34059}}||{{BS43721}}||{{BS44669}}||{{BS46101}}||{{BS46109}} | |||
|- | |||
|{{BS46211}}||{{BS46219}}||{{BS46239}}||{{BS46301}}||{{BS47711}} | |||
|- | |||
|{{BS48101}}||{{BS48109}}||{{BS49021}}||{{BS49029}}||{{BS49199}} | |||
|- | |||
|{{BS49209}}||{{BS50169}}||{{BS51091}}||{{BS56061}}||{{BS56081}} | |||
|- | |||
|{{BS58019}}||{{BS66391}}||{{BS66409}}||{{BS80069}}||{{BS82141}} | |||
|- | |||
|style='text-align:center' colspan=5|{{BS97149}} | |||
|} | |||
== Service 170X == | |||
For the past few months, I noticed 170X starts from Kranji station (Berth 2) instead of Opp Kranji station. Not too sure of the routing 170X took cause I didn't take 170X from Kranji. SBS Transit staff is present there to manage and guide commuters, so suspected already route amendment without announcement. Didn't really spotted any 170X anymore at Opp Kranji Station (45131). | |||
== Re: Nearby Attractions == | |||
As far as I had done, I will try my best to add in big shopping mall when creating the pages, especially those near interchanges, and tourist attractions like 858 (Jewel) and 138 (Mandai Zoo etc). But of course there may be some part where I can missed out. I don't think school should be included, nor those neighbourhood malls, nor some temple/mosque (unless prominent ones where tourist/local would visited). Maybe there should be a better heading? | |||
==Opinion== | |||
Hi, | |||
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. | |||
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. | |||
Regarding the subpages, I have launched the following: [[Scania K230UB (Euro IV) (Batch 2)]]. Deployment details have been transferred to the respective subpages. | |||
As a trial, I finalised the layout for the first subpage: [[Scania K230UB (Euro IV) (Batch 2)/1]], incorporating your valuable feedback. | |||
Please confirm if the following criteria are met: | |||
# Clear visibility and usability on mobile devices. | |||
# Ease of information references. | |||
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. | |||
Regards, Supernutorcrazy | |||
<!-- | |||
== Re == | |||
Hi, | |||
I guess you are planning to focus more on your new wiki rather than sgWiki... It's ok. I thank you for your contributions. Because Wiki itself is open source, so we can't say copy over to others or what. In fact even LTG or Wikipedia copy over things from here then they cite LTG. | |||
I like your idea very much, but one word of caution I would like to inform you, there is a deep reason why I wanted to shift to this version - similiar to LTG, because editors don't need to maintain or spot the bus. The bus community is very scattered. They kept information to themself, not even posting on this wiki. They claim this wiki is outdated and blast me. So your wiki will share the same fate. | |||
I kept the rego etc there for legacy. If not I will just follow the MRT stations method. You see how I don't need to maintain until erm - Breakdown, Rail opening which comes once in a while? New bus service amendment comes once in a while? | |||
Sorry for the late message, I don't care if anyone steal information over from this wiki or what (it's not my wiki btw, but trying to remain to enforce rules so that it remains civil and less spam), because wiki is supposed to be free, creative-commons non-copyrighted materials that you wish to highlight and share as a community to the public. | |||
As for getting flamed, I don't mind per se, I already had a bad reputation, but I noticed that those who like to flamed others had low ethics, thinking the world resolved around their needs and wants, not sharing or give a thoughts to a bigger picture. While many editors here still support me, and the idea to improve, while those critics still thinking of past practices yet not willing to come here to share, edit and improve. If got fault - push around - it will never be them. | |||
Like what I told you, the community is already flaming me for outdated bus deployment (due to banning people like nobody business) but most of the ban for editing ban is done by other administrators, for me is non-compliance of username requirement as stated. So guess that everything all push to me. So by creating another wiki, this flaming will now attribute it to you. That was my piece of caution for you. :) | |||
--> | |||
==Re:== | |||
Hi, | |||
Using your example: | |||
{|class='wikitable sortable' | |||
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}' width=10%|Registration no. | |||
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}' width=10%|Deployment | |||
!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 | |||
|- | |||
|{{Livery/LTA|SG3101K}} | |||
|{{Bus/SD|LTA|KCDEP}} | |||
|{{N/A}} | |||
|{{LTA Storage/1}} N/A | |||
|- | |||
|{{Livery/LTA|SG3102H}} | |||
|{{Bus/SD|SBST|SWDEP|{{Bus/T|86}}}} | |||
|style='text-align:left'|'''L & R:''' Championing Sustainable Mobility. '''B:''' We Operate The Downtown Line Which Is One Of The World's Most Reliable MRT Lines. We Are Also Singapore's Largest And Most Established Public Bus Operator. | |||
|style='text-align:left'|{{SBST/1}} AMDEP 86 (Dec 2024 - Jan 2025) | |||
|- | |||
|{{Livery/SBST|SG3103E}} | |||
|{{Bus/SD|SBST|SWDEP|{{Bus/T|86}}}} | |||
|style='text-align:left'|Luen Fook Medicine Co Pte Ltd - African Sea-Coconut Brand Cough Mixture 非洲海底椰標止咳露: Effective Against Coughs & Loosens Phlegm. Soothes Irritated & Sore Throats. 止咳化痰 润喉顺气. Relief You Can Trust Since 1945. Made In Singapore. (5th Gen: Yellow & Red) | |||
|style='text-align:left'|{{SBST/1}} AMDEP 86 (Dec 2024 - Jan 2025) | |||
|- | |||
|{{Livery/LTA|SG3104C}} | |||
|{{Bus/SD|SBST|SWDEP|{{Bus/T|86}}}} | |||
|style='style='text-align:left'|Land Transport Authority: Welcoming Our 10 New Electric Buses! | |||
|style='text-align:left'|{{SBST/1}} AMDEP 130 (Jun 2008 - May 2016), AMDEP SP (May 2016 - Aug 2016), AMDEP 21 (Aug 2016 - Oct 2016), AMDEP 13 (Oct 2016 - Dec 2016), AMDEP SP (Dec 2016 - Sep 2017), BNDEP 5 (Sep 2017 - Nov 2018), HGDEP SP (Nov 2018 - Dec 2018), HGDEP 112 (Dec 2018 - Apr 2022), HGDEP SP (Apr 2022 - Dec 2022), HGDEP 156 (Dec 2022 - Jan 2025) | |||
|} | |||
I tried to refrain from using "rowspan" because of the missing line or long scrolling effect, but this is the outcome at Scania subpage, which I chose the 2 longest one available. I'm thinking there may be more longer one at other deployment page, and it feel cramp or cause a long scrolling effect, I feel. Not too sure about you or other. If that is ok, like my previous response, I'm fine with it. But the issue we need to tackle is long-scrolling on mobile. | |||
Regards | |||
===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. |
Latest revision as of 08:54, 12 February 2025
Re:[edit]
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[edit]
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,
User Talk:SBS5251K
Roads Page[edit]
List of roads in Tampines[edit]
Hi,
Can you help me with the bus stops on this page?
Regards,
User Talk: SBS5251K
Merging of pages[edit]
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[edit]
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[edit]
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, 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[edit]
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[edit]
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[edit]
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)
Adding Bus Service Page Links to the “Bus Deployments By Package” Page[edit]
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,
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[edit]
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,
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[edit]
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
![]() |
[ V • T • E ] | ||
---|---|---|---|
![]() |
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[edit]
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)
Non-Wheelchair Accessible Bus Stop[edit]
I had verify some bus stop via the LTA Datamall, there are only 76 bus stop that are non-wheelchair accessible as followed:
Sembawang Shopping Centre | |||||
Service 170X[edit]
For the past few months, I noticed 170X starts from Kranji station (Berth 2) instead of Opp Kranji station. Not too sure of the routing 170X took cause I didn't take 170X from Kranji. SBS Transit staff is present there to manage and guide commuters, so suspected already route amendment without announcement. Didn't really spotted any 170X anymore at Opp Kranji Station (45131).
Re: Nearby Attractions[edit]
As far as I had done, I will try my best to add in big shopping mall when creating the pages, especially those near interchanges, and tourist attractions like 858 (Jewel) and 138 (Mandai Zoo etc). But of course there may be some part where I can missed out. I don't think school should be included, nor those neighbourhood malls, nor some temple/mosque (unless prominent ones where tourist/local would visited). Maybe there should be a better heading?
Opinion[edit]
Hi,
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.
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.
Regarding the subpages, I have launched the following: Scania K230UB (Euro IV) (Batch 2). Deployment details have been transferred to the respective subpages.
As a trial, I finalised the layout for the first subpage: Scania K230UB (Euro IV) (Batch 2)/1, incorporating your valuable feedback.
Please confirm if the following criteria are met:
- Clear visibility and usability on mobile devices.
- Ease of information references.
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.
Regards, Supernutorcrazy
Re:[edit]
Hi,
Using your example:
Registration no. | Deployment | Advertisement | Former Deployments |
---|---|---|---|
SG3101K |
![]() KCDEPSP
|
N/A | LTA Storage: N/A |
SG3102H |
![]() SWDEP86
|
L & R: Championing Sustainable Mobility. B: We Operate The Downtown Line Which Is One Of The World's Most Reliable MRT Lines. We Are Also Singapore's Largest And Most Established Public Bus Operator. | SBS Transit: AMDEP 86 (Dec 2024 - Jan 2025) |
SG3103E |
![]() SWDEP86
|
Luen Fook Medicine Co Pte Ltd - African Sea-Coconut Brand Cough Mixture 非洲海底椰標止咳露: Effective Against Coughs & Loosens Phlegm. Soothes Irritated & Sore Throats. 止咳化痰 润喉顺气. Relief You Can Trust Since 1945. Made In Singapore. (5th Gen: Yellow & Red) | SBS Transit: AMDEP 86 (Dec 2024 - Jan 2025) |
SG3104C |
![]() SWDEP86
|
Land Transport Authority: Welcoming Our 10 New Electric Buses! | SBS Transit: AMDEP 130 (Jun 2008 - May 2016), AMDEP SP (May 2016 - Aug 2016), AMDEP 21 (Aug 2016 - Oct 2016), AMDEP 13 (Oct 2016 - Dec 2016), AMDEP SP (Dec 2016 - Sep 2017), BNDEP 5 (Sep 2017 - Nov 2018), HGDEP SP (Nov 2018 - Dec 2018), HGDEP 112 (Dec 2018 - Apr 2022), HGDEP SP (Apr 2022 - Dec 2022), HGDEP 156 (Dec 2022 - Jan 2025) |
I tried to refrain from using "rowspan" because of the missing line or long scrolling effect, but this is the outcome at Scania subpage, which I chose the 2 longest one available. I'm thinking there may be more longer one at other deployment page, and it feel cramp or cause a long scrolling effect, I feel. Not too sure about you or other. If that is ok, like my previous response, I'm fine with it. But the issue we need to tackle is long-scrolling on mobile.
Regards
Merging of Euro Emission & Batches[edit]
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:
Registration no. | Deployment | Batches (Optional Column) | Advertisement | Former Deployments |
---|
Bodywork differences such as Volvo B9TL CDGE/WEG/Gemilang will not be affected, similiarily to 2D/3D variants.