Answers on A Table for Bundesliga

[enadol]

A few answers regarding my adaptation of A Table:

-Why didn't you submit a pull request to https://github.com/INRIA/atable and instead created your own repository? You could have done that directly from your the repo you forked https://github.com/enadol/atable
A: I am relatively new to Github and didn't want to risk messing the original data. I still don't know exactly how I could integrate the adapted code without erasing or modifying the actual structure. Maybe it is the next step?

-Are you hosting the A-Table table with Bundesliga anywhere online? Any other cool visual/soccer stuff you are doing with D3?
A: It is currently here. As you can see, I also worked on the CSS to style it a little. The original idea, in which I am still working, was to adapt the dragit repository to make the nations example a Bundesliga data visualization. I'm still working on that. I already have the json in the desired structure (also via a python script). I also have this and this . All are works in progress.

-Finally where did you get your data? Did you get them from https://github.com/openfootball ? I've been looking for a good source of soccer data for a while, and ended up scraping them from maxifoot.and then building my own repositories like https://github.com/romsson/champions-league-social-metadata.
A: For some weeks now I have been colaborating with openfootball in keeping the Bundesliga data up-to-date. Season 2015/2016 is complete now. I wrote several scripts in python to adapt the json from openfootball to the requirements of A Table. I think I included those on my fork. I haven't had time to further explain on the README file but since the project worked that fine, I can elaborate on next commits.

Many thanks and best regards,