Published in


Loading F1 Historical Data into Snowflake using the Ergast Developer API

Ergast Developer API Banner

Recently I blogged about loading F1 Historical Data into Snowflake. The first time I downloaded the related .csv-files from Kaggle. In a consecutive post I loaded the data directly using the Kaggle API.

  1. From .csv to Snowflake
  2. From Kaggle to Snowflake

Snowflake articles from engineers using Snowflake to power their data.

Recommended from Medium

Braintree hosted fields with Ruby on Rails

Best hands-on and highest-rated PySpark course: gain skillset with this interactive course

The Mineral Extractor Guide Planet Crafter

Write a clean code: SonarQube

Data Platform – Ingestion

Simple scorecard for evaluating software

Image of sample RFP scorecard

Simple Azure Marketplace Virtual Machine Offer: creating VM images and publishing in Partner Center

Working with Oanda’s API, Part 2 — HTTP request and storing data in MongoDB with Golang

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Daan Bakboord

Daan Bakboord

Cloud ☁️ Data & Analytics 📊 Engineer @ DaAnalytics | Manager Data & Analytics @ Pong | Snowflake ❄️ Data Superhero | Modern Cloud ☁️ Data Stack enthusiast

More from Medium

Difference between execute as a CALLER and OWNER in Snowflake procedure:

Automating Data Loading from a Cloud Data Lake into Snowflake

Data Mesh & Snowflake = Peanut butter & Jelly

Snowflake’s Snowpark Day with Hashmap, an NTT DATA Company