Local dev DB with realistic sample data

[Gabe-Levin]

What changed

• New dockerized postgres database for local development using realistic S2S for Kenya and Uganda.
• Three steps to get the local database running:
  1. Create the db.env files within dev-db directory
  2. Download the parquet files from s3
  3. Run 'make up' in the terminal (from the dev-db directory)

[github-actions]

PR Deployment Details:
🚀 PR deployed to https://aaf7unsja2.execute-api.us-east-1.amazonaws.com/

[Copilot]

Pull Request Overview

This PR sets up a local PostgreSQL development database environment for Space2Stats. It provides Docker-based infrastructure with sample data loading capabilities, enabling developers to work with representative datasets locally.

• Adds Docker-based PostgreSQL setup with PostGIS and H3 extensions
• Implements Python seeding script to load sample parquet data into the database
• Includes SQL initialization scripts for schema creation
• Provides Makefile commands for database management and a Jupyter notebook for generating sample data

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
dev-db/seed_sample_data.py	Python script to load parquet sample data into PostgreSQL with chunked insertion and conflict handling
dev-db/init-scripts/01-init.sql	SQL schema initialization for space2stats and climate tables with indexes
dev-db/docker-compose.yaml	Docker Compose configuration for PostgreSQL with pgAdmin and optimized settings
dev-db/create_sample_parquets.ipynb	Jupyter notebook for fetching and preparing sample datasets from Kenya and Uganda
dev-db/README.md	Documentation for setup, usage, and troubleshooting of the development database
dev-db/Makefile	Build automation for database lifecycle management (up, down, reset, seed, clean)
dev-db/Dockerfile	Custom PostgreSQL image with PostGIS and H3 extensions

Comments suppressed due to low confidence (1)

dev-db/README.md:62

• Extra closing code fence that doesn't match an opening fence. This should be removed as the file already has proper closing fences for the code block.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The table_name and column names are directly interpolated into the SQL query string without sanitization, creating a potential SQL injection vulnerability. Consider using psycopg's SQL composition tools (psycopg.sql.SQL, psycopg.sql.Identifier) to safely construct queries with dynamic identifiers.

[Copilot]

There is trailing whitespace on this line that should be removed for cleaner code.

Suggested change

[Copilot]

Multiple consecutive blank lines at the end of the file should be reduced to a single blank line for consistency.

Suggested change