Difference between revisions of "User talk:Supernutorcrazy"

From SgWiki
Jump to navigation Jump to search
Tag: Manual revert
(Replaced content with "SgWiki is shit and retarded")
Tag: Replaced
Line 1: Line 1:
<!--C851E : 2018 6 NEL 11 CCL 2019 12 CCL-->
SgWiki is shit and retarded
Rules for my feedback to stop irritate me.
 
*Please kindly wait for up to 7 days unless stated otherwise for my reply to your feedback. No reply will be given if your feedback does not require reply or I could not answer to your feedback.
*Please do not ask for general question like '''How to''' etc.
*Please do not ask for permission to do something.
*Please refrain from requesting to retrieved deleted article as excessive history will be cleared.
*When requesting me to edit locked pages, please give either
**Affected sections code
**Advertisement in full
**Affected parts to change in details.
**Avoid statement like '''same as other vehicle'''
*Please kindly indicate Autoblock ID if you have been affected from it.
*I will not entertain any request under BCM transition.
 
<!--
Hi, didnt really watch the whole video (skipped here and there) due to time constraints, will watch it next time, so im going to use your brief summary.
 
I belief that the video was made as some sort of “propaganda” to defame this wiki by just yapping random bullshit which shouldnt really affect most people. However, not every solution can fix problems and could instead generate more unnecessary problems. Such as LTA’s desto eds on buses,  which i dont really see placed into effect in every bus, causes issues especially during peak hours when the bus is queuing up making you have the inability to see the svc number. Those affected by colorblindness probably should know what color it is even if its inverted or a different color. Those affected also should have seen the color of logos (even if different color) before and know what operator it is. The only thing that there is no solution for is white-black color blindness which is rare and not nessescary to find a solution.
 
Next, about rowspan or colspan that is just a common sense problem idk who would jist see an empty blank and uhh say theres nothing there, lmao what shit is he doing. One solution, is not using vertical-align:top.
 
Yea and thats all.
 
==Staggered Bus Stop for Bus Service Pages==
{| class="wikitable"
!Bus Stop!!Service
!Bus Stop!!Service
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS10017|int=(Front Berth)}}||{{Bus/61}} {{Bus/124}} {{Bus/143}} {{Bus/147}} {{Bus/166}} {{Bus/197}} {{Bus/961}} {{Bus/961|a=M}}
|{{BS10017|int=(Rear Berth)}}||{{Bus/2}} {{Bus/12}} {{Bus/12|a=e}} {{Bus/54}} {{Bus/122}} {{Bus/167}} {{Bus/174}} {{Bus/174|a=e}} {{Bus/190}} {{Bus/196}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS45139|int=(Berth 1)}}||{{Bus/160}} {{Bus/170}} {{Bus/178}} {{Bus/960}} {{Bus/961}} {{Bus/961|a=M}}
|{{BS45139|int=(Berth 2)}}||{{Bus/170|a=X}} {{Bus/925}} {{Bus/925|a=M}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS46101|int=(SG Buses Berth)}}||{{Bus/160}} {{Bus/170}} {{Bus/170|a=X}} {{Bus/950}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS46109|int=(SG Buses Berth)}}||{{Bus/160}} {{Bus/170}} {{Bus/170|a=X}} {{Bus/950}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS46211|int=(Berth 11 & 12)}}||{{Bus/160}} {{Bus/170}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS46219|int=(Platform A, SBS Transit Berth)}}||{{Bus/160}} {{Bus/170}} {{Bus/170|a=X}}
|{{BS46219|int=(Platform B, SMRT Buses Berth)}}||{{Bus/950}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS51071|int=(Inner Berth)}}||{{Bus/93}} {{Bus/156}} {{Bus/157}}
|{{BS51071|int=(Outer Berth)}}||{{Bus/52}} {{Bus/74}} {{Bus/130}} {{Bus/132}} {{Bus/165}} {{Bus/166}} {{Bus/167}} {{Bus/852}} {{Bus/855}} {{Bus/980}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS65191|int=(Berth 1a)}}||{{Bus/3}} {{Bus/34}} {{Bus/109}} {{Bus/110}} {{Bus/118}} {{Bus/168}} {{Bus/858}} {{Bus/969}}
|{{BS65191|int=(Berth 1b)}}||{{Bus/27}} {{Bus/88}} {{Bus/89}} {{Bus/89|a=e}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS65199|int=(Berth 1a)}}||{{Bus/27}} {{Bus/34}} {{Bus/110}} {{Bus/118}} {{Bus/168}} {{Bus/858}} {{Bus/969}}
|{{BS65199|int=(Berth 1b)}}||{{Bus/3}} {{Bus/88}} {{Bus/89}} {{Bus/89|a=e}} {{Bus/109}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS92041|int=(Front Berth)}}||{{Bus/15}} {{Bus/36}} {{Bus/135}} {{Bus/966}}
|{{BS92041|int=(Rear Berth)}}||{{Bus/31}} {{Bus/43}} {{Bus/43|a=e}} {{Bus/48}} {{Bus/134}} {{Bus/196}} {{Bus/196|a=e}} {{Bus/197}} {{Bus/853|a=M}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS95029|int=(Berth 1)}}||{{Bus/36}}
|{{BS95029|int=(Berth 2)}}||{{Bus/53}} {{Bus/110}} {{Bus/858}}
|-
|{{BS95029|int=(Berth 3)}}||{{Bus/24}} {{Bus/27}} {{Bus/34}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS95109|int=(Berth 1)}}||{{Bus/36}}
|{{BS95109|int=(Berth 2)}}||{{Bus/53}} {{Bus/110}} {{Bus/858}}
|-
|{{BS95109|int=(Berth 3)}}||{{Bus/24}} {{Bus/27}} {{Bus/34}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS95129|int=(Berth 1)}}||{{Bus/36}}
|{{BS95129|int=(Berth 2)}}||{{Bus/53}}
|-
|{{BS95129|int=(Berth 3)}}||{{Bus/110}} {{Bus/858}}
|{{BS95129|int=(Berth 4)}}||{{Bus/27}}
|-
|{{BS95129|int=(Berth 5)}}||{{Bus/34}}
|{{BS95129|int=(Berth 6)}}||{{Bus/24}}
|-
|height=1 style='background-color:#000;' colspan=4|
|-
|{{BS95209|int=(Berth 1)}}||{{Bus/36}} {{Bus/110}}
|{{BS95209|int=(Berth 2)}}||{{Bus/24}} {{Bus/34}}
|-
|height=1 style='background-color:#000;' colspan=4|
|}
 
 
<!--
== Affiliation with my wiki ==
Hi,
 
I created my own wiki on [www.miraheze.org Miraheze] a free wiki creation page. I created it to mimic the [transportsg.me/lookup Bus Lookup], since that website uses the info from your wiki, so i thought of the affiliation thing, the wiki is currently still a WIP with one page called SBS1Z as of this message. If you want to discuss about accepting the affiliation or terms & conditions, do drop a message. The wiki is called [sgbusdeploymentinfo.miraheze.org SG Bus Deployment Info]. Don't spread info about the wiki as its still in its very early stages of development.
 
Nah, i will still focus on sgWiki more since im forking pretty much everything or most of it, I actually want a way where the community can actually find deployments easier like transportsg.me/lookup (if I didn't clarify properly). About flaming, I stated clearly that the wiki forks information from your wiki so eventually you will still get flamed (I'm sorry if that happens).
 
So my intentions for my wiki (to make things clear):
 
* A convenient tool for checking deployments. (nobody wants to scroll a whole list of regos in a bus model page)
* They can't edit every page, they have to edit using your wiki and I will transfer information to my wiki. (to protect your wiki)
* NO INTENTIONS TO TAKE OVER YOUR WIKI (since yours is about Transport in Singapore for the community and the public's use while mine is meant for the community as a convenient tool)
 
Read my wiki about page for more information.
-->
 
==Leave your message below==
===Rail Wiki Expansion===
Hi Supernutorcrazy,
 
Is it OK to add info of train deployments (including TRNs and their sequences), acronyms legend and train fleet info (similar to what's done for buses)?<br>
Data can be obtained from here: https://docs.google.com/document/d/1PMuCeF31etWzPv_U42qMaFoHvYwDpnkSWHgjvuuTxdg/edit<br>
All data collated in the above document are based on spottings and observations from fellow enthusiasts.
 
I hope you will support us to make these valuable information more accessible to all. Thank you.
 
== White/blue UPD sticker ==
 
Hi,
 
The white/blue UPD stickers differentiate UPDEP buses between those under tendered contract (white) and those not (blue). This is exspecially a problem for UPDEP spare fleet, and buses in depots like AMDEP, BNDEP meant for Bukit Merah package. Hope this helps.
 
Regards,
Kay
 
== Re formatting of some svc fleet and all bus fleet pages ==
 
Hi I’m just wondering why is all bus fleet pages alongside some svc fleet pages completely changed by someone who's “destroying” sgwiki completely & thinking it’s his own personal website and this makes it annoying for us editors to edit things right now I really hope u do revert most of the old format changes back as editors like me definitely do prefer it.
 
== Re: reformatting of bus service pages ==
 
Hi, I see why you and sgbustrain may want to reformat it to make information more easily accessible by displaying information about each bus service all on 1 page. However, by reformatting these pages, they basically show information similar to what other websites and apps display. They will just be like landtransportguru’s bus service pages, but with much less information (i.e. route length, travelling time, and many photos of the bus service), rendering these SgWiki pages useless and replaceable. Even if you still insist on reformatting pages to have a page for each individual bus service, I hope that it will also include information like perm buses, down routes, duty table, etc. In conclusion, Sgwiki’s pages should offer something different and not just duplicate existing pages. Thanks.
 
Regards,
LTA Bus Irrationalisation
 
== Bus History page ==
 
Hi is it possible that 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)
 
==Nearby Attraction issues==
Hey, do people even add nearby attractions, schools, malls, etc. editiors just add train stations and not care, is it still even right to use the term "Nearby Attractions" or should it be "Train Stations".
 
==Bus Service 298 Fleet Trial==
Please consider quantity of a particular bus model to make it easier for people to count and add a link to bus model pages to navigate easily.
 
== removal of overnight parking bus park like BRBP, CGBP etc and using the parent depot control like AMDEP, BNDEP etc for former deployments ==
Hi,
 
As BRBP is an overnight parking bus park, I would suggest those former deployments for BRBP to be edited to AMDEP because BRBP parent depot control was formerly under AMDEP before being given to HGDEP due to the permanent closure.
 
For example BRBP 60, BRBP 90, BRBP 141 etc to AMDEP 60, AMDEP 90, AMDEP 141 etc
 
As CGBP was an overnight parking bus park before closure and the parent depot control was BNDEP, I suggest the removal of overnight parking bus park and usage of parent depot control instead.
 
For example CGBP 4, CGBP 47, CGBP 81 etc to be removed
 
Thanks.
 
== SBS prefix section on bus ad page lags badly on phone ==
 
Hi, can you consider removing all the N/A columns on the bus ad page as they cause unneccesary lag. What's the point of having the N/A columns, just like how the non revenue buses page only list buses that are non revenue instead of all buses.
 
My suggestion:
 
===Double deckers===
====SBS-registered====
{| class="toccolours" border="1" cellpadding="3" style="border-collapse:collapse"
|-class="BUS"
!Registration no.
!Model
!Advertisement
|-
|SBS18B
|Volvo B9TL<br>''(WEG2 Batch 4)''
|rowspan="2"|ABC Holdings • ABC Enterprise: Join Us Now.
|-
|SBS3888L
|Volvo B9TL<br>''(WEG2 Batch 3)''
|-
|SBS7588B
|Volvo B9TL<br>''(WEG2 Batch 1)''
|Lorem Ipsum Pte Ltd - Lorem Services: Flat Rate For New Users.
|}
 
== New Bus Service Pages ==
 
Hi there,
 
Just wanted to point this out as my capacity as a user of this site, I do not think it is right for the new Bus Service pages to have its service description completely copy pasted from Land Transport Guru, even if only certain paragraphs are copy pasted.
 
This is in violation with the Copyright Act and is a serious issue. Unless the person editing the information here is also the person who is editing the information on Land Transport Guru, this is very unethical in practice. Even if credit is given to the source, Land Transport Guru, it seems like no effort is being made at all to paraphrase or craft out any service description to be uniquely for sgWiki.
 
Regards,
Themystery
 
== History Page for Defunct Services ==
 
Hi supernutocrazy,
 
Just wanted to propose something for the bus service history pages. After all existing services have their own page with their own history, perhaps we could remove all the "refer to bus service xxx for more info" and compile all the defunct services' history into one single page, like what was done with advertisements. However, this may be inconvenient for users as the page will be extremely long. So another option is to seperate them by SBST defunct services and TIBS/SMRT defunct services (or TTS/GAS if any).
 
Regards,
svc135bsoe
 
== Reply regarding to opinions of proposal changes ==
 
===Put your replies here===
*23ispolo:
*8549H:
*Al92:
*Alphabetlorefan1: Hi, I saw what you wrote on my discussions page. I would like to say, it would be so great if we have a bus spotting page. This can help everyone to type in what they saw. This one can go easy. Second, speaking of subpages for respective bus models, that would be so cool if we do that. I mean I would like to see what it looks like. Never seen a subpage in sgWiki before. sgWiki should be improved with suggestions like these. Thanks.
*BusFan74: Hi, I saw the message that you wrote on my discussions page. Like Alphabetlorefan1 said, bus spotting page can be useful based on observations. I like that suggestion because this wiki has not created a subpage here before. First of all, the page is neatly organized and I liked it, easier than cluttered. Thank you.
*CastJared: Hi. I agree with this format, because, I praise on the subpages that hasn't created it before on this wiki. Thanks.
*Gabrielcheong:
*Haram:
*Hearmeout:
*Matthiasgoh76:
*SBS3720L: Yes, in agreement with other editors, bus spotting page is indeed useful in terms of deployment accuracy. As for sub-pages in regards to advertisements, personally, I feel it is redundant to include that as part of the main table. Because, advertisements are just there for maybe 3-4 months before they are removed, whereas all other information are a necessity to keep track of the bus activity throughout its lifespan (I.e. operator, service and depot are needed info to update former deployments). Unless there's a page that keep track of ALL the advertisements a bus had pasted in its lifespan, I feel there's not a need to include advertisement as a column. On mobile, the current 4 columns already looks very squeezy.
*Sgbusntrain: Yes, subpages would be better especially since some enthusiast go to places to spot buses using the deployment pages, but most of them use their phones as it is the easiest thing to carry around instead of a tablet or a computer. For the advertisement page, it would be better to merge them into their own bus model deployment pages, for easier reference, especially {{TTS}} buses where you can check whether the ad has expired (BUD/MDD FD) or whether it is still active (BUD/MDD Svc). Now about the bus spotting page, i do not see the need to create one as this wiki already has problems about pofma, like how deployments are changed when a bus does a cameo once. Due to the pofma problems, and the gradually increasing amount of fake cameos, the bus spotting page will be not be that useful if wrong information gets increasingly added. About the columns, I believe they all should work fine, just wondering about the operators and deployments, as the operators can also be found at the former deployments section why not use that to show operators since dupe info anyways. E.g. {{TTS}}/{{TTS/1}} MDDEP FD (Jun 2020 - Sep 2024) '''MDDEP 169 (Sep 2024 - Present)'''
*Sgeditransport5929:
*Svc135bsoe: Sorry for the late reply. Anyways I wanted to say that the bus spotting idea is wonderful, for both deployment accuracy and also since we currently do not have much bus spotting lists online. It happens to be out today and is looking great, so keep it up! About the bus deployments by model, I am completely fine with maintaining the status quo, as advertisements change over time and have to be updated frequently. Hence I feel it is unnecessary to include advertisements as a column and the current seperate advertisements and deployments lists are fine. However I am in agreement that the seperate pages for each 100 buses are more mobile-friendly and can be implemented.
*Themystery:
*TTEDC: While I advocate for the integration of the advertisement page into the main fleet page, I must stress my view that foldable boxes (where one has to click to open the information) should be implemented simultaneously to accommodate the long information of advertisements and former deployments. I express no strong opinions on the sub-page or bus spotting pages proposals.
 
== What is going on with sgWiki right now? ==
 
On my last edit in 2024, the layout is normal. But when I came back today, what I saw on the [[Alexander Dennis Enviro500 (Batch 1)]] page, the layout changed, and something happened. What is sgWiki now?
 
== Reply: Opinion ==
 
Good day.
 
I shall pass the first question.
 
Yes, I have to admit that the information is inaccurate these days, and I don't wish to update it as the process is more complicated than the previous version of the wiki.
 
If we are heading towards the subpages, I suggest merging all the batches under one main page.
 
Take Volvo B9TL fleet as an example:
* Volvo B9TL/SBSxx
* Volvo B9TL/SBS30xx
* Volvo B9TL/SBS31xx
* Volvo B9TL/SBS32xx
* Volvo B9TL/SBS33xx
* Volvo B9TL/SBS34xx
* Volvo B9TL/SBS35xx
* Volvo B9TL/SBS36xx
* Volvo B9TL/SBS37xx
* Volvo B9TL/SBS38xx
* Volvo B9TL/SBS39xx
* Volvo B9TL/SBS75xx
* Volvo B9TL/SBS76xx
* Volvo B9TL/SBS77xx
* Volvo B9TL/SG50xx
* Volvo B9TL/SG51xx
* Volvo B9TL/SG53xx
* Volvo B9TL/SG54xx
* Volvo B9TL/SG55xx
* Volvo B9TL/SG56xx
 
===Current deployments===
{|class="wikitable sortable"
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Registration no.
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Operator
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Deployments
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Advertisement
|-
|{{Livery/LTA|SBS1Z}}
|rowspan=3|{{GAS|75px}}
|'''LYDEP''' 2
|{{N/A}}
|-
|{{Livery/LTA|SBS2X}}
|'''LYDEP''' 3
|ViewQuest
|-
|{{Livery/LTA|SBS3T}}
|'''LYDEP''' 6
|Parkway East Hospital
|}
 
===Former deployments===
{|class="wikitable mw-collapsible mw-collapsed" border="1" cellpadding="3" style="border-collapse:collapse"
!colspan=2|Click to expand/collapse
|-
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Registration no.
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Former deployments
|-
|SBS1Z
|{{SBST/1}} BNDEP 7 (Aug 2015 - 2016), BNDEP 2 (2016 - Sep 2016)<br>{{GAS/1}} LYDEP FD (Sep 2016 - Sep 2022), LYDEP 12 (Sep 2022 - Feb 2023)</span>
|-
|SBS2X
|{{SBST/1}} BNDEP SP (2015 - 2016), BNDEP 2 (2016 - Sep 2016)<br>{{GAS/1}} LYDEP FD (Sep 2016 - Oct 2022), LYDEP 518 (Oct 2022 - Jan 2023)
|-
|SBS3T
|{{SBST/1}} SLBP 181 (2015 - 2016), BNDEP SP (2016), BNDEP 118 (2016 - Sep 2016)<br>{{GAS/1}} LYDEP FD (Sep 2016 - Mar 2017), LYDEP 43 (Mar 2017 - May 2017)
|}
 
Cheers.
 
===Deployments page (alternative with Batch & lifespan expiry date) & registration coloring===
 
Specs will still be different across all 4 batches. Will work on a sample soon
 
Ads do not need to be that detailed imo. Just company & campaign/product will do
 
{|class="wikitable sortable"
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Registration no.
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Batch
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Operator
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Deployment
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Advertisement
!style='{{CSS/BUS|xfc=|xbc=|bgop=a0}}'|Lifespan expiry date
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Former deployments
|-
|{{Livery/SBST|{{SBS3238M}}}}
|2
|rowspan=3|{{SBST|75px}}
|'''SWDEP''' 25/660*//80/80A*
|ABC Holdings Inc • Peach Mart - 3.3 Mega Sale
|23 Dec<br>2029
|style='text-align:left'|<span class='mw-collapsible mw-collapsed'>{{SBST/1}} AMDEP 13/13A* (2012 - May 2024), AMDEP 145 (May 2024 - Jan 2025)
|-
|{{Livery/SBST|SBS3240E}}
|rowspan=4|3
|'''BNDEP''' 39
|Land Transport Authority - Friendly Streets
|rowspan=3|29 Jan<br>2030
|style='text-align:left'|<span class='mw-collapsible mw-collapsed'>{{SBST/1}} AMDEP 22 (Feb 2013 - May 2022)
|-
|{{Livery/SBST|SBS3241C}}
|'''HGDEP''' 410W
|Land Transport Authority - Chinese New Year Celebrations 2025
|style='text-align:left'|<span class='mw-collapsible mw-collapsed'>{{SBST/1}} AMDEP 59, AMDEP 410W (till Jan 2025)
|-
|{{Livery/SBST|SBS3242A}}
|colspan=3 {{BDRS}}
|style='text-align:left'|<span class='mw-collapsible mw-collapsed'>{{SBST/1}} AMDEP 133 (Feb 2013 - Oct 2017), HGDEP 161 (Oct 2017 - Dec 2022), HGDEP 80 (Dec 2022 - Mar 2023), HGDEP 89 (Mar 2023 - Dec 2024), HGDEP 80 (Dec 2024 - Jan 2025), SWDEP 80 (Jan 2025)
|-
|{{Livery/SBST|{{SBS3243Y}}}}
|{{SMB|75px}}
|{{BUR}}<!--'''SLDEP''' 249-->
|{{N/A}}
|12 Feb<br>2030
|style='text-align:left'|<span class='mw-collapsible mw-collapsed'>{{SBST/1}} SLBP 199 (Feb 2013 - Aug 2024)<br>{{SMB/1}} N/A
|}
 
Notice for {{SBS3238M}} & {{SBS3243Y}} there's a template so that operator column will no longer be needed. When a bus transfers to another operator just change the template format
 
Plus, emissions shall have seperate pages (ie. for K230UB, NL323F & ND323F one page for each emission. SG2017C would be an issue though but I would put it as Euro 6 demo
 
===Question===
Have you considered the opinions of other users before implementing the updated format? Defeats the purpose of our inputs if you are going to implement your idea.
 
== Merging of Euro Emission & Batches ==
 
Yes I feel Merging of Euro Emission & Batches is a good idea.
 
== Disagreement in Merging of Euro Emission & Batches ==
 
Disagree. As we all know, these models, namely Volvo B9TL (Wright Eclipse Gemini), Mercedes-Benz O530 Citaro have more than 1000 buses each. And there will be important variants here and there, which is the main reason why the page separates the variants according to Batch and Emissions.
 
 
I would also like to point out that what we are currently doing, splitting clustered current bus service pages into individual services - has been a way of easing and segregating the volume of editing, and focuses more attention on the bus service itself.
 
 
However, merging everything into one bus model page makes the subpages extremely clustered and defeats the purpose of trying to track a bus. Let me explain in detail why.
 
 
The current split Scania K230UB Euro IV (Batch 2)/1 to Scania K230UB Euro IV(Batch 2)/4 has made editing easier because of simpler titles for respective regos, a lesser need to scroll down, and from a batch of 400 buses, is simplified to finding 100 buses each out of 4 subpages - similar to Scania K230UB Euro IV (Batch 1) which has only 100 buses. This only requires 2 steps - searching batch, then click on subpage, which takes negligible time, and scrolling through 100 buses, which is just a short timespan.
 
 
However, when putting everything into one Scania K230UB page, it is going to be 1400 buses and 12 subpages. That means a more time is spent on hesitation to check which subpage one should click on to find the registration. Furthermore, some of the K230UB registrations already crisscross one another in emissions and registrations, namely 81xx in Batches 1 & 2, 85xx in Euro IV and Euro V, and SBS8888D, a supposed Euro V registration registered into a Euro IV bus.
 
 
Similarly for B9TL (Wright Eclipse Gemini), that is more than 1600 buses in at least 19 subpages, and Citaro in more than 1100 buses in 14 subpages. The current problem that the admin wants to address is about too many buses based on Batch/Emissions, but having too many registration subpages based on one model isn't going to solve the root cause of the issue. Would users rather find 1÷100 OR 1÷14÷100?
 
 
From what I understand, when most in the bus community search for a registration with bus specifications they already know, they look for the emission/batch first, then they view the current and the former deployment. In the other way round, if an unfamiliar newcomer searches for a bus registration, the wiki results can already generate the page that clearly states the model and batch/emission in the title. See pic below.
 
[[File:Sample Bus Rego Search Result.png|left|300px]]
 
 
If batch numbers and emissions are to be squeezed beside the bus registration box, it is going to be viewed as excessive information by readers, which is the opposite effect of what is intended on the current batch/emission pages. As many editors here explore many factors including mobile viewing - this proposed arrangement is also going to make things difficult for mobile users too, as each column has little space to display so much information in one table.
 
 
To conclude my opinion, merging too much information is not going to simplify the search for a bus registration.
 
 
If there is anything I would suggest, I would say that the current subpages among batch/emission pages is already an improvement for viewing and editing - the Scania K230UB Euro IV (Batch 2)/1 to Scania K230UB Euro IV(Batch 2)/4 already addresses the main issue and this should be implemented on other bus model pages with hundreds of buses.
 
Wekelwrady
 
: I would like to voice my agreement with the views expressed above by Wekelwrady.<br/>Regards, TTEDC
 
Yeah. I think I didn't want for this because it creates a confusion.
 
==Ur plan for merging==
 
I think its good idea where we can just see one page for one specific model which is good, less troublesome just changing pages when editing the exact same model but different batch.
 
But the issue comes when buses just have the continuous number e.g. ND323F EV B2 which goes from 5740 to 5799, subpages just gonna have one batch making it useless (SG57XX like what you did in the kub), next is spec, im concerned about the specifications as each batch has its unique specs squeezing all specs into one main page will confuse people, no one wants to read the crammed tables just to find what they need.
 
So, i HIGHLY do not recommend merging.
 
To rethink erm, ill give a proposed format
 
[[User:Sgbusntrain/Proposed format]] (interactive)
 
or
 
<div style='display:flex;flex-wrap:wrap;text-align:center;margin-bottom:1em'>
<div style='padding:0 .5em;flex-grow:1;border-bottom:1px solid #888'>[[Alexander Dennis Enviro500 (3-Door)]]</div>
<div style='padding:0 .5em;flex-grow:1;border-bottom:1px solid #888'>[[Alexander Dennis Enviro500 (Batch 1)]]</div>
<div style='padding:0 .5em;flex-grow:1;border-bottom:1px solid #888'>[[Alexander Dennis Enviro500 (Batch 2)]]</div>
</div>
 
just putting this on top
 
Give some thought and probably ask around for feedback
 
== Adding links to bus interchanges in BS Template ==
 
Hi Supernutorcrazy, is it ok if I add a link into the BS template when there is a bus interchange page? It will look something like this as an example:
 
{{BS00000|code=65009|stop=[[Punggol Bus Interchange|Punggol Temp Int]]<span style='font-weight:normal;padding-left:.3em;'>{{{int|}}}</span>|road=Punggol Pl|icon=Bus}}
 
An example of this template (note its not edited yet) when the Punggol Bus Interchange is created. Lets see if you are ok with it when replying.
 
Thanks
 
[[User:Alphabetlorefan1|Alphabetlorefan1]] ([[User talk:Alphabetlorefan1|talk]]) 10 February 2025, 11:23
 
===Reply===
Hi Supernutorcrazy, nice template design tho. I think I am ok with that template design due to it having hyperlinks.
 
Thanks
 
[[User:Alphabetlorefan1|Alphabetlorefan1]] ([[User talk:Alphabetlorefan1|talk]]) 11 February 2025, 11:39
 
===Add on===
Is it possible to introduce subpages of the bus stop templates to standardise the nearby attractions of these bus stops?
 
===Elaboration to support Hearmeout's case===
I think that landmark standardisation is an advantage that we can make use of to display where the bus routes stop at, because it first and foremost provides community benefits. I won't ask the admin to rush/immediately create for my elaboration, but I can say positively that when I see admin displaying "CCK Polyclinic" in the 975 page (even I wont be reminded abt Polyclinics until I now know), this gives me a framework to display the following important landmarks. <br>
- MRT stations (first and foremost, already implemented) <br>
- Shopping malls/plazas that are publicly known <br>
- Town Centres (Grouped into a name, eg. Tampines Hub, Heartbeat@Bedok, J Connect, One Punggol) <br>
- Government Polyclinics <br>
- Publicly known Civil Service Institutions (ie. "Official Open" classification such as NS Hub, CMPB)<br>
- Tertiary Institutions (priority for those approved under AGC, followed by ITE)<br>
- Major tourist destinations like theme parks, museums, building icons (that cover a suitable and specific area eg. Gardens by the Bay, National Gallery Singapore) <br>
I of course know that there's still lot to do, but I think we can make this the first item as an afterthought only after all bus services are created (and of course I will bundle that completion of the truncation of alternate travel pages tgt with the bus services).
 
== Phase 1 work on TWE ==
 
Heads up, I will be starting to renewing templates for TWE and finish up on Tampines.
 
<!--
The situation looks like CRL3 will remain a dotted line in the long run so I think Joo Koon's hub status is going to remain as such.
!-->
 
== Reply ==
 
Hey, replied to you on my [[User talk:Dragomir7|talk page]]. [[User:Dragomir7|Dragomir7]] ([[User talk:Dragomir7|talk]]) 12:03, 7 March 2025 (+08)
 
^
 
:Dude ... tell you what. Sure you can reserve all the pages for defunct services (move their titles to "History of defunct services XX - YY" or whatnot) but listing each and every one of current service [https://sgwiki.com/index.php?title=History_of_Bus_Services&diff=668528&oldid=668483 in this way] is more than not just going to increase the clutter and colour glare on the page, AND it creates trouble for users who want to look at the histories of current services with a smooth flow because now they have to backtrack for each step, and comparing side-by-side (say svcs 2 and 3, or 2 and 2A) also becomes difficult.
 
:That's why I added the [https://sgwiki.com/index.php?title=Bus_Service_10&diff=prev&oldid=668476 transclusions] earlier on to facilitate the smooth display of historical information of existing services in their own right on a dedicated page (which you appear to have [[:Special:Log|deleted]]), in a way that doesn't result in repetition while causing the least disruption to existing viewing habits. Hope this explains. [[User:Dragomir7|Dragomir7]] ([[User talk:Dragomir7|talk]]) 12:52, 7 March 2025 (+08)
 
== Reply to the upgrades ==
 
Yeap, I am aware about the significant upgrades that you have made to a few bus service pages. It actually took quite some time for me to digest each of the new templates and revised tables that admin has introduced, especially on the Service 15 page. Therefore, I created a new Service 154 page for your review to ensure that I have completely understood the new page formats.
 
Once done, I will also allocate time to completely upgrade 2-3 batches of bus service pages + 5xx express services. Thanks and Regards
 
== Re: Warning Point ==
 
Hi, I saw what you put on my talk page. Ok I am sorry for not updating the former deployments but I will update them. That is because they have been doing these service in the past few weeks so thats why.
 
I did not know former deployments is needed to update
 
RobloxXF

Revision as of 22:43, 14 March 2025

SgWiki is shit and retarded

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