Jump to content

Transit Tracker - Greater Montréal, Greater Toronto, Sherbrooke and Lévis


FelixINX
 Share

Recommended Posts

42 minutes ago, Technet9090 said:

I don't know what's going on but I cannot use the tracker on my phone for the past few days!

Phone is Google Pixel 6 Pro 

But for some reason it works just fine on my PC

I have also noticed this issue yesterday. I also have a Pixel 6, and the issue seems only present in Chrome. Try Firefox, it should work just fine.

I have no clue what's happening but I'll keep looking!

Link to comment
Share on other sites

1 hour ago, FelixINX said:

I have also noticed this issue yesterday. I also have a Pixel 6, and the issue seems only present in Chrome. Try Firefox, it should work just fine.

I have no clue what's happening but I'll keep looking!

Thanks for the reply, I tried it with Opera GX and it works now!

Link to comment
Share on other sites

On 12/6/2021 at 2:31 PM, Technet9090 said:

Thanks for the reply, I tried it with Opera GX and it works now!

Seems like the issue has fixed itself on my side.

Here is a workaround : you can try to force Chrome to recheck the SSL/HTTPS security certificate. Open Transit Tracker then type this in the address bar:

javascript:(window.location='https://api.transittracker.ca/v2/landing')

Go back and it should work. If it still doesn't after selecting a region, type this:

javascript:(window.location='https://api.transittracker.ca/v2/regions')

Link to comment
Share on other sites

  • 3 weeks later...

Exo vin

 

TM

 

2MG3JMEA1AW065635

2010 J4500

2PCH33492EC712501

2014 H3-45

2PCH33490EC712559

2014 H3-45

RTCR

 

7GZ67UBG0HN003747

217-40

7GZ67UBG3HN003502

217-40

7GZ67UBG3HN003600

2017-40

2FYD9VR03EB044997

29703

2G9B30AA2MA098231

221-906

2NVYL82J1M3753132

221-20

2NVYL82J2M3753124

221-20

2NVYL82J4M3753125

221-20

CITVR

 

2PCH334938C711183

8034

2PCH334938C711152

2007 H3-45

2PCH3349161010408

604

2G9B27AAXGA098039

6029216

SURF

 

2MGTRMEA18W065007

2008 MCI E4500

1FDFE4FS3KDC59973

2019 Ford

  • Thanks 1
Link to comment
Share on other sites

1709475628_Notificationspush.thumb.png.21a0a63dfb208cf9a25061603e364d0d.png

Transit Tracker v2.6

With version 2.6, you can now subscribe to push notifications! These notifications are available for most browsers, except for iOS devices which do not yet have this feature.

There are three types of notifications:

  1. New vehicles: receive a notification when there is a new vehicle, for the selected agencies;
  2. STM New Flyer: Receive a notification when one of the STM's new electric buses starts a service for the day. With GTFS Tools by @Gerbil, quickly follow the next bus departures;
  3. General alerts: be the first to know about new features or other news from Transit Tracker.
  4. (Coming soon, in Q1 2022) Favourite buses: select your favourite buses and receive notifications when they enter service for the day. Similar to STM New Flyer notification, but it will be available to all buses.

The notification centre is accessible from the settings menu, or by using the bell icon on the home page.

This feature is in beta. This is the most complex feature I've ever launched for Transit Tracker. If you encounter any bugs, please let me know!

Along push notifications, the exo VIN database has been updated and should allow me to accept suggestions faster than before. Some previous bugs were also corrected.

Happy holidays everyone and happy new year 2022!

  • Like 2
Link to comment
Share on other sites

Last exo vins

 

TM

 

2MG3JMEA1AW065635

2010 MCI

2PCH33492EC712501

2014 H3

 

VR

2PCH334938C711152

2007 H3

RTCR

 

2NVYL82J1M3753132

221-203-221-206-221-208

 

2NVYL82J2M3753124

221-203-221-206-221-208

 

2NVYL82J4M3753125

221-203-221-206-221-208

Not sure what this is about 

11111111111111111

for exo Roussillon 

 

it’s either 80701 or 80801 because 81201 does not have a tracker and I saw it on the 130 and it was not tracking 

Link to comment
Share on other sites

  • 4 weeks later...
7 hours ago, rgilmtl said:

Is there a naming convention for sectors with multiple operators? I've seen one of the REM shuttles marked as FDL ####. Will that be an expectation from now on?

The naming convention is use the fleet label that is displayed outside the vehicle.
FDL is the only exception (it's a temporary contract).

Link to comment
Share on other sites

On 2/14/2022 at 8:31 PM, citfan2020 said:

Is there anyway for the tracker to have the schedule of the busses like the STM ones on gerbils?

It's something I've already thought about, but for now I don't intend to integrate the schedule. If I ever would, there would also be the real-time schedule which is more complex and requires more resources (on the server side), especially given the scope of Transit Tracker.

I'm not saying no, just not now :)

Link to comment
Share on other sites

  • 1 month later...

Vins 

 

SURF

 

2MG3JMBA4CW066026

 

1T88SAE1XE1271913 =602

 

TM

 

2PCH33492EC712501 ?

 

2NVYL82J5G3750335=29276

 

2PCG33491BC735002?

 

2FYD9VR06GB049212=29713

 

2FYD9VR04GB049225

 

2FYD9VR09GB049222 =29723

 

2NVYL82J1G3750333=29274

 

2FYD9VR09GB049219?

 

2FYD9VR05GB049220 =29719

 

Link to comment
Share on other sites

On 3/28/2022 at 6:41 AM, citfan2020 said:

Vins 

 

SURF

 

2MG3JMBA4CW066026

 

1T88SAE1XE1271913 =602

 

TM

 

2PCH33492EC712501 ?

 

2NVYL82J5G3750335=29276

 

2PCG33491BC735002?

 

2FYD9VR06GB049212=29713

 

2FYD9VR04GB049225

 

2FYD9VR09GB049222 =29723

 

2NVYL82J1G3750333=29274

 

2FYD9VR09GB049219?

 

2FYD9VR05GB049220 =29719

 

Are these confirmed sightings? If so I will add them on the tracker. When I mean confirmed, I mean seen with and compared with the map. There were a lot of errors on the TM Vins, just trying to get them as accurate as possible

Link to comment
Share on other sites

  • 1 month later...

Haven't been posting much in the last couple of months, but working behind the scenes trying to get the tracker up to date the exo side on the Montreal area. As of right now, we only need to confirm 10 more units, to make it even easier, they are all units from exo Terrebonne-Mascouche. My goal in the next couple of weeks is to spend some more time in areas served by exo TM.

exo TM was rifled with errors from erroneous VINs associated to the wrong bus. At 1 point there were 4 buses tracking as 29278... Those erros have been fixed over the last couple of months, most of the VINs left to confirm are local buses (297xx series), as the VINs posted on the wiki pages were wrong.

Link to comment
Share on other sites

13 hours ago, yikeslol said:

From what I've seen irl and from what i know

2FYD9VR09GB049219 is 29718 which has the green livery

2PCG33491BC735002 is 6101, a Prevost X3-45 with a blue exo livery which has only be sent in service the summer of last year, it's also ex-Orléans Express 6101

The tracker from 6101 is now on different unit. They have not updated the ID of the unit. 6101 was retired in September. The unit is 63XX, I for get off the top of my head which unit, but until they change the VIN we can't put it up. I will update 29718 accordingly.

  • Like 1
Link to comment
Share on other sites

On 5/1/2022 at 1:18 AM, MTL66 said:

As of right now, we only need to confirm 10 more units, to make it even easier, they are all units from exo Terrebonne-Mascouche.

Seems like some new VIN recently popped up at Dufresne, ruining this statement temporarily.

It's 82107M (1HA6GVB72MN006870), some Chevrolet + Aerotech (reading off what it says on the body) thing in a watermelon pink exo livery. I can't input "82107M" into the VIN suggestion form, it tells me it can't end with a letter, so kindly take this one.

Another thing I've noticed: on the wiki, 81607 is indicated to have the VIN 4RKG33498G9737302 (some X3-45), however on Transit Tracker VIN project page, this fleet number is assigned to 2MG3JM8A7GW067653, which is that of a 2016 MCI J4500.

Link to comment
Share on other sites

3 hours ago, Frozen Yogurt said:

Seems like some new VIN recently popped up at Dufresne, ruining this statement temporarily.

It's 82107M (1HA6GVB72MN006870), some Chevrolet + Aerotech (reading off what it says on the body) thing in a watermelon pink exo livery. I can't input "82107M" into the VIN suggestion form, it tells me it can't end with a letter, so kindly take this one.

Another thing I've noticed: on the wiki, 81607 is indicated to have the VIN 4RKG33498G9737302 (some X3-45), however on Transit Tracker VIN project page, this fleet number is assigned to 2MG3JM8A7GW067653, which is that of a 2016 MCI J4500.

So 82107 finally made it into service. That bus has a long and complicated history. Last I heard it was still in court. The dealership said the bus was delivered and signed for, but no one at either Dufresne garage had ever seen the bus. It was a fight back and forth, Dufresne saying they never signed for that bus, and the dealership saying they have a signature.

I can confirm 81607 is indeed an X3-45 (Ex-Indian Trails), I had a friend working there last year and spent almost every weekend riding his bus and was at the garage very often. I can tell you for sure, neither Dufresne contract for exo has a 2016 MCI on their roster. The only 2016 MCI that Dufresne owns is a charter bus in Gold livery numbered 3161 if memory serves. If a bus is tracking with that VIN, then the wrong VIN was entered into the chrono system.

81607

exo_ROUSS-81607-15082021-01

 

Link to comment
Share on other sites

13 hours ago, MTL66 said:

So 82107 finally made it into service. That bus has a long and complicated history. Last I heard it was still in court. The dealership said the bus was delivered and signed for, but no one at either Dufresne garage had ever seen the bus. It was a fight back and forth, Dufresne saying they never signed for that bus, and the dealership saying they have a signature.

82107 is definitely last-minute delivered and rushed into service, the new Opus reader was only half assembled and the wiring near the destination signs looks like bird's nest. 

Thanks for the additional information about 81607. 3161 is indeed on the wiki, and shown as a 2016 J4500, so hopefully we got its VIN for free.

===

Now moving on to Laurentides:

1) I'm not sure what is with this VIN 2NVYL82jXG3750184 saying 3-629: on the wiki, this same VIN is attributed to Keolis 29271. When one looks up the VIN of 3-629 also on the wiki, it says it's an MTA reject with some Plattsburgh VIN instead. I wonder if someone has some clarifications on this.

2) https://plc.ua/en/auctions/lot/newflyer-transit-bus-2014-vin-2fyd9vr0xeb044611-ia-11345558/ This may have been Transcobec 630, which does have the same color.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...