I would like to suggest the addition of some roster information to your roster_data. I came to this need when I noticed that players have a profile id and an esb id in addition to the gsis id. The esb id is needed to build the url for headshots.
I have developed a solution which I show below. Since scraping the esb ids on my laptop took 0.7s on average for each profile this is no solution which should be run every time the ebs id is needed. That's why I ask you to add it to your csv data.
Another possibility would be to add esb_id and headshot_url to all the data in player_info_json (that would probably take more than an hour and a half) and save it as a new csv.
Hi Ron,
I would like to suggest the addition of some roster information to your roster_data. I came to this need when I noticed that players have a profile id and an esb id in addition to the gsis id. The esb id is needed to build the url for headshots.
I have developed a solution which I show below. Since scraping the esb ids on my laptop took 0.7s on average for each profile this is no solution which should be run every time the ebs id is needed. That's why I ask you to add it to your csv data.
Another possibility would be to add
esb_id
andheadshot_url
to all the data inplayer_info_json
(that would probably take more than an hour and a half) and save it as a new csv.