You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a sample of the json I'm currently using for the running tally and shift charts. There's several "types" of objects within it:
type: "period" (stores the duration of each period)
type: "player" (stores each player's name, total toi, etc.)
type: "shift" (stores the player id, time, length, etc. of each shift)
type: "teammates" (stores the toi shared by every combination of 2 teammates -- used to estimate lines)
type: "opponents" (stores the toi shared by every combination of 2 opponents -- used for the matchup chart, so you can ignore it for the tally and shift charts)
type: "powerplay" (stores the team, time, length) of each powerplay
type: "event" (stores corsi events)
type: "teams" (stores the team names and home/away status)
I'm not sure combining all this data into a single json file is the best way to serve the data, so I'm completely open to you providing this data in a different way, and I can change the d3.js code to use it.
Jumping to the page should call be woi.com/individual_game//shift_chart
I think it makes the most sense to populate the page with json data in the flask view, since it seems like this is a one call and done kinda page.
Thinking through the logic in pseudo sql:
select * from individual game as game
join teams on team.id in game.teams
join players on players.id in teams.id
join shifts on shifts.player_id = player.id and shifts.game_id = game.id
join events on ;
Here's a sample of the json I'm currently using for the running tally and shift charts. There's several "types" of objects within it:
I'm not sure combining all this data into a single json file is the best way to serve the data, so I'm completely open to you providing this data in a different way, and I can change the d3.js code to use it.
Sample data
corsi-and-shift-chart-data.txt
Sample chart
The text was updated successfully, but these errors were encountered: