Difference between revisions of "User talk:Supernutorcrazy"

From SgWiki
Jump to navigation Jump to search
(125 intermediate revisions by 19 users not shown)
Line 1: Line 1:
<!--C851E : 2018 6 NEL 11 CCL 2019 12 CCL-->
<!--C851E : 2018 6 NEL 11 CCL 2019 12 CCL-->
<!--This section are reserved for unsolved case
== User SBS3107H ==
Hi could you remove SBS3107H as admin? I feel he doesn't deserve the admin role from the way he reverts edit for no rhyme or reason,and editing it back himself, before he starts blocking users
== User SBS3107H ==
to add on the above feedback regarding SBS3107H, i have actually make the same feedback earlier to APEX-LW21 last week. many incorrect edit by this user and also, recently he undo CORRECT edit for new registration for B5LH page and lock the page and reedit himself with the same information. why? is that B5lH section reserve entirely for him?
EDIT: ADD ON 20/3, just discover that he is doing the same for MAN A95/MAN A22 BATCH 4 PAGE. other person edits new registration (under Go-ahead) and he undo all the edit of these registrations? and he edit it back himself? so being a moderator is allowed to do this?
rgds
lemon1974
-->
Rules for my feedback to stop irritate me.
Rules for my feedback to stop irritate me.


Line 28: Line 12:
**Avoid statement like '''same as other vehicle'''
**Avoid statement like '''same as other vehicle'''
*Please kindly indicate Autoblock ID if you have been affected from it.
*Please kindly indicate Autoblock ID if you have been affected from it.
*I will not entertain any request under BCM transition.


==Leave your message below==
==Leave your message below==


== RE: About the Wiki ==
===Rail Wiki Expansion===


Hi Supernutorcrazy,
Hi Supernutorcrazy,


I'm sorry to hear about the false accusations which led to the Wiki's current state, however I believe that does not mean that their "beliefs" should get in the way of maintaining order in the Wiki.
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.
 
== Sengkang / Punggol LRT Route Map, Plaform Layout ==
 
No objections for Sengkang / Punggol LRT route to be entirely based on geological layout. Initially thought that the EWL Changi branch can also be my point of reference, but geological layout is more logical. For the subsequent LRT stations do we just only include the stations that are within the direction of travel within the loop + opposite loop?
 
Looking at the platform layouts, I believe we have more than enough space to implement the pictograms bah. Nothing comes to mind that any of the elevators/escalators, faregates, Passenger Service Centre would clash together in one layout. Ticketing machines should be easy to find unless the machines that only accept cash are hard to find within a station, so I don't think that would be a priority.
 
I have two different takes on exit layouts. One is within the station concourse, and the other, the Locality maps that we are all familiar with. I personally feel that it is more important to indicate the exit locations within the concourse. As for Locality maps, would rather think of putting it on the Alternative Travel Methods pages of certain stations. Can disregard if the locality maps are very detailed in indicating bus stops eg. Maxwell, otherwise, maps that date back to the early 2010s eg. Chinatown, Boon Lay or lacking in detail really need some updated exit map guidance so that we can convey to them where the bus stops are.
 
===Reply===
I think we are good to go with sticking with a single line option for an LRT layout so that there is a clear sense of direction. We will not need an entire loop.
 
And just nice! City Hall platform and concourse illustrations perfectly fit what we are looking for. I would strongly encourage to give this kind of design a go. Maybe you are right, provided if no size constraints on the wiki page, for an afterthought, we can consider putting the ticketing machine positions after we get everything laid out.
 
You and I are also on the same page when it comes to Locality Map presentation. There is indeed lots of inconsistency in various stations. I had once wrote in asking the authorities and MRT operator to get the 2013 Chinatown map upgraded, they say they would, but I have not heard a word from them ever since, nor was it renewed. I believe getting every MRT/LRT station to have the newer TEL standard map will take eternity. Raffles Place map may have upgraded, but in turn did not reflect OCBC Bldg or Prudential Twr bus stops.
 
For a start, I think we can focus on just three details on a map on this wiki: Road Shape, Exit Alphabets/Numbers, and Bus Stops with numbers. Important amenities second, that would be an afterthought. In this way it will be less exhausting, and we can make better effort and productivity for make such map layouts for every station.
 
===Reply (11/1/2023)===
Road name, 5-digit bus stop code, the suggested visual markers and exit numbers as the main map details should work fine. Looking forward to implementation! Maybe we can try out City Hall first, the road shapes there are almost straight, and not really much development happening nearby. Do let me know how much time it takes to make such a sample map.
 
Oh and one more question, is the line layout supposed to like only reflect one station code at transfer stations?
 
Would like to seek advice. Thanks and regards.
 
===Reply (12/1/2023)===
 
In chemistry, only a suitable range of the amount of catalyst added will increase the rate of reaction. If we use an excessive amount of catalyst, there will be little effect on the rate of reaction.
 
Like how we have 200+ stations in Singapore, we will find that implementing locality map on an image graphic can be done within a year, which you say can use Photoshop for processing, and that might spur us in finishing the job. Even if editing means that we have to replace the image graphic, but assuming replacing the image graphic=same process as implementing image graphic first hand, few days of editing will still be worth it. On the opposite hand, we might find ourselves giving up halfway in implementing a wiki html, though initially it sounded tempting that a future edit would be easier, and that adds up to more than a decade and a half. That would be comparable to growing a gingko tree and waiting for it to bear fruit.
 
I was also thinking, we can straightaway dive directly into exits numbers/layout to platform layout/concourse as one of the choices selected, since this type of implementation is also doable within the one day range. Looking forward to how the effect will look like so that we can compare.
 
== Map progress ==
 
Thanks for the update! Will this 5 min walking speed be the standard plan for all stations? Because I am about to plan to send over the map screenshots with all the required 5-digit stop codes(as remarks) reflected in the alternative travel pages.I will do my best to assist in this process.
 
== Reply: Fleet Size of 912 ==
Hi.
 
I will leave the fleet size as 4 for now. As far as I know they only have 4 buses scheduled with 5 AP duties every day.
 
== Concourse and exit layout WIP ==
 
Bedok draft has been sketched from Photoshop, and I am on my way to collect more icons, and will make a visit to Admiralty probably next week to trial a similar layout.
 
Current elevator dimension is 160x160 on a side note.
 
As discussed before, I agree that there is indeed a need for a file sharing system, especially for icons. Thanks and Regards
 
== User : Draconite Dragon ==
 
Hi Admin,
 
I would like to bring your attention to this user : https://sgwiki.com/wiki/Special:Contributions/Draconite_Dragon
 
 
On 30 Jun 2023, he claimed that SG6198L and SG6199J has been on 161 for a week on his talk page. As I am a regular passenger of Service 161, I have never seen these 2 buses perform any trips of 161.
 
(Link : https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584281)
 
 
He then removed SG6077C and SG6102M from 161. However, these 2 buses were still being spotted daily.
 
(Link for pictorial proof : https://www.instagram.com/p/Ct9AGtXxp8T/)
 
 
After playing a cat and mouse game of undoing and redoing edits, he suddenly removed the two buses (SG6198L and SG6199J) from 161 and added them into 154, despite "saw it doing 161 for a week or more.".


As much as you are "not allowed to moderate", I believe that, at the very least, sgWiki Guidebook guidelines should be enforced until Jason resolves the issue with all Administrators & involved infiltrators.
(Link : https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584379 and https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584379)


I know that there are other wikis out there that are getting constantly vandalized, and it is also just as difficult keeping things in order as well as starting a whole new wiki, having to set up all pages again to provide relevant info.


I'm sorry if I sound imposing, but it is for the good of the wiki.
I believe this is not the only standalone case. The user has made many edits and some edits involved shuffling in buses into a service and then removing them a few hours later.  


Regards,<br>DarkNight
(Link : https://sgwiki.com/index.php?title=Special:Contributions/Draconite_Dragon&offset=&limit=500&target=Draconite+Dragon)


== About a username change... ==


Good evening sir,
I believe his edits are just merely acts of vandalism, and those buses he proclaimed to be on whichever services, do not actually exist.


I was wondering if I could get a username change to a SMRT registration number. Just like how some users have bus plates in their username. Eg. SG5064X, SMB1572U etc.
 
Please do take a while to look at his edits, as there are a lot of inconsistencies in his edits, which would cause a lot of reliability issues with the wiki.  


Regards,
Regards,


SimonLim88
Haram
 
== Recent edits==
 
Hi admin,


== Reply: Seeking informations ==
Please kindly take a look at this user edits on service 5, user had placed false info on bus deployments and undoing them will make it hard for other users. There are more new accounts created like this. Thanks
Hi.
 
=== Bus model naming ===
https://sgwiki.com/index.php?title=Trunk_Services_2_-_9&action=history
==== Scania K230UB ====
We will proceed to make these changes to the existing Scania K230UB pages:
* Scania K230UB (Euro IV Batch 1) → <font color="#01796F"><b>Scania K230UB (Euro IV) (Batch 1)</b></font>
* Scania K230UB (Euro IV Batch 2) → <font color="#01796F"><b>Scania K230UB (Euro IV) (Batch 2)</b></font>
* Scania K230UB (Euro V Batch 1) → <font color="#01796F"><b>Scania K230UB (Euro V) (Batch 1)</b></font>
* Scania K230UB (Euro V Batch 2) → <font color="#01796F"><b>Scania K230UB (Euro V) (Batch 2)</b></font>
----
==== MAN NL323F ====
We will proceed to make these changes to the existing MAN NL323F pages:
* MAN NL323F (Batch 1) → <font color="#01796F"><b>MAN NL323F (Euro V) (Batch 1)</b></font>
* MAN NL323F (Batch 2) → <font color="#01796F"><b>MAN NL323F (Euro V) (Batch 2)</b></font>
* MAN NL323F (Batch 3) → <font color="#01796F"><b>MAN NL323F (Euro V) (Batch 3)</b></font>
* MAN NL323F (Batch 4) → <font color="#01796F"><b>MAN NL323F (Euro VI)</b></font>


A new page will be created to cater SG3100M:
== ItsRaboot ==
* <font color="#01796F"><b>ST Engineering Retrofitted Electric Bus</b></font>
:<i>(Working title, to be finalised after changes are made to the Make/Model details in OM)</i>
----
==== MAN ND323F ====
The existing MAN ND323F 3-Door page will be renamed from:
* MAN ND323F (3-Door) → <font color="#01796F"><b>MAN ND323F (3-Door) (Euro V)</b></font>


A new page will be created to cater the 3-Door production batch buses:
Hi, <br/>Would like to bring the above user's edits to your attention. They have edited the AWBDR CDGEs into the grey box section in the infobox, even though these units aren't deregistered yet. See https://sgwiki.com/index.php?title=Volvo_B9TL_(CDGE)&curid=7032&oldid=590814 . This is their 3rd time editing this, despite me & another user telling them not to. I would've reverted their edits if not for 3RR.<br/>Thanks,<br/>AirFan19
* <font color="#01796F"><b>MAN ND323F (3-Door) (Euro VI)</b></font>


No changes for existing MAN ND323F 2-Door pages.
== User Weilong ==
----
==== Alexander Dennis Enviro500 ====
A new page will be created to cater the 3-Door buses:
* <font color="#01796F"><b>Alexander Dennis Enviro500 (3-Door)</b></font>


No changes for existing ADL E500 2-Door pages.
Hi could you keep an eye on this user Weilong, his edits look dubious, plus he doesn't edit the relevant pages, not even sure if his edits are correct or not
----
==== Volvo B9TL (WEG2) ====
No changes for existing Volvo B9TL WEG2 pages.
----
=== Deployment Pages ===
==== Long page with more than 30 headers ====
Noted on that.
==== Merger of SWT to Parent Services ====
We will proceed to merge the Short-Trip services to the Parent services.
==== Merger of some pages between operators ====
This is a list of new pages to be created:
* <font color="#01796F"><b>Basic Services 2 - 10</b></font><br><i>consisting of Services 2, 2A, 3, 3A, 4, 5, 6, 7, 7A, 7B, 8, 9, 9A, 10</i> <b>(14 subheadings)</b>
* <font color="#01796F"><b>Basic Services 11 - 20</b></font><br><i>consisting of Services 11, 12, 13, 13A, 14, 14A, 15, 15A, 16/M, 17, 17A, 18, 19, 20</i> <b>(14 subheadings)</b>
* <font color="#01796F"><b>Basic Services 21 - 30</b></font><br><i>consisting of Services 21, 21A, 22, 23, 24, 25, 26, 27, 27A, 28, 29, 29A, 30</i> <b>(13 subheadings)</b>
* <font color="#01796F"><b>Basic Services 31 - 40</b></font><br><i>consisting of Services 31, 31A, 32, 33, 33A, 33B, 34, 34A, 34B, 35/M, 36, 36A, 36B, 37, 38, 39, 40</i> <b>(17 subheadings)</b>
* <font color="#01796F"><b>Basic Services 41 - 50</b></font><br><i>consisting of Services 41, 42, 43, 43M, 45, 45A, 46, 47, 48, 49, 50</i> <b>(11 subheadings)</b>
* <font color="#01796F"><b>Basic Services 51 - 60</b></font><br><i>consisting of Services 51, 51A, 52, 53, 53A, 54, 55, 55B, 56, 57, 58, 58A, 58B, 59, 60, 60A</i> <b>(16 subheadings)</b>
* <font color="#01796F"><b>Basic Services 61 - 70</b></font><br><i>consisting of Services 61, 62, 62A, 63, 63M, 64, 65, 66, 66A, 66B, 67, 67W, 68, 68A, 68B, 69, 70/M, 70A, 70B</i> <b>(19 subheadings)</b>
* <font color="#01796F"><b>Basic Services 71 - 80</b></font><br><i>consisting of Services 71, 72, 72A, 72B, 73, 74, 75, 75A, 76, 77, 78, 78A, 79, 79A, 80, 80A</i> <b>(16 subheadings)</b>
* <font color="#01796F"><b>Basic Services 81 - 90</b></font><br><i>consisting of Services 81, 82, 83, 84, 85, 85A, 86, 87, 88, 88A, 88B, 89, 89A, 90, 90A</i> <b>(15 subheadings)</b>
* <font color="#01796F"><b>Basic Services 91 - 100</b></font><br><i>consisting of Services 91, 92, 92A, 92B, 93, 94, 94A, 95, 95B, 96, 96A, 96B, 97, 98/M, 98A, 98B, 99, 100, 100A</i> <b>(19 subheadings)</b>
* <font color="#01796F"><b>Basic Services 101 - 110</b></font><br><i>consisting of Services 101, 102, 103, 105, 105B, 106, 106A, 107/M, 109, 109A, 110</i> <b>(11 subheadings)</b>
* <font color="#01796F"><b>Basic Services 111 - 120</b></font><br><i>consisting of Services 111, 112, 112A, 113, 113A, 114, 115, 116, 116A, 117, 117A, 118, 118A, 118B, 119, 120 </i> <b>(16 subheadings)</b>
* <font color="#01796F"><b>Basic Services 121 - 130</b></font><br><i>consisting of Services 121, 122, 123, 123M, 124, 125, 125A, 127, 127A, 129, 130 </i> <b>(11 subheadings)</b>
* <font color="#01796F"><b>Basic Services 131 - 140</b></font><br><i>consisting of Services 131, 131A, 131M, 132, 133, 134, 135, 135A, 136, 137, 137A, 138, 138A, 138B, 139, 139M, 140 </i> <b>(17 subheadings)</b>
* <font color="#01796F"><b>Basic Services 141 - 150</b></font><br><i>consisting of Services 141, 142, 142A, 143, 143M, 145, 145A, 147, 147A, 150 </i> <b>(10 subheadings)</b>
* <font color="#01796F"><b>Basic Services 151 - 160</b></font><br><i>consisting of Services 151, 153, 154, 154A, 154B, 155, 156, 157, 158, 158A, 159, 159A, 159B, 160, 160M </i> <b>(15 subheadings)</b>
* <font color="#01796F"><b>Basic Services 161 - 170</b></font><br><i>consisting of Services 161, 162/M, 163, 163A, 165, 166, 167, 168, 169, 169A, 169B, 170, 170A, 170X </i> <b>(14 subheadings)</b>
* <font color="#01796F"><b>Basic Services 171 - 180</b></font><br><i>consisting of Services 171, 172, 173, 173A, 174, 175, 176, 177, 178, 178A, 179, 179A, 180, 180A </i> <b>(14 subheadings)</b>
* <font color="#01796F"><b>Basic Services 181 - 190</b></font><br><i>consisting of Services 181/M, 182/M, 183, 183B, 184, 185, 186, 187, 188, 189, 189A, 190, 190A </i> <b>(13 subheadings)</b>
* <font color="#01796F"><b>Basic Services 191 - 201</b></font><br><i>consisting of Services 191, 192, 193, 194, 195, 195A, 196, 196A, 197, 198, 198A, 199, 200, 200A, 201 </i> <b>(15 subheadings)</b>
* <font color="#01796F"><b>Basic Services 246 - 258</b></font><br><i>consisting of Services 246, 247, 248, 249, 251, 252, 253, 254, 255, 257, 258 </i> <b>(11 subheadings)</b>
* <font color="#01796F"><b>Basic Services 400 - 405</b></font><br><i>consisting of Services 400, 401, 403, 405 </i> <b>(4 subheadings)</b>
* <font color="#01796F"><b>Basic Services 825 - 883</b></font><br><i>consisting of Services 825, 851, 852, 853, 853M, 854, 855, 856, 856A, 857, 857A, 858, 858A, 858B, 859, 859A, 859B, 860, 882, 882A, 883, 883A, 883B, 883M </i> <b>(24 subheadings)</b>
* <font color="#01796F"><b>Basic Services 925 - 969</b></font><br><i>consisting of Services 925, 925A, 925M, 926, 927, 950, 960, 961/M, 962, 962B, 962C, 963, 964, 965, 965A, 966, 969, 969A </i> <b>(18 subheadings)</b>
* <font color="#01796F"><b>Basic Services 970 - 991</b></font><br><i>consisting of Services 970, 971, 972/M, 972A, 973, 973A, 974, 974A, 975, 975A, 975B, 976, 979, 980, 981, 983, 983A, 985, 990, 991, 991A, 991B </i> <b>(22 subheadings)</b>
* <font color="#01796F"><b>City Direct Services</b></font><br><i>consisting of Services 651, 652, 653, 654, 655, 656, 657, 660, 661, 663, 665, 666, 667, 668, 670, 671, 672 </i> <b>(17 subheadings)</b>
* <font color="#01796F"><b>Express Services</b></font><br><i>consisting of Services 10e, 12e, 14e, 30e, 43e, 74e, 89e, 97e, 151e, 167e, 174e, 188e, 188R, 196e, 502, 502A, 506, 513, 518, 518A, 850E, 851e, 854e, 868E, 951E, 960e, 963e, 963R, 982E </i> <b>(29 subheadings)</b>
* <font color="#01796F"><b>Night Services</b></font><br><i>consisting of Services 1N, 2N, 3N, 4N, 5N, 6N, N1, N2, NR3, NR5, NR6, NR8 </i> <b>(12 subheadings)</b>


Several changes to the existing pages:
== user: Draconite Dragon ==
* Ang Mo Kio Feeders<br><i>to consist Services 261, 262, 265, 268, 268A, 268B, 269, 269A</i> <b>(8 subheadings)</b>
* Bedok Feeders<br><i>to consist Services 222, 222A, 225G, 225W, 228, 229</i> <b>(6 subheadings)</b>
* Bishan Feeders<br><i>to consist Services 410G, 410W</i> <b>(2 subheadings)</b>
* Boon Lay Feeders<br><i>to consist Services 240, 240A, 240M, 241, 241A, 242, 243G, 243W</i> <b>(8 subheadings)</b>
* Choa Chu Kang Feeders<br><i>to consist Services 300, 301, 302, 302A, 307, 307A</i> <b>(6 subheadings)</b>
* Punggol Feeders<br><i>to consist Services 381, 382A, 382G, 382W, 386, 386A</i> <b>(6 subheadings)</b>
* Woodlands Feeders<br><i>to consist Services 900/A, 901, 901M, 902, 903, 903M, 904, 911, 912, 912A, 912B, 912M, 913, 913M</i> <b>(14 subheadings)</b>
* Yishun Feeders<br><i>to consist Services 800, 803, 804, 805, 806, 807, 807A, 811, 811A, 812</i> <b>(10 subheadings)</b>


I think we can just drop the idea of grouping the services by operator. This would mean that the existing NavBox will be eliminated as it would not be possible for us to link the respective services.
pls look into the edit for this user Draconite Dragon


==== Timetable for existing basic services ====
all incomplete edit... alway fail to edit former deployment.
We will proceed to add the departure times for all services.
and even when he edit former deployment, the dates are all wrong (many are backdate to Jun 2023? or Dec 2023??)


Thanks.
seem like his edit are based on single day spotting.  alway have to undo his edit...

Revision as of 12:57, 11 March 2024

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.

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)?
Data can be obtained from here: https://docs.google.com/document/d/1PMuCeF31etWzPv_U42qMaFoHvYwDpnkSWHgjvuuTxdg/edit
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.

Sengkang / Punggol LRT Route Map, Plaform Layout

No objections for Sengkang / Punggol LRT route to be entirely based on geological layout. Initially thought that the EWL Changi branch can also be my point of reference, but geological layout is more logical. For the subsequent LRT stations do we just only include the stations that are within the direction of travel within the loop + opposite loop?

Looking at the platform layouts, I believe we have more than enough space to implement the pictograms bah. Nothing comes to mind that any of the elevators/escalators, faregates, Passenger Service Centre would clash together in one layout. Ticketing machines should be easy to find unless the machines that only accept cash are hard to find within a station, so I don't think that would be a priority.

I have two different takes on exit layouts. One is within the station concourse, and the other, the Locality maps that we are all familiar with. I personally feel that it is more important to indicate the exit locations within the concourse. As for Locality maps, would rather think of putting it on the Alternative Travel Methods pages of certain stations. Can disregard if the locality maps are very detailed in indicating bus stops eg. Maxwell, otherwise, maps that date back to the early 2010s eg. Chinatown, Boon Lay or lacking in detail really need some updated exit map guidance so that we can convey to them where the bus stops are.

Reply

I think we are good to go with sticking with a single line option for an LRT layout so that there is a clear sense of direction. We will not need an entire loop.

And just nice! City Hall platform and concourse illustrations perfectly fit what we are looking for. I would strongly encourage to give this kind of design a go. Maybe you are right, provided if no size constraints on the wiki page, for an afterthought, we can consider putting the ticketing machine positions after we get everything laid out.

You and I are also on the same page when it comes to Locality Map presentation. There is indeed lots of inconsistency in various stations. I had once wrote in asking the authorities and MRT operator to get the 2013 Chinatown map upgraded, they say they would, but I have not heard a word from them ever since, nor was it renewed. I believe getting every MRT/LRT station to have the newer TEL standard map will take eternity. Raffles Place map may have upgraded, but in turn did not reflect OCBC Bldg or Prudential Twr bus stops.

For a start, I think we can focus on just three details on a map on this wiki: Road Shape, Exit Alphabets/Numbers, and Bus Stops with numbers. Important amenities second, that would be an afterthought. In this way it will be less exhausting, and we can make better effort and productivity for make such map layouts for every station.

Reply (11/1/2023)

Road name, 5-digit bus stop code, the suggested visual markers and exit numbers as the main map details should work fine. Looking forward to implementation! Maybe we can try out City Hall first, the road shapes there are almost straight, and not really much development happening nearby. Do let me know how much time it takes to make such a sample map.

Oh and one more question, is the line layout supposed to like only reflect one station code at transfer stations?

Would like to seek advice. Thanks and regards.

Reply (12/1/2023)

In chemistry, only a suitable range of the amount of catalyst added will increase the rate of reaction. If we use an excessive amount of catalyst, there will be little effect on the rate of reaction.

Like how we have 200+ stations in Singapore, we will find that implementing locality map on an image graphic can be done within a year, which you say can use Photoshop for processing, and that might spur us in finishing the job. Even if editing means that we have to replace the image graphic, but assuming replacing the image graphic=same process as implementing image graphic first hand, few days of editing will still be worth it. On the opposite hand, we might find ourselves giving up halfway in implementing a wiki html, though initially it sounded tempting that a future edit would be easier, and that adds up to more than a decade and a half. That would be comparable to growing a gingko tree and waiting for it to bear fruit.

I was also thinking, we can straightaway dive directly into exits numbers/layout to platform layout/concourse as one of the choices selected, since this type of implementation is also doable within the one day range. Looking forward to how the effect will look like so that we can compare.

Map progress

Thanks for the update! Will this 5 min walking speed be the standard plan for all stations? Because I am about to plan to send over the map screenshots with all the required 5-digit stop codes(as remarks) reflected in the alternative travel pages.I will do my best to assist in this process.

Reply: Fleet Size of 912

Hi.

I will leave the fleet size as 4 for now. As far as I know they only have 4 buses scheduled with 5 AP duties every day.

Concourse and exit layout WIP

Bedok draft has been sketched from Photoshop, and I am on my way to collect more icons, and will make a visit to Admiralty probably next week to trial a similar layout.

Current elevator dimension is 160x160 on a side note.

As discussed before, I agree that there is indeed a need for a file sharing system, especially for icons. Thanks and Regards

User : Draconite Dragon

Hi Admin,

I would like to bring your attention to this user : https://sgwiki.com/wiki/Special:Contributions/Draconite_Dragon


On 30 Jun 2023, he claimed that SG6198L and SG6199J has been on 161 for a week on his talk page. As I am a regular passenger of Service 161, I have never seen these 2 buses perform any trips of 161.

(Link : https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584281)


He then removed SG6077C and SG6102M from 161. However, these 2 buses were still being spotted daily.

(Link for pictorial proof : https://www.instagram.com/p/Ct9AGtXxp8T/)


After playing a cat and mouse game of undoing and redoing edits, he suddenly removed the two buses (SG6198L and SG6199J) from 161 and added them into 154, despite "saw it doing 161 for a week or more.".

(Link : https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584379 and https://sgwiki.com/index.php?title=Trunk_Services_160_-_169&diff=prev&oldid=584379)


I believe this is not the only standalone case. The user has made many edits and some edits involved shuffling in buses into a service and then removing them a few hours later.

(Link : https://sgwiki.com/index.php?title=Special:Contributions/Draconite_Dragon&offset=&limit=500&target=Draconite+Dragon)


I believe his edits are just merely acts of vandalism, and those buses he proclaimed to be on whichever services, do not actually exist.


Please do take a while to look at his edits, as there are a lot of inconsistencies in his edits, which would cause a lot of reliability issues with the wiki.

Regards,

Haram

Recent edits

Hi admin,

Please kindly take a look at this user edits on service 5, user had placed false info on bus deployments and undoing them will make it hard for other users. There are more new accounts created like this. Thanks

https://sgwiki.com/index.php?title=Trunk_Services_2_-_9&action=history

ItsRaboot

Hi,
Would like to bring the above user's edits to your attention. They have edited the AWBDR CDGEs into the grey box section in the infobox, even though these units aren't deregistered yet. See https://sgwiki.com/index.php?title=Volvo_B9TL_(CDGE)&curid=7032&oldid=590814 . This is their 3rd time editing this, despite me & another user telling them not to. I would've reverted their edits if not for 3RR.
Thanks,
AirFan19

User Weilong

Hi could you keep an eye on this user Weilong, his edits look dubious, plus he doesn't edit the relevant pages, not even sure if his edits are correct or not

user: Draconite Dragon

pls look into the edit for this user Draconite Dragon

all incomplete edit... alway fail to edit former deployment. and even when he edit former deployment, the dates are all wrong (many are backdate to Jun 2023? or Dec 2023??)

seem like his edit are based on single day spotting. alway have to undo his edit...