|
|
| Re: Queens Bus Redesign Results In Slower Speeds (350838) | |||
 |
|||
| Home > BusChat | |||
|
[ Read Responses | Post a New Response | Return to the Index ] |
|
||
|
Re: Queens Bus Redesign Results In Slower Speeds |
|
|
Posted by Stephen Bauman on Mon Mar 9 20:33:00 2026, in response to Re: Queens Bus Redesign Results In Slower Speeds, posted by New Flyer #857 on Sun Mar 8 09:47:35 2026. The MTA got back to me. What I thought was a bug, turns out to be a "feature". I made a mistake in calculating the speeds in my last post. Here's the the corrected version.before month/year: 7/2024, before avg speed: 8.75, after month/year: 7/2025, after avg speed: 8.96 before month/year: 8/2024, before avg speed: 8.75, after month/year: 8/2025, after avg speed: 9.06 before month/year: 9/2024, before avg speed: 8.53, after month/year: 9/2025, after avg speed: 8.87 before month/year: 10/2024, before avg speed: 8.57, after month/year: 10/2025, after avg speed: 8.91 before month/year: 11/2024, before avg speed: 8.66, after month/year: 11/2025, after avg speed: 9.06 before month/year: 12/2024, before avg speed: 8.69, after month/year: 12/2025, after avg speed: 9.0 before month/year: 1/2025, before avg speed: 8.98, after month/year: 1/2026, after avg speed: 8.92 It would be nice, if the MTA provided raw source data. By that I mean for each trip there would be entries for: trip id that corresponds to the GTFS trip id; arrival/departure timestamps for each stop, stop identification that corresponds to the GTFS stop id; number of passengers on/off the bus at that stop; number of wheelchair on/off at the stop; unique vehicle id for the trip. The don't. Their staff massages the raw data to answer board member questions. This means aggregating the data in various and inconsistent ways. The output is posted on the state's open data website. The result is akin to resolving the elephant in a box problem. |
|
(There are no responses to this message.)
|
|