How ivan-cardenas/crosstwin works
CrossTwin is a Django urban digital-twin platform for Dutch geospatial data. Users explore spatial layers and domain indicators through a map; the platform also supports data import, urbanisation analysis, and heat tools including LST and SOLWEIG. PostGIS-backed domain models and signal-driven updates form an important internal layer. The README establishes the product capabilities and stack, while source excerpts and the index support only selected implementation relationships; unverified workflow links are dashed.
Main entry points: models.py Administrative geography · urbanisation.py Urbanisation analysis · builtup/signals.py Built-up updates · physicalEnv/signals.py Environment updates
Components 24
Platform and map
- Django application
DigitalTwin/settings.py - Map interface
core/static/js/mainMap.js - Map data views
mainMap/views.py - Data import
importer - Raster tile service
tiler.py
Spatial foundation
- Spatial database
- Administrative geography
administrative/models.py - Population projections
administrative/calculations/population.py - Administrative updates
administrative/signals.py - Layer cache versions
core/cache.py
Built environment
- Built-up features
builtup/models.py - Urbanisation analysis
builtup/calculations/urbanisation.py - Built-up updates
builtup/signals.py
Environment and climate
- Physical environment
physicalEnv/models.py - Land-cover overlays
physicalEnv/calculations/landcover.py - Environment updates
physicalEnv/signals.py
Urban systems
- Housing indicators
housing - Energy data
Energy/models.py - Nature data
nature/models.py - Water supply indicators
watersupply/calculations/indicators.py - Land-surface temperature
urban_heat/lst/pipeline.py - Thermal comfort analysis
urban_heat/solweig/pipeline.py - Weather and climate
weather/calculations/climate.py
Other components
- Map user
Connections 27
- Map user → Map interface: explores
- Map interface → Map data views: requests layers
- Map data views → Spatial database: reads spatial data
- Data import → Spatial database: loads data
- Spatial database → Raster tile service: serves raster tiles
- Administrative geography → Population projections: provides units
administrative/calculations/population.py - Administrative updates → Administrative geography: updates
administrative/signals.py - Administrative updates → Layer cache versions: bumps versions
administrative/signals.py - Environment updates → Land-cover overlays: rewrites overlays
physicalEnv/signals.py - Environment updates → Physical environment: updates
physicalEnv/signals.py - Environment updates → Built-up features: reads features
physicalEnv/signals.py - Built-up updates → Built-up features: handles changes
builtup/signals.py - Built-up updates → Land-cover overlays: updates overlays
builtup/signals.py - Built-up updates → Layer cache versions: bumps versions
builtup/signals.py - Urbanisation analysis → Administrative geography: allocates population
builtup/calculations/urbanisation.py - Urbanisation analysis → Built-up features: uses built features
builtup/calculations/urbanisation.py - Urbanisation analysis → Population projections: uses projections
builtup/calculations/urbanisation.py - Land-surface temperature → Physical environment: reads NDVI layers
urban_heat/lst/pipeline.py - Land-surface temperature → Land-surface temperature: fetches scene inputs
urban_heat/lst/pipeline.py - Thermal comfort analysis → Physical environment: uses surface inputs
urban_heat/solweig/pipeline.py - Thermal comfort analysis → Weather and climate: uses weather inputs
- Water supply indicators → Administrative geography: uses units
watersupply/calculations/indicators.py - Water supply indicators → Population projections: uses population
watersupply/calculations/indicators.py - Water supply indicators → Weather and climate: uses water balance
watersupply/calculations/indicators.py - Housing indicators → Spatial database: stores indicators
- Energy data → Spatial database: stores energy data
- Nature data → Spatial database: stores nature data