Incorrect column data in 2022-23/gws/merged_gw.csv

[karlwjackson]

I believe I have just found an issue with incorrect columns being passed into the merged csv file within GW15.

I only noticed as i'm creating a power bi dashboard with the data (which I will share when complete) and it's failed to refresh because of the issue.

Image attached hopefully.

[vaastav]

The FPL API added xG,xA, xGI, and xGC data from GW15 onwards. The current merged_gw.csv file should have all the column entries. Please re-download the file and try again.

[karlwjackson]

Hi Brian,

Try This: " https://raw.githubusercontent.com/vaastav/Fantasy-Premier-League/master/data/2022-23/gws/merged_gw.csv "

I'm importing into power bi rather than python.

Karl Jackson, Expanding Data web: https://sites.google.com/expandingdata.co.uk/expandingdata/home

On Thu, 5 Jan 2023 at 15:51, Brian Kariuki @.***> wrote:

I'm also facing an issue importing the 2022-23/gws/merged_gw.csv into pandas. Could you please share how can I recreate this data from the api from my end. I believe the events endpoint https://fantasy.premierleague.com/api/event/{eventId}/live/ does not contain some of the data for players, e.g transfers

— Reply to this email directly, view it on GitHub https://github.com/vaastav/Fantasy-Premier-League/issues/150#issuecomment-1372394747, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5B5MJWO7NNOW33D6Z27RQDWQ3UXBANCNFSM6AAAAAATP3MFME . You are receiving this because you authored the thread.Message ID: @.***>

[briankariuki]

I've been able to get the data. But seems to be a problem with the csv file. We have headers in between the data. You may need to scroll towards the bottom to see it

[vaastav]

Ok this should be fixed now @briankariuki

[karlwjackson]

@vaastav Here is a link to a dashboard I created using your data with extra data from fpl api: Just if you wanted to add a link in your Notables: https://app.powerbi.com/view?r=eyJrIjoiZjVlYmU1ZTktMzFhNC00MDY2LTg4MGItZGI0Nzk5NmMzOTBiIiwidCI6IjcxYjViYWVjLWVkM2ItNDk2Ni05MWE4LThmMWEzYzBhMGE2YyJ9&pageName=ReportSection1fdfe2a5b22d10ea9e1c

[vaastav]

Closing this issue now. THanks @briankariuki and @karlwjackson