in the end I guess it doesn’t really matter as bunching will probably occur almost daily on those lines because the headways are so small. However, months without holidays and as least impacted by curfew or other pandemic-related measures seem to be more suitable because those data reflect the “normal” operation the best.
So if you can provide timeframes for a few consecutive weeks (no need for the sharp month frame) and for lines with headways preferably under 10 mins, I am optimistic that these will fit the problem.
thanks so much, that’s awesome news. I will still need to double-check with my professor whether 5 days of GPS mapping on my mined bunching incidents from the BOAM data are sufficient as a validation for my method, but I am optimistic that this will seal the deal.
My question is about accessing historical data for rail and ferry. We were able to get real-time trip updates and vehicle positions for them using, for example, the Realtime Vehicle Positions API. However, for this dataset, we are encountering a ‘401’ issue with the API key, which seems to indicate that the key is invalid.
I followed the instructions provided in the user guide at https://opendata.transport.nsw.gov.au/user-guide, but the generated API token key is not working. I kindly ask where I can find the appropriate API key for historical GTFS for ferries, in the same way of “vehicle position data for buses from 17 May 2021 to 21 May 2021” or real-time “vehicle position” and “trip update” key.