Published in

Snowflake

Apr 12

3 min read

Loading F1 Historical Data into Snowflake using the Ergast Developer API

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.

From .csv to Snowflake
From Kaggle to Snowflake

More from 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

Analytics Vidhya

Write a clean code: SonarQube

Urban Company – Engineering

Data Platform – Ingestion

Simple scorecard for evaluating software

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

About Help Terms Privacy

Loading F1 Historical Data into Snowflake using the Ergast Developer API

More from Snowflake

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

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

Daan Bakboord

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