{
  "id": 298160,
  "title": "Data Cleaning: Patches For PFF/Tracking Data Mismatches",
  "url": "/competitions/nfl-big-data-bowl-2022/discussion/298160",
  "author_name": "Vinesh Kannan",
  "post_date": "2022-01-01T08:28:30.863000",
  "votes": 2,
  "comment_count": 0,
  "views": 0,
  "content": "<p>I didn't see another post about this data quality issue, so I thought other teams might benefit from this, especially teams using the PFF special teams annotations.</p>\n<p>We found that the PFF data annotations (e.g. gunners, vises, tacklers, etc.) sometimes reference jersey numbers that do not match any players in the tracking data for the corresponding play. We looked at all the cases and found the correct jersey number from the tracking data.</p>\n<p>For example, in game <code>2020100400</code>, play <code>169</code>, vises are listed as CAR 25 and CAR 20, but there is no CAR 20 in the tracking data. It should be CAR 41, Eli Apple.</p>\n<p>There was also one game where two Bills players had the jersey number 44, where one of them should be number 40.</p>\n<p>The patches can be found in the last section of this notebook: <a href=\"https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches\" target=\"_blank\">https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches</a></p>\n<p>I included both the raw CSV data for the patches for everyone to use, as well as sample code to apply the patches for Python users.</p>\n<p>Thank you to the organizers, as the dataset is very high quality! Hopefully this small patch helps other teams.</p>",
  "messages": [
    {
      "id": 1634827,
      "postDate": "2022-01-01T08:28:30.863Z",
      "content": "<p>I didn't see another post about this data quality issue, so I thought other teams might benefit from this, especially teams using the PFF special teams annotations.</p>\n<p>We found that the PFF data annotations (e.g. gunners, vises, tacklers, etc.) sometimes reference jersey numbers that do not match any players in the tracking data for the corresponding play. We looked at all the cases and found the correct jersey number from the tracking data.</p>\n<p>For example, in game <code>2020100400</code>, play <code>169</code>, vises are listed as CAR 25 and CAR 20, but there is no CAR 20 in the tracking data. It should be CAR 41, Eli Apple.</p>\n<p>There was also one game where two Bills players had the jersey number 44, where one of them should be number 40.</p>\n<p>The patches can be found in the last section of this notebook: <a href=\"https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches\" target=\"_blank\">https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches</a></p>\n<p>I included both the raw CSV data for the patches for everyone to use, as well as sample code to apply the patches for Python users.</p>\n<p>Thank you to the organizers, as the dataset is very high quality! Hopefully this small patch helps other teams.</p>",
      "rawMarkdown": "I didn't see another post about this data quality issue, so I thought other teams might benefit from this, especially teams using the PFF special teams annotations.\n\nWe found that the PFF data annotations (e.g. gunners, vises, tacklers, etc.) sometimes reference jersey numbers that do not match any players in the tracking data for the corresponding play. We looked at all the cases and found the correct jersey number from the tracking data.\n\nFor example, in game `2020100400`, play `169`, vises are listed as CAR 25 and CAR 20, but there is no CAR 20 in the tracking data. It should be CAR 41, Eli Apple.\n\nThere was also one game where two Bills players had the jersey number 44, where one of them should be number 40.\n\nThe patches can be found in the last section of this notebook: https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches\n\nI included both the raw CSV data for the patches for everyone to use, as well as sample code to apply the patches for Python users.\n\nThank you to the organizers, as the dataset is very high quality! Hopefully this small patch helps other teams.",
      "votes": 2
    }
  ],
  "comments": [],
  "raw_markdown_by_id": {
    "1634827": "I didn't see another post about this data quality issue, so I thought other teams might benefit from this, especially teams using the PFF special teams annotations.\n\nWe found that the PFF data annotations (e.g. gunners, vises, tacklers, etc.) sometimes reference jersey numbers that do not match any players in the tracking data for the corresponding play. We looked at all the cases and found the correct jersey number from the tracking data.\n\nFor example, in game `2020100400`, play `169`, vises are listed as CAR 25 and CAR 20, but there is no CAR 20 in the tracking data. It should be CAR 41, Eli Apple.\n\nThere was also one game where two Bills players had the jersey number 44, where one of them should be number 40.\n\nThe patches can be found in the last section of this notebook: https://www.kaggle.com/vingkan/pff-tracking-data-player-mismatches\n\nI included both the raw CSV data for the patches for everyone to use, as well as sample code to apply the patches for Python users.\n\nThank you to the organizers, as the dataset is very high quality! Hopefully this small patch helps other teams."
  }
}