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

New NFL gamebooks code #210

Open
andr3w321 opened this issue Nov 2, 2016 · 25 comments
Open

New NFL gamebooks code #210

andr3w321 opened this issue Nov 2, 2016 · 25 comments

Comments

@andr3w321
Copy link

This is not so much of an open issue - more of an announcement/enhancement. I decided to open source my NFL gamebooks code that should work well with this nfldb project which you can find here: https://github.com/andr3w321/nflgamebooks I figured I would post here so it would get coverage. The main thing I use it for is stadium data and starting QB data, but it has plenty more info not included in this project.

@BurntSushi
Copy link
Owner

Cool! If you submit a PR with a link to your project in nfldb's README then I'd be fine with that!

@andr3w321
Copy link
Author

andr3w321 commented Nov 7, 2016

I can't seem to find the xml URLs for week 9 or NFL stopped posting them? Anyone have a clue? Week 8 urls work fine http:https://www.nflgsis.com/2016/Reg/08/57020/Gamebook.xml

However even the Thursday night game isn't up http:https://www.nflgsis.com/2016/Reg/09/57021/Gamebook.xml

The pdf is there though http:https://www.nflgsis.com/2016/Reg/09/57021/Gamebook.pdf

@tsteussie
Copy link

@andr3w321 - I am also seeing the same issue. I tried signing into nflgsis under multiple usernames, thinking there may be a permissions issue, and continue to have the same problem. Wondering if this may be due to a licensing agreement the NFL signed with sportradar (exclusive access for a certain time period after the game), but it does not make sense that it starts happening week 9 of the season. I have noticed that nflgsis just posted the detailed lineup information (see attached screenshot) for the Rams and a few other teams. Possibly an error within a larger update?

capture

@Sajorin
Copy link

Sajorin commented Nov 9, 2016

Hello, I have a project very similar to yours. I am experiencing the same issue as of today, Do you have any idea if it has happened before?

@andr3w321
Copy link
Author

Not that I'm aware of. It's clearly affecting a lot of people's code though. Even football outsiders is reporting technical difficulties this week which I believe are due to this issue.

@iliketowel
Copy link

For what it's worth, Football Outsiders posted the following note on their page:

Update: Unfortunately, the technical issues with NFL feeds mean we will not be able to update drive stats or pace stats for an unknown period of time. We are working on a solution to the problem, but until then, those pages will not be updated.

I would think they are paying for feed and it would be odd for NFL to stop in middle of season without warning.

@Sajorin
Copy link

Sajorin commented Nov 9, 2016

I agree, it is so strange this is happening in mid season

@tsteussie
Copy link

I have spent a fair amount of time searching the web and there is no mention of this issue. Are you aware if the NFL JSON feed is still functioning?

Todd Steussie
Co-founder, Executive Vice-President, PotentiaMetrics, President, PotentiaPRO
Office: 866-285-7841 Ext. 73 | Fax: 314-248-0100
[email protected] | http:https://www.potentiametrics.com

This email and any files transmitted may contain confidential and proprietary information for the use of the recipient named above. If you are not the intended recipient, you are notified that you are not authorized to disclose, copy, distribute, or take any action in the reliance on the contents of this email. Please notify the sender immediately by email if you have received this message in error and delete this email and any attachments from your computer. Thank you.

On Nov 9, 2016, at 4:16 PM, Sajorin [email protected] wrote:

I agree, it is so strange this is happening in mid season


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@tsteussie
Copy link

Not since I began my project in 2013. There have been a few broken links that have been resolved within 24-48 hours. I have a few connections at the NFL. If this issue is not resolved by next week, I will make some calls to get more information.

Todd

Todd Steussie
Co-founder, Executive Vice-President, PotentiaMetrics, President, PotentiaPRO
Office: 866-285-7841 Ext. 73 | Fax: 314-248-0100
[email protected] | http:https://www.potentiametrics.com

This email and any files transmitted may contain confidential and proprietary information for the use of the recipient named above. If you are not the intended recipient, you are notified that you are not authorized to disclose, copy, distribute, or take any action in the reliance on the contents of this email. Please notify the sender immediately by email if you have received this message in error and delete this email and any attachments from your computer. Thank you.

On Nov 9, 2016, at 4:01 PM, Sajorin [email protected] wrote:

Hello, I have a project very similar to yours. I am experiencing the same issue as of today, Do you have any idea if it has happened before?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ochawkeye
Copy link
Contributor

Are you aware if the NFL JSON feed is still functioning?

If you're referring to the JSON from the Game Center that powers nfldb, then yep, that is still working through all games to date.

import nfldb

db = nfldb.connect()
q = nfldb.Query(db)
q.game(season_year=2016, week=9, season_type='Regular')

for game in q.as_games():
    print game
Regular 2016 week 9 on 11/03 at 07:25PM, ATL (43) at TB (28)
Regular 2016 week 9 on 11/06 at 07:30PM, DEN (20) at OAK (30)
Regular 2016 week 9 on 11/06 at 12:00PM, PIT (14) at BAL (21)
Regular 2016 week 9 on 11/06 at 12:00PM, DAL (35) at CLE (10)
Regular 2016 week 9 on 11/06 at 12:00PM, JAC (14) at KC (19)
Regular 2016 week 9 on 11/06 at 12:00PM, NYJ (23) at MIA (27)
Regular 2016 week 9 on 11/06 at 12:00PM, DET (22) at MIN (16)
Regular 2016 week 9 on 11/06 at 12:00PM, PHI (23) at NYG (28)
Regular 2016 week 9 on 11/06 at 03:05PM, CAR (13) at LA (10)
Regular 2016 week 9 on 11/06 at 03:05PM, NO (41) at SF (23)
Regular 2016 week 9 on 11/06 at 03:25PM, IND (31) at GB (26)
Regular 2016 week 9 on 11/06 at 03:25PM, TEN (35) at SD (43)
Regular 2016 week 9 on 11/07 at 07:30PM, BUF (25) at SEA (31)

Obligatory "SKOL Vikings"

@tsteussie
Copy link

Thanks! SKOL Vikings

On Wed, Nov 9, 2016 at 9:38 PM, ochawkeye [email protected] wrote:

Are you aware if the NFL JSON feed is still functioning?

If you're referring to the JSON from the Game Center that powers nfldb,
then yep, that is still working through all games to date.

import nfldb

db = nfldb.connect()
q = nfldb.Query(db)
q.game(season_year=2016, week=9, season_type='Regular')
for game in q.as_games():
print game

Regular 2016 week 9 on 11/03 at 07:25PM, ATL (43) at TB (28)
Regular 2016 week 9 on 11/06 at 07:30PM, DEN (20) at OAK (30)
Regular 2016 week 9 on 11/06 at 12:00PM, PIT (14) at BAL (21)
Regular 2016 week 9 on 11/06 at 12:00PM, DAL (35) at CLE (10)
Regular 2016 week 9 on 11/06 at 12:00PM, JAC (14) at KC (19)
Regular 2016 week 9 on 11/06 at 12:00PM, NYJ (23) at MIA (27)
Regular 2016 week 9 on 11/06 at 12:00PM, DET (22) at MIN (16)
Regular 2016 week 9 on 11/06 at 12:00PM, PHI (23) at NYG (28)
Regular 2016 week 9 on 11/06 at 03:05PM, CAR (13) at LA (10)
Regular 2016 week 9 on 11/06 at 03:05PM, NO (41) at SF (23)
Regular 2016 week 9 on 11/06 at 03:25PM, IND (31) at GB (26)
Regular 2016 week 9 on 11/06 at 03:25PM, TEN (35) at SD (43)
Regular 2016 week 9 on 11/07 at 07:30PM, BUF (25) at SEA (31)

Obligatory "SKOL Vikings"


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#210 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOZ6d8m82MkPQEfWpzP_0Iq7j8-hvAZks5q8pHBgaJpZM4KnvoL
.

Todd Steussie

Co-founder, Executive Vice-President, PotentiaMetrics, President,
PotentiaPRO

Office: 866-285-7841 Ext. 73 | Fax: 314-248-0100

[email protected] | http:https://www.potentiametrics.com

http:https://www.potentiametrics.com


[image: Facebook] http:https://www.potentiametrics.com
https://www.facebook.com/potentiametrics [image: Twitter]
https://twitter.com/PotentiaMetrics [image: Google Plus]
https://plus.google.com/115670021481207889252 [image: Linkedin]
https://www.linkedin.com/company/potentia-metrics

@Sajorin
Copy link

Sajorin commented Nov 10, 2016

Thank you so much Todd

@andr3w321
Copy link
Author

I still don't see any xml gamebooks for week 10. All the new pdfs are posted like last week though.
http:https://www.nflgsis.com/2016/Reg/10/57035/Gamebook.xml
http:https://www.nflgsis.com/2016/Reg/10/57035/Gamebook.pdf

@tsteussie
Copy link

I see the same thing. I will reach out this week to see when they will be
restoring the links.

Todd

On Sun, Nov 13, 2016 at 8:18 PM, andr3w321 [email protected] wrote:

I still don't see any xml gamebooks for week 10. All the new pdfs are
posted like last week though.

http:https://www.nflgsis.com/2016/Reg/10/57035/Gamebook.xml
http:https://www.nflgsis.com/2016/Reg/10/57035/Gamebook.pdf


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#210 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOZ6UwcT0U4teRK5K3hWRJNT4lkdrw-ks5q98T5gaJpZM4KnvoL
.

Todd Steussie

Co-founder, Executive Vice-President, PotentiaMetrics, President,
PotentiaPRO

Office: 866-285-7841 Ext. 73 | Fax: 314-248-0100

[email protected] | http:https://www.potentiametrics.com

http:https://www.potentiametrics.com


[image: Facebook] http:https://www.potentiametrics.com
https://www.facebook.com/potentiametrics [image: Twitter]
https://twitter.com/PotentiaMetrics [image: Google Plus]
https://plus.google.com/115670021481207889252 [image: Linkedin]
https://www.linkedin.com/company/potentia-metrics

@andr3w321
Copy link
Author

Any news Todd? It would be nice to know if they stopped posting on purpose or if it's a temporary bug that may one day be fixed.

@tsteussie
Copy link

Sorry, I have not had a chance to inquire. I will reach out to a couple of
contacts next week.

Todd

On Mon, Nov 21, 2016 at 2:08 PM, andr3w321 [email protected] wrote:

Any news Todd? It would be nice to know if they stopped posting on purpose
or if it's a temporary bug that may one day be fixed.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#210 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOZ6Z7jMwqQkgGMBiJFwF3APNjvmznsks5rAfotgaJpZM4KnvoL
.

Todd Steussie

Co-founder, Executive Vice-President, PotentiaMetrics, President,
PotentiaPRO

Office: 866-285-7841 Ext. 73 | Fax: 314-248-0100

[email protected] | http:https://www.potentiametrics.com

http:https://www.potentiametrics.com


[image: Facebook] http:https://www.potentiametrics.com
https://www.facebook.com/potentiametrics [image: Twitter]
https://twitter.com/PotentiaMetrics [image: Google Plus]
https://plus.google.com/115670021481207889252 [image: Linkedin]
https://www.linkedin.com/company/potentia-metrics

@danabrey
Copy link

Did you ever get any insight on this @tsteussie ? I've been trying to parse Gamebook PDFs with (as you'd expect) limited results. That XML would be a godsend!

@tsteussie
Copy link

tsteussie commented Nov 16, 2017 via email

@danabrey
Copy link

Thanks a lot for that, @tsteussie. I'll investigate the possibility of getting what I need from parsing the PDFs.

I'm able to get the play-by-play data and stats that I need from a combination of the Game Center JSON files and another fantasy API, but what I'm really interested in getting hold of is the snap count data from the final section of the PDFs.

I note that earlier in this issue, it was mentioned that Football Outsiders had hit problems in updating their snap count data due to the disappearance of the XML version of the Gamebook. I wonder how they are still able to update their data every Tuesday! It surely can't be a manual process; perhaps they're parsing the PDFs too, or they have an alternative private API source.

@tsteussie
Copy link

tsteussie commented Nov 16, 2017 via email

@tsteussie
Copy link

tsteussie commented Nov 17, 2017 via email

@JimHewitt
Copy link

JimHewitt commented Jul 19, 2018

@tsteussie Regarding your comment about the "J.Brown" issue, the json play by play data includes the playerid for players involved for each play (there are actually 2 playerids NFL.com uses, but that is a different story) For example the two ARI J.Browns are from a SQL Server database I created by scraping NFL.com by playerid. ( I also have all of the json play by play data since 2009 in a SQL Server database).

00-0030300 ARI J.Brown wr Jaron Brown
00-0031051 ARI J.Brown wr John Brown

@danabrey
Copy link

@JimHewitt I believe that's in reference to the snap count 'data' available in the Gamebook PDFs, which only list players by name.

@tsteussie
Copy link

tsteussie commented Jul 19, 2018 via email

@JimHewitt
Copy link

@danabrey OK, I see the issue. In this case you would need to know that John Brown played special teams and Jaron didn't. However, that doesn't really solve the larger issue.

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

8 participants