How hotosm/fmtm works
Main Components
a. Frontend Layer:
• React-based web application (src/frontend)
• Svelte-based mapper interface (src/mapper)
• Mobile interface for ODK Collect integration
b. Backend Layer:
• FastAPI application (src/backend)
• Authentication system with OSM integration
• Task management system
• Project management system
• Organization management system
c. Data Storage:
• PostgreSQL database with PostGIS extension
• MinIO for file storage
• ODK Central for form storage and submissions
d. Infrastructure:
• Nginx reverse proxy
• Docker containerization
• Kubernetes orchestration
Relationships and Data Flow
1. User Authentication Flow:
• Browser -> Nginx -> FastAPI -> OSM OAuth -> Database
2. Project Creation Flow:
• Frontend -> FastAPI -> Database
• > ODK Central (form creation)
• > MinIO (file storage)
3. Mapping Flow:
• Mobile App -> ODK Central -> FastAPI -> Database
• > Frontend (real-time updates)
4. Data Submission Flow:
• ODK Collect -> ODK Central -> FastAPI
• > PostgreSQL/PostGIS -> Frontend
Important Elements to Highlight
a. Integration Points:
• ODK Central integration
• OSM authentication
• MinIO storage interface
• PostGIS spatial capabilities
b. Security Layers:
• Authentication middleware
• API gateway
• Role-based access control
c. Data Processing:
• Task splitting system
• Geospatial processing
• Data validation and conflation
Architectural Patterns to Emphasize
• Microservices architecture (multiple containers)
• API-first design
• Event-driven updates for real-time features
• Spatial data handling capabilities
• Offline-first mobile capabilities
[Client Layer]
• ↓
[API Gateway/Nginx]
• ↓
[Application Services]
• ↓
[Data Services]
• ↓
[Storage Layer]
Technical Details to Note
• FastAPI backend with PostgreSQL
• React frontend with Redux state management
• Svelte mapper interface
• Docker containerization
• Kubernetes orchestration
• ODK ecosystem integration
• OSM authentication and data flow