Table of content

Table of content 2

1   Introduction  2

1.1.. This document 2

1.2.. Objective. 2

1.3.. Main Audience. 2

1.4.. Glossary. 2

1.5.. Related Documents. 2

2   Overall Perspective  2

2.1.. Objective. 2

2.2.. End to End data flow. 2

3   Messages  2

3.1.. Applicable Messages. 2

3.2.. Messages. 2

3.2.1... List of participants by discipline / List of participants by discipline Update. 2

3.2.1.1    Description. 2

3.2.1.2    Header Values. 2

3.2.1.2.1     PiT Header 2

3.2.1.3    Trigger and Frequency. 2

3.2.1.3.1     PiT Triggers. 2

3.2.1.4    Message Structure. 2

3.2.1.5    Message Values. 2

3.2.1.6    Message Sort 2

3.2.2... List of teams / List of teams update. 2

3.2.2.1    Description. 2

3.2.2.2    Header Values. 2

3.2.2.2.1     PiT Header 2

3.2.2.3    Trigger and Frequency. 2

3.2.2.3.1     PiT Triggers. 2

3.2.2.4    Message Structure. 2

3.2.2.5    Message Values. 2

3.2.2.6    Message Sort 2

3.2.3... Start List 2

3.2.3.1    Description. 2

3.2.3.2    Header Values. 2

3.2.3.2.1     PiT Header 2

3.2.3.3    Trigger and Frequency. 2

3.2.3.3.1     PiT Triggers. 2

3.2.3.4    Message Structure. 2

3.2.3.5    Message Values. 2

3.2.3.6    Message Sort 2

3.2.4... Event Unit Results. 2

3.2.4.1    Description. 2

3.2.4.2    Header Values. 2

3.2.4.2.1     PiT Header 2

3.2.4.2.2     RT Header 2

3.2.4.3    Trigger and Frequency. 2

3.2.4.3.1     PiT Triggers. 2

3.2.4.3.2     RT Triggers. 2

3.2.4.4    Message Structure. 2

3.2.4.5    Message Values. 2

3.2.4.6    Message Sort 2

3.2.5... Cumulative Results. 2

3.2.5.1    Description. 2

3.2.5.2    Header Values. 2

3.2.5.2.1     PiT Header 2

3.2.5.2.2     RT Header 2

3.2.5.3    Trigger and Frequency. 2

3.2.5.3.1     PiT Triggers. 2

3.2.5.3.2     RT Triggers. 2

3.2.5.4    Message Structure. 2

3.2.5.5    Message Values. 2

3.2.5.6    Message Sort 2

3.2.6... Event Final Ranking. 2

3.2.6.1    Description. 2

3.2.6.2    Header Values. 2

3.2.6.2.1     PiT Header 2

3.2.6.3    Trigger and Frequency. 2

3.2.6.3.1     PiT Triggers. 2

3.2.6.4    Message Structure. 2

3.2.6.5    Message Values. 2

3.2.6.6    Message Sort 2

3.2.7... Event’s Medallists. 2

3.2.7.1    Description. 2

3.2.7.2    Header Values. 2

3.2.7.2.1     PiT Header 2

3.2.7.3    Trigger and Frequency. 2

3.2.7.3.1     PiT Triggers. 2

3.2.7.4    Message Structure. 2

3.2.7.5    Message Values. 2

3.2.7.6    Message Sort 2

3.2.8... Discipline Configuration. 2

3.2.8.1    Description. 2

3.2.8.2    Header Values. 2

3.2.8.2.1     PiT Header 2

3.2.8.3    Trigger and Frequency. 2

3.2.8.3.1     PiT Triggers. 2

3.2.8.4    Message Structure. 2

3.2.8.5    Message Values. 2

3.2.8.6    Message Sort 2

3.2.9... Event Unit Weather Conditions. 2

3.2.9.1    Description. 2

3.2.9.2    Header Values. 2

3.2.9.2.1     PiT Header 2

3.2.9.3    Trigger and Frequency. 2

3.2.9.3.1     PiT Triggers. 2

3.2.9.4    Message Structure. 2

3.2.9.5    Message Values. 2

3.2.9.6    Message Sort 2

4   Messages Sequence  2

5   Codes  2

5.1.. Global Codes. 2

5.2.. Ski Jumping Codes. 2

6   General definitions  2

6.1.. ODF Message Structure. Error! Bookmark not defined.

6.1.1... ODF Declaration. Error! Bookmark not defined.

6.1.2... ODF Header Error! Bookmark not defined.

6.1.3... ODF Body. Error! Bookmark not defined.

6.2.. ODF Data Types and Formats. Error! Bookmark not defined.

6.2.1... Rules for rounding numbers. Error! Bookmark not defined.

6.2.2... Measures format Error! Bookmark not defined.

6.2.3... Rules for measures conversion. Error! Bookmark not defined.

6.3.. ODF Message Update. Error! Bookmark not defined.

7   DOCUMENT CONTROL  2

7.1.. File Reference.2

7.2.. Version history. 2

7.3.. Change Log. 2

 

1    Introduction

1.1    This document

This document includes the ODF Ski Jumping Data Dictionary. This document refines the messages described in the ODF General Messages Interface Document specifically for Ski Jumping, as well as defines the codes used in these messages.

1.2    Objective

The objective of this document is to provide a complete and formal definition of the ODF Ski Jumping Data Dictionary, with the intention that the information message producer and the message consumer can successfully interchange the information as the Ski Jumping competition is run.

1.3    Main Audience

The main audience of this document is the IOC as the ODF promoter, ODF users such as the World News Press Agencies, Rights Holding Broadcasters and International Sports Federations.

1.4    Glossary

The following abbreviations are used in this document

Acronym

Description

IF or International Federation

The international governing body of an Olympic Sport as recognized by the IOC

IOC

International Olympic Committee

IPC

International Paralympic Committee

NOC

National Olympic Committee recognized as such by the IOC

NPC

National Paralympic Committee as recognized by the IPC

ODF

Olympic Data Feed

ODF Light

It is a type of ODF message that includes extensions to standard ODF messages in order to resolve references between messages and common codes. These extensions facilitate the message processing for ODF customers

ODF-PiT

Olympic Data Feed Point in Time, messages that are generated at certain point during competition

ODF-RT

Olympic Data Feed Real Time, messages that are generated when available

OPNS

Olympic and Paralympic News Service

RSC

Results System Codes, determine uniquely one unit of the competition, specifying the discipline, gender, event, phase and unit.

Sport

is administered by an international federation and can be composed of one or more disciplines

WNPA

World News Press Agencies

 

 

 


 

1.5    Related Documents

 

Document Reference

Document Title

Document Description

ODF/INT001

ODF Message Transmission Document

This document describes the technical standards to be used to transfer ODF messages between the message generators and the final ODF users

ODF/COD001

ODF Common Codes Document

This document describes the ODF codes used across the rest of the ODF documents

ODF/INT004

ODF General Messages Interface Document

This document describes the ODF general messages

 

 

2    Overall Perspective

2.1    Objective

The objective of this document is to focus on the formal definition of the ODF Ski Jumping Data Dictionary.

2.2    End to End data flow

In the following chapters, for each ODF message the general description, header values, triggers and frequency, structure, values and sort of the message will be defined.


3    Messages

3.1    Applicable Messages

The following table is a full list of all ODF messages and describes the list of messages used in this sport.

 

    The column “Message type” indicates the DocumentType that identifies a message

 

    The column “Message name” is the message name identified by the message type

 

    The column “Feed” identifies the message feed (PiT for Point in Time messages, RT for Real Time messages and PDF for PDF messages)

 

    The column “Message extended in this document” indicates whether a particular message has extended definition in regards to those that are general for all sports. If one message has extended definition, it should be considered both, the extensions as well as the general rules for one message that is used in the case of the sport. However, if one particular message is not extended, then it should follow the general definition rules.

 

Message Type

Message Name

Feed

Message extended

DT_SCHEDULE

Competition schedule

PiT

 

DT_SCHEDULE_UPDATE

Competition schedule update

PiT

 

DT_PARTIC / DT_PARTIC_UPDATE

List of participants by discipline / List of participants by discipline Update

PiT

X

DT_PARTIC_TEAMS / DT_PARTIC_TEAMS_UPDATE

List of teams / List of teams update

PiT

X

DT_MEDALS

Medal standings

PiT

 

DT_MEDALLISTS_DAY

Medallists of the day

PiT

 

DT_GLOBAL_GM

Global good morning

PiT

 

DT_GLOBAL_GN

Global good night

PiT

 

DT_START_LIST

Start List

PiT

X

DT_RESULT

Event Unit Results

PiT/RT

X

DT_CUMULATIVE_RESULT

Cumulative Results

PiT/RT

X

DT_RANKING

Event Final Ranking

PiT

X

DT_MEDALLISTS

Event’s Medallists

PiT

X

DT_MEDALLISTS_DISCIPLINE

Medallists by discipline

PiT

 

DT_COMMUNICATION

Official Communication

PiT

 

DT_GM

Discipline/venue good morning

PiT

 

DT_GN

Discipline/venue good night

PiT

 

DT_CONFIG

Discipline Configuration

PiT

X

DT_WEATHER

Event Unit Weather Conditions

PiT

X

DT_SERIAL

List of Current PiT Serial

PiT

 

DT_RT_KA

RT Discipline/Venue keep alive

RT

 

DT_PDF

PDF Message

PDF

 

DT_PDF_GM

PDF Discipline/Venue good morning

PDF

 

DT_PDF_GN

PDF Discipline/Venue good night

PDF

 

DT_PDF_SERIAL

List of Current PDF Serial

PDF

 

DT_RT_GM

RT Discipline/venue good morning

RT

 

DT_RT_GN

RT Discipline/venue good night

RT

 

 

 

 

 


 

3.2    Messages

 

3.2.1     List of participants by discipline / List of participants by discipline Update

3.2.1.1  Description

A participant is considered as an individual competitor (type athlete, participating or not in the current games) or as an official in one or several disciplines or as a competitor being part of a team (team member).

 

Although the participant participates in more than one event or more than one discipline, this message just contains all the information for the discipline of the message, although listing the information of all the events for that discipline.

 

This message includes historical athletes that do not participate in the current competition. Historical athletes will not be registered to any event.

 

It is important to point out that all the sport messages that make references to athletes (start list, event unit results, etc.) will always match the athlete ID with the athlete ID as it is being sent in the List of athletes by discipline message. The historical athletes will be used to match historical athlete information as it is in the records message when sending the previous record information and this previous record was an historical record not being broken in the current competition.

 

This message also includes the historical team members of the historical teams’ messages. It could happen these historical athletes would appear in this message just for this reason (being part of historical teams).

 

List of participants by discipline (DT_PARTIC) is a bulk message, provided for each discipline. It is a complete participant information message for one particular discipline.  The arrival of this message resets all the previous participants’ information for one particular discipline. This message can include a list of current athletes, officials, coaches, guides, technical officials, Reserves and historical athletes.

 

List of participants by discipline update (DT_PARTIC_UPDATE) is an update message. It is not a complete list of participants’ information by discipline message, only the participant data being modified, i.e. if some data of one participant changes, the element Participant for it with all its children and attributes must mbe sent.

 

The key of the information updated consists of the following attribute: Participant @Code. Therefore, any new or updated Participant Discipline-Event will be identified by all these attributes.

 

 

3.2.1.2  Header Values

3.2.1.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC / DT_PARTIC_UPDATE

List of participants  by discipline message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.1.3  Trigger and Frequency

3.2.1.3.1  PiT Triggers

The DT_PARTIC message is sent as a bulk message one month before the Games.

 

It is sent several times up to the date from what only DT_PARTIC_UPDATE messages are sent.

 

 The DT_PARTIC_UPDATE message is triggered when there is a modification in a DT_PARTIC bulk message sent before.

 

 


3.2.1.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition

 

 

 

 

 

Code

 

 

 

 

Participant (1,N)

 

 

 

 

 

Code

 

 

 

 

Parent

 

 

 

 

Status

 

 

 

 

GivenName

 

 

 

 

FamilyName

 

 

 

 

PrintName

 

 

 

 

PrintInitialName

 

 

 

 

TVName

 

 

 

 

TVInitialName

 

 

 

 

Gender

 

 

 

 

Organisation

 

 

 

 

BirthDate

 

 

 

 

Height

 

 

 

 

Weight

 

 

 

 

PlaceofBirth

 

 

 

 

CountryofBirth

 

 

 

 

PlaceofResidence

 

 

 

 

CountryofResidence

 

 

 

 

Nationality

 

 

 

 

MainFunctionId

 

 

 

 

Current

 

 

 

 

OlympicSolidarity

 

 

 

 

ModificationIndicator

 

 

 

 

Discipline

 

 

 

 

 

Code

 

 

 

 

InternationalFederationId

 

 

 

 

RegisteredEvent (0,N)

 

 

 

 

 

Gender

 

 

 

 

Event

 

 

OfficialFunction (0,N)

 

 

 

 

 

FunctionId

 

 


3.2.1.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Participant

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Participant’s ID.

 

It identifies an athlete or an official and the holding participant’s valid information for one particular period of time.

 

It is used to link other messages to the participant’s information.

 

Participant’s information (example @Organisation) will not be the latest for the athlete/official, unless the @Code attribute is the same as the @Parent attribute. However, this information could be the one being valid in the particular moment of a start list, event unit results, etc.

 

When the participant is an historical one, then this ID will start with “A” when it is an Athlete, “C” when Coach and “O” when Official.

Parent

M

S(20) with no leading zeroes

Participant’s parent ID, which is used to link to the latest valid information for one participant. @Parent attribute should be linked to the latest participant‘s information, by retrieving that Athlete/Official whose @Code attribute is the same as @Parent.

 

The participant containing @Code attribute being the same as the @Parent attribute will be the one with the latest information for the participant.

The @Parent attribute will only be different from @Code in the case that critial personal information has changed from previous competitions. The typical examples are Organisation (for change of country) or Name (particularly for women changing their name at marriage). Further to be clear, @Parent and @Code can only be different if Current = "false".

Status

O

CC @AccreditationStatus

Participant’s accreditation status this atribute is Mandatory in the case of @Current=”true” and it is optional in the case that @Current=”false”.

 

To delete a participant, a specific value of the Status attribute is used.

GivenName

O

S(25)

Given name in WNPA format (mixed case)

FamilyName

M

S(25)

Family name in WNPA format (mixed case)

PrintName

M

S(35)

Print name (family name in upper case + given name in mixed case)

PrintInitialName

M

S(18)

Print Initial name (for the given name it is sent just the initial, without dot)

TVName

M

S(35)

TV name

TVInitialName

M

S(18)

TV initial name

Gender

M

CC @PersonGender

Participant’s gender

Organisation

M

CC @Organisation

Organisation ID

BirthDate

O

YYYYMMDD

Date of birth. This information could be not known at the very beginning, but it will be completed for all participants after successive updates

Height

O

N(3)

999

Height in centimetres. It will be included if this information is available. This information is not needed in the case of officials/referees.

Weight

O

N(3)

999

Weight in kilograms. It will be included if this information is available.

This information is not needed in the case of officials/referees.

PlaceofBirth

O

S(75)

Place of Birth

CountryofBirth

O

CC @Country

Country ID of Birth

PlaceofResidence

O

S(75)

Place of Residence

CountryofResidence

O

CC @Country

Country ID of Residence

Nationality

O

CC @Country

Participant’s nationality.

 

Although this attribute is optional, in very exceptional situations it will not be known, and for this reason not ready to be sent.

MainFunctionId

O

CC @Function

Main function

In the Case of Current=”true” this attribute is Mandatory.

Current

M

boolean

It defines if a participant is participating in the games (true) or is a Historical participant (false).

OlympicSolidarity

O

Y or N

Flag indicating if the participant participates in the Olympic Movement program.

ModificationIndicator

M

N, U

Attribute is mandatory in the  DT_PARTIC_UPDATE message only

 

N-New participant (in the case that this information comes as a late entry)

U-Update participant

 

If ModificationIndicator=’N’, then include new participant to the previous bulk-loaded list of participants

 

If ModificationIndicator=’U’, then update the participant to the previous bulk-loaded list of participants

 

To delete a participant, a specific value of the Status attribute is used.

 

Participant /Discipline

Although any participating athlete will be assigned at least one discipline, it could be more. Any accredited official will be assigned at least one discipline, but it could be more. If an athlete or official is assigned to more than one discipline, it will be included in the participant message of both disciplines.

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

It is the discipline code used to fill the OdfBody @DocumentCode attribute.

InternationalFederationId

M

S(16)

Competitor’s federation number for Ski Jumping

 

Participant /Discipline /RegisteredEvent

Any accredited athlete will be assigned to one or more events. There is one exception: in some sports, substitutes may be accredited without any associated event.

 

Historical athletes are not register to any event.

Attribute

M/O

Value

Comments

Gender

M

CC @DisciplineGender

Discipline Gender Code

Event

M

CC @Event

Event ID

 

Participant /OfficialFunction

Send if the official has optional functions. Do not send, otherwise.

Attribute

M/O

Value

Comments

FunctionId

M

CC @Function

Additional officials’ function code

 

 

3.2.1.6  Message Sort

The message is sorted by Participant @Code


 

 

3.2.2     List of teams / List of teams update

3.2.2.1  Description

DT_PARTIC_TEAMS contains the list of teams related to the current competition.

 

A team is a type of competitor, being a group of two or more individual athletes participating together in one event. Pairs (tennis, figure skating, etc.) are also defined as team of two competitors. One team participates in one event of one discipline. When one team participates in multiple events, there will be one team for each event for the same group. Also when the same organisation participates in the same event twice, there will different teams.

 

A historical team is defined as a group of athletes (team members) competing in the past in a competition event for an organisation. The historical team members appearing in this message will be listed in the list of historical athletes’ messages. The list of historical teams just associates historical team members with the corresponding historical teams. Historical teams will not be registered to any event.

 

For equestrian one athlete and one horse are not considered a team, the horse is an attribute of the athlete.

 

List of teams (DT_PARTIC_TEAMS) is a bulk message by discipline. The list is always complete. The arrival of this message resets all the previous participant teams’ information for that discipline. It is assumed that all teams appearing in this list are valid, in the meaning that they are participating or they could participate in one event.

 

List of teams update (DT_PARTIC_TEAMS_UPDATE) is an update message. It is not a complete list of teams’ information message. It only contains the team data being modified.

 

The key of the information updated consists of the following attribute: Team @Code. Therefore, any new or updated Team Discipline-Event will be identified by all these attributes.

 

 

3.2.2.2  Header Values

3.2.2.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD is defined according to CC @Discipline

DocumentType

DT_PARTIC_TEAMS_UPDATE / DT_PARTIC_TEAMS

List of participant teams message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

Venue

CC @VenueCode

Venue where the message is generated.

 

 

3.2.2.3  Trigger and Frequency

3.2.2.3.1  PiT Triggers

The DT_PARTIC_TEAMS message is sent as a bulk message one month before the Games.

 

It is sent several times up to the date from what only DT_PARTIC_TEAMS_UPDATE messages are sent.

 

The DT_PARTIC_TEAMS_UPDATE message is triggered when there is a modification in a DT_PARTIC_TEAMS bulk message sent before.

 

 


3.2.2.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition

 

 

 

 

 

Code

 

 

 

 

Team (1,N)

 

 

 

 

 

Code

 

 

 

 

Organisation

 

 

 

 

Number

 

 

 

 

Name

 

 

 

 

Gender

 

 

 

 

Current

 

 

 

 

ModificationIndicator

 

 

 

 

Composition (0,1)

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

Code

 

 

 

 

Order

 

 

Discipline (0,1)

 

 

 

 

 

Code

 

 

 

 

InternationalFederationId

 

 

 

 

RegisteredEvent (0,1)

 

 

 

 

 

Event

 

 

 

 

Gender

 

 

 

 

Bib

 


3.2.2.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Team

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Team’s ID (example SJM490ESP01)

Organisation

M

CC @Organisation

Team organisation’s ID

Number

M

N(2)

Team’s number. In the case there is not more than one team for one organisation participating in one event, it will be 1.

Name

O

S(73)

Team’s name.

 

It will apply to some of the disciplines. If there is not any special rule for that discipline, send the Description of the code CC@Organisation. It is Optional in the case of  List of Team Update when the @ ModificationIndicator=D

Gender

M

CC @DisciplineGender

Discipline Gender Code of the Team

Current

M

boolean

It defines if a team is participating in the games (true) or it is a Historical team (false)

ModificationIndicator

M

N, U, D

Attribute is mandatory in the DT_PARTIC_TEAMS_UPDATE  message only

 

N-New team (in the case that this information comes as a late entry)

U-Update team

D-Delete team

 

If ModificationIndicator=’N’, then include new team to the previous bulk-loaded list of teams

 

If ModificationIndicator=’U’, then update the team to the previous bulk-loaded list of teams

 

If ModificationIndicator=’D’, then delete the team to the previous bulk-loaded list of teams

 

Team /Composition /Athlete

In the case of current teams the number of athletes is 2 or more.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID of the listed team’s member. 

 

Therefore, he/she makes part of the team’s composition.

Order

O

Numeric

Team member order

 

Team /Discipline

Each team is assigned just to one discipline.

Attribute

M/O

Value

Comments

Code

M

CC @Discipline

It must be the discipline code used to fill the OdfBody @DocumentCode attribute

InternationalFederationId

M

S(16)

Federation number for the corresponding discipline (include if the discipline assigns international federation codes to teams)

 

Team /Discipline /RegisteredEvent

Each team is assigned at least to one event, except for a historical team, which will not be registered to any event.

Attribute

M/O

Value

Comments

Event

M

CC @Event

Event ID

Gender

M

CC @DisciplineGender

Discipline Gender Code

Bib

O

N(3) 990

Team bib number to be sent when available

 

 

3.2.2.6  Message Sort

The message is sorted by Team @Code.


 

 

3.2.3     Start List

3.2.3.1  Description

The Start List is a message containing the list of competitors for one particular event unit (individual or team event unit).

 

The Start List is a mandatory message for all disciplines.

 

Each ODF Sport Data Dictionary will include the mandatory attributes /elements of this message and redefine the optional ones.

 

 

3.2.3.2  Header Values

3.2.3.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).

DocumentType

DT_START_LIST

Start List message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.3.3  Trigger and Frequency

3.2.3.3.1  PiT Triggers

The general rule is that this message is sent as soon as some of the information arriving in this message and associated to the event unit (PhaseInfos, UnitInfos, and Officials) is known and also when all the competitors for one particular event unit are known.

 

For team event units this message is sent as soon as the teams are available (maybe first teams, and after another message with team members).

 

In the final round of the team event, the Start List message is expected after the last jump of the third group. This message should contain the final alignment of the fourth group competitors.

 

 This Start List message should be followed by a DT_RT_RESULT message with the Result status Live Mandatory.

 

Trigger also after any major change.

 

 


3.2.3.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Competition

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

StartDate

 

 

 

 

Officials (0,1)

 

 

 

 

 

 

 

Official (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Function

 

 

 

 

 

 

Order

 

 

 

 

 

 

ExtOfficial (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 

 

 

Start (0,N)

 

 

 

 

 

 

 

StartOrder

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

Competitor

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Type

 

 

 

 

 

 

Bib

 

 

 

 

 

 

Composition (0,1)

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

Order

 

 

 

 

 

 

Bib

 

 

 

 

 

 

EventUnitEntry (0,N)

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

Code

 

 

 

 

 

 

Pos

 

 

 

 

 

 

Value

 


3.2.3.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

UnitInfos /UnitDateTime

Scheduled start date and time.

Attribute

M/O

Value

Comments

StartDate

M

DateTime

Actual start date and time. For multiday units, the start time is on the first day.

 

Officials /Official

Official associated to the event unit.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Key of the official, to uniquely identify this element

Function

M

CC @Function

Send the function code for:

FIS Race Director

FIS Technical Delegate

Chief of Competition

FIS Assistant Technical Delegate

FIS Assistant Race Director

FIS Equipment Controller

Judge

Order

M

Numeric

Order of the Officials following the Sports Rule

 

Officials /Official /ExtOfficial

Official’s extended information.

Type

Code

Pos

Value

Description

EO_SJ

SJ_POSITION

 

S(2)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Position of the Judge, i.e. A, B, C, SC…

SJ_JUDGE

 

S(2)

Y,N,SC

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Value:

Send ‘SC’ if the official is a Start Controller.

Send ‘Y’ if the official is a Judge but not the Start Controller.

Send ‘N’ for the rest of the officials.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

EO_SJ/ SJ_POSITION

Position of the Judge.

Always

EO_SJ/ SJ_JUDGE

Indicates if the official is a Judge.

Always

 

 

 

Start

This element is optional (due to the information availability, the information related to the event unit can be sent before the competitors information).

Attribute

M/O

Value

Comments

StartOrder

M

Numeric

Start order of the competitor in the start list (either single athlete or team).

 

In the case of team competitor, start order of the team. The team members will have the order within the team in their respective Competitor /Composition /Athlete elements (@Order attribute).

SortOrder

M

Numeric

Same as @StartOrder

 

Start /Competitor

Competitor participating in the event unit

 

Start /Competitor /Composition is optional for a similar reason: knowing the teams participating in one event unit, it is not known yet the team members participating.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

T,A

T for team

A for athlete

Bib

O

N(3) 999

Team’s bib number, to be sent mandatory just in the case of team event units

 

Start /Competitor /Composition /Athlete

Athlete or team member’s extended information.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to either a team member or an individual athlete

Order

M

Numeric

Order attribute used to sort team

members (i.e.: 1, 2..4) in a team (if Competitor @Type=”T”) or 1 if Competitor @Type=”A”.

Bib

M

For team members:

N(3)-N(1) 990-9

 

Or

 

For single athletes:

N(3) 999

Athlete’s bib number.

In case of a team member it will be constructed from team’s bib and the order within the team (e.g.: for team event:

“11-2” means team with bib 11 and this is the second jumper of the team).

 

Start /Competitor /Composition /Athlete /EventUnitEntry

Team member or individual athlete’s event unit entry.

Type

Code

Pos

Value

Description

EU_ENTRY

SJ_JUMP_ORDER

 

N(2)

99

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Field used to order the athletes in the team event final.

SJ_QM

 

CC @QualificationMark

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Indicates if the jumper is prequalified.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

EU_ENTRY/ SJ_JUMP_ORDER

Field used to order the athletes in the team event final.

Just for Team event units.

EU_ENTRY/ SJ_QM

Indicates if the jumper is prequalified.

Just for the qualification round

 

 

 

 

3.2.3.6  Message Sort

The message is sorted by the Start@SortOrder attribute.


 

 

3.2.4     Event Unit Results

3.2.4.1  Description

The Event Unit Results is a message containing the results of the competitors in one (individual or team) event unit.

The Event Unit Results is a mandatory message for all sports. The definition includes as much generic information as possible due to the fact that each discipline and event has its own format for the results information (example: score of a match, time in a race, distance in a throw…).

The unofficial ResultStatus is not used for trainings and trials.

 

 

3.2.4.2  Header Values

3.2.4.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).

DocumentType

DT_RESULT

Event Unit Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or unofficial (or intermediate, interim, partial).

“OFFICIAL” /

“UNOFFICIAL” /

“INTERMEDIATE” /

“INTERIM”/

“PARTIAL”

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

DocumentSubtype

N/A

Not used in SJ.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

3.2.4.2.2  RT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

P according to CC @Phase

UU according to CC @Unit

DocumentType

DT_RT_RESULT

Event Unit Real Time Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is live update or live full (or live Mandatory, Live Last).

“LIVE_UPDATE” /

“LIVE_FULL” /

“LIVE_MANDATORY” /

“LIVE_LAST

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.4.3  Trigger and Frequency

3.2.4.3.1  PiT Triggers

The general rule is that this message is sent when the event unit finishes and the results are still unofficial.

 

Also, this message is expected when the results become official. The official/unofficial status is included in the ODF headers (ResultStatus attribute).

 

Trigger also after any major change.

 

 

3.2.4.3.2  RT Triggers

•  For ResultStatus=LIVE_UPDATE:

 

o  T1: Trigger when the gate number is known

 

o  T2: Trigger when the  traffic lights turns to green( the competitor starts the jump)

 

o  T3: Trigger when each competitor completes his jump

 

o  T4: Trigger when the results are known

 

o  T5: Trigger at the beginning of each Group  (Team competition)

 

•  For ResultStatus=LIVE_FULL

Send as it will be defined for each RT transmission in the parameters of the DT_RT_GM message.

 

•  For ResultStatus=LIVE_MANDATORY

It is sent when a correction in the previous messages has to be done.

 

•  For ResultStatus=LIVE_LAST

Send as the last message (that indicates that no new messages are expected for the given ODF unique key, unless something unexpected, that needs correction of previous messages data, happens while the transmission is still open (Good night message has not been sent)).

 

 


3.2.4.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Level 7

Level 8

Competition

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

UnitInfos (0,1)

 

 

 

 

 

 

 

 

UnitDateTime (0,1)

 

 

 

 

 

 

 

 

StartDate

 

 

 

 

 

 

 

EndDate

 

 

 

 

 

 

UnitInfo (0,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

 

 

Rank

 

 

 

 

 

 

 

RankEqual

 

 

 

 

 

 

 

Result

 

 

 

 

 

 

 

IRM

 

 

 

 

 

 

 

QualificationMark

 

 

 

 

 

 

 

SortOrder

 

 

 

 

 

 

 

ResultType

 

 

 

 

 

 

 

Competitor (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 

 

 

 

 

Composition

 

 

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Order

 

 

 

 

 

 

 

Bib

 

 

 

 

 

 

 

ExtendedResults (0,1)

 

 

 

 

 

 

 

 

ExtendedResult (1,N)

 

 

 

 

 

 

 

 

Type

 

 

 

 

 

 

 

Code

 

 

 

 

 

 

 

Pos

 

 

 

 

 

 

 

Value

 


3.2.4.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

UnitInfos /UnitDateTime

Actual start –and/or end- dates and times.

 

This element is just for PiT.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

StartDate

O

DateTime

Actual start date-time. For multi-day units, the start date-time is that on the first day.

N

When available

EndDate

O

DateTime

Actual end date-time (The attribute should be informed, when available, for ResultStatus UNOFFICIAL and OFFICIAL)

N

When available

 

UnitInfos /UnitInfo

Unit info item associated to the event unit.

Type

Code

Pos

Value

Description

UI_GENERAL

SJ_ATTENDANCE

 

   N(6)

999999

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Number of spectators

UI_SJ

SJ_BASE_GATE

N(1)

9

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

For team events: send the number of the group (1,2,3,4)

For individual events: send 0

For @Value:

Base Gate

SJ_DIST_BEAT

N(1)

9

N(4).N(1)

9990.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Number of the rank.

It’s a sequential number from 1 to 3.

For @Value:

Send the distance needed (to beat) for the corresponding rank (in @Pos) in meters (with one decimal digit) for a competitor in the final.

Do not send for the first competitor.

SJ_LAST_QUALIFIED

 

S(20) with no leading zeroes

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

For the team competition first round: it is the code of the last qualified team.

For Individual qualification and first round: it is the code of the last qualified athlete.

Don’t send until the moment when a competitor is ranked in this position.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

RT Only

RT Trigger

UI_GENERAL/ SJ_ATTENDANCE

Number of spectators

Always, if available

N

When available

UI_SJ/ SJ_BASE_GATE

Base Gate of a group (@Pos 1,2,3,4 in the team events) or an individual athlete (@Pos 0 in the individual events).

Always

N

When available

UI_SJ/ SJ_DIST_BEAT

Distance needed (to beat) for the corresponding rank (in @Pos) for a competitor.

Just for Final rounds of Individual or Team events (except if competitor is the first one)

Y

T4

UI_SJ/ SJ_LAST_QUALIFIED

For the team competition first round: it is the code of the last qualified team.

For Individual qualification and first round: it is the code of the last qualified athlete.

Don’t send until the moment when a competitor is ranked in this position.

For Individual and Team events (all phases excepting final, training and trial).

N

T4

 

 

 

Result

For each Event Unit Results message, there must be at least one competitor being awarded with a result in the event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

Rank of the competitor in the corresponding event unit. This attribute is optional because the skier could get an invalid rank mark.

Don’t send this attribute for prequalified jumpers in the Qualification phase.

N

T4

RankEqual

O

Y or N

It identifies if a rank has been equalled.

For Pit just include this attribute in case of equalled ranks with value "Y".

N

T4

Result

O

N(4).N(1)

9990.0

Result points for the particular event unit

 

Send just in the case @ResultType requests for this (see codes section)

N

T4

IRM

O

CC @IRM

IRM for the particular event unit

 

Send according @ResultType casuistic (see codes section)

N

T4

QualificationMark

O

CC @QualificationMark

Send just in the case when the jumper qualifies, according to the codes

N

T4

SortOrder

M

Numeric

This attribute is a sequential number with the order of the results for the particular event unit, if they were to be presented. It is mostly based on the rank, but it should be used to sort out rank ties as well as results without rank.

 

SortOrder should also take care of IRM rules (please, refer to CC @IRM)

 

(further order detail: Competition, Quali by Points for this round only and Training and Trial by start order)

 

Also for Real Time,  any sort order change from the initial start list order for any competitor will be provided in this attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).

N

T4

ResultType

O

CC @ResultType

Result type

N

T4

 

Result /Competitor

Competitor related to the result of one event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Competitor’s ID

N

T4

Type

M

T,A

T for team

A for athlete

N

T4

Bib

O

N(3) 990

Team’s bib number, to be sent mandatory just in the case of team event units

N

T4

 

Result /Competitor /ExtendedResults /ExtendedResult

Type and extension Type

Code

Extension Code

Pos or extension Pos

Value or extension Value

Description

ER_SJ

SJ_GROUP

 

N(1)

9

N/A

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Number of group, one team member-.

It’s a sequential number from 1 to 4, between different members of the team.

For @Value:

Do not send anything

SJ_RANK

 

N(1)

9

For @Type:

Send proposed code (as type)

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Team’s rank in the group (used only in the team events except trial).

Not used in the case of IRM.

SJ_ERANK

 

S(1)

(Y)

For @Type:

Send proposed code (as type)

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

It identifies if the rank of the team’s member has been equalled, send “Y” in this case.

(used only in the team events except trial).

Not used in the case of IRM.

SJ_ORDER

 

N(2)

90

For @Type:

Send proposed code (as type)

For @Code:

Send proposed extension code

For @Pos:

Do not send anything

For @Value:

Result’s order at this Group result (based in the rank).

(used only in the team events except trial).

SJ_CURRENT

 

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send “Y” when this team is currently jumping, and “N” otherwise (if not and it has changed).

SJ_LAST_FINISHED

 

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send “Y” when the last results corresponds to this competitor of a group (finishes the jump), “N” otherwise.

SJ_NEXT

 

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send “Y” when this team is the next to jump, “N” otherwise.

 

For the table above, we have the following additional/summary information:

 

Type/Code/Extension Code

Description

Expected

RT Only

RT Trigger

ER_SJ/ SJ_GROUP

Team’s results at each group (per leg): rank, equalled rank and order achieved by the team’s members.

Always, just for Team event units (except Trial Round)

N

T4

ER_SJ/ SJ_GROUP/ SJ_RANK

Team’s results at each group (per leg): rank, equalled rank and order achieved by the team’s members.

Not used in the case of IRM.

Always, just for Team event units (except Trial Round)

N

T4

ER_SJ/ SJ_GROUP/ SJ_ERANK

Team’s results at each group (per leg): rank, equalled rank and order achieved by the team’s members.

Not used in the case of IRM.

Always, just for Team event units (except Trial Round)

N

T4

ER_SJ/ SJ_GROUP/ SJ_ORDER

Team’s results at each group (per leg): rank, equalled rank and order achieved by the team’s members.

Always, just for Team event units (except Trial Round)

N

T4

ER_SJ/ SJ_CURRENT

Indicates that this team is currently jumping.

Always, just for Team event units (except Trial Round)

Y

T5

ER_SJ/ SJ_LAST_FINISHED

Indicates that this team has just finished the jump.

Always, just for Team event units (except Trial Round)

Y

T5

ER_SJ/ SJ_NEXT

Indicates that this team (a team member) is the next to jump.

Always, just for Team event units (except Trial Round)

Y

T5

 

 

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID. Can belong to a team member or an individual athlete.

N

T4

Order

M

Numeric

Order attribute used to sort team members in a team (if Competitor @Type=”T”) or 1 if Competitor @Type=”A”.

N

T4

Bib

M

For team members:

N(3)-N(1) 990-9

 

Or

 

For individual athletes:

N(3) 990

Athlete’s bib number.

In case of a team member it will be constructed from team’s bib and the order within the team (e.g.: for team event:

“11-2” means team with bib 11 and this is the second jumper of the team).

N

T4

 

Result /Competitor /Composition /Athlete /ExtendedResults /ExtendedResult

Team member or individual athlete’s extended result.

Type

Code

Pos

Value

Description

ER_SJ

SJ_LENGTH

 

N(4).N(1)

9990.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send jump length in meters, with one decimal digit

SJ_LENGTH_POINTS

 

N(4).N(1)

9990.0

 

Or

 

-N(4).N(1)

-9990.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos

Do not send anything

For @Value:

Send points for length, with one decimal digit

SJ_SPEED

 

N(4).N(1)

9990.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Speed in km/h, with one decimal digit

SJ_JUMP_POINTS

 

N(4).N(1)

9990.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send points for jump, with one decimal digit

SJ_JUDGE

Numeric

N(2).N(1)

90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send judge number, from 1 to 5

For @Value:

Send points from the judge identified by @Pos, with one decimal digit.

SJ_JUDGE_CROSS

Numeric

S(1)

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Send judge number, from 1 to 5

For @Value:

Send Y or N for the crossed judge points from the judge identified by @Pos.

SJ_JUDGES

 

N(2).N(1)

90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send total points from judges, with one decimal digit

SJ_IND_IRM

 

CC @IRM

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Invalid result mark for an individual in a team event unit (team member)

SJ_RULE

 

Text

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Rule Number

SJ_RULE_TEXT

 

Text

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Rule text

SJ_GATE

 

S(6)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Start Gate position

SJ_RANK_SPEED

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Rank for the speed overall

SJ_RANK_DISTANCE

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Rank for the jump distance overall

SJ_RANK

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Overall rank of the athlete for the jump.

Used just in the team trial event.

SJ_ERANK

 

Y or N

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

It identifies if the rank has been equalled, send “Y” in this case.

Used just in the team trial event.

SJ_COMP_GATE

 

N(2).N(1)

90.0

 

Or

 

-N(2).N(1)

-90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Gate compensation points

Send empty when base gate.

Send 0.0 if no other value available.

SJ_TANG_WIND

 

N(1).N(2)

0.00

 

Or

 

-N(1).N(2)

-0.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Tangential wind speed.

 

Send 0.00 if no other value available.

SJ_COMP_WIND

 

N(2).N(1)

90.0

 

Or

 

-N(2).N(1)

-90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Wind compensation points.

 

Send 0.0 if no other value available.

SJ_COMP_TOTAL

 

N(2).N(1)

90.0

 

Or

 

-N(2).N(1)

-90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Total compensation points (Gate compensation points plus Wind compensation points).

 

Send 0.0 if no other value available.

SJ_CURRENT

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Send Y when this competitor is currently jumping and he didn't receive the total score, and N otherwise (if not and it has changed).

SJ_LAST_FINISHED

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send “Y” when this competitor is the last finished the jump, “N” otherwise.

SJ_NEXT

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send “Y” when this competitor is the next to jump, “N” otherwise.

SJ_IRF

 

S(1)

(Y,N)

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send “Y” when the athlete is in ‘Inrun fall’. Else send ‘N’

SJ_IDX_ORDER

 

Numeric

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Do not send anything

For @Value:

Send the display order of the athlete in the team trial event.

 

Any idx order change from the initial start list order for any competitor will be provided in this attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).

 

Used just in the team trial event.

SJ_JUMP_FINISHED

 

S(1) (Y,N)

For @Type: Send proposed type

 

For @Code: Send proposed code

 

For @ Pos: Do not send anything

 

For @Value: Send “Y” when this competitor is the last receiving his distance result, “N” when the final result is received or otherwise.

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

RT Only

RT Trigger

ER_SJ/ SJ_LENGTH

Jump length in meters

Always

N

T3

ER_SJ/ SJ_LENGTH_POINTS

Points for length

Always

N

T4

ER_SJ/ SJ_SPEED

Speed in km/h

Always

N

T2

ER_SJ/ SJ_JUMP_POINTS

Points for jump

Always, except for Training and Trial (individual) and except for prequalified jumpers in the Qualification Phase

N

T4

ER_SJ/ SJ_JUDGE

Points for a particular judge

Just in competition round (first round and final round) and qualification (except for prequalified jumpers)

N

T4

ER_SJ/ SJ_JUDGE_CROSS

Status indicating if the points for a particular judge are crossed or not.

Just in competition round (first round and final round) and qualification (except for prequalified jumpers)

N

T4

ER_SJ/ SJ_JUDGES

Total points from judges

Just in competition round (first round and final round) and qualification (except for prequalified jumpers)

N

T4

ER_SJ/ SJ_IND_IRM

Invalid result mark for a team member.

Just in case of team event unit, if not team-trial

N

T4

ER_SJ/ SJ_RULE

Rule Text of Disqualification

Just in case of Disqualification

N

When available

ER_SJ/ SJ_RULE_TEXT

Rule Number of Disqualification

Just in case of Disqualification

N

When available

ER_SJ/ SJ_GATE

Start Gate position

Always

N

T1

ER_SJ/ SJ_RANK_SPEED

Rank for the speed overall

Always in the Training and Trial events

N

T4

ER_SJ/ SJ_RANK_DISTANCE

Rank for the jump distance overall

Always in the Training and Trial events

N

T4

ER_SJ/ SJ_RANK

Overall rank of the athlete for the jump in the team trial event.

Always in the Training and Trial events

N

T4

ER_SJ/ SJ_ERANK

Equalled rank

Always in the Training and Trial events

N

T4

ER_SJ/ SJ_COMP_GATE

Gate compensation points.

Send empty when base gate.

Is 0.0 when no other value available.

Always

N

T4

ER_SJ/ SJ_TANG_WIND

Tangential wind speed

 

Is 0.00 when no other value available.

Always

N

When available

ER_SJ/ SJ_COMP_WIND

Wind compensation points

 

Is 0.0 when no other value available.

Always

N

T4

ER_SJ/ SJ_COMP_TOTAL

Total compensation points (gate plus wind).

 

Is 0.0 when no other value available.

Always

N

T4

ER_SJ/ SJ_CURRENT

Indicates that this competitor is currently jumping and he didn't receive the total score .

Always

Y

T4

ER_SJ/ SJ_LAST_FINISHED

Indicates that this competitor has just finished the jump.

Always

Y

T4

ER_SJ/ SJ_NEXT

Indicates that this competitor is the next to jump.

Always

Y

T4

ER_SJ/ SJ_IRF

Indicates that this competitor is in ‘Inrun fall’

Always

N

When available

ER_SJ/ SJ_IDX_ORDER

Send the display order of the athlete in the team trial event.

 

Any idx_order changed from the initial start list order for any competitor, will be provided in this attribute regardless the competitor is ranked or not (this includes ranked, none-ranked and IRM athletes/team).

Always in the Team Trial event.

Y

T4

ER_SJ/ SJ_JUMP_FINISHED

Send “Y” when this competitor is the last receiving his distance result, “N” when the final result is received or otherwise.

Always

Y

T3

 

 

 

 

3.2.4.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.5     Cumulative Results

3.2.5.1  Description

The Cumulative Results is a message containing the cumulative results for the list of competitors in one phase, up to the end of this phase (including information regarding to previous phases), or up to the end of an event unit within a phase (including also the units prior the current one) either competing as single athletes or as aggregated athletes according to the team definition.

 

The difference between the Phase Results message (DT_PHASE_RESULTS) and the Cumulative Results (DT_CUMULATIVE_RESULT) is that the first one includes only the results for the phase independently from previous phases, while the Cumulative Results takes into account the results of previous phases, and therefore it gives an idea about how a competition is progressing up to the end of an intermediate phase.

 

The Cumulative Results message may be used to send an interim summary of results (including rank) part way through a phase. In this case, the DocumentSubtype is used to specify the last phase or event unit that contributed results to the message.

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports, although each ODF Sport Data Dictionary will have to explain with further detail the optional attributes or optional elements of the message.

 

 

3.2.5.2  Header Values

3.2.5.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEE000

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

DocumentType

DT_CUMULATIVE_RESULT

Cumulative Results message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or unofficial.

“OFFICIAL” /

“UNOFFICIAL”

DocumentSubtype

DDGEEEPUU

Cumulative results up to the end of the referenced event unit.

 

However, it only applies to event units of phase 1 of competition excepting the trial round (neither to be sent for qualification phases).

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

3.2.5.2.2  RT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEE000

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

DocumentType

DT_RT_CUMULATIVE_RESULT

Cumulative Real Time Results message

DocumentSubtype

CC @Phase

or

CC @Unit

It is the RSC code up to the moment the cumulative message contains information:

 

E.g.: DDGEEEPUU would be cumulative results up to the end of the referenced event unit

E.g.: DDGEEEP00 would be cumulative results up to the end of the referenced phase

ResultStatus

CC @ResultStatus

It indicates whether the result is live update or live full (or live Mandatory, Live Last).

“LIVE_UPDATE” /

“LIVE_FULL” /

“LIVE_MANDATORY” /

“LIVE_LAST”

 

For Real Time, live update (for the normal operative), or live full for the resynchronization messages, as explained in chapter 6.1 and ResultStatus codes as seen in chapter 3, live Mandatory when there is a correction of previous messages and Live Last for the last message of this key of messages.

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

RTSerial

Numeric

Incremental and unique sequence number for ODF-RT messages.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.5.3  Trigger and Frequency

3.2.5.3.1  PiT Triggers

The general rule is that this message is sent as soon as:

 

 If results are accumulating accross phases (i.e. the message is sent at event level and the Document Subtype of the message is DDGEEEP00):

 

It is sent after the last event unit for the first phase, in addition to subsequent phases. The message becomes unofficial just at the end of the event unit, and afterwards when the message becomes official (when the last event unit becomes official).

 

 If results are accumulated across event units (i.e. the message is sent at phase level and the Document Subtype of the message is DDGEEEPUU):

 

It is sent after the first event unit, in addition to subsequent event units; (in this case, the first DT_CUMULATIVE_RESULT message and the DT_RESULT message may contain the same information).The message becomes unofficial just at the end of the event unit, and afterwards when the message becomes official (when the last event unit becomes official).

 

The sequence is clarified below. The version number, n, is the version of the last DT_RESULT message sent for the same RSC code (n=0 if no DT_RESULT messages have been sent). The version number, m, is the version of the last DT_CUMULATIVE_RESULT message sent for the same RSC code (m=0 if no DT_CUMULATIVE_RESULT messages have been sent).

 

The clarification of this sequence can be:

Case 1:

a) Event has been complete and the results are unofficials:

1. Sent DT_RESULT with ODF Version n+1 and ResultStatus =” UNOFFICIAL”.

 

2. Sent DT_CUMULATIVE_RESULT with ODF Version m+1 and ResultStatus =” UNOFFICIAL”.

 

b) Results are checked and signed off by referee:

1. Sent DT_RESULT with ODF Version n+2 and ResultStatus =” OFFICIAL”.

 

2. Sent DT_CUMULATIVE_RESULT with ODF Version m+2 and ResultStatus =” OFFICIAL”.

 

Case 2:

a) Event has been complete and the results are directly officials:

1. Sent DT_RESULT with ODF Version n+1 and ResultStatus =” OFFICIAL”.

 

2. Sent DT_CUMULATIVE_RESULT with ODF Version m+1 and ResultStatus =” OFFICIAL”.

 

Trigger also after any major change.

 

However, if there is any kind of sport specific rule, it may be overridden in each of the ODF Sport Data Dictionaries: example to send interim results, partial results, etc.

 

 

3.2.5.3.2  RT Triggers

•  For ResultStatus=LIVE_UPDATE:

 

o  T4: Trigger when the results are known (after the competitor completes his jump)

 

•  For ResultStatus=LIVE_FULL:

 

Send as it will be defined for each RT transmission in the parameters of the DT_RT_GM message.

 

•  For ResultStatus=LIVE_MANDATORY

It is sending when a correction in the previous messages has been done.

 

•  For ResultStatus=LIVE_LAST

Send as the last message (that indicates that no new messages are expected for the given ODF unique key, unless something unexpected, that needs correction of previous messages data, happens while the transmission is still open (Good night message has not been sent)).

 

•  For ResultStatus=LIVE_LAST

Send as the last message (that indicates that no new messages are expected for the given ODF unique key, unless something unexpected, that needs correction of previous messages data, happens while the transmission is still open (Good night message has not been sent)).

 

 


3.2.5.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

Rank

 

 

 

 

 

RankEqual

 

 

 

 

 

ResultType

 

 

 

 

 

Result

 

 

 

 

 

IRM

 

 

 

 

 

QualificationMark

 

 

 

 

 

SortOrder

 

 

 

 

 

ResultItems

 

 

 

 

 

 

ResultItem (1,N)

 

 

 

 

 

 

Phase

 

 

 

 

 

Unit

 

 

 

 

 

Result

 

 

 

 

 

 

Rank

 

 

 

 

 

RankEqual

 

 

 

 

 

ResultType

 

 

 

 

 

Result

 

 

 

 

 

IRM

 

 

 

 

 

QualificationMark

 

 

 

 

 

SortOrder

 

 

Competitor

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Bib

 

 

 

 

 

Composition

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 

 

 

 

 

Bib

 


3.2.5.5  Message Values

Competition

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

CC @Competition

Unique ID for competition

N

When available

 

Result

For any cumulative results message, there should be at least one competitor being awarded a cumulative result after one event unit or phase.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

Cumulative rank of the competitor after the finalisation of the current event unit, so it takes into account the previous event units.

 

This attribute is optional because the skier may have got an invalid rank mark

N

T4

RankEqual

O

Y or N

It identifies if a rank has been equalled.

In PiT message only Y value has sense.

N

T4

ResultType

O

CC @ResultType

Result type, either points or IRM for the corresponding cumulative results

N

T4

Result

O

N(4).N(1)

9990.0

Result points after the finalisation of the current event unit. Points with one decimal digit.

 

Send just in the case @ResultType is points (see codes section)

N

T4

IRM

O

CC @IRM

IRM after the finalisation of the current event unit. It will depend on the results of all the event units up to the moment of the message sending.

 

Send just in the case @ResultType is IRM (see codes section)

N

T4

QualificationMark

O

CC @QualificationMark

Send just in the case the jumper qualified, according to the codes

N

T4

SortOrder

M

Numeric

This attribute is a sequential number with the order of the results after the finalisation of the current event unit (within the particular phase), if they were to be presented. It is mostly based on the rank, but it could be used to sort out rank ties as well as results without rank.

 

SortOrder should also take care of IRM rules (please, refer to CC @IRM)

N

T4

 

Result /ResultItems /ResultItem

Identifier of either phase or unit, for the schedule item to which it is going to be included the result summary. ResultItem /Result will be for either one particular previous phase -identified by @Phase- or unit (if @Unit is also informed or just phase otherwise.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Phase

M

CC @Phase

Phase code of the latest RSC schedule item (either phase or unit) to which the cumulative results is updated to.

N

T4

Unit

O

CC @Unit

Unit code of the latest RSC schedule item to which the cumulative results is updated to.

N

T4

 

Result /ResultItems /ResultItem /Result

For any Event Unit Results message, there should be at least one competitor being awarded a result for the event unit.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Rank

O

Numeric

Rank of the competitor in the result for the event unit identified by /ResultsItems /ResultItem.

 

This attribute is optional because the competitor could get an invalid rank mark (in this case, it will be blank).

N

T4

RankEqual

O

Y or N

It identifies if a rank has been equalled.

In PiT message only Y value has sense.

N

T4

ResultType

M

CC @ResultType

Type of the @Result attribute for the event unit identified by /ResultsItems /ResultItem

N

T4

Result

O

N(4).N(1)

9990.0

The result of the competitor for the event unit identified by /ResultsItems /ResultItem

N

T4

IRM

O

CC @IRM

The invalid rank mark, in case it is assigned for the event unit or phase identified by /ResultItems /ResultItem

N

T4

QualificationMark

O

CC @QualificationMark

The code which gives an indication on the qualification of the competitor for the next round of the competition for the event unit or phase identified by /ResultsItems /ResultItem

N

T4

SortOrder

M

Numeric

Used to sort all results in an event unit or phase identified by /ResultItems /ResultItem

N

T4

 

Result /Competitor

Competitor related to one cumulative result.

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Competitor’s ID

N

T4

Type

M

T,A

T for team

A for athlete

N

T4

Bib

O

N(3) 990

Team’s bib number, to be sent mandatory just in the case of team event units

N

T4

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

RT Only

RT Trigger

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to either a team member or a single athlete

N

T4

Order

M

Numeric

Order attribute used to sort team members in a team (if Competitor @Type=”T”) or 1 if Competitor @Type=”A”.

N

T4

Bib

M

For team members:

N(3)-N(1) 990-9

 

Or

 

For individual athletes:

N(3) 990

Athlete’s bib number.

In case of a team member it will be constructed from team’s bib and the order within the team (e.g.: for team event:

“11-2” means team with bib 11 and this is the second jumper of the team).

N

T4

 

 

3.2.5.6  Message Sort

The message sorting order is the same as that explained in the Event Unit / Phase Results messages.


 

 

3.2.6     Event Final Ranking

3.2.6.1  Description

The event final ranking is a message containing the final results and ranking at the completion of one particular event, either for individual athletes or for aggregated athletes.

 

The final ranking message is a generic message for all sports, including the full event final result for all competitors who were either ranked, got an Invalid Rank Mark (disqualified, etc.), or both.

 

The mandatory attributes and mandatory elements defined in this message will have to be used by all the sports, although each ODF Sport Data Dictionary will have to explain with further detail the optional attributes or optional elements of the message.

 

Depending on the sport rules include all competitors in the competition as all can be ranked (as in Marathon) or only include those with a final ranking as other are unranked (as in tennis).

 

 

3.2.6.2  Header Values

3.2.6.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEE000

The DocumentCode attribute in the ODF header will be sent according for all the competition events to the ODF Common Codes document (header values sheet).

DocumentType

DT_RANKING

Event Final ranking message

ResultStatus

CC @ResultStatus

Result status

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

 

3.2.6.3  Trigger and Frequency

3.2.6.3.1  PiT Triggers

The general rule is that this message is sent just at the end of the last event unit of one particular event.

 

Trigger also after any major change.

 

 


3.2.6.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Result (1,N)

 

 

 

 

 

 

Rank

 

 

 

 

 

RankEqual

 

 

 

 

 

ResultType

 

 

 

 

 

Result

 

 

 

 

 

IRM

 

 

 

 

 

SortOrder

 

 

 

 

 

Competitor

 

 

 

 

 

 

Code

 

 

 

 

 

Type

 

 

 

 

 

Composition

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 


3.2.6.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Result

For any event final ranking message, there should be at least one competitor being awarded a result for the event.

Attribute

M/O

Value

Comments

Rank

O

Numeric

Final rank of the competitor in the corresponding event. This attribute is optional because the skier may have got an invalid rank mark.

RankEqual

O

Y

It identifies if a rank has been equalled.

ResultType

M

CC @ResultType

Result type, either points or IRM for the corresponding event.

Result

O

N(4).N(1)

9990.0

Final result points for the particular event. Points should have one decimal digit.

 

Send just in the case @ResultType is points or IRM (see codes section)

IRM

O

CC @IRM

IRM for the particular event.

 

Send just in the case @ResultType is IRM (see codes section)

SortOrder

M

Numeric

This attribute is a sequential number with the order of the results for the particular event, if they were to be presented. It is mostly based on the rank, but it could be used to sort out rank ties as well as results without rank.

 

SortOrder should also take care of IRM rules (please, refer to CC @IRM)

 

Result /Competitor

Competitor related to one final event result.

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Competitor’s ID

Type

M

T,A

T for team

A for athlete

 

Result /Competitor /Composition /Athlete

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding to an individual athlete or a team member.

 

Team members should be participating in the event.

Order

M

Numeric

Order attribute used to sort team members in a team (if Competitor @Type=”T”) or 1 if Competitor @Type=”A”.

 

 

3.2.6.6  Message Sort

Sort by Result @SortOrder


 

 

3.2.7     Event’s Medallists

3.2.7.1  Description

The “Event’s Medallists” is a message containing the list of medallists awarded in one particular event.

 

 

3.2.7.2  Header Values

3.2.7.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEE000

DD according to CC @Discipline

G according to CC @DisciplineGender

EEE according to CC @Event

DocumentType

DT_MEDALLISTS

Event’s Medallists message

ResultStatus

CC @ResultStatus

It indicates whether the result is official or partial.

“OFFICIAL” /

“PARTIAL”

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.7.3  Trigger and Frequency

3.2.7.3.1  PiT Triggers

The message is sent with ResultStatus=PARTIAL when the information of the medallist is know but the final event Unit is not yet finished.

 

The message is sent with ResultStatus=OFFICIAL when the medallists are official known.

 

For some sports, bronze medals are known before the end of the final event unit. In this case the message is sent the first time with the bronze medallists, and the second time with all the medallists.

 

Trigger also after any major change.

 

 


3.2.7.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Level 6

Competition

 

 

 

 

 

 

Code

 

 

 

 

 

Medal (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Phase

 

 

 

 

 

Unit

 

 

 

 

 

Competitor

 

 

 

 

 

 

Type

 

 

 

 

 

Code

 

 

 

 

 

Order

 

 

 

 

 

Composition

 

 

 

 

 

 

Athlete (1,N)

 

 

 

 

 

 

Code

 

 

 

 

 

Order

 


3.2.7.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Medal

Attribute

M/O

Value

Comments

Code

M

CC @MedalType

Medal type.

 

All the Competitors with the same CC@MedalType are not grouped in the same element.

Phase

M

CC @Phase

Phase code in which a medal was awarded.

 

It is used in case of disciplines like Ice Hockey or Basketball, with the bronze medal and the gold medal awarded in different event units.

Unit

M

CC @Unit

Unit code in which a medal was awarded.

 

It is used in case of disciplines like Ice Hockey or Basketball, with the bronze medal and the gold medal awarded in different event units.

 

Medal /Competitor

Attribute

M/O

Value

Comments

Type

M

T, A

T for team

A for athlete

Code

M

S(20) with no leading zeroes

Competitor’s ID

Order

M

Numeric

Competitor order (Send 1 by default). In the case of tie the order is defined for the sport rules.

 

Medal /Competitor /Composition /Athlete

(Include all members that won the medal according to sport rules if Competitor @Type=”T”)

Attribute

M/O

Value

Comments

Code

M

S(20) with no leading zeroes

Athlete’s ID, corresponding either to a team member or an individual athlete

Order

M

Numeric

Order of the team members in a team if Competitor @Type=”T”.

 

1 if Competitor @Type=”A”.

 

 

3.2.7.6  Message Sort

The message is sorted according to the medal type. Moreover, in case of tie the order is according to the Competitor@Order (given by the sport rule). Team members are sorted according to the Athlete@Order.


 

 

3.2.8     Discipline Configuration

3.2.8.1  Description

The Discipline Configuration is a message containing discipline general configuration.

 

Ideally the configuration for the discipline should be provided before competition. However it may be possible that the configuration for one particular event, phase or event unit is not known in advance. In that case send the unknown attributes blank (Value=“”).

 

 

3.2.8.2  Header Values

3.2.8.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DD0000000

DD according to CC @Discipline

DocumentType

DT_CONFIG

Discipline Configuration message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.8.3  Trigger and Frequency

3.2.8.3.1  PiT Triggers

The message is sent when:

•  When this information is available.

 

 


3.2.8.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition

 

 

 

 

 

Code

 

 

 

 

Configs

 

 

 

 

 

Config (1,N)

 

 

 

 

 

Gender

 

 

 

 

Event

 

 

 

 

Phase

 

 

 

 

Unit

 

 

 

 

ExtendedConfig (1,N)

 

 

 

 

 

Type

 

 

 

 

Code

 

 

 

 

Pos

 

 

 

 

Value

 


3.2.8.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Configs /Config

Attribute

M/O

Value

Comments

Gender

M

CC @DisciplineGender

Gender code of the RSC.

Event

M

CC @Event

Event code of the RSC.

Phase

O

CC @Phase

Phase code of the RSC.

There are the following phases:

(O) Official Training

(9) Qualification (for Individual events)

(1) Competition

 

It should be informed just in the case that the Information is by Phase or by Event Unit.

Unit

O

CC @Unit

Unit code of the RSC.

 

It should be informed just in the case that the information is by Event Unit.

 

Configs /Config /ExtendedConfig

Type

Code

Pos

Value

Description

EC_QUALIFICATION_RULE

SJ_RANK_QUALIFY_NEXT_ROUND

(Send by event unit)

Numeric

Numeric

For @Type:

Send proposed type

For @Code:

Send the proposed code for the qualification rule.

 

SJ_RANK_QUALIFY_NEXT_ROUND is the code that indicates the qualification for next round based on rank.

For @Pos:

Send 1 to indicate first rank included in the @Code rule

 

Send 2 to indicate last rank included in the @Code rule

For @Value:

Send the rank according to @Code rule and @Pos

SJ_PREQUALIFIED

(Send by phase)

 

Numeric

For @Type:

Send proposed type

For @Code:

Send the proposed code for the qualification rule.

 

SJ_PREQUALIFIED is the code that indicates the qualification for next round based on pre-qualification.

For @Pos:

Do not send anything

For @Value:

Send the number of pre-qualified jumpers

EC_SJ

(Send by event)

SJ_HILL_TYPE

 

CC @HillType

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Hill type (Normal Hill or Large Hill)

SJ_HILL_SIZE

 

N(3)

999

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Hill size in meters

SJ_K_POINT

 

N(3)

999

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

K-point in meters

SJ_METRE_VALUE

 

N(2).N(1)

90.0

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Metre value (Points per metre)

SJ_GATE_FACTOR

 

N(2).N(2)

90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Gate factor (Points per metre)

SJ_WIND_FACTOR

 

N(2).N(2)

90.00

For @Type:

Send proposed type

For @Code:

Send proposed code

For @Pos:

Do not send anything

For @Value:

Wind factor (Points per metre)

SJ_GATE_IR_LEN

Numeric

N(2).N(2) m

 

99.99 m

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Send from 1…n to identify each gate

For @Value:

In-run length of  the gate

SJ_GATE_NUMBER

Numeric

S(5)

-9H

For @Type:

Send proposed type

For @Code:

Send proposed code

For @ Pos:

Send from 1…n to identify each gate

For @Value:

The official number of the gate

 

For the table above, we have the following additional/summary information:

 

Type/Code

Description

Expected

EC_QUALIFICATION_RULE/ SJ_RANK_QUALIFY_NEXT_ROUND

(Send by event unit)

Qualification for next round based on rank

Send by event unit Qualification and first Round, always if the rule applies to the competition.

EC_QUALIFICATION_RULE/ SJ_PREQUALIFIED

(Send by phase)

Qualification for next round based on pre-qualification

Send by event unit Qualification and first Round, always if the rule applies to the competition.

EC_SJ

(Send by event)/ SJ_HILL_TYPE

Hill type

Always, send by event

EC_SJ

(Send by event)/ SJ_HILL_SIZE

Hill size in metres

Always, send by event

EC_SJ

(Send by event)/ SJ_K_POINT

K-point in metres

Always, send by event

EC_SJ

(Send by event)/ SJ_METRE_VALUE

Metre value (in Points per m)

Always, send by event

EC_SJ

(Send by event)/ SJ_GATE_FACTOR

Gate factor (in Points per m)

Always, send by event

EC_SJ

(Send by event)/ SJ_WIND_FACTOR

Wind factor (in Points per m)

Always, send by event

EC_SJ

(Send by event)/ SJ_GATE_IR_LEN

In-run length of  the gate

Always, send by event

EC_SJ

(Send by event)/ SJ_GATE_NUMBER

The official number of the gate

Always, send by event

 

 

 

 

3.2.8.6  Message Sort

There is no general message sorting rule.


 

 

3.2.9     Event Unit Weather Conditions

3.2.9.1  Description

The “Event Unit Weather Conditions” is a message containing the weather conditions in the Event Unit.

 

 

3.2.9.2  Header Values

3.2.9.2.1  PiT Header

The following table describes the ODF header attributes

 

Attribute

Value

Comment

DocumentCode

DDGEEEPUU

The DocumentCode attribute in the ODF header will be sent according to the ODF Common Codes document (header values sheet).

DocumentType

DT_WEATHER

Weather conditions in the match message

Version

1..V

Version number associated to the message’s content. Ascendant number

FeedFlag

“P”-Production

“T”-Test

Test message or production message.

Date

Date

Date when the message is generated, expressed in the local time zone where the message was produced.

Time

MillisTime

Time up to milliseconds when the message is generated, expressed in the local time zone where the message was produced.

LogicalDate

Date

Logical Date of events that extends until next day.

If an event unit continues after midnight (24:00), all messages produced will be considered as happening at the logical date on which the event unit began (e.g. for a session which began at 21:00 on Aug 2 and ended at 1:20 on Aug 3, the output will be dated Aug 2).

 

The end of the logical day is defined by default at 03:00 a.m.

 

For messages corrections, like invalidating medals or Records, it will be the LogicalDate of the correction.

 

Logical Date is expressed in the local time zone where the message was produced

Venue

CC @VenueCode

Venue where the message is generated.

Serial

Numeric

Sequence number for ODF-PiT messages.

 

Serial starts with 1 each day session at every different venue.

 

In the case of RT transmission, this attribute contains the last PiT message Serial number in order to ensure that RT information is processed over the last PiT information

 

 

3.2.9.3  Trigger and Frequency

3.2.9.3.1  PiT Triggers

Once per unit and after every major change.

 

 


3.2.9.4  Message Structure

Following table defines the structure of the message.

Level 1

Level 2

Level 3

Level 4

Level 5

Competition

 

 

 

 

 

Code

 

 

 

 

Weather

 

 

 

 

 

Conditions (1,N)

 

 

 

 

 

Code

 

 

 

 

Humidity

 

 

 

 

Wind_Direction

 

 

 

 

Condition (0,3)

 

 

 

 

 

Code

 

 

 

 

Value

 

 

 

Temperature (0,N)

 

 

 

 

 

Code

 

 

 

 

Unit

 

 

 

 

Value

 

 

 

Wind (0,N)

 

 

 

 

 

Code

 

 

 

 

Unit

 

 

 

 

Value

 


3.2.9.5  Message Values

Competition

Attribute

M/O

Value

Comments

Code

M

CC @Competition

Unique ID for competition

 

Weather /Conditions

Attribute

M/O

Value

Comments

Code

M

CC @WeatherPoints

Weather Points

Humidity

M

N(3)

990

Humidity in %

Wind_Direction

M

CC @WindDirection

Wind direction

 

Weather /Conditions /Condition

Send two times in the case of Winter conditions.

Attribute

M/O

Value

Comments

Code

M

SKY, SNOW

Weather conditions type

Value

M

CC @SnowConditions

Or

CC @WeatherConditions

CC @WeatherConditions for SKY Conditions and as CC @SnowConditions for SNOW conditions

 

Weather /Conditions /Temperature

Send with two different @Code in the case of Winter conditions.

Attribute

M/O

Value

Comments

Code

M

AIR, SNOW

Air, Snow temperature

Unit

M

CC @TemperatureUnit

Celsius and Fahrenheit unit for temperature

Value

M

-N(3).N(1) -990.0 or N(3).N(1) 990.0

Temperature in Celsius and Fahrenheit degrees (in case of positive temperature, do not send '+')

 

Weather /Conditions /Wind

Attribute

M/O

Value

Comments

Code

M

SPEED

Wind  Speed

Unit

M

CC @SpeedUnit

Metric system unit for Wind

Value

M

N(3).N(1)

990.0

Wind speed in @Unit degrees.

 

According to the requirements, the Base Wind will be always 0.00

 

 

3.2.9.6  Message Sort

There is no special sort order requirement for this message. Usually, Conditions@code is the attribute used to sort the conditions.


 

 


 

4    Messages Sequence

1. Training, Trial and Qualification Rounds

Message

DocumentCode

DocumentSubType

ResultStatus

Comments

DT_START_LIST

DDGEEEPUU

N/A

N/A

Start List

DT_RESULT

DDGEEEPUU

N/A

LIVE_UPDAT

Real Time Results

DT_RESULT

DDGEEEPUU

N/A

UNOFFICIAL

Unofficial Results

DT_RESULT

DDGEEEPUU

N/A

LIVE_LAST

End of Real Time Results

DT_RESULT

DDGEEEPUU

N/A

OFFICIAL

Official Results

 

2. First Round and Final Rounds

Message

DocumentCode

DocumentSubType

ResultStatus

Comments

DT_START_LIST

DDGEEEPUU

N/A

N/A

Start List for First Round

DT_RESULT

DDGEEEPUU

N/A

LIVE_UPDAT

Real Time Results for First Round

DT_CUMULATIVE_RESULT

DDGEEE000

DDGEEEPUU

LIVE_UPDAT

Real Time Cumulative Results for First Round

DT_RESULT

DDGEEEPUU

N/A

UNOFFICIAL

Unofficial Results for First Round

DT_RESULT

DDGEEEPUU

N/A

LIVE_LAST

End of Real Time Results for First Round

DT_CUMULATIVE_RESULT

DDGEEE000

DDGEEEPUU

LIVE_LAST

End of Real Time Cumulative Results for First Round

DT_RESULT

DDGEEEPUU

N/A

OFFICIAL

Official Results for First Round

DT_START_LIST

DDGEEEPUU

N/A

N/A

Start List for Final Round

DT_RESULT

DDGEEEPUU

N/A

LIVE_UPDAT

Real Time Results for Final Round

DT_CUMULATIVE_RESULT

DDGEEE000

DDGEEEPUU

LIVE_UPDAT

Real Time Cumulative Results for Final Round

DT_RESULT

DDGEEEPUU

N/A

UNOFFICIAL

Unofficial Results for Final Round

DT_RESULT

DDGEEEPUU

N/A

LIVE_LAST