-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
@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 |
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. |
@yubozhao, sorry, I didn't see this. Are you still working on this? |
Some more details:
That file is just for Jan 2019. Let's make it work for dates in January 2019 first, then expand it later. |
|
@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) |
@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. |
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 |
The text was updated successfully, but these errors were encountered: