How Does Remote Athlete Data Aggregate into Activities on OpenField Cloud

How does data uploaded from the Catapult Athlete App aggregate into Activities in my OpenField account?

Remote Athlete Data uploaded from the Catapult Athlete app will be aggregated into activities owned by the default user of your OpenField account.

Remote Athlete data that is aggregated into activities will be tagged with a 'Remote' Activity Participation tag. 
This tag can be used for custom aggregation when reporting via OpenField Cloud Widgets or when requesting data via the API. 
For more information see Reporting on Data Uploaded from the Catapult Athlete App.

Whether a new activity is automatically created or not, and the number of activities created automatically will be determined by OpenField's Data Aggregation flow.

 

OpenField Data Aggregation Flow

1. A Remote Athlete raw file is uploaded to OpenField Cloud from the Catapult Athlete app.
    
2. OpenField will then check if the athlete this raw file is mapped to is already added to an overlapping activity.
    
3. If the athlete is already added to an overlapping activity, the athlete will be tagged with the 'Remote' Participation tag, and that activity will automatically reprocess, so that the data for this athlete can be reported on and displayed in Cloud Widgets and the API.
    
4. If the athlete is not already added to an overlapping activity, OpenField will check for an overlapping Activity.
    

5. If an overlapping Activity exists, the athlete will be added to this Activity via an Auto Created Period.
    

   Note: The auto created period will be extended if needed to cover the duration of the uploaded raw file.
6. Else, OpenField will create a new 'Auto Created Activity', add the athlete to this activity, then tag the Athlete with the 'Remote' Participation tag.
   
   
   
    

What is considered an Overlapping Activity?

An Overlapping Activity is an existing activity owned by the default user that overlaps with the timeframe of the data within the uploaded raw file, up to one hour either side of the start and end time of the file.
 

• For example, if an uploaded raw file starts at 9am and ends at 10am, an overlapping activity is one that has any periods between 8am (1 hour before raw file start) to 11am  (1 hour after raw file end).
  
  If an uploaded raw file starts at 9am and ends at 10am, an activity with its last period ending at 7.59am is not considered as an overlapping activity. 
  
  Similarly, an activity with its first period starting at 11.01am is not considered an overlapping activity.

How many activities will be created by OpenField's data aggregation?

The number of activities that may be automatically created will depend on:
 

• If the uploaded raw file's associated athlete is already added to an overlapping activity: no additional activity will be created.
  
   
• If the start and end time of the uploaded raw file, and an existing activity overlaps with the uploaded raw file - the raw file will be added to an overlapping activity, otherwise a new one will be created.

Example Scenarios

The two example flows below highlight how there can be a difference in the number of automatically created activities for the same raw files that are uploaded.

For each example three different Remote Athlete raw files are to be uploaded, all recorded on the same day:

• Raw file A - Starting at 9am and ending at 10am
• Raw file B - Starting at 10.30am and ending at 11.30am
• Raw file C - Starting at 12pm and ending at 1pm

Example 1

Raw file A is uploaded first, Raw file B is uploaded second, and Raw file C is uploaded last.
There are no existing overlapping activities for this account.

• Raw file A is uploaded first and will cause an Auto Created Activity to be generated, with the Auto Created Period covering the raw file timeframe of 9am - 10am
  
  
  
   
• Raw file B is uploaded second, and the Auto Created Activity is detected as overlapping (as the end time is within 1 hour of the start time of Raw file B). Raw file B's athlete is added to the Auto Created Activity, and the Activity's period is extended to end at 11.30am to cover both Raw File A and B
  
  
  
   
• Raw file C is uploaded last, and the Auto Created Activity is detected as overlapping (as the end time is within 1 hour of the start time of Raw file C). Raw file C's athlete is added to the Auto Created Activity, and the Activity's period is extended to end at 1.00pm to cover Raw File A, B and C
  
  
  
   
• Result: 1 Auto Created Activity is generated
  

Example 2

Raw file A is uploaded first, Raw file C is uploaded second, and Raw file B is uploaded last.
There are no existing overlapping activities for this account.

• Raw file A is uploaded first and will cause an Auto Created Activity to be generated, with the Auto Created Period covering the raw file timeframe of 9am - 10am
  
  
  
   
• Raw file C is uploaded second. The Auto Created Activity generated from Raw file A does not overlap with Raw file C, as this activity ends at 10am and this is not within 1 hour of Raw file C start time of 12pm.
  Therefore an additional Auto Created Activity is generated ('Auto Created Activity 2'), with the Auto Created Period covering the raw file timeframe of 12pm - 1pm
  
  
  
   
• Raw file B is uploaded last. Given both Auto Created Activities generated by Raw file A and C overlap with Raw file B, Raw file B will be associated with one of the existing Auto Created Activities. The Auto Created Activity it is added to will have its period extended to cover Raw file B's timeframe.
  
  
  
   
• Result: 2 Auto Created Activities are generated