|
|
| Re: PM AWOL Report For 12 Jan 2018 (1462055) | |||
 |
|||
| Home > SubChat | |||
|
[ Read Responses | Post a New Response | Return to the Index ] |
|
||
|
Re: PM AWOL Report For 12 Jan 2018 |
|
|
Posted by Stephen Bauman on Sat Jan 13 11:22:12 2018, in response to Re: PM AWOL Report For 12 Jan 2018, posted by BrooklynTrain on Sat Jan 13 09:33:29 2018. The D only has 13 northbound scheduled departures from 4pm to 7pm out of Coney Island?Here's a listing from the gtf-rt feed for the D trains scheduled to depart from Coney Island from 2pm through 7pm. "1D 1402+ STL/205" "1D 1412+ STL/205" "1D 1422+ STL/205" "1D 1432+ STL/205" "1D 1549 STL/205" "1D 1609 STL/205" "1D 1739+ STL/205" "1D 1749 STL/205" "1D 1801 STL/205" "1D 1810 STL/205" "1D 1820 STL/205" "1D 1830+ STL/205" "1D 1840+ STL/205" "1D 1850+ STL/205" There was a 6 minute gap in the real time feed but it should not have affected the scheduled trains. They are supposed to be included in the feed for 30 minutes before scheduled departure. As you can see, problems started at 2:32:30 pm and were not straightened out until 5:39:00 pm. I did not see anything on the MTA email feed to indicate there were any problems. I also checked the position portion of the feed, which I don't use for the AWOL report. It shows a similar gap with no northbound D trains between "1D 1609 STL/205" and "1D 1739+ STL/205". This should not be surprising in itself. The trip update is followed by position in the MTA's gtfs-rt implementation. If there were no trip update record, a position record should not be expected. countdown clock at 36th northbound dropped yesterday's ~6:30pm D arrival (indicated next D train was over 20 minutes away) but correctly showed the N and R arrivals. The N/R are on a separate real time feed from the D. If this were a problem with the real time feed, it's understandable that it would not have affected the Q/N/R/W feed. It's nice to know somebody is looking at these reports. |
|
(There are no responses to this message.)
|
|