How stadt-bielefeld/bielefeldgeoclient works
Project type and purpose
• Full-stack, containerized web mapping application
• Purpose: Interactive mapping portal with user/role management, print-outs (via MapFish), digitizing, transport planning, and embed-in-portal integration
Main components
A. Client Layer (Browser)
– “Admin UI” (AngularJS-based)
– “Map UI” (AngularJS-based map viewer with plugins: digitize, transport, geoEDITOR)
B. Edge / Proxy
– Nginx reverse proxy (serves static files + routes to backend)
C. Application Layer
– Python Flask/Gunicorn server (“munimap-app” container)
– REST API endpoints (views/api.py, views/frontend.py, etc.)
– Admin modules (views/admin.py + Angular controllers under munimap/frontend/js/admin)
– Export/Print service (munimap/export + MapFish v3 integration)
– Digitize + Transport plugins (munimap/munimap_transport + munimap/export)
– Queue and worker (munimap/queue for background jobs: print, exports)
D. Data Layer
– PostgreSQL/PostGIS database (“munimap-postgis” container)
– Mapbender schema & data (“munimap-postgis-mapbender” container or init scripts)
E. External Services
– WMS/WFS map services (configured via YAML under dev/data/map-configs)
– Third-party transport API (invoked by munimap_transport/transport-api-service.js)
– Form-Solutions portal (optional embed with token access)
Relationships and data flows
• Browser → Nginx → Gunicorn/Flask: all UI/API calls
• Browser → WMS/WFS: map tile/feature requests (configured endpoints)
• Flask → PostgreSQL: reads/writes user, maps, layers, project settings
• Flask → Queue → Worker → Filesystem/DB: asynchronous print job generation
• Flask → MapFish v3 (embedded) → PDF/JRXML templates → returns print output
• Flask → External transport API for journey planning
• Browser ↔ Flask: JSON config load/save, login/auth, administrative CRUD
Architectural patterns & design principles
• MVC separation inside Flask (views, forms, models under munimap/model)
• Modular frontend: AngularJS modules per feature (admin, digitize, transport)
• Configuration-driven: YAML under dev/data and dev/configs
• Containerization via Docker Compose (services for app, DB, nginx)
• Schema migrations with Alembic