Skip to content
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

Make a tool to assess schedule adherence #65

Open
mmorang opened this issue May 27, 2017 · 3 comments
Open

Make a tool to assess schedule adherence #65

mmorang opened this issue May 27, 2017 · 3 comments

Comments

@mmorang
Copy link
Collaborator

mmorang commented May 27, 2017

Collect gtfs-rt over a period of time and compare it with the schedule data to highlight areas where the schedule needs work (and possibly export a corrected schedule back out to GTFS). Let's close the feedback loop!

Do you want a tool like this?
If you work for a transit agency and are interested in studying schedule adherence, I would love to talk to you. Please contact me.

@mmorang
Copy link
Collaborator Author

mmorang commented May 29, 2017

From some preliminary research, it looks like the Vehicle Positions portion of the GTFS-rt feeds would be the most relevant, if they can be recorded over time. It contains far more information than I initially assumed, though it's not clear how many agencies actually populate all that information.

For accessing the feeds through python, this will be helpful: https://github.com/google/gtfs-realtime-bindings/tree/master/python

@mmorang
Copy link
Collaborator Author

mmorang commented Jun 5, 2017

For future reference, for messing around with installing python packages:

  • To download the VirtualEnv package that works with Python 2.7, get the latest .tar.gz file from https://pypi.python.org/pypi/virtualenv and unzip using 7-zip.
  • Then to create a new virtualenv called “env” in a folder called “test” with access to global site packages (in case you need to use arcpy): "E:\PyPlay\virtualenv-15.1.0\virtualenv.py" test\env –system-site-packages
  • Always remember to activate the virtualenv before using it. test\env\scripts\activate.bat
  • Then you can run pip to get the package in your virtualenv

@d-wasserman
Copy link
Contributor

As previously discussed, I could see a use case for this. As you noted, the information inside of a real time GTFS feed is potentially very dense (schedule adherence and other info). I think the historical component (over a week or month) could be good for speed/reliability analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants