Starting with the 2024 scouting data, we should load the data from the Blue Alliance API into the duckdb database inside the "pull_api_data" function.
The endpoint to use is "/match/{match_key}" (docs are here: https://www.thebluealliance.com/apidocs/v3), and the output table should somewhat match the table "tba_match_data" defined in data_structure.txt. Replace the columns named "metric_1", "metric_2", etc with the actual name of the metrics returned by the API. We may need to use other endpoints to get the list of matches first - use your judgement on how to do this.
Do not store the API key in plain text, it should be in an environment variable that is not checked into the repo.
It's okay to hard code which event we're pulling data from for now. In the future we can update the code to get the event key from a command line argument.
This could look like this: https://github.com/AGPapa/frclocks/blob/main/collect_data.py
Starting with the 2024 scouting data, we should load the data from the Blue Alliance API into the duckdb database inside the "pull_api_data" function.
The endpoint to use is "/match/{match_key}" (docs are here: https://www.thebluealliance.com/apidocs/v3), and the output table should somewhat match the table "tba_match_data" defined in data_structure.txt. Replace the columns named "metric_1", "metric_2", etc with the actual name of the metrics returned by the API. We may need to use other endpoints to get the list of matches first - use your judgement on how to do this.
Do not store the API key in plain text, it should be in an environment variable that is not checked into the repo.
It's okay to hard code which event we're pulling data from for now. In the future we can update the code to get the event key from a command line argument.
This could look like this: https://github.com/AGPapa/frclocks/blob/main/collect_data.py