User talk:Svc135bsoe

From SgWiki
Jump to navigation Jump to search

Future Bus Services from Woodleigh Int[edit]

Service Destination
81 Tampines Int
82 Punggol Temp Int
104 Punggol Coast Int
146 Hougang St 21 / Kovan MRT (Loop)
506 Jurong East Int

Future Bus Services from Punggol Coast Int[edit]

Service Destination
34/e Changi Airport (Loop)
104 Woodleigh Int
117/M Sembawang Int
383 Punggol Central / Punggol MRT (Loop)

Predictions for Bus Services from Beauty World Int[edit]

Service Destination
41 Jurong East Int
66 Jurong East Int
92 Science Park Dr (Loop)
100 Serangoon Int
111 Temasek Ave (Loop)
170 Larkin Ter (Johor Bahru)
871 Tengah Int

Predictions for Bus Services from Kallang Int[edit]

Service Destination
11 Rhu Cross (Loop)
62 Punggol Temp Int
64 Mei Ling St (Loop)
134 Marine Terrace (Loop)
137 Upp East Coast Ter
140 St Wilfred Road (Loop)
141 Toa Payoh Int
175 Clementi Int
853 Yishun Int
961/M Woodlands Temp Int
980 Sembawang Int
985 Choa Chu Kang Int

Random Ideas and Stuff[edit]

135 I've always liked Service 135 since it gets me from home to important places such as school. There's Woodleigh on the way and Marine Parade is not too far down. Aside from that, there's a full fleet of MB Citaros, which are personally my favourite bus model. That's my opinion, but what do you think? More information at Bus Service 135, created by me.
Seletar Bus Package Seletar somehow gets all those lush greenies. LG Citaros, LG B9TLs, LG A22s... I feel that there are the least variety of batches and liveries in Seletar. But what do you think?
Buona Vista Bus Interchange I always thought a bus interchange (whether ITH or normal) should be built at Buona Vista, which would merge and operate services from the existing Buona Vista Ter and perhaps some from Ghim Moh Ter. Another option would be one closer to Holland Village. But what do you think?

Undo of your edits[edit]

Hi,

I had undo your edit on Bus Deployments by Service, as I do not want to be flamed by critics for implementing disorientation into this page for the following:

1. Trunk Service:

  • 130 - 134, 136, 137, 139
  • 135 138

Now, it will be very confusing at a glance and reader will think that Service 135 and 138 had discontinued due to lack of continuous numbering. If we split it up like this:

  • 130 - 134
  • 135
  • 136, 137
  • 138
  • 139

Then it will be too long and weird. That was why there are quite a few service - despite having a separated pages, didn't have its listing indicated here but rather required a double click action.

2. Feeder service

  • Choa Chu Kang: 300 301
  • Feeder Service 302 & 307 (Choa Chu Kang)

This make it looks like there is two seperate town called "Choa Chu Kang". That is the reason why it will only be reflected when ALL pages is converted in it.

I hope you understand the rationale behind my undo.

Regards

RE: History Page for Defunct Services[edit]

Hi,

Sounds good. I was thinking what if we merged all (including those at respective bus pages) into the year page?

Regards

Supernutorcrazy

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:

  1. Clear visibility and usability on mobile devices.
  2. 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

English Usage[edit]

Hi, saw your edits to help improve the language usage, but there is this part there is something that need to be adjusted:

Over here I used benefit(s/ed) instead of introduced or extended because - the count actually tally into it. For example, if we take 230 as an example, it is the 1st bus service that extended, because all the previous one is introduced, but on paper, they say it is the 16th bus service under BCEP.

If we look at bus service 41, it is not 34th bus service to be introduced, because the 34th didn't include - peak period bus services before it being introduced (9 of them), supplementary route, or operating hours extension. But on paper, it stated 34th bus service.

As for the term residential estates or residents, let's make it simpler - if it is road - use residents, if it is town name based on URA, then use residential estates.

  • Residential estates - Town-centric, Building-centric
  • Residents - People-centric

Using this method, I feel is clearer because a road can have industrial on one side, and residential on the other side, which means, residentials estates only means cater to one side of the road. But residents, we didn't say xxx's residents, so I guess it can inferred as Singapore residents (anyone) regardless of whether they live there or not.

I look forward to your suggestion on the term and structure.

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.