Home · Maps · About
Home > SubChat

[ Post a New Response | Return to the Index ]

(1492039)

view threaded

AM AWOL Report for 07 Nov 2018

Posted by Stephen Bauman on Wed Nov 7 15:06:34 2018

Totals for time period: 11/07/2018 06:00:00 to 11/07/2018 08:59:59 1516 scheduled; 1402 operated; 92%

Totals for time period 11/07/2018 06:00:00 to 11/07/2018 08:59:59 by direction:
Direction: NORTH: 724 scheduled; 669 operated; 92%
Direction: SOUTH: 792 scheduled; 733 operated; 93%

Totals for time period 11/07/2018 06:00:00 to 11/07/2018 08:59:59 by Route and Direction
1: N: 33 sched, 33 dep, 100%; S: 45 sched, 44 dep, 98%;
2: N: 24 sched, 24 dep, 100%; S: 31 sched, 31 dep, 100%;
3: N: 22 sched, 22 dep, 100%; S: 29 sched, 29 dep, 100%;
4: N: 31 sched, 31 dep, 100%; S: 39 sched, 39 dep, 100%;
5: N: 30 sched, 30 dep, 100%; S: 39 sched, 39 dep, 100%;
6: N: 57 sched, 44 dep, 77%; S: 28 sched, 28 dep, 100%;
6X: S: 27 sched, 25 dep, 93%;
7: N: 65 sched, 34 dep, 52%; S: 43 sched, 27 dep, 63%;
7X: S: 38 sched, 23 dep, 61%;
A: N: 38 sched, 38 dep, 100%; S: 29 sched, 29 dep, 100%;
B: N: 24 sched, 24 dep, 100%; S: 25 sched, 19 dep, 76%;
C: N: 20 sched, 20 dep, 100%; S: 19 sched, 17 dep, 89%;
D: N: 25 sched, 25 dep, 100%; S: 39 sched, 35 dep, 90%;
E: N: 32 sched, 32 dep, 100%; S: 38 sched, 38 dep, 100%;
F: N: 33 sched, 33 dep, 100%; S: 39 sched, 39 dep, 100%;
FS: N: 17 sched, 17 dep, 100%; S: 17 sched, 15 dep, 88%;
G: N: 27 sched, 26 dep, 96%; S: 23 sched, 23 dep, 100%;
GS: N: 58 sched, 58 dep, 100%; S: 57 sched, 56 dep, 98%;
H: N: 10 sched, 10 dep, 100%; S: 10 sched, 8 dep, 80%;
J: N: 30 sched, 27 dep, 90%; S: 21 sched, 18 dep, 86%;
L: N: 42 sched, 42 dep, 100%; S: 38 sched, 38 dep, 100%;
M: N: 22 sched, 22 dep, 100%; S: 23 sched, 23 dep, 100%;
N: N: 23 sched, 21 dep, 91%; S: 20 sched, 19 dep, 95%;
Q: N: 25 sched, 25 dep, 100%; S: 24 sched, 24 dep, 100%;
R: N: 24 sched, 22 dep, 92%; S: 27 sched, 26 dep, 96%;
W: N: 12 sched, 9 dep, 75%; S: 18 sched, 15 dep, 83%;
Z: S: 6 sched, 6 dep, 100%;

Post a New Response

(1492182)

view threaded

Re: AM AWOL Report for 07 Nov 2018

Posted by transitbuff on Thu Nov 8 17:22:36 2018, in response to AM AWOL Report for 07 Nov 2018, posted by Stephen Bauman on Wed Nov 7 15:06:34 2018.

Hi, Stephen... Is there some simple method to track trains, rather than the cumbersome method that Transsee uses? For instance. .trip id 143550 has no meaning in real time, other than the fact that it is 5 min behind 143050.

Post a New Response

(1492191)

view threaded

Re: AM AWOL Report for 07 Nov 2018

Posted by Stephen Bauman on Thu Nov 8 18:25:26 2018, in response to Re: AM AWOL Report for 07 Nov 2018, posted by transitbuff on Thu Nov 8 17:22:36 2018.

I'm not familiar with Transsee. However, what they do is dictated to a great extent by how the MTA chooses to implement the GTFS (Google) specification.

With respect to NYCT's trip id's: the numerical portion represents the scheduled departure time. For example: 143550 represents a departure time of 23:55:30. The first 4 digits: 1435 represent the departure time in minutes after midnight. The last two digits: 50 represent the hundredths of a minute for the seconds.

I don't know precisely what you mean by "track trains". There are 3 schedules that the MTA provides.

There's a static schedule that the MTA hasn't maintained after November 3rd. The static schedule is supposed to be updated every few months and it's supposed to reflect the printed schedule. I have notified the MTA's Developer's Forum that their static GTFS schedule is out of date.

There's also a "supplemented" schedule that's issued daily or even hourly. It's supposed to reflect scheduled maintenance changes. It usually has about a week's worth of schedules. It's the schedule baseline from which service metrics like on time performance are based. Someone complained to Andy Byford at the first Fast Forward event that service metrics should be based on the static schedule. Maybe, that's why the MTA has stopped updating the static schedule.

Finally, there's the real time schedule that's updated every 30 seconds. It uses a variation of the GTFS-RT specification. The underlying data is what's used for most real time apps to give you the next train arrival at a particular station. It's also supposedly what the station arrival clocks use. It's what I use for my AWOL and Late Start reports.

There's a Developers Resources link on the MTA's website that will point you in the proper direction, if you want to use the data for yourself.

Post a New Response

(Sponsored)

iPhone 6 (4.7 Inch) Premium PU Leather Wallet Case - Red w/ Floral Interior - by Notch-It


[ Return to the Message Index ]