{
  "fetched_at": "2026-10-25T02:28:48Z",
  "source_url": "https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/data",
  "pages": [
    {
      "name": "rules",
      "content": "### Rules Updated September 21, 2022 - See Section A. COMPETITION-SPECIFIC RULES\n\n### One account per participant\n\nYou cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.\n\n### No private sharing outside teams\n\nPrivately sharing code or data, in particular Competition Data, outside of teams is not permitted. It is okay to share code if made available to all participants on the forums.\n\n### Team Mergers\n\nTeam mergers are allowed and can be performed by the team leader. In order to merge, the combined team must have a total submission count less than or equal to the maximum allowed as of the Team Merger Deadline. The maximum allowed is the number of submissions per day multiplied by the number of days the competition has been running.\n\n### Team Limits\n\nThe maximum team size is 5.\n\n### Submission Limits\n\nYou may submit a maximum of 5 entries per day.\n\nYou may select up to 2 final submissions for judging.\n\n### Competition Timeline\n\nCompetition Timeline dates (including Entry Deadline, Final Submission Deadline, Start Date, and Team Merger Deadline, as applicable) are reflected on the competition’s Overview > Timeline page.  Any submissions received after the Final Submission Deadline will not be considered.\n\n### COMPETITION-SPECIFIC TERMS\n\n**COMPETITION TITLE**: DFL - Bundesliga Data Shootout\n\n**COMPETITION SPONSOR**: DFL Deutsche Fußball Liga e.V. \n\n**COMPETITION SPONSOR ADDRESS**: Guiollettstrasse 44-46, 60325 Frankfurt am Main, Germany\n\n**COMPETITION WEBSITE**: https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout\n\n**TOTAL PRIZES AVAILABLE: $25,000**\n\nFirst Prize: $12,000\n\nSecond Prize: $8,000\n\nThird Prize: $5,000\n\n**WINNER LICENSE TYPE**: Non-Exclusive License\n\n**DATA ACCESS AND USE**: Competition-Use Only \n\nThe Competition is open to residents worldwide that have reached the age of maturity in their resident state, except that if you are a resident of Crimea, so-called Donetsk People's Republic (DNR) or Luhansk People's Republic (LNR), Cuba, Iran, Syria, North Korea, or are subject to U.S. export controls or sanctions, you may not enter the Competition. You also may not enter the Competition if you are one a sanction list or if you represent an entity which is on such a sanction list. Other local rules and regulations may apply to you, so please check your local laws to ensure that you are eligible to participate in skills-based competitions. The Competition Sponsor reserves the right to award alternative Prizes where needed to comply with local laws.\n\n**ENTRY IN THIS COMPETITION CONSTITUTES YOUR ACCEPTANCE OF THESE OFFICIAL COMPETITION RULES.**\n\nThe Competition named above is a skills-based competition to promote and further the field of data science. You must register via the Competition Website to enter. Your competition submissions (\"Submissions\") must conform to the requirements stated on the Competition Website. Your Submissions will be scored based on the evaluation metric described on the Competition Website. Subject to compliance with the Competition Rules, Prizes, if any, will be awarded to participants with the best scores, based on the merits of the data science models submitted. See below for the complete Competition Rules.\n\n### A. COMPETITION-SPECIFIC RULES\n\nIn addition to the provisions of the General Competition Rules below, you understand and agree to these Competition-Specific Rules required by the Competition Sponsor:\n\n#### **1. WINNER LICENSE.** \n\nNon-Exclusive \nUnder Section 11 (Winners Obligations) of the General Rules below, you hereby grant and will grant Competition Sponsor the following license(s) with respect to your Submission if you are a Competition winner:\n\nYou hereby grant and will grant to Competition Sponsor the non-exclusive rights, unlimited in terms of content and territory for the duration of the protective period applicable in the respective country of the worldwide contract territory, to use your Submission (including its source code and corresponding documentation) and to allow the rights to be used by the Competition Sponsor’s affiliates, as well as by third parties and in cooperation with third parties by further transferring the rights and granting other rights of use free of any consent, unless a restriction is agreed in the following paragraph. Competition Sponsor is especially authorized, without limitation, to exploit your Submission and allow your Submission to be exploited in every physical and non-physical form and in every non-commercial and commercial manner and to reproduce and process your Submission, to also combine your Submission with other programs and redesign your Submission and convert it to other programing languages and for other operating systems and to transfer your Submission in other forms of representation and modify, update and supplement it in any other manner and to distribute your Submission in unmodified and modified form, to publicly communicate your Submission on using landline and wireless means, to grant sublicenses as well as to transfer all rights of use granted under these Rules without further approval by or payment to you. The rights procured for Competition Sponsor also include technical processes, forms of appearance and use and relate in accordance with § 31a of the German Copyright Act [Urheberrechtsgesetz, “UrhG”] and § 32c UrhG also to types of use which are not yet known at the time when you submitted your Submission.\n\nTo the extent that your Submission includes open source components (see Section 8.B and Section 8.C for further details regarding the use of open source components), the terms of the respective of the open source license applies. You must make that that the chosen open source license in no event limits commercial use of such source code containing or depending on such code. To the extent your Submission makes use of generally commercially available software not owned by you that you used to generate your submission, but that can be procured by the Competition Sponsor without undue expense, you do not grant the license in the preceding paragraph to that software.\n\nThe decision whether and how the Submission will be used will be made solely by Competition Sponsor.\n\n\n### B. GENERAL COMPETITION RULES\n#### **1.\tBINDING AGREEMENT.** \n\nTo enter the Competition, you must agree to these Official Competition Rules, which incorporate by reference the provisions and content of the Competition Website and any Specific Competition Rules above (collectively, the \"Rules\"). Please read these Rules carefully before entry to ensure you understand and agree. You further agree that submission of an entry in the Competition constitutes agreement to these Rules. You may not submit an entry to the Competition and are not eligible to receive the prizes associated with this Competition (“Prizes”) unless you agree to these Rules. These Rules form a binding legal agreement between you and the Competition Sponsor with respect to the Competition.\n\n#### **2.\tELIGIBILITY.** \n\nA. To be eligible to enter the Competition, you must be:\n\n\t(i) be a registered account holder at Kaggle.com; \n\n\t(ii) have reached the age of maturity in your resident state;  \n\n\t(iii) not a resident of Crimea, so-called Donetsk People's Republic (DNR) or Luhansk People's Republic (LNR), Cuba, Iran, Syria, or North Korea; and\n\n\t(iv) not be a person or representative of an entity who/which is on a sanction list.\n\n\nIf you are entering as a representative of a company, educational institution or other legal entity, and/or on behalf of your employer, these Rules are binding on you, individually, and the entity you represent or are an employee. If you are acting within the scope of your employment, as an employee, contractor, or agent of another party, you warrant that such party has full knowledge of your actions and has consented thereto, including your potential receipt of a Prize. You further warrant that your actions do not violate your employer's or entity's policies and procedures.   \n\nThe Competition Sponsor reserves the right to verify eligibility and to adjudicate on any dispute at any time. If you provide any fake or false information relating to the Competition concerning your identity, residency, contact details, ownership of right, or information required for entering the Competition, you may be immediately disqualified from the Competition.\n\nB. Unless otherwise stated in the Specific Competition Rules above or prohibited by internal policies of the Competition Entities, employees, interns, contractors, officers and directors of Competition Entities may enter and participate in the Competition, but are not eligible to win any Prizes. \"Competition Entities\" means the Competition Sponsor, Kaggle Inc., and their respective parent companies, subsidiaries and affiliates. If you are such a participant from a Competition Entity, you are subject to all applicable internal policies of your employer with respect to your participation.\n\n#### **3.\tSPONSOR AND HOSTING PLATFORM.** \n\nThe Competition is sponsored by Competition Sponsor named above. The Competition is hosted on behalf of Competition Sponsor by Kaggle Inc. (\"Kaggle\"). Kaggle is an independent contractor of Competition Sponsor, and is not a party to this or any agreement between you and Competition Sponsor. You understand that Kaggle has no responsibility with respect to selecting the potential Competition winner(s) or awarding any Prizes. Kaggle will perform certain administrative functions relating to hosting the Competition, and you agree to abide by the provisions relating to Kaggle under these Rules. As a Kaggle.com account holder and user of the Kaggle competition platform, remember you have accepted and are subject to the Kaggle Terms of Service at [www.kaggle.com/terms][2] in addition to these Rules.\n\n#### **4.\tCOMPETITION PERIOD.** \n\nFor the purposes of Prizes, the Competition will run from the Start Date and time to the Final Submission Deadline (such duration the “Competition Period”). The Competition Timeline is subject to change, and Competition Sponsor may introduce additional hurdle deadlines during the Competition Period. Any updated or additional deadlines will be publicized on the Competition Website. It is your responsibility to check the Competition Website regularly to stay informed of any deadline changes. *YOU ARE RESPONSIBLE FOR DETERMINING THE CORRESPONDING TIME ZONE IN YOUR LOCATION.* \n\n#### **5.\tCOMPETITION ENTRY.** \n\nNO PURCHASE OR PAYMENT OF ANY KIND IS NECESSARY TO ENTER OR WIN. To enter the Competition, you must register on the Competition Website prior to the Entry Deadline, and follow the instructions for developing and entering your Submission through the Competition Website. Your Submissions must be made in the manner and format, and in compliance with all other requirements, stated on the Competition Website (the \"Requirements\"). Submissions must be received before any Submission deadlines stated on the Competition Website. Submissions not received by the stated deadlines will not be eligible to receive a Prize.\n\nSubmissions may not use or incorporate information from hand labeling or human prediction of the validation dataset or test data records.\n\nIf the Competition is a multi-stage competition with temporally separate training and/or test data, one or more valid Submissions may be required during each Competition stage in the manner described on the Competition Website in order for the Submissions to be Prize eligible.\n\nSubmissions are void if they are in whole or part illegible, incomplete, damaged, altered, counterfeit, obtained through fraud, or late. Competition Sponsor reserves the right to disqualify any entrant who does not follow these Rules, including making a Submission that does not meet the Requirements. \n\n#### **6.\tINDIVIDUALS AND TEAMS.** \n\nA. *Individual Account*. You may make Submissions only under one, unique Kaggle.com account. You will be disqualified if you make Submissions through more than one Kaggle account, or attempt to falsify an account to act as your proxy. You may submit up to the maximum number of Submissions per day as specified on the Competition Website. \n\nB. *Teams*. Multiple individuals may collaborate as a team (a \"Team\"); however, you may join or form only one Team. Each Team member must be a single individual with a separate Kaggle account. You must register individually for the Competition before joining a Team. You must confirm your Team membership to make it official by responding to the Team notification message sent to your Kaggle account. Team membership may not exceed the Maximum Team Size stated on the Competition Website.\n\nC. *Team Merger*. Teams may request to merge via the Competition Website. Team mergers may be allowed provided that: (i) the combined Team does not exceed the Maximum Team Size; (ii) the number of Submissions made by the merging Teams does not exceed the number of Submissions permissible for one Team at the date of the merger request; (iii) the merger is completed before the earlier of: any merger deadline or the Competition deadline; and (iv) the proposed combined Team otherwise meets all the requirements of these Rules. \n\n#### **7.\tCOMPETITION DATA.** \n\n\"Competition Data\" means the data or datasets available from the Competition Website for the purpose of use in the Competition, including any prototype or executable code provided on the Competition Website. The Competition Data will contain private and public test sets. Which data belongs to which set will not be made available to participants. \n\nA. *Data Access and Use*. \nYou may access and use the Competition Data only for participating in the Competition and on Kaggle.com forums. The Competition Sponsor reserves the right to disqualify any participant who uses the Competition Data other than as permitted by the Competition Website and these Rules.\n\n*To avoid any further doubt, you are not eligible to use the Competition Data for further developments, publications or any purposes after the end of the Competition. You have to delete the Competition Data and all copies made thereof after the end of the Competition.*\n\n\nB. *Data Security*. You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\n\nC. *External Data*. You may use data other than the Competition Data (“External Data”) to develop and test your Submissions. However, you will ensure the External Data is publicly available and equally accessible to use by all participants of the Competition for purposes of the competition at no cost to the other participants. The ability to use External Data under this Section 7.C (External Data) does not limit your other obligations under these Rules, including but not limited to Section 11 (Winners Obligations). \n\n#### **8.\tSUBMISSION CODE REQUIREMENTS.**\n\nA. *Private Code Sharing*. Unless otherwise specifically permitted under the Competition Website or Competition Specific Rules above, during the Competition Period, you are not allowed to privately share source or executable code developed in connection with or based upon the Competition Data or other source or executable code relevant to the Competition (“Competition Code”). This prohibition includes sharing Competition Code between separate Teams, unless a Team merger occurs. Any such sharing of Competition Code is a breach of these Rules and may result in disqualification.\n\nB. *Public Code Sharing*. You are permitted to publicly share Competition Code, provided that such public sharing does not violate the intellectual property rights of any third party. If you do choose to share Competition Code or other such code, you are required to share it on Kaggle.com on the discussion forum or notebooks associated specifically with the Competition for the benefit of all competitors. By so sharing, you are deemed to have licensed the shared code under an Open Source Initiative-approved license without a copyleft effect (see www.opensource.org) that in no event limits commercial use of such Competition Code or model containing or depending on such Competition Code. I.e. you are not allowed to use open source licenses with strict or even week copyleft rules.\n\nC. *Use of Open Source*. Unless otherwise stated in the Specific Competition Rules above, if open source code is used in the model to generate the Submission, then you must only use open source code licensed under an Open Source Initiative-approved license without a copyleft effect (see www.opensource.org) that in no event limits commercial use of such code containing or depending on such code. I.e. you are not allowed to use open source licenses with strict or even weak copyleft rules.\n\n#### **9.\tDETERMINING WINNERS.** \n\nEach Submission will be scored and ranked by the evaluation metric stated on the Competition Website. During the Competition Period, the current ranking will be visible on the Competition Website's public leaderboard. The potential winner(s) are determined solely by the leaderboard ranking on the private leaderboard, subject to compliance with these Rules. The public leaderboard will be based on the public test set and the private leaderboard will be based on the private test set.\n\nIn the event of a tie, the Submission that was entered first to the Competition will be the winner. \n\nIn the event a potential winner is disqualified for any reason in accordance with these Rules, the Submission that received the next highest score rank will be chosen as the potential winner.\n\n#### **10.\tNOTIFICATION OF WINNERS & DISQUALIFICATION.**\n\nThe potential winner(s) will notified by email within two weeks after the Final Submission Deadline. \n \nIf a potential winner (i) does not respond to the notification attempt within one (1) week from the first notification attempt, (ii) does return all required Prize acceptance documents within two (2) weeks following notification of such required documents or (iii) notifies Competition Sponsor and/or Kaggle within one week after the Final Submission Deadline that he/she does not want to be nominated as a winner or does not want to receive a Prize, then, in each case (i), (ii) and (iii) such potential winner will not receive any Prize, and an alternate potential winner will be selected from among all eligible entries received based on the Competition’s judging criteria.\n \nIn case (i), (ii) and (iii) above the participant may be disqualified. However, in case (iii) above, if requested, such potential winner may provide code and documentation to verify the participant’s compliance with these Rules. If the potential winner provides satisfying code and documentation, the participant will not be disqualified pursuant to this paragraph.\n \nCompetition Sponsor reserves the right to disqualify any participant from the Competition if the Competition Sponsor reasonably believes that the participant has attempted to undermine the legitimate operation of the Competition by cheating, deception, or other unfair playing practices or abuses, threatens or harasses any other participants, Competition Sponsor or Kaggle.\n \nA disqualified participant may be removed from the Competition leaderboard, at Competition Sponsor and/or Kaggle's sole discretion. If a Participant is removed from the Competition Leaderboard, additional winning features associated with the Kaggle competition platform, for example Kaggle points or medals, may also not be awarded.\n \nThe final leaderboard list will be publicly displayed at Kaggle.com. Determinations of Competition Sponsor are final and binding.\n\n#### **11.\tWINNERS OBLIGATIONS.**\n\nAs a condition to being awarded a Prize, a Prize winner must fulfill the following obligations:\n\n(a) deliver to the Competition Sponsor the final model's software code as used to generate the winning Submission and associated documentation. The delivered software code should follow [these documentation guidelines][5], must be capable of generating the winning Submission, and contain a description of resources required to build and/or run the executable code successfully. To the extent that the final model’s software code includes generally commercially available software that is not owned by you, but that can be procured by the Competition Sponsor without undue expense, then instead of delivering the code for that software to the Competition Sponsor, you must identify that software, method for procuring it, and any parameters or other information necessary to replicate the winning Submission;\n\n(b) grant to the Competition Sponsor the license to the winning Submission stated in the Competition Specific Rules above, and represent that you have the unrestricted right to grant that license; \n\n(c) sign and return all Prize acceptance documents as may be required by Competition Sponsor or Kaggle, including without limitation: (i) eligibility certifications; (ii) licenses, releases and other agreements required under the Rules; and (iii) necessary tax forms.\n\n#### **12.\tPRIZES.** \n\nPrize(s) are as described on the Competition Website and are only available for winning during the time period described on the Competition Website. The odds of winning any Prize depends on the number of eligible Submissions received during the Competition Period and the skill of the participants. \n\nAll Prizes are subject to Competition Sponsor's review and verification of the participant’s eligibility and compliance with these Rules, and the compliance of the winning Submissions with the Submissions Requirements. In the event that the Submission demonstrates non-compliance with these Rules, Competition Sponsor may at its discretion take either of the following actions: (i) disqualify the Submission(s); or (ii) require the potential winner to remediate within one week after notice all issues identified in the Submission(s) (including, without limitation, the resolution of license conflicts, the fulfillment of all obligations required by software licenses, and the removal of any software that violates the software restrictions).\n\nA potential winner may decline to be nominated as a Competition winner in accordance with Section 10.\n\nPotential winners must return all required Prize acceptance documents within two (2) weeks following notification of such required documents, or such potential winner will be deemed to have forfeited the prize and another potential winner will be selected. Prize(s) will be awarded within approximately 30 days after receipt by Competition Sponsor or Kaggle of the required Prize acceptance documents. Transfer or assignment of a Prize is not allowed. A payout with physical items is also excluded. \n\nYou are not eligible to receive any Prize if you do not meet the Eligibility requirements in Section 2 above.\n\nIf a Team wins a monetary Prize, the Prize money will be allocated in even shares between the eligible Team members, unless the Team unanimously opts for a different Prize split and notifies Kaggle before Prizes are issued.\n\n#### **13.\tTAXES.** \n\nALL TAXES IMPOSED ON PRIZES ARE THE SOLE RESPONSIBILITY OF THE WINNERS. Payments to potential winners are subject to the express requirement that they submit all documentation requested by Competition Sponsor or Kaggle for compliance with applicable state, federal, local and foreign (including provincial) tax reporting and withholding requirements. Prizes will be net of any taxes that Competition Sponsor is required by law to withhold. If a potential winner fails to provide any required documentation or comply with applicable laws, the Prize may be forfeited and Competition Sponsor may select an alternative potential winner. Any winners who are U.S. residents will receive an IRS Form-1099 in the amount of their Prize.\n\nMoney prizes will be transferred to the respective winner to a bank account designated by the winner.  Upon transfer to the designated account, Competition Sponsor and Kaggle are released from the obligation to pay that prize. In the event that the information about the personal data or the bank account of the respective winner is incorrect or a transfer of the money prize does not occur due to other circumstances for which Competition Sponsor and/or Kaggle are not responsible, there are no claims against them.\n\n#### **14.\tGENERAL CONDITIONS.**  \n\nAll federal, state, provincial and local laws and regulations apply.   \n\n#### **15.\tPRIVACY.**\n\nIn return for your participation in the Competition, the Competition Entities will use your name to promote the current Competition and further similar competitions of Competition Sponsor. This may include visual and/or audiovisual recordings being produced by the Competition Sponsor and/or a third party named by Competition Sponsor. Such use is expressly limited in content to showing the respective winner in this capacity. The legal basis for processing is Art. 6 para. 1 b) of the European General Data Protection Regulation (“GDPR”).\n\nYou acknowledge and agree that Competition Sponsor and Kaggle may collect, store, share and otherwise use personally identifiable information provided by you during the Kaggle account registration process and the Competition, including but not limited to, name, mailing address, phone number, and email address (“Personal Information”). Kaggle acts as an independent controller with regard to its collection, storage, sharing, and other use of this Personal Information, and will use this Personal Information in accordance with its Privacy Policy <www.kaggle.com/privacy>, including for administering the Competition. As a Kaggle.com account holder, you have the right to request access to, review, rectification, portability or deletion of any personal data held by Kaggle about you by logging into your account and/or contacting Kaggle Support at <www.kaggle.com/contact>. The legal basis for processing is Art. 6 para. 1 b) GDPR.\n\nAs part of Competition Sponsor performing this contract between you and the Competition Sponsor, Kaggle will transfer your Personal Information to Competition Sponsor, which acts as an independent controller with regard to this Personal Information. The legal basis for processing is Art. 6 para. 1 b) GDPR. The further data protection provisions including the rights of the User and the contact details for the Competition Sponsor’s data protection officer can be found in the Competition Sponsor’s privacy statement <https://www.dfl.de/en/data-privacy/>.\n\nIn the event that it is necessary to redeem a prize, Competition Sponsor and/or Kaggle may also ask you for additional contact information (e.g. bank account information). In the event that a prize is redeemed through retailers or other providers, Competition Sponsor and/or Kaggle are entitled to share your data with the respective retailer or provider. The legal basis for processing is Art. 6 para. 1 b) GDPR.\n\nCompetition Sponsor and Kaggle will each observe all legal provisions on data protection and data safety. All data provided by you by participating in the Competition will be solely collected, processed and stored for the conduction of the Competition and deleted afterwards, unless it has been publicly published in accordance with these Rules, especially with this Section, or that Competition Sponsor and/or Kaggle are legally required to further store the respective information.\n\n\n#### **16.\tWARRANTY, INDEMNITY AND RELEASE.** \n\nYou warrant that your Submission is your own original work and, as such, you are the sole and exclusive owner and rights holder of the Submission, and you have the right to make the Submission and grant all required licenses.  You agree not to make any Submission that: (i) infringes any third party proprietary rights, intellectual property rights, industrial property rights, personal or moral rights or any other rights, including without limitation, copyright, trademark, patent, trade secret, privacy, publicity or confidentiality obligations, or defames any person; or (ii) otherwise violates any applicable law. You also confirm that you have not entered into any agreements with third parties which would adversely affect the right of use your Submission by Competition Sponsor and third parties which are permitted to such usage.\n\nTo the maximum extent permitted by law, you indemnify and agree to keep indemnified Competition Entities at all times from and against any liability, claims, demands, losses, damages, costs and expenses resulting from any of your acts, defaults or omissions and/or a breach of any warranty set forth herein. To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless the Competition Entities from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable costs for defending against claims) arising out of or accruing from: (a) your Submission or other material uploaded or otherwise provided by you that infringes any third party proprietary rights, intellectual property rights, industrial property rights, personal or moral rights or any other rights, including without limitation, copyright, trademark, patent, trade secret, privacy, publicity or confidentiality obligations, or defames any person; (b) any misrepresentation made by you in connection with the Competition; (c) any non-compliance by you with these Rules or any applicable law; (d) claims brought by persons or entities other than the parties to these Rules arising from or related to your involvement with the Competition; and (e) your acceptance, possession, misuse or use of any Prize, or your participation in the Competition and any Competition-related activity.\n\nYou hereby release Competition Entities from any liability associated with: (a) any malfunction or other problem with the Competition Website; (b) any error in the collection, processing, or retention of any Submission; or (c) any typographical or other error in the printing, offering or announcement of any Prize or winners.\n\n#### **17.\tINTERNET.** \n\nCompetition Entities are not responsible for any malfunction of the Competition Website or any late, lost, damaged, misdirected, incomplete, illegible, undeliverable, or destroyed Submissions or entry materials due to system errors, failed, incomplete or garbled computer or other telecommunication transmission malfunctions, hardware or software failures of any kind, lost or unavailable network connections, typographical or system/human errors and failures, technical malfunction(s) of any telephone network or lines, cable connections, satellite transmissions, servers or providers, or computer equipment, traffic congestion on the Internet or at the Competition Website, or any combination thereof, which may limit a participant’s ability to participate.\n\n#### **18.\tRIGHT TO CANCEL, MODIFY OR DISQUALIFY.**\n\nCompetition Sponsor reserves the right to interrupt or shut down the Competition at any time without stating reasons. Especially reasons involving technology and/or legal matters, as a result of which the Competition can no longer be properly conducted, can be the basis for the end of the Competition. \n\nCompetition Sponsor further reserves the right to disqualify any participant who tampers with the submission process or any other part of the Competition or Competition Website. Any attempt by a participant to deliberately damage any website, including the Competition Website, or undermine the legitimate operation of the Competition is a violation of criminal and civil laws. Should such an attempt be made, Competition Sponsor and Kaggle each reserves the right to seek damages from any such participant to the fullest extent of the applicable law.\n\n\n#### **19.\tNOT AN OFFER OR CONTRACT OF EMPLOYMENT.**\n\nUnder no circumstances will the entry of a Submission, the awarding of a Prize, or anything in these Rules be construed as an offer or contract of employment with Competition Sponsor or any of the Competition Entities. You acknowledge that you have submitted your Submission voluntarily and not in confidence or in trust. You acknowledge that no confidential, fiduciary, agency, employment or other similar relationship is created between you and Competition Sponsor or any of the Competition Entities by your acceptance of these Rules or your entry of your Submission.\n\n#### **20.\tGOVERNING LAW.** \n\nThese Rules are subject to the law of the Federal Republic of Germany. The application of the United Nations Convention on Contracts for the International Sale of Goods (CISG) is excluded.\n\nExclusive jurisdiction for all disputes under or in connection with the Competition is Frankfurt am Main, Germany. The parties consent to personal jurisdiction in those courts. \n\nIf any provision of these Rules is or becomes completely or partially legally invalid or unenforceable, this does not affect the remaining provisions of the Rules which will remain in full force and effect.\n\n\n\n  [1]: https://www.treasury.gov/resource-center/sanctions/Programs/Pages/Programs.aspx\n  [2]: http://www.kaggle.com/terms\n  [3]: http://www.opensource.org\n  [4]: http://www.opensource.org\n  [5]: https://www.kaggle.com/WinningModelDocumentationGuidelines\n  [6]: http://www.kaggle.com/privacy\n  [7]: http://www.kaggle.com/contact",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "### Goal of the Competition\n\n<img src=\"https://storage.googleapis.com/kaggle-media/competitions/DFL/220425_BL_Data_Shoot_Out.png\" style=\"float: right; width: 300px\">\n\nGoal! In this competition, you'll detect football (soccer) passes&mdash;including throw-ins and crosses&mdash;and challenges in original Bundesliga matches. You'll develop a computer vision model that can automatically classify these events in long video recordings.\n\nYour work will help scale the data collection process. Automatic event annotation could enable event data from currently unexplored competitions, like youth or semi-professional leagues or even training sessions.\n\n\n\n### Context\n\nWhat does it take to go pro in football (soccer)? From a young age, hopeful talents devote time, money, and training to the sport. Yet, while the next superstar is guaranteed to start off in youth or semi-professional leagues, these leagues often have the fewest resources to invest. This includes resources for the collection of event data which helps generate insights into the performance of the teams and players.\n\n\nCurrently, event data is mostly collected manually by human operators, who gather data in several steps and through numerous personnel involved. This manual process has room for innovation as in its current shape and form it involves a lot of resources and multiple iterations/quality checks. As a result, event data collection is usually reserved for professional competitions only.\n\nBased in Frankfurt, the [Deutsche Fußball Liga (DFL)](https://www.dfl.de/en/) manages Germany's professional football (soccer) leagues: [Bundesliga and Bundesliga 2](https://www.bundesliga.com/en/bundesliga). DFL partners with the operator of one of the largest sports databases in the world, [Sportec Solutions.](https://www.sportec-solutions.de/en/index.html) They're responsible for the leagues' sports data and sports technology activities. In addition, Sportec Solutions provides services to global sports entities and media companies.\n\n  \n\nAutomatic event detection could provide event data faster and with greater depth. Having access to a broader range of competitions, match conditions and data scouts would be able to ensure no talented player is overlooked.\n\n\n\n<br>\n> **This is a Code Competition. Refer to [Code Requirements](https://www.kaggle.com/c/dfl-bundesliga-data-shootout/overview/code-requirements) for details.**",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "Submissions are evaluated on the [average precision](https://scikit-learn.org/stable/modules/generated/sklearn.metrics.average_precision_score.html) of detected events, averaged over timestamp error thresholds, averaged over event classes.\n\nDetections are matched to ground-truth events by class-specific error tolerances, with ambiguities resolved in order of decreasing confidence. The timestamp error tolerances, in seconds, for each class are:\n- **Challenge**: `[ 0.30, 0.40, 0.50, 0.60, 0.70 ]`\n- **Play**: `[ 0.15, 0.20, 0.25, 0.30, 0.35 ]`\n- **Throw-In**: `[ 0.15, 0.20, 0.25, 0.30, 0.35 ]`\n\nYou may find a Python implementation of the metric in this notebook: [**Competition Metric - DFL Event Detection AP**](https://www.kaggle.com/code/ryanholbrook/competition-metric-dfl-event-detection-ap).\n\n## Detailed Description ##\n\nEvaluation proceeds in four steps:\n1. **Selection** - Predictions not within a video's scoring intervals are dropped.\n2. **Assignment** - Predicted events are matched with ground-truth events.\n3. **Scoring** - Each group of predictions is scored against its corresponding group of ground-truth events via Average Precision. \n4. **Reduction** - The multiple AP scores are averaged to produce a single overall score.\n\n### Selection ###\n\nWith each video there is a defined set of **scoring intervals** giving the intervals of time over which zero or more ground-truth events might be annotated in that video. A prediction is only evaluated if it falls within a scoring interval. These scoring intervals were chosen to improve the fairness of evaluation by, for instance, ignoring edge-cases or ambiguous events.\n\nFor reference, we provide the scoring intervals for the training data. The scoring intervals for the test data will not be available to your model during evaluation, however.\n\n### Assignment ###\n\nFor each set of predictions and ground-truths within the same `event x tolerance x video_id` group, we **match** each ground-truth to the highest-confidence unmatched prediction occurring within the allowed `tolerance`.\n\nSome ground-truths may not be matched to a prediction and some predictions may not be matched to a ground-truth. They will still be accounted for in the scoring, however.\n\n### Scoring ###\n\nCollecting the events within each `video_id`, we compute an **Average Precision** score for each `event x tolerance` group. The average precision score is the area under the precision-recall curve generated by decreasing confidence `score` thresholds over the predictions. In this calculation, matched predictions over the threshold are scored as TP and unmatched predictions as FP. Unmatched ground-truths are scored as FN.\n\n### Reduction ###\n\nThe final score is the average of the above AP scores, first averaged over `tolerance`, then over `event`.\n\n## Submission File ##\n\nFor each video indicated by `video_id`, predict each event occurring in that video by giving the `event` type and the `time` of occurrence (in seconds) as well as a confidence `score` for that event.\n\nThe file should contain a header and have the following format:\n\n```\nvideo_id,time,event,score\n13bfe65e_0,100.0,play,0.0\n13bfe65e_0,110.5,challenge,0.07\n13bfe65e_1,90.25,throwin,0.13\n13bfe65e_1,105.0,play,0.2\n40f283bc_0,100.0,challenge,0.27\n40f283bc_0,110.5,throwin,0.33\n...\n```\n\nOnly predictions occurring within a video's defined **scoring intervals** will be scored; the metric ignores any predictions occurring outside of these scoring intervals. You will not be given the scoring intervals for videos in the test set.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Timeline",
      "content": "#### This is a forecasting competition with an active training phase and a second period where models will be run against games played in the fall of 2022.\n\n### Training Timeline\n\n* **July 29, 2022** - Start Date.\n\n* **October 6, 2022** - Entry Deadline. You must accept the competition rules before this date in order to compete.\n\n* **October 6, 2022** - Team Merger Deadline. This is the last day participants may join or merge teams.\n\n* **October 13, 2022** - Final Submission Deadline.\n\nAll deadlines are at 11:59 PM UTC on the corresponding day unless otherwise noted. The competition organizers reserve the right to update the contest timeline if they deem it necessary.\n\n### Forecasting Timeline:\nStarting after the final submission deadline new games will be collected and annotated and will be run against notebooks selected at the end of the training phase. \n\n- December 20, 2022 - Competition End Date",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "## NOTE: DATA IS NO LONGER AVAILABLE FOR THIS COMPLETED COMPETITION. ##\n\nThe competition dataset comprises video recordings of nine football games divided into halves. You're challenged to detect three kinds of player events, both the time of occurrence and the type, within these videos. See the [**Event Descriptions**](https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/overview/event-descriptions) page for a full description of each event type.\n\nThis is a [**Code Competition**](https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/overview/code-requirements) that will run in [**two stages**](https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/overview/timeline). During the **training stage**, your submission will only be run against test data for the public leaderboard. The test data for the private leaderboard, however, will comprise games occuring after the training period closes, the **forecasting stage**.\n\n## Training Data ##\n- **train/** - Folder containing videos to be used as training data, comprising video recordings from eight games. Both halves are included for four of the games, while only one half is included for the other four games.\n- **test/** - Folder containing videos to be used as test data. The test data for the public leaderboard comprises video recordings from one full game and four half-games, the other half of each game being in the training set.\n- **clips/** - Short clips from ten additional games, provided without event annotations. You may wish to use these clips to help your model generalize to environments not represented in the training data.\n- **train.csv** - Event annotations for videos in the `train/` folder.\n  - `video_id` - Identifies which video the event occurred in.\n  - `event` - The type of event occurrence, one of `challenge`, `play`, or `throwin`. Also present are labels `start` and `end` indicating the **scoring intervals** of the video. See the [**Evaluation**](https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/overview/evaluation) page for information about scoring intervals. Scoring intervals are not provided for the test set videos.\n  - `event_attributes` - Additional descriptive attributes for the event.\n  - `time` - The time, in seconds, the event occurred within the video.\n\n## Example Test Data ##\n\nPlease note that this is a [**Code Competition**](https://www.kaggle.com/competitions/dfl-bundesliga-data-shootout/overview/code-requirements), which means you will submit a notebook that makes predictions against a **hidden test set**. The test set visible here is only an example to help you author submission code. When you submit your notebook for scoring, this example data will be replaced by the actual test data.\n\nNote in particular that the example test videos are only short clips (~30 sec.), while the true hidden test videos are full halves (~50 min.). The name and number of videos may also be different. To ensure your submission completes successfully, you should make your code robust to such variations. See our [**Code Competition Debugging**](https://www.kaggle.com/code-competition-debugging) page for tips.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Prizes",
      "content": "* 1st Place - $ 12,000\n* 2nd Place - $ 8,000\n* 3rd Place - $ 5,000",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Code Requirements",
      "content": "<img src=\"https://storage.googleapis.com/kaggle-media/competitions/general/Kerneler-white-desc2_transparent.png\" style=\"float: right; width: 70px; padding: 10px\">\n\n### This is a Code Competition\n\nSubmissions to this competition must be made through Notebooks. In order for the \"Submit\" button to be active after a commit, the following conditions must be met:\n\n- CPU Notebook <= 9 hours run-time\n- GPU Notebook <= 9 hours run-time\n- Internet access disabled\n- Freely & publicly available external data is allowed, including pre-trained models\n- Submission file must be named `submission.csv`\n\nPlease see the [Code Competition FAQ](https://www.kaggle.com/docs/competitions#notebooks-only-FAQ) for more information on how to submit. And review the [code debugging doc](https://www.kaggle.com/code-competition-debugging) if you are encountering submission errors.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Event Descriptions",
      "content": "### Plays ###\n\nA **Play** describes a player’s attempt to switch ball control to another member of his team. A play event may be executed as a **Pass** or as a **Cross**.\n\nWhether a play is a **Cross** depends upon the positions of the acting player and of the possible recipient. The player playing the cross must be located approx. inside one of the four **crossing zones**. The four zones are marked by the touchlines, the extended sides of the penalty area, the goal lines and the imaginary quarter-way lines, which would be drawn at a quarter of the length of the pitch parallel to the half-way line (see figure below). The possible cross recipient must be located approx. inside the penalty area. Furthermore, the distance of the ball played must be medium-length (from 10 to 30 meters) or long (more than 30 meters) and the height of the ball played must be high (played above knee height). In order to classify a ball played as a cross if the ball is blocked by an opposing player, it is not the actual height or distance travelled that is decisive, but the intended height or distance. \n\n[<img src=\"https://storage.googleapis.com/kaggle-media/competitions/DFL/crossing.png\" width=\"200\" />](https://storage.googleapis.com/kaggle-media/competitions/DFL/crossing.png)\n\n(Click the thumbnail above for a larger image.)\n\nThe second type of play is a **Pass**, defined to be any attempt to switch ball control to another team member that doesn’t satisfy cross definition.\n\nAdditionally, every Play action (both Pass and Cross) is executed in within a context, making it an **Open Play**, a **Corner Kick**, or a **Free Kick**.\n\nA **Corner Kick** refers to a situation where the Play is executed to restart the game after the ball went out of play over the goal line following the touch of the defending team player. The ball must be kicked from the closest field corner and be stationary on the ground when it’s kicked off.\n\nA **Free Kick** refers to a situation where the Play is executed to restart the game after the referee had stopped it due to an infringement of the rules. The ball must be kicked and be stationary on the ground when it's kicked off.\n\nAn **Open Play** refers to any Play that is executed in-play and not from a dead ball situation (like corner kick, free kick or any other set piece).\n\n### Throw-Ins ##\n\nA **Throw-In** refers to a situation where the game is restarted after the ball went out of play over the sideline following the touch of the opposite team. The ball must be thrown with hands, from behind and over the head of executing player.\n\n### Challenge ###\n\nA **Challenge** is a player action during which two players of opposing teams are physically capable of either gaining or receiving ball control and attempt to do so. A Challenge requires one of the two players to touch the ball or to foul the opposing player.\n\nA distinction is made between the following cases: \n- **Opponent rounded**: a player in ball control stays in ball control after the challenge, having left the opposing player behind him. Situations where the opponent is not able to gain possession (e.g. when the ball is “flicked” over the opponent) are also to be recorded as challenges.\n- **Ball action carried out**: applies when none of the players involved in the challenge are in ball control at the start of the challenge (e.g. aerial challenges, challenges for the first touch of the ball) and one player determines the direction of the ball at the end of the challenge.\n- **Fouled**: the referee called a foul. \n- **Opponent dispossessed**: a player not in ball control dispossesses the opposing player in ball control.\n- **Challenge during release of the ball**: applies when shots or balls played are forced or blocked during challenges. A challenge is only recorded, if the ball played or shot travels through the area that the defending player is attempting to cover from a tactical perspective. All other cases are not recorded as challenges.\n- **Possession retained during challenge**: applies when one of the players involved in the challenge has certain ball control at the start of the challenge and manages to retain it, despite the efforts to dispossess him of the opponent involved in the challenge. \n\n**Note: The definition of the challenge timestamp depends on its type.**",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}