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.

Sign up for GitHub

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

Jump to bottom

Time is off by a few minutes. #4

Open
edward-shen opened this issue Oct 20, 2017 · 4 comments
Open

Time is off by a few minutes. #4

edward-shen opened this issue Oct 20, 2017 · 4 comments
Labels
bug

Comments

@edward-shen
Copy link
Owner

See #2.
@edward-shen edward-shen mentioned this issue Oct 20, 2017
Closed
@edward-shen
Copy link
Owner Author

Perhaps this is because I'm using the RESTful API rather than the other one. Or it's possible that MBTA is giving priority to their app instead.

@jamiec117
Copy link

Hey Edward,

I took a photo/screenshot at the same time for you to demonstrate the time difference. The mirror showed a bus coming in 11:23sec but the ProximiT app said the next bus was in 19min. I'm guessing the "Kendall/MIT 21:33" on the mirror is the same bus as the app (19min)?

Side note: do you know what the difference between the 3 Kendall/MIT buses that are on my mirror in the first photo?

img_1184
img_1183

@edward-shen
Copy link
Owner Author

Possible cause: they use schedule time instead of predicted time.

@edward-shen edward-shen mentioned this issue Jan 23, 2018
Merged
@edward-shen
Copy link
Owner Author

Can someone verify that this is still a problem, with APIv3 and changes to the backend?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edward-shen @jamiec117