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

add transit delay endpoint #30

Open
EddyIonescu opened this issue Dec 26, 2018 · 8 comments
Open

add transit delay endpoint #30

EddyIonescu opened this issue Dec 26, 2018 · 8 comments

Comments

@EddyIonescu
Copy link
Member

EddyIonescu commented Dec 26, 2018

@yubozhao
Copy link

yubozhao commented Jan 31, 2019

@EddyIonescu I am working on this issue. You can find discussion about the opentransit-map issue page with Luke

You can follow the branch here: https://github.com/yubozhao/tryn-api/tree/22-map-incidents

@yubozhao
Copy link

also, any idea where is the dataset(file format/fields/etc)? Don't want to write that part yet, until we have something to look at.

@EddyIonescu
Copy link
Member Author

@yubozhao, sorry, I didn't see this. Are you still working on this?
Here's the dataset for 2019 - https://www.toronto.ca/ext/open_data/catalog/data_set_files/Bus_2019.xlsx
Data for other years can be found at the link in the description.
Feel free to export it to CSV, then the API can just load it directly into memory.

@EddyIonescu
Copy link
Member Author

Some more details:
For the date in startTime, return a list of all the delays for each route.
Each delay is an object containing the same info as each row in the delay spreadsheet.

incidents: {
  "39": [ ... ],
  "111": [ ... ]
}

That file is just for Jan 2019. Let's make it work for dates in January 2019 first, then expand it later.

@EddyIonescu
Copy link
Member Author

  • also, incidents would be loaded only when agency === 'ttc'. The route #s are the same as the ones the API already returns.

@yubozhao
Copy link

yubozhao commented Mar 5, 2019

@EddyIonescu I am not working on it anymore. I was wondering why we were using Toronto's data instead of SF one, that is why I asked about where is the data(refer to SF)

@EddyIonescu
Copy link
Member Author

@yubozhao I see, I started with Toronto since they have the data available and that they're the other city available in the web-app. I couldn't find any equivalent data for Muni, but I did send out a request a while ago but I'm still waiting for a response (will follow-up again soon).

It's pretty standard for agencies to record these kind of delays (ie. vehicle breaks down, not enough operators were available, car accident, etc.)...making them open is not though.

@yubozhao
Copy link

yubozhao commented Mar 6, 2019

I am not sure how much the fetcher/parser will translate for SF muni's data. Since it is not available or we have a general timeline. I propose we hold off on this issue and related issue in the frontend, until the data is available for us to consume

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