Data-driven architecture generates increasingly rich datasets — energy simulations, daylight analysis, pedestrian flow models, environmental impact assessments, post-occupancy sensor data. Architects are getting better at producing this data. We are not getting better at communicating it.
The typical data presentation in an architectural project is a PDF appendix with colour-coded floor plans (daylight levels), line charts (annual energy consumption), and CFD vector plots (wind analysis). These are meaningful to the design team and MEP engineers. They are largely meaningless to:
- Clients who need to make investment decisions based on performance projections
- Planning committees who need to assess whether a project meets sustainability requirements
- Community members who want to understand how a development will affect their neighbourhood
- Building occupants who could use real-time data to improve their comfort and reduce energy waste
Specific questions:
-
Spatial data vs. abstract charts: Environmental performance data is inherently spatial — temperature varies by room, daylight by orientation, air quality by floor. Yet we often reduce this to building-wide averages presented as bar charts. What are the best examples you've seen of spatial data visualisation that preserves the location-specificity that matters for architectural decisions?
-
Temporal dynamics: Buildings perform very differently at 2pm in July versus 6am in January. Static visualisations flatten this. How do you communicate temporal variation effectively — animation, interactive sliders, small multiples, or something else?