Difference between revisions of "User talk:Sgbusntrain"
m |
|||
Line 130: | Line 130: | ||
I didnt forget about it. :) | I didnt forget about it. :) | ||
===Re=== | |||
Trial page refer to the creating of it, for scrutinising and feedback by other editors. On top of that is to trial the layout of the new format. | |||
Right now there are three different layout of it, so whichever to apply will matters also. | |||
Then SWT and parent service there so much of duplicate information so will need to think how to condense into 1 simpler page. | |||
If the response or feedback is not very good, then had to revert to the original. | |||
==Warning Points== | ==Warning Points== |
Revision as of 19:31, 13 October 2024
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.
Roads Page
List of roads in Tampines
Hi,
Can you help me with the bus stops on this page?
Regards,
User Talk: SBS5251K
Merging of pages
Hi,
Just a curiosity, are you going to create 10000 plus page for each and every roads in Singapore that just state some unnecessary information such as a list of bus stop and some connecting roads with no real meaningful like histories etc especially for minor roads. If so, I would encourage you to condenses and merge multiple pages into one for the sake of it to be more meaningful.
Regards
In reply
I appreciate your perspective but it is just a passion of mine to create these. I’ll try to add more relevant and important information to major roads, and dig out as much information as possible for minor ones. I’ll try to consider merging pages.
Thanks
Non-revenue buses
Hi Sgbustrain,
If you want to list the bus as non-revenue, you must include what happened to the bus in the edit summary for example an accident with another vehicle. So what really happened to SG1756J???? Reply if you know!
Alphabetlorefan1
In reply
Hi,
SG1756J got into an accident with a white BMW yesterday. Thats all the info I know as of then and i hoped it answers your question. I will make sure the add a brief description next time.
Sgbusntrain
To anyone who wants the reason since i forgotten to put it.
there was an incident involving SMB304J
Aircraft
Please limit the creation of aircraft listing with little or not purpose.
FYI, the future of sgWiki Buses may be merged to be something like sgWiki Rails so it should hold meaningful information and not listing of all planes etc.
I had move all the Former Operators into the talk page for you to merge into one single page.
With regards to:
- Asian Corporate Aviation Management
- Blourbit
- BOC Aviation
- MyJet Asia
- Orient Global (Singapore)
You may wish to think twice as those aircraft listed are not registered in Singapore, and they had no rights to fly and land in Singapore without a proper flight plan, and thus may not be based in Singapore.
In reply,
Even though the planes in the listed companies above are not registered in Singapore, the companies are registered and even host operations in Singapore, thus it is still considered as Singapore Based.
In reply, under the ICAO law, those planes are not Singapore based, and Singapore Safety Transport Investigation Board or Singapore Law will not applied to those carrier onboard international private flight.
Therefore, I will proceed to delete those page in accordance to the rule unless you can dispute the fact.
In reply, Some of the operators above have headquarters in Seletar Airport and usually have planes take off and land there like the Asian Corporate Aviation Management do fly around Southeast Asia with those planes. BOC Aviation is an aircraft leasing company, which leases aircrafts to certain operators but these are kept in storage overseas where it is much cheaper to store. Even if the planes are not registered in Singapore and not considered Singapore based, the companies are registered in Singapore with headquarters located in Singapore. They went to registered it in different countries mostly for its benefits, so it is considered Singapore based as companies have headquarters in Singapore. You may also see List of Singapore Operator Aircraft of companies registered in Singapore and their fleet. This should be able to also be considered as Singapore based.
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, 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.
Re
Regarding your question, as long as it was reasonable and infomative, then you are allowed to create. However, avoid pages with the main function as listing or keeping track of fleet as it holds no value information.
Re: Bus Info Page
Hi,
Before creating the info page, I would like you to figure out if there a better way to present the information for Service 900 and 974 first as a trial.
Thanks
Bus Info Page
Hi,
Can we trail mearging SWT with the parent page together, and stop listing bus deployment (exact Rego) in the bus info page. Cause lots of editor won't even bother to update both concurrently...
Bus Service Page
Do not create yet. Still need to fine tune the three pages, and also there are editor that feedback why change. So put on hold first.
I didnt forget about it. :)
Re
Trial page refer to the creating of it, for scrutinising and feedback by other editors. On top of that is to trial the layout of the new format.
Right now there are three different layout of it, so whichever to apply will matters also.
Then SWT and parent service there so much of duplicate information so will need to think how to condense into 1 simpler page.
If the response or feedback is not very good, then had to revert to the original.
Warning Points
!
|
Warning Point (13 September 2023) | !
| ||||
---|---|---|---|---|---|---|
You have committed the follow offense that may warrant an immediate ban: Excessive Editing on a page.
Please refrain from excessive a single page multiple time as this will hinder the abilities of Administrator to patrol or monitor for rouge editor. You may use the "Preview" button to preview your change before clicking on the "Save" to avoid mistake. In the event of suspected session lost error encounter, just scroll down and press "save" one more time and the latest change will be reflected. Thank you for your understanding. |
!
|
Warning Point (19 March 2024) | !
| ||||
---|---|---|---|---|---|---|
You have committed the follow offense that may warrant an immediate ban: Creating unnecessary template.
For Varients/Supplementry/Express Services, please use the parent template. Eg. {{Bus/963e}} can be written as {{Bus/963|a=e}} |
!
|
Warning Point (19 March 2024) | !
| ||||
---|---|---|---|---|---|---|
You have committed the follow offense that may warrant an immediate ban: Excessive Template creation (Revoke rejection by user: Asking the admin to go through and deleting
Template for bus stops should not be created unless such bus stop may served as important transport nodes (major bus stop for transfering between services or rail). For other bus stop, please use the template BS00000 instead and manual populate the entries. |