Boxer-Basketball 20221228

Overview

Purpose

The diagram was to demonstrate the possible use of heatmapping to show impacts and intensity on a body drawing

[jco-issue host=”7″ key=”SWA-3″]

Scope

The solution does address the requirement …

Each row is an impact level. It will be contextualised to show the location of the impact grouped by Head, Upper body, Leg and lower leg. these can be the 4 sections of the outlined body to start with.

There are currently 100 possible targets, (there can be more), these can be grouped to create parent and child relationships

The shade of colour Green, Amber, Red (and dark to light shades) is to be based on a set of arbitary numbers.

The solution does NOT address the requirement …

I'll provide some now but the key for this is that this is easily changable for the user which is a requirement. 
These will be a sum of the individual rows of data which meet the same date and session code criterias (must match)
Green-100 (linear au) (sum of the linear acceleration values in g)
Amber-200
Red-300

Solution

https://github.com/sjkp/heatmap/wiki/Usage-Guide

The solution provides for heat rings to be targeted at an image by coordinates

The heat rings get larger (more intense) for each ‘hit’ in the same location

Data Sources

There are two data sources

Flat File

The Flat file source is an excel spreadsheet attached to ticket SWA-3

The original source is imported into PBI but not exposed on the report, this is ‘cut;’ into Dimensions and Facts by referencing the imported data as a source.

Tables & Entities

Entity/Dimensions

Dim_Athelete {“Athlete ID”, “Athlete Name”, “Country”, “Sex”, “Weight Division”, “Fighting Stance”}

Dim_Session {“Session ID”, “Session Date”, “Session Length”, “Competitive Level”, “Organisation”, “Venue”}

Event_Sample {“Sample ID”, “Athlete ID”, “Session ID”, “Impact Time”}

Sample event data for Athelete:Session at Impact Time

Meta Data

meta_Session_Activity

eventmeta_Sample_Acc

{“Sample ID”, “Video Time”, “Raw Linear Acc”, “Raw Rotational Acc”, “Filtered Linear Acc”, “Filtered Rotational Acc”, “Log Linear”, “Log Rotational”}

Fact (Continuous value) data for Sample event including acceleration (possible source of intensity)

eventmeta_Sample_Category

{“Sample ID”, “Fighter Status”, “Opponent Status”, “Distance”, “Type of Impact”, “Target”, “Side”, “Collision Outcome”, “Collision Sub-Outcome”, “Event Success”}

Fact (Categorisation) data for Sample Event, source of filter lists

myHelastel (SWA.DEV)

myHelastel is used to manage the bodyparts and the associated image mapping coordinates

Entity 25: Body Parts

Entity 26: Images

Item 27: Mapping Image:BodyPart with relative coordinates