## Motivation - The provided example data is in Google Sheets that are not the most intuitive to interpret (Example data folder: https://drive.google.com/drive/folders/1qZ3OsAAguJRF0_V32bH3mY0nRwjuma1Q) - As a developer, I want the core tables and schema written out so that I can easily implement the design in SQL - Tables are reviewed by the team ## Acceptance Criteria - Core tables and their schema are clearly listed and described in a Notion or doc - Each table should have information on its column name, type, nullable or not, and a one-line note on any non-obvious choice ## Tasks - Review the product spec to better understand data needs - Review the example data ([daily](https://docs.google.com/spreadsheets/d/1B9-gnDdrJyxS6-7ZFkVZhmGUtKFskUwW/edit?gid=143548897#gid=143548897), [hourly precipitation](https://docs.google.com/spreadsheets/d/1jLbtxy_8cI0rGSdPQ6whkBeV_dFQAAJw/edit?gid=502173441#gid=502173441), [july detailed daily data](https://docs.google.com/spreadsheets/d/1cWloMpYHZDGkUFulmeW0g1bY3J97Ts4b/edit?gid=1643257732#gid=1643257732)) - historical data to come - Create a Notion page or Google Doc with the tables, and their column names, data type, nullable or not, and a one-line note on any non-obvious choice - Think about how we'll use the data in our application and design accordingly - Review the tables with the team
Motivation
Acceptance Criteria
Tasks