|
|
| Line 1: |
Line 1: |
| Just discuss below. | | Just discuss below. |
|
| |
|
|
| |
|
| |
| == Travel Time (East to West) ==
| |
| Hi,
| |
|
| |
| For Pasir Ris to Jurong East (in the event of EWL down), do you think the following route would be much faster than going to Bus -> Kaki Bukit -> Buona Vista -> Bus?
| |
| *3/88/109 to TPE (Bef Punggol Road) <-- This 1 roughly 20 mins I feel.
| |
| *858/969 from TPE (Bef Punggol Road) to Khatib MRT <-- This 1 roughly 20 mins
| |
| *NSL from Khatib all the way to Jurong East <-- This 1 just 40 mins.
| |
|
| |
| Thanks & Regards
| |
|
| |
| ===RE: 81===
| |
| According to Transitlink: Svc 81 from Pasir Ris to Kovan is around 40 mins, from my rail experience, Kovan to Buona Vista is around 35 mins (25 mins CCL, 5 mins transfer, 5 mins NEL). Based on this 2 the time taken should already far exceed the long north detour path. I think this was partial cause we make full use of the TPE "Express" trunk routes. Do correct me wrong if the bus trip timing is wrong. Cause I don't really take those services.
| |
|
| |
| On the side note, should we include the estimated travel time so it would be easier to benchmark in the future?
| |
|
| |
| ===Re: Exits ===
| |
| Good idea. I did for the [[Alternative Travel Method/Pasir Ris]] for between Expo & Changi Airport. See if it looks goods?
| |
|
| |
| For travel time, let round it to the nearer 5 mins, cause some route may deviate from each other between 1-2 mins?, so a 5 mins deviation should be ok. Then if other alternative come we can help to benchmark those if it offers quick alternative. Maybe we need to include disclaimer that is an estimate and it may varies.
| |
|
| |
| Secondly, for rail transfer between lines is usually 5 mins, even for Jurong East, City Hall and Raffles Place thanks to the mismatch of trains arriving/departing. For Bus I feel a waiting time of 10 mins should be average? so we can include those in disclaimer.
| |
|
| |
| I now developing the new station layout format for more information and clarity, feel more can be included. Maybe escalator and lift according to the carriage diagram like those in Japan/Korea? Let me know your take.
| |
|
| |
| ===Re: MRT Transfer Time===
| |
| I had transfer quite a lots of time between the various line at Jurong East, Caldecott, Bishan, Paya Lebar, Buona Vista, City Hall/Raffles Place, Dhoby Ghaut, Newton during peak hours/off-peaks and 5 minutes transfer time are included in the walking/waiting time in average.
| |
|
| |
| Trains between different lines are typically sync according to walking time. So after a walk transfer, 1 would usually do not need to wait, or at most 2 minutes between transfer of lines. This is exception to NS-EW transfer. The NS-EW transfer at Jurong East/City Hall/Raffles Place are by luck and direction (most of the time are just missed a train or 1 minutes wait), but usually trains arrived at 5 minutes, with peak hours may need to miss a train at times (so equal to 5 minutes) due to overcrowding.
| |
|
| |
| For EW-CG transfer at Tanah Merah, 5 minutes are enough as trains arrive at every 8 minutes, stop at platform for 3 minutes which covered most cases. So rail transfer is roughly 5 minutes. I not too sure about buses, but most of the time between transferring of bus can be done in 10 minutes after factoring in waiting time, rarely exceeding 10 minutes in both peaks and off-peak based on my experience.
| |
|
| |
| ===Re: Transfer Time===
| |
| Looks good, but the 3rd pointer on those pages doesn't hold any meaning if we are not going to include the estimated travel time. I'm more concerned about the transfer time, as how can 1 route alternative is better than the other in terms of time when trains break down?
| |
|
| |
| As for the dispersion of the crowd, I am not that afraid as the crowd itself will be dispersed based on their end destination. Furthermore, commuters may reach different destinations and hence it is an auto dispersion without the need to cater to many routes. There is always a Rail Bridging Service available when train breakdown, abit - those never always be ready when we need it. hahaha. But it will come surely.
| |
|
| |
| I think the format being tucked inside is good, maybe collapsible, as this is an odd chance it will happen and it's more of a remark.
| |
|
| |
| Reply: Noted suggestions.
| |
|
| |
| ==Re: Walking ==
| |
| It looks ok. however, I had a concern about walking between BayFront and Marina Bay. Even though it look short and near, however, I noticed that BayFront MRT is located nearer to the North side of MBS (Floating Platform/NS Square that area) instead of the South side of MBS. This means that we need to factor in the additional walking distance of 100 to 200m.
| |
|
| |
| I had modified/remove based on the travel time & waiting time. I compiled it into [[User:Supernutorcrazy/Travel Time]] for certain legs. Some assumptions that I made:
| |
| * MRT = Waiting Time = 5 mins, transfer time neglectable as it part of waiting time due to train arriving and departing is close to sync after transfer for all lines.
| |
| * Feeder Service = 10 mins waiting time in average.
| |
| * Trunk Service = 15 mins waiting time in average.
| |
| * Train Travel Time = Based on the fastest travel time of each leg according to First/Last Train.
| |
| * Bus Travel Time = From Transitlink website, rounded to the nearest 5 minutes.
| |
|
| |
| I had made some changes to Outram Park and Woodlands North station, see if this is ok. Thanks.
| |
|
| |
| ===Re: Walking/Outram Park===
| |
| Noted for your 81 take. I do agree the Kovan part, in fact I was looking at Sengkang/Punggol to TPE transfer if it is faster or not too. As Pasir Ris is big, those staying Elias/Pasir Ris West would more likely use the TPE/KPE bus to Pasir Ris as it would reach their home first. For those staying in Loyang/Pasir Ris East would more likely use the Loyang Ave to Pasir Ris as it would reach their home first.
| |
|
| |
| But in this case, we are looking at the generic flow from Station to Station and not Station to Home. Also agree that peak hour travel time vs off peak is slightly different, but I noticed a trend in bus service that ply stretches on expressway to follow the speed in peak hour during off peak, resulting in crawling bus service on highway during off-peak. Of course, the deviation for peak and off-peak is kept to the minimum, so it would only be faster a bit.
| |
|
| |
| Hmmm. Agree the part on walking between BayFront and Marina Bay, I personally had walk it before everytime I watch fireworks at MBS. It took 10 minutes to walk even for me as a fast walker. For bus, because the road network and the bus service, it the same as Outram Park/Maxwell problem. I was looking at Marina Bay walk to Downtown then take DTL to BayFront as an alternative. Waiting and travelling time for DTL should be comparable to the additional walking time if we walk directly to BayFront. But of course, we can keep both option, 1 for the less mobility and 1 for the general public.
| |
|
| |
| ==Travelling between Maxwell & Outram Park==
| |
| Hi, would walking be faster than bus between this 2 pair. Distance wise should be around 300-500m, and roughly map into 5 mins walk?
| |
|
| |
| ===Re: Road Name===
| |
| Good idea to include the road name to help, furthermore, we can also include the exit number/letters to help also. Yes, I do agree that Maxwell is not really connected by bus due to the 1 direction road network so I also scratching my head on how the rail briging service will works also.
| |
|
| |
| ===Re: Deletion===
| |
| Hi, I can only do full page deletion, and not history deletion. Do let me know if you want me to delete your user page. Thanks.
| |
|
| |
| Reply: Alright thanks for the info, appreciate it!
| |
|
| |
| == RE: Waiting Time ==
| |
|
| |
| Hi,
| |
|
| |
| Looks good. It seems like when bus service > 3 between 2 stops, then the maximum waiting time reduce by 5 mins. However, you need to pay attention to varient that operates at night and main service at day = same service.
| |
|
| |
| Regarding to high frequency trunk: 168, 190, 975 etc. There is quite a few, but for sure I know 975 didn't fall into it, unless you include 975A/B. For obvious service like 190, we can use 10 mins as max.
| |
|
| |
| As for 807, even with 3-7 mins, if we round to nearest 5 mins, it still 10 mins max.
| |
|
| |
| Regarding 857/858 missing API, I would say it is unique to TTS. TTS is famous for missing API, but there still arrival within the said frequency published, hence the missing service
| |
|
| |
|
| == Sengkang / Punggol LRT Route Map, Plaform Layout == | | == Sengkang / Punggol LRT Route Map, Plaform Layout == |
Just discuss below.
Sengkang / Punggol LRT Route Map, Plaform Layout
Hi,
I think for the loop service for Sengkang and Punggol I think we follow the geological map in Google Map / LTA Station map?
So for
- Sengkang
- SW4 - SW1 | STC | SE1 - SE3
SW5 - SW8 | | SE5 - SE4
- Punggol
- PW4 - PW1 | PTC | PE7 - PE4
PW5 - PW7 | | PE1 - PE3
I shift the Layout Template - UR to UL (This one my naming wrong), then UR2 to UR.
As for the Platform Layout, I trial it at Admiralty Station. Do take a look and let me know what need to improve. I not too sure if the escalator/stairs/lift should change to pictograms, this include the Faregates, Ticketing Machine and the Passenger Service Control.
As for the Exit, I not to sure if we do a simplified drawing or use screenshot of a Map, instead of the table.
Do let me know if you have any suggestion.
Re:
For the subsequent station on SKLRT & PGLRT, there is 2 takes.
- Treat it as a normal route map, reached until Sengkang/Punggol as a single line and that's it.
- Follow the same as Sengkang/Punggol, but only keep the East/West Loop segment
I think this would also affect the layout for those stations on the BPLRT, especially for the BP7 - BP13 ones as they are in a loop.
Noted on your Platform Layout takes. I will think of how I can improve it.
Ideally if we can implement something like this [1] would be better as it would fit in the concourse exit directory easily.
As for Alternate Travel Method for Locality Map, it would be a good idea, but there is lack of consistency between the various MRT operators, and also LRT stations. Furthermore, some online map services are not even accurate and differ from 1 another, with no clear indication of Bus Stop Numbers on their maps. Will consider/ponders more about it or if you had an alternative do let me know and let see how we can implement it out.
Thanks & Regards
Supernutorcrazy
Re:
1. Noted to keep to single line option to reach the end-terminus (CCK/Sengkang/Punggol).
2. Yes. The City Hall illustration is good, but there is no consistency, all station don't even have those. Outram Park transfer is a nightmare one, but it look way off/different. Also how can we implement it in sgWiki is another question.
3. Agree with you. LTA do take a handsoff approached in terms of updating it. I once wrote to LTA regarding to put maps and Train Arrival Time on their myTransport.sg App, but their response is, they will not do it. So theoretically, their app is way worse than Google Map because they treat public transport into 3 category, bus, mrt/lrt and taxi, and not as 1 - point to point connectivity mode. It's a joke on how they always say with it. So getting those map updated will take eternalty unless the station will get a new line serving it.
Yes. Making a map for this wiki should be doable. Need to find way on how to implement it. sgWiki doesn't allow svg format, so image wise only png would be better, and it hard to make/update changes in the future if they is a change in the future. HTML is box-like and hard to do a diagonally layout so the map will look weird. For the details - I was thinking about the following would be better so that at least there is a visual cue:
- Bus Stop (with 5-digit numbers only, without name)
- Road Layout (with Road Name)
- Exit Markers (Numbers / Alphabets)
- Visual Markers such as Shopping Centre / Well-known landmarks
But this would be very exhausting and we need to plan well before making such a map. As of now, the station layout and the exit location like the City Hall diagram seems possible to implement first. By the way, there is no limit on Wiki, just that the page can get too long and it hard for the user to scroll that much if viewing on mobile phone. :)