File-Based Aggregate Match Demographics Contributions
Overview
Participants contribute aggregate number of matches played by category. Counts are broken down by zipcode + effective_start_date + effective_end_date.
Aggregate data is serviced by file contribution only.
Please escape any special characters such as embedded quotes with a '\' (backslash) before including it in any field in the file. See https://ustadigital.atlassian.net/wiki/spaces/DEV/pages/39648460801
File Submission Attributes
The following criteria applies to the data submissions
Attribute | Detail |
|---|---|
Frequency | Monthly |
Timeframe to included | Cummulative Year to Date based on Match date |
Inclusion Criteria | Only US Zipcodes should be included |
Effective Start/End Dates | Should be based on Play Date |
Aggregation Grain | effective_start_date, effective_end_date, 5 digit Zipcode Monthly |
File Name Convention
Player files use the following naming convention
MATCH-DEMOGRAPHICS-[SOURCENAME]-[YYYYMMDD].csv
Where:
SOURCENAME: The contributor name assigned by USTA.
YYYYMMDD: Effective date of contribution
Column Definitions
The following table lists the fields and formats.
Field | Required/Optional | Identifying | Format | Description | |
|---|---|---|---|---|---|
| 1 | source_name | Required | Yes | Text | Contributor (USTA will assign) |
| 2 | zip_code | Required | Yes | 5 digit zipcode - must include any leading zeros | Postal code |
| 3 | effective_start_date | Required | Yes | YYYY-MM-DD | Start of reported data (shipping date), Should always be jan 1 of the current year |
| 4 | effective_end_date | Required | Yes | YYYY-MM-DD | End of reported data (shipping date) - Should always be the last day of the reporting month, ie 2023-10-31 |
| 5 | total_players | Required | No | Number | Total number of registered players that played matches |
| 6 | total_matches_played | Required | No | Number | Total matches played |
| 7 | total_matches_collegiate | Required | No | Number | Total collegiate matches out of total_matches |
| 8 | player_demographic_u18 | Required | No | Number | Count of Players age < 18yo at time of match |
| 9 | player_demographic_18_to_34 | Required | No | Number | Count of Players age 18 - 34 at time of match |
| 10 | player_demographic_35_to_49 | Required | No | Number | Count of Players age 35 - 49 at time of match |
| 11 | player_demographic_50_to_69 | Required | No | Number | Count of Players age 50 - 69 at time of match |
| 12 | player_demographic_70_over | Required | No | Number | Count of Players 70 and over at time of match |
Example
MATCH-DEMOGRAPHICS-ACTIONSPORTS-20240620.csv
Where:
Source Name: ACTIONSPORTS
Effective Date: 2024-02-01
source_name, zip_code,effective_start_date,effective_end_date,total_players,total_matches_played,total_matches_collegiate,player_demographic_u18,player_demographic_18_to_34,player_demographic_35_to_49,player_demographic_50_to_69,player_demographic_70_over
ACTION_SPORTS, 10019, 2024-01-01, 2024-01-31, 100, 50, 10, 0, 20, 20, 20, 20
On This Page: