What it does
It recreates F1 races in a 3D web experience. (show the F1 and race fans another way to review the race)
How we built it
We used 3D models from Blender, integrated Google Maps API, pulled race data with FastF1, and brought it all together using Three.js.
We started by collecting 3D track data from the Google Tiles API and imported it into Blender. There, we cleaned up the geometry, fixed vertex issues, and enhanced the overall quality.
In parallel, we used the FastF1 API to get race data and collected a 2D image of the track. That image was converted into a path and then mapped onto the 3D track inside Blender. We ran a Python script to extract that path as vertex data.
Once the 3D track and the path were ready, we exported them and brought everything into Three.js. Meanwhile, we processed and cleaned the race data, converted it into JSON format containing physics-related data (e.g. car positions, speeds, etc.).
Finally, we mapped this physics data to each racer and rendered their motion live inside the 3D track using Three.js.
Challenges we ran into
Google Maps API doesn't offer 3D data for every location.
Handling detailed 3D maps was performance-heavy and tricky.
What we learned
We improved our coding skills and gained more experience in working with APIs and 3D development.
Log in or sign up for Devpost to join the conversation.