How loomaimarketing-create/safehour works
SafeHour is a city-safety intelligence and navigation MVP. Its implemented user workflow selects a city in the map UI, requests city-specific incidents from FastAPI, fetches and normalizes public records through source adapters, deduplicates them, and displays historical incidents on a map. Chicago also has a sync path that persists records to Supabase. Discovery and schema checks, risk scoring, hourly aggregation, personalization, and safety-aware routing are distinct product capabilities, but the sampled runtime does not establish their full implementations or connections; those uncertain links are omitted or marked unverified.
Main entry points: main.py FastAPI endpoints · runner.py Chicago sync · normalize.py Normalize records · chicago.py Chicago adapter
Components 24
Map experience
- Incident map
frontend/src/App.jsx - Safety-aware routing
frontend/src - Personalization
frontend/src
API and discovery
- FastAPI endpoints
backend/app/main.py - Source discovery
backend/app/discovery/discover.py - Source registry
backend/app/discovery/registry.py - Schema detection
backend/app/discovery/schema_detector.py - Risk scoring
backend/app/risk.py - Hourly aggregation
backend/app
Incident ingestion
- Chicago sync
backend/app/ingestion/runner.py - Normalize records
backend/app/ingestion/normalize.py - Deduplicate records
backend/app/ingestion/dedupe.py - Quality reporting
backend/app/ingestion/quality.py - Incident model
backend/app/models.py
Data sources
- Adapter contract
backend/app/sources/base.py - Chicago adapter
backend/app/sources/chicago.py - NYC adapter
backend/app/sources/nyc.py - Los Angeles adapter
backend/app/sources/la.py - Socrata client
backend/app/sources/socrata.py
Persistence
- Supabase client
backend/app/db.py - Supabase / Postgres
database/schema.sql
Other components
- City explorer
- Socrata open data
- OpenStreetMap tiles
Connections 30
- City explorer → Incident map: selects city
frontend/src/App.jsx - Incident map → FastAPI endpoints: requests incidents
frontend/src/App.jsx - FastAPI endpoints → Chicago adapter: creates adapter
backend/app/main.py - FastAPI endpoints → NYC adapter: creates adapter
backend/app/main.py - FastAPI endpoints → Los Angeles adapter: creates adapter
backend/app/main.py - FastAPI endpoints → Normalize records: fetches normalized
backend/app/main.py - FastAPI endpoints → Deduplicate records: deduplicates
backend/app/main.py - FastAPI endpoints → Quality reporting: reports quality
backend/app/main.py - FastAPI endpoints → Source discovery: lists sources
backend/app/main.py - Source discovery → Source registry: reads registry
backend/app/discovery/discover.py - Chicago sync → Chicago adapter: creates adapter
backend/app/ingestion/runner.py - Chicago sync → Normalize records: fetches normalized
backend/app/ingestion/runner.py - Chicago sync → Deduplicate records: deduplicates
backend/app/ingestion/runner.py - Chicago sync → Quality reporting: reports quality
backend/app/ingestion/runner.py - Normalize records → Adapter contract: calls adapter
backend/app/ingestion/normalize.py - Normalize records → Incident model: returns incidents
backend/app/ingestion/normalize.py - Chicago adapter → Adapter contract: implements
backend/app/sources/chicago.py - NYC adapter → Adapter contract: implements
backend/app/sources/nyc.py - Los Angeles adapter → Adapter contract: implements
backend/app/sources/la.py - Chicago adapter → Socrata client: queries dataset
backend/app/sources/chicago.py - NYC adapter → Socrata client: queries dataset
backend/app/sources/nyc.py - Los Angeles adapter → Socrata client: queries dataset
backend/app/sources/la.py - Socrata client → Socrata open data: fetches records
backend/app/sources/socrata.py - Chicago sync → Supabase client: upserts incidents
backend/app/ingestion/runner.py - Supabase client → Supabase / Postgres: connects to store
backend/app/db.py - Incident map → OpenStreetMap tiles: loads tiles
frontend/src/App.jsx - FastAPI endpoints → Chicago sync: runs Chicago sync
backend/app/main.py - Risk scoring → Hourly aggregation
- Safety-aware routing → Risk scoring
- Personalization → Risk scoring