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
right now when querying https://api.jolpi.ca/ergast/f1/2024/races/, there are some countries' values which are populated inconsistently. For example Las Vegas GP is listed in the United States whereas the Austin GP is listed in the USA (neither of which respects the ISO country standard as far as I know). Silverstone and Yas Marina are another offenders. This leads to slightly more cumbersome data processing than it has to be.
Changing the country name itself could be a breaking change (I guess) so that's why I am proposing to use e.g. ISO 3166-1 alpha-2 country codes.
This is by no means a huge issue for me. It's just an idea to have the API a little bit tidier.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion, this is definitely something we'd be interested in doing in the future. Right now we're focused on data ingest for existing ergast compatible endpoints, but next year we hope to start implementing new endpoints / data such as this.
I'm very bored right now so i thought i would start on this, i think the script will work, lmk if there are any issues or @jolpica if you share the json that matches your current import schema, i can get to implementing that.
Hi,
right now when querying https://api.jolpi.ca/ergast/f1/2024/races/, there are some countries' values which are populated inconsistently. For example Las Vegas GP is listed in the United States whereas the Austin GP is listed in the USA (neither of which respects the ISO country standard as far as I know). Silverstone and Yas Marina are another offenders. This leads to slightly more cumbersome data processing than it has to be.
Changing the country name itself could be a breaking change (I guess) so that's why I am proposing to use e.g. ISO 3166-1 alpha-2 country codes.
This is by no means a huge issue for me. It's just an idea to have the API a little bit tidier.
The text was updated successfully, but these errors were encountered: