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

Consistency needed for delayed/postponed/cancelled gameStatus #80

Open
ryoustra opened this issue May 15, 2018 · 0 comments
Open

Consistency needed for delayed/postponed/cancelled gameStatus #80

ryoustra opened this issue May 15, 2018 · 0 comments

Comments

@ryoustra
Copy link

When games are postponed or delayed, we're not consistently getting that information via the data feeds. This seems to be exacerbated when it's a game that has already been postponed, as was the case with the SEA/MIN baseball game on 5/14/2018. The game was delayed due to weather, but it had already been rescheduled from 4/8/2018, also due to weather. Brad indicated that there's a limitation in the data model that prevented the subsequent delay from being recorded properly. Thus, there was no way to know on 5/14 that the game was being delayed, and the data appeared to be stuck.

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

No branches or pull requests

1 participant