Woodbridge_Heights
Senior Member
*points at EnviroTO's satire laden post*
I'm willing to place a bet that the UPX service will not be discontinued by Dec 31 2016. There's no reason or basis for you to make that comment.
Last edited:
*points at EnviroTO's satire laden post*
I'm willing to place a bet that the UPX service will not be discontinued by Dec 31 2016. There's no reason or basis for you to make that comment.
TOareaFan
Superstar
you may be giving me credit for someone's good work.
but I agree.
SaugeenJunction
Senior Member
Bonnie Crombie's (Mississauga) Transit plan includes an LRT that runs from Malton GO, to Terminal 3, Terminal 1, Dixon, and Renforth Gateway, where it would connect with SmartTrack/extended Eglinton LRT and the Mississauga Transitway BRT. It would act as a perfect "shuttle" to connect many different services to Pearson. See map: http://bonniecrombie.ca/wp-content/uploads/2014/09/Mississauaga-transit-Map-Simple-2.pdf
drum118
Superstar
When they built the grade separation for the West Toronto Diamond, provision was made for a 2nd track of the Lambton-Mactire cut off to allow a UPX service from Milton.
I can't see a Bonnie Crombie LRT line for at least 20 years or more as there is not enough ridership for a light BRT, let alone more buses on Derry Rd or Airport Rd. Have you every look at the ridership on the 7 these days or 21??
I would invest more fund for LRT in other parts of the city before doing it here.
officedweller
Senior Member
I think I read the delay could be as long as 8 seconds.
I wonder if the plan was too ambitious.
On SSP, we were wondering if there is any other system that is trying to have tap in / tap off in real time on moving buses? (i.e. someone mentioned 1500 buses?)
TOareaFan
Superstar
55 minutes from desk to terminal today leaving DT @ 3:15......been worse but that is enough for me to take the train.
rbt
Senior Member
Very poor implementation choice. Probably not chosen by the contractor (must be a requirement buried in the agreement somewhere).
Immediate authorization combined with an asynchronous state distribution (Card X free transfers until $TIME, Balance $N), or (Card Y Fruad, Ban!). A few free trips would be given out, but its easy to implement and those free trips won't be able to make any transfers. A small message queue for incoming/outgoing messages to handle persistence issues.
The catch is every card reader needs a copy of minimal state for every card in the system, but that would fit on a 2GB storage card without any effort and it can be very slow memory, so perhaps $15 per unit.
Last edited:
muller877
Senior Member
It may be required to be faster then you think (and added data per user) if you have to tap on and off. But not difficult...a simple mesh network (doesn't have to be fully connected).
Think of it this way. I tap on the 501 at Brant St and all the machines are wirelessly connected to the main machine on the streetcar. It records when I get on and deducts a set amount ($2.70). I then get off at Spadina and tap off. The 501 records this and must then transfer the updated information to the 510. I tap on when I get on the Northbound train. 510 must have the information from the 501 instantaneously (within 10 seconds as I ran to catch the streetcar). The 510 record must show where I got on and how much I paid. I then tap off the 510 at Harbord. It must close the transaction and record that I completed my trip and the transaction is closed.
But every other streetcar that went through Queen and Spadina when you transferred must also record that you may board and you have a valid transfer. So they will have an open potential traansaction waiting (which will then close after a certain time or a certain number of streetcars that go through the intersection).
The node connectors must connect and record my trip information on the local computer. So every time I tap off at a transfer point, all potential transfers must record my information in case I board that bus/train/subway/streetcar.
Each node will also record any changes to the balances of all users of the system whenever they update.
There would be a seperate node that connects to the internet/terminals for loading cards and would push out the data to all other nodes.
All nodes can be either connected via wireless (think of your LTE USB dongle) or via wired for underground services (static IP DSL with a very efficient route with a central hub at 150 Front)
To summarize, there must be a mesh that is designed to connect with each other at each transfer point in the system (and in special situations when they put a bus out of service). The nodes will share potential transfer information on users that tap off at the specific transfer point. The nodes will also share any changes in the balances of all users at all times. This is all very small bits of data (<256 per record) so it should not be hard to code it into a computer nor take long to transfer. Prioritization of data transfer would be important (#1 for taps, #2 for transfers and #3 for balances)
To be honest, give some university students some pizza, beer and a Raspberry Pi ($30) and they would have the source code and a sample software and hardware ready in a few weeks.
It becomes harder with distance based fares, time-limited travel and time-limited transfers. Again not rocket science but it would increase the amount of data reuqired to be transferred and the number of nodes that have to be updated with your transfer data. May degrade the system but I'm still thinking a few seconds to transfer all the data (and milliseconds to access the computer and approve the transaction).
Platform 27
Active Member
For those who get excited about such things, looks like at least part of the Weston tunnel trackage is being laid on concrete ties.
@GTS_Project said:
Attachments
W. K. Lis
Superstar
Adjei
Senior Member
Hated that bridge, was so ugly, glad that its been rebuilt.
jimmy3
New Member
Man Thanks,
Its almost embarssing, but there is something so modern and clean looking about those concrete ties
