You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this would be very helpful, i have no clue how hard this would be to add, if its possible im happy to enter in the data myself, but i would just really like this
The text was updated successfully, but these errors were encountered:
This is something we'd consider when we start creating new endpoints and move away from the ergast compatible endpoints (probably sometime in the next season). But theres no reason why we can't start working on data sources for this sooner.
Some notes on this, corner numbers can have additional letters appended. For example, Hungary has corner "1" and "1A" as well as "12" and "12A". This might be relevant for parsing data sources or for storing the numbers themselves, if we wanted to do such a thing.
Also, trying to count corners based on track curvature using telemetry data as input source does not work. People have tried this extensively. But there is no real consistency between what counts as a corner or what doesn't.
Therefore, we need some sort of official document that includes corner numbers as an input source. IMO, event notes are the best choice here, as pointed out by @harningle already.
this would be very helpful, i have no clue how hard this would be to add, if its possible im happy to enter in the data myself, but i would just really like this
The text was updated successfully, but these errors were encountered: