[GH-ISSUE #124] [FBref] pulling back "out of date" statistics #25

New issue

Closed

opened 2026-03-02 15:55:08 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 15:55:08 +03:00

Owner

Originally created by @philbywalsh on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/124

When using the API to scrape from FBRef I noticed something odd.

The APIs for each category of stats (e.g. shooting, passing) don't seem to be working off the same baseline of minutes played.

For example: take Emiliano Martínez (Argentina). The "90s" value should be consistent across each of these categories - but across the 5 categories below it varies extensively.

fbref.read_player_season_stats(stat_type="standard") = 2.0
fbref.read_player_season_stats(stat_type="shooting") = 2.0
fbref.read_player_season_stats(stat_type="goal_shot_creation") = 3.0
fbref.read_player_season_stats(stat_type="passing") = 3.0
fbref.read_player_season_stats(stat_type="defense") = 5.3

Note: This didn't seem to be an issue earlier in the tournament. Also, I only recently scraped "defense" statistics for the first time, so I wonder if somehow the results of old queries are being cached?

Also, when I navigate to the specific pages in by browser the data looks to be consistent & fully up to-date (i.e. a value of 6.3 for the "90s" attribute for Emiliano Martínez)

https://fbref.com/en/comps/1/passing/World-Cup-Stats

Originally created by @philbywalsh on GitHub (Dec 16, 2022). Original GitHub issue: https://github.com/probberechts/soccerdata/issues/124 When using the API to scrape from FBRef I noticed something odd. The APIs for each category of stats (e.g. shooting, passing) don't seem to be working off the same baseline of minutes played. For example: take Emiliano Martínez (Argentina). The "90s" value should be consistent across each of these categories - but across the 5 categories below it varies extensively. fbref.read_player_season_stats(stat_type="standard") = 2.0 fbref.read_player_season_stats(stat_type="shooting") = 2.0 fbref.read_player_season_stats(stat_type="goal_shot_creation") = 3.0 fbref.read_player_season_stats(stat_type="passing") = 3.0 fbref.read_player_season_stats(stat_type="defense") = 5.3 Note: This didn't seem to be an issue earlier in the tournament. Also, I only recently scraped "defense" statistics for the first time, so I wonder if somehow the results of old queries are being cached? Also, when I navigate to the specific pages in by browser the data looks to be consistent & fully up to-date (i.e. a value of 6.3 for the "90s" attribute for Emiliano Martínez) https://fbref.com/en/comps/1/passing/World-Cup-Stats

kerem closed this issue

2026-03-02 15:55:08 +03:00

kerem commented

2026-03-02 15:55:09 +03:00

Author

Owner

@probberechts commented on GitHub (Dec 16, 2022):

Yes, all data is cached by default. To pull up-to-date data you should use socerdata.FBref(no_cache=True). To disable caching you can use socerdata.FBref(no_store=True).

@probberechts commented on GitHub (Dec 16, 2022): Yes, all data is cached by default. To pull up-to-date data you should use `socerdata.FBref(no_cache=True)`. To disable caching you can use `socerdata.FBref(no_store=True)`.

kerem commented

2026-03-02 15:55:09 +03:00

Author

Owner

@philbywalsh commented on GitHub (Dec 16, 2022):

Ah yes, much appreciated!

@philbywalsh commented on GitHub (Dec 16, 2022): Ah yes, much appreciated!

kerem referenced this issue

2026-03-02 15:56:57 +03:00

[PR #25] [MERGED] Update dependency mypy to ^0.942 #225