This Data Connector is not included in the Graphics license and requires payment of an additional licensing fee. If you need access please contact your designated Customer Success Manager.
Requirements
Don't need an API KEY.
Local files provided by Matsport:
Json (1 per stage, Jersey, Competitors)
XML (GPS, Groups)
Middleware installed to push local files, with a datasource, with an endpoint race:
https://discover.flowics.com/discover/public/matsport/push/{token}/{racecode}. {token} is a security token (to avoid anyone pushing data. for now is obtain out of band). {racecode} is the natural race code (TDF - tour de france. is provided by MATSPORT).
Adding the Data Source
Add a Data Source Push, if it is not available in your Catalog, please contact the Customer Success Manager of your account.
The next step is to configure the Data Source, (1) Add a name, (2) Set the path (Example, file:///C:/MATSPORT/RACE_2022_ETAPE05_GRP.xml) where the local files provided by Matsport are located, (3) Set the endpoint with the race information. (4) configure the integration (5) Select the Middleware and (6) finally this configuration is not modified.
Adding the Data Connector to the Graphics Editor
First, you need to add a data Connector to your tree (1) and then click on Connect (2).
From the DataConnector panel choose MATSPORT (if it's not listed contact your designated Customer Success Manager)
Datasets / Tables
Complete the dataset settings by selecting a table. Each table has its own schema and represents different kinds of information. The tables supported are:
“Chronometer”: This data set is a webservice that makes available all the stopwatches that Matsport has for all competitions.
“Info”: This data set contains event information such as name, start date, organizer, type, and racecode.
“GPS”: With this data set you can obtain information such as distance to the goal from the start, Global positioning information (lat, long, alt).
“Groups”: With this data set you can obtain information on the peloton, such as distance, information on the runners and the teams that make up the peloton, such as name, nationality, position, image of the jersey, among others.
“Riders”: This data set contains detailed information of the riders such as name, surname, nationality, jersey, team, category among others.
“Stage - Jerseys”: This data set contains information of the riders by stage.
“Stage - Rankings”: This dataset contains information on the top 20 riders as well as their time and position on the board.
“Teams”: This data set contains team information such as name, jersey, nationality, members, category and more.
Matsport example graphics
With the data now set up, you can start creating your tree by using building blocks, binding content, and formatting the Graphics. In this example, we use the information from the data sets Chronometer, Stage Jerseys and Groups.
Acquisition Style
The following table lists the acquisition style of each of the datasets available in this connector.
If style is Unattended. it means that the connector will automatically refresh the data every certain period of time specified by the user (by default it's 300 seconds).
If style is attended, then the graphics operator needs to manually refresh the data to get the latest version of the stats.
Datasets / Tables | Unattended |
Chrono | ❌ |
Info | ❌ |
GPS | ✅ |
Groups | ❌ |
Riders | ❌ |
Jerseys | ❌ |
Rankings | ❌ |
Teams | ❌ |