-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate Stop Arrival Times #13
Comments
Or we could use the form developed by my friend of use date + interval for the timestamps. |
First draft SELECT DISTINCT ON (pollid, lineid, trainid, traindirection, stationid) lineid, create_date, traindirection, trainid, stationid, timint, train_message
FROM ntas_data
INNER JOIN requests USING (requestid)
INNER JOIN polls USING (pollid)
WHERE train_message = 'AtStation' OR timint < 1
ORDER BY pollid, lineid, trainid, traindirection, stationid, create_date Which leads to some problems with delayed trains
|
The arrival time inference algorithm I built in SQL has some issues. The below graph shows the difference in the number of trips having different lengths (number of stops) for inferred vs scheduled (gtfs). Digging into where these problems might Interesting finding of where my SQL query creates a lot of short (2,3 station) trips |
@moh-osman is also working on this for headway analysis https://github.com/moh-osman/ttc_subway_times/blob/master/doc/ttc_headway_analysis.ipynb |
Turns out those |
PostgreSQL function that gets called every scraper run.
Following the gtfs spec
Note: The times would actually be timestamps.
Which brings up:
The text was updated successfully, but these errors were encountered: