Jump to content

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


FelixINX
 Share

Recommended Posts

I was able to talk directly to the team involved in the realtime data project, and they were happy to share the feed with me as the first developer outside of Google Maps! If you notice anything wrong, let me know and I will pass on the comments to the team (like vehicles not appearing when on highways). The feed is updated each 2 minutes, will be more frequent when/if the RTC is ready.

On another note, recently added on Transit Tracker:

  • Multiple Zenbus agencies: Inter Laurentides, MRC Haut-Saint-Laurent, STC Pierre-de-Saurel (and I'm trying to add more agencies soon!)
  • Other agencies in Ontario (UP, London, Stratford, Milton, Orangeville, St. Thomas)
  • There is a new report button to send a suggestion for a fleet label (Zenbus) or a wrong identifier (Wrong VIN or others)
  • @MTL66 has corrected some incorrect VIN numbers, they will now display correctly across the app. Thanks!


Coming soon:

  • View related trips on the same block (when supported, mostly in Ontario and STSH, STLévis)
  • On the map, stops will be shown alongside the route and next stop will be highlighted (when supported)
  • Like 1
Link to comment
Share on other sites

1 hour ago, FelixINX said:

I was able to talk directly to the team involved in the realtime data project, and they were happy to share the feed with me as the first developer outside of Google Maps! If you notice anything wrong, let me know and I will pass on the comments to the team (like vehicles not appearing when on highways). The feed is updated each 2 minutes, will be more frequent when/if the RTC is ready.

The vehicule not appearing on the highway is more a weakness of the internal system inside the bus, i remember when i was riding eXpress buses on the highway sometimes the next stoop screen inside the bus would blank out showing instead the famous "Information not avaliable" message, seems the system has a hard time to keep up with tracking when travelling at a high rate of speed

Link to comment
Share on other sites

7 minutes ago, eclair14 said:

The vehicule not appearing on the highway is more a weakness of the internal system inside the bus, i remember when i was riding eXpress buses on the highway sometimes the next stoop screen inside the bus would blank out showing instead the famous "Information not avaliable" message, seems the system has a hard time to keep up with tracking when travelling at a high rate of speed

Thanks for the info, being from Montreal I would never have known!

Link to comment
Share on other sites

Another terrific update! It's great to see RTC available. 

7 hours ago, FelixINX said:
  • There is a new report button to send a suggestion for a fleet label (Zenbus) or a wrong identifier (Wrong VIN or others)

Just a question regarding the Zenbus feed: is the fleet label unique to each vehicle or simply a placeholder for whichever vehicle that is tracking? If it's the latter case, then the fleet label might not be very helpful (unless it's temporary). 

7 hours ago, FelixINX said:
  • On the map, stops will be shown alongside the route and next stop will be highlighted (when supported)

I think I'll like this one a lot! 

Finally, just a small request: on mobile, I can't see the "All" option on the menu to adjust the number of rows to display, since it's hidden behind the navigation bar on the bottom. Could it be adjusted upwards to show the "All" option?

Thanks and keep up the nice work!

  • Like 1
Link to comment
Share on other sites

45 minutes ago, Frozen Yogurt said:

Just a question regarding the Zenbus feed: is the fleet label unique to each vehicle or simply a placeholder for whichever vehicle that is tracking? If it's the latter case, then the fleet label might not be very helpful (unless it's temporary). 

I've always wondered. Zenbus is available in two format: onboard (like iBus) and on a phone/tablet (more common since it's cheaper). Is the Vehicule ID by vehicule, by employee or by phone? It's hard to say.

I had a contract in Mont-Tremblant last year where I've checked and the fleet number I entered did match each week (there were two buses at the time).

On MRC Haut-Saint-Laurent, three vehicles have been recorded while 12 on Pierre-de-Saurel. Only verification in time will tell!

51 minutes ago, Frozen Yogurt said:

Finally, just a small request: on mobile, I can't see the "All" option on the menu to adjust the number of rows to display, since it's hidden behind the navigation bar on the bottom. Could it be adjusted upwards to show the "All" option?

I see, I'll ship a fix with the next version. Would it be useful to save the state of the page size so it's kept between sessions?

Link to comment
Share on other sites

On 2/16/2023 at 10:50 PM, FelixINX said:

I've always wondered. Zenbus is available in two format: onboard (like iBus) and on a phone/tablet (more common since it's cheaper). Is the Vehicule ID by vehicule, by employee or by phone? It's hard to say.

I had a contract in Mont-Tremblant last year where I've checked and the fleet number I entered did match each week (there were two buses at the time).

On MRC Haut-Saint-Laurent, three vehicles have been recorded while 12 on Pierre-de-Saurel. Only verification in time will tell!

Interesting, I can try to spot STC at some point to verify if the numbers are consistent. From my memory, last time the local line had a phone (although that was when Fleur de Lys was using the Dodge Caravan from Kiroule...), and I didn't really check the Longueuil line. 

Quote

I see, I'll ship a fix with the next version. Would it be useful to save the state of the page size so it's kept between sessions?

Thanks! I think I might prefer to not save the state of the page: depending on the number of agencies selected, displaying all vehicles while loading the website might be a little bit overwhelming.

  • Like 1
Link to comment
Share on other sites

All missing fleet numbers on the tracker are now up. Finally found the mystery J4500 in TM thanks to @Frozen Yogurt

The only one still showing as no fleet number is the 2004 GMC Savanna that tracked on the 9. Pretty sure that was an error, as it was only active for a couple of hours and has yet to return.

  • Thanks 1
Link to comment
Share on other sites

  • 3 weeks later...

Version 2.9 is now available! Here's what's new:

  • When selecting a bus on the map, stops are now displayed along the route.
  • Support for blocks, view trips made by a vehicle in a day. Linked trips can be viewed when selecting a vehicle on the map or using the button in the "Actions" column of the table. Only when agencies provide this data:
    • Montreal: none
    • Toronto: GO, Durham DRT, York YRT, Burlington, Hamilton HSR, London LTC, Grand River Transit, Guelph, Barrie
    • Sherbrooke: STSherbrooke
    • Quebec / Capitale-Nationale: STLévis and RTC
    • Outaouais: STO and Transcollines
    • Laurentians: none
  • The "All" option on the table is now visible.
  • New fonts in the app.
Link to comment
Share on other sites

Not sure if it's just me but I've noticed that STM school an industrial extras haven't been tracking lately. Not sure if this has something to do with the tracker or the STM itself. 

On 3/14/2023 at 2:37 PM, FelixINX said:

Support for blocks, view trips made by a vehicle in a day. Linked trips can be viewed when selecting a vehicle on the map or using the button in the "Actions" column of the table. Only when agencies provide this data:

On this note, I would like to mention that the RTL does provide block information which can be found in the trip ID information. 

Ex. A bus currently doing trip 44_1_A_SE_1063_naoc_07:04 (7:04 departure of line 44 to TCV) would end up doing trip 15_1_A_SE_1063_mtro_08:10 (8:10 departure of line 15 to TCV) next as their block id (1063 in this case) matches. 

Link to comment
Share on other sites

8 hours ago, jge0364 said:

Not sure if it's just me but I've noticed that STM school an industrial extras haven't been tracking lately. Not sure if this has something to do with the tracker or the STM itself. 

There has been no change on Transit Tracker regarding this, so I suspect they are now excluding Industrial or Ecole routes. The STM made a server update in late January, perhaps that's when the change occured.

8 hours ago, jge0364 said:

On this note, I would like to mention that the RTL does provide block information which can be found in the trip ID information. 

I've just noticed that they are also using the block_id field, just incorrectly! It will now be corrected automatically.

On a side note, most RTL buses have a trip_id that is not present in their feed. Looks like an update hasn't been published yet.

Link to comment
Share on other sites

12 hours ago, FelixINX said:

I've just noticed that they are also using the block_id field, just incorrectly! It will now be corrected automatically.

On a side note, most RTL buses have a trip_id that is not present in their feed. Looks like an update hasn't been published yet.

Nice update as usual! Glad to see the "all" option fixed.

I think the way the RTL implemented the block ID actually makes sense - many of their routes only have one terminus (the other end is a continuous loop, think about e.g. 107 Verdun at the stm) - in which case the outbound and inbound trips share the same block ID. This would show up on Transit app as "this trip continues to [...]" for example, but not for instances when the bus needs to layover.

On the other hand, at some point the STL had block IDs in their feed, but seems to not provide it anymore. However if needed, the block ID can still be extracted from the trip ID: for example in the trip ID JANV2322E1L24618080059, L246 is the block ID. But from what I observe on TT, the STL seems to only provide minimal real time informations, so this is perhaps not helpful.

In any case, the STL seems to have trouble to properly program their GTFS. It has happened in the past that a combination of weekday + weekend schedule showed up (even on Transit) on holidays, and obviously it confused many people waiting for ghost departures.

Link to comment
Share on other sites

4 minutes ago, Frozen Yogurt said:

I think the way the RTL implemented the block ID actually makes sense - many of their routes only have one terminus

In that case, yes it makes sense. I just removed the part after the underscore and we can now see the block for the entire day.

 

4 minutes ago, Frozen Yogurt said:

But from what I observe on TT, the STL seems to only provide minimal real time informations, so this is perhaps not helpful.

STL, with the TTC, are the only agencies powered by Nextbus. This feed only includes the route and direction, making it impossible to associate a vehicle to a trip. The TTC will soon change their provider to use the GTFS-RT standard, maybe the STL will migrate in the future.

Link to comment
Share on other sites

3 hours ago, FelixINX said:

In that case, yes it makes sense. I just removed the part after the underscore and we can now see the block for the entire day.

 

STL, with the TTC, are the only agencies powered by Nextbus. This feed only includes the route and direction, making it impossible to associate a vehicle to a trip. The TTC will soon change their provider to use the GTFS-RT standard, maybe the STL will migrate in the future.

I've been hearing the STL will eventually move over to Chrono as their curent system uses 3G to connect and wit the 3G sunset, they will have to change that.

Link to comment
Share on other sites

On 3/17/2023 at 12:26 AM, jge0364 said:

Ex. A bus currently doing trip 44_1_A_SE_1063_naoc_07:04 (7:04 departure of line 44 to TCV) would end up doing trip 15_1_A_SE_1063_mtro_08:10 (8:10 departure of line 15 to TCV) next as their block id (1063 in this case) matches. 

The block ID is the run number. Currently, the operator leaving Napoleon and Oceanie (HASTUS code naoc) heads to TCV as a 44, then deadheads to Terminus Longueuil (HASTUS code mtro) to start a 15 heading once again to TCV.

  • Like 1
Link to comment
Share on other sites

On 3/18/2023 at 1:04 AM, MTL66 said:

I've been hearing the STL will eventually move over to Chrono as their curent system uses 3G to connect and wit the 3G sunset, they will have to change that.

Since Chrono now belongs to the ARTM, it makes perfect sense for the STL to adopt this system. It would be great news if it happen, we could have as much data as the other agencies.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...