Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Current »

As STATSCORE, we distinguish several types of incidents that our Scouts use in the process of providing coverge for a given sport event. Each of these incidents is briefly described and included in the relevant table.

  1. Event incidents - their use directly influences the change in match statuses or triggers specific parts of the match. Match statuses are described in a separate section - “Statuses: American football”.

 Id

Incident name

Is important for trader

Affect on statuses

Affect on results

Affect on time

Affect on betstatus

601

1st quarter started

yes

set “1st quarter” status

Result = 0

Regular time = 0

First half = 0
First quarter = 0

no

bet_status = no change

602

2nd quarter started

yes

set “2nd quarter” status

Second quarter = 0

no

bet_status = no change

603

3rd quarter started

yes

set “3rd quarter” status

Second half = 0

Third quarter = 0

no

bet_status = no change

604

4th quarter started

yes

set “4th quarter” status

Fourth quarter = 0

no

bet_status = no change

605

Extratime 1 started

yes

set “Extratime 1” status

Extratime = 0

Extratime 1 = 0

no

bet_status = no change

606

Extratime 2 started

yes

set “Extratime 2” status

Extratime 2 = 0

no

bet_status = no change

607

Extratime 3 started

yes

set “Extratime 3” status

Extratime 3 = 0

no

bet_status = no change

608

Extratime 4 started

yes

set “Extratime 4” status

Extratime 4 = 0

no

bet_status = no change

609

Extratime 5 started

yes

set “Extratime 5” status

Extratime 5 = 0

no

bet_status = no change

610

End of quarter

yes

no

no

no

bet_status = no change

611

Break

yes

no

no

no

bet_status = no change

612

Break after 1st quarter

yes

set “Break after 1st quarter” status

no

clock_status = stopped

bet_status = no change

613

Break after 2nd quarter

yes

set “Break after 2nd quarter” status

no

clock_status = stopped

bet_status = no change

614

Break after 3rd quarter

yes

set “Break after 3rd quarter” status

no

clock_status = stopped

bet_status = no change

615

Break after 4th quarter

yes

set “Break after 4th quarter” status

no

clock_status = stopped

bet_status = no change

616

Break after extratime 1

yes

set “Break after extratime 1” status

no

clock_status = stopped

bet_status = no change

617

Break after extratime 2

yes

set “Break after extratime 2” status

no

clock_status = stopped

bet_status = no change

618

Break after extratime 3

yes

set “Break after extratime 3” status

no

clock_status = stopped

bet_status = no change

619

Break after extratime 4

yes

set “Break after extratime 4” status

no

clock_status = stopped

bet_status = no change

2055

First half started

yes

set “1st half” status

Result = 0

Regular time = 0

First half = 0

no

bet_status = no change

2056

Halftime

yes

set “Halftime” status

no

clock_status = stopped

bet_status = no change

2057

Second half started

yes

set “2nd half” status

Second half = 0

no

bet_status = no change

621

Cancelled

yes

set “Cancelled” status

no

clock_status = stopped

bet_status = no change

627

Postponed

yes

set “Postponed” status

no

clock_status = stopped

bet_status = no change

626

Interrupted

yes

set “Interrupted” status

no

clock_status = stopped

bet_status = no change

620

Abandoned

yes

set “Abandoned” status

no

clock_status = stopped

bet_status = no change

622

Finished after extratime

yes

set “Finished after extratime” status

no

clock_status = stopped

bet_status = inactive

623

Finished awarded win

yes

set “Finished awarded win” status

no

clock_status = stopped

bet_status = inactive

624

Finished regular time

yes

set “Finished regular time” status

no

clock_status = stopped

bet_status = inactive

  1. Team Incidents: Incidents whose use directly impacts on results and team/player statistics. Results and statistics are described in a separate sections - “Results: American football” and “Statistics: American football”

 Id

Incident name

Is important for trader

Participant

Add info possible values

(Attributes and properties)

Add info format

(attribute_IDs and properties vaules)

Note

631

Possesion

no

properties: yards

properties values: 0-100

635

Kickoff

no

2618

Touchback

no

652

Pass

no

Pass complete

attr. ID: 704

Pass incomplete

attr. ID: 703

properties: yards

properties values: -99 - 99

653

Rush

no

properties: yards

properties values: -99 - 99

650

Turnover

yes

661

Interception

yes

637

Touchdown

yes

Passing

attr. ID: 643

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

Rushing

attr. ID: 644

Interception return

attr. ID: 645

Fumble recovery

attr. ID: 646

Punt return

attr. ID: 647

Kickoff return

attr. ID: 648

2619

Possible 2-points conversion

yes

641

2-point conversion

yes

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

642

Failed 2-point conversion

yes

2620

Possible extra point

yes

646

Extra point

yes

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

2621

Extra point failed

yes

647

Possible field goal

yes

648

Field goal

yes

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

649

No field goal

yes

640

Safety

yes

Please note: This incident has a 'confirmation' parameter for which the possible values are: 'tbd, 'confirmed' and 'cancelled'. More details can be found in the 'User guide - Key incidents confirmation' section

654

Sack

no

Assisted

attr. ID: 649

655

Fumble

no

656

Fumble recovered

no

2623

Flag

yes

634

Penalty

yes

properties: yards

properties values: 0-100

659

Fair catch

no

639

Onside kick

no

651

Punt

no

properties: yards

properties values: -99 - 100

643

Challenge

yes

644

Challenge correct

yes

645

Challenge incorrect

yes

632

Timeout

yes

633

TV timeout

no

662

First down

yes

properties:

  • yards

    • value

    • base_yards_value

properties values: 0-100

663

Second down

yes

properties:

  • yards

    • value

    • base_yards_value

properties values: 0-100

664

Third down

yes

properties:

  • yards

    • value

    • base_yards_value

properties values: 0-100

665

Fourth down

yes

properties:

  • yards

    • value

    • base_yards_value

properties values: 0-100

657

Defensive return

no

Fumble

attr. ID: 660

Interception

attr. ID: 661

Kickoff

attr. ID: 662

Punt

attr. ID: 663

properties: yards

properties values: -99 - 99

  1. Informing incidents - incidents that can pertain to the entire match or a specific team but do not affect any statistics.

 Id

Incident name

Is important for trader

Participant

Add info possible values

(Attributes and properties)

Add info format

(attribute_IDs and properties vaules)

Note

628

Start delayed

yes

2763

Match about to start

yes

2613

In play

no

625

Injury

no

1001

Match resumed

yes

630

To finish

yes

  1. Incidents related to managing match markets - incidents where their use causes specific match markets to be closed or opened.

 Id

Incident name

Is important for trader

Participant

Add info possible values

(Attributes and properties)

Add info format

(attribute_IDs and properties vaules)

Note

1000

Betstart

yes

 

 

 

Betstart indicates that betting markets can be activated

1010

Betstop

yes

 

 

 

Betstop indicates that all betting markets are closed due to strong possibility of score change or others.

2622

Play under review

yes

1200

Technical problems

yes

Indicates technical issues during the providing of the coverage and automatically closes all match markets

  • No labels