https://orcid.org/0000-0002-9097-2246
The third session I participated in at GWF 2026 shifted register somewhat away from the explicitly military framing of the earlier panels and toward something that affects a broader audience: how artificial intelligence is being applied to understand, manage, and secure urban infrastructure at scale. The audience was a mix of city planners, defence-adjacent technologists, data scientists, and policy people. That breadth made for a different kind of conversation.
Session 1 carried the title AI-Powered Urban Analytics: Data Science for Infrastructure Intelligence and the framing was deliberately wide. Urban infrastructure is a category that encompasses power grids, water systems, transport networks, telecommunications, public health monitoring, and the physical built environment. The question the session kept returning to was: what does it actually mean to apply AI to something this complex, this consequential, and this hard to fully observe?
The Infrastructure Intelligence Problem
Modern cities generate continuous data. Sensors embedded in roads, buildings, utilities, and public spaces produce streams that no human analyst team could meaningfully process at speed. AI-powered urban analytics is the attempt to make that data operationally useful not just archived, but acted upon.
The infrastructure intelligence framing matters because it shifts the goal from description to anticipation. A system that tells you a water main failed is useful. A system that identifies the precursor signatures of failure before it happens is transformative. That gap between reactive monitoring and predictive intelligence is where most of the serious work is being done, and where most of the serious risks live.
Bayesian Program Learning for Urban Pattern Recognition
One of the contributions I brought to this session was the relevance of Bayesian program learning as a framework for urban analytics problems. Most deployed urban AI systems are pattern-matchers they learn from historical data and recognise recurrences. That works well in stable environments with abundant labelled data. Urban infrastructure is neither.
Bayesian program learning approaches the problem differently: rather than learning from volume, it learns programmes structured representations of how things work from very few examples, and generalises from those. In an urban context, this matters when you're trying to reason about rare events: infrastructure failure modes that have only occurred once or twice, novel threat signatures in a utility network, or unusual movement patterns in a city under stress. A purely statistical model trained on normal conditions will miss these. A model that has learned a causal programme for how the system behaves has a better chance of flagging the anomalous.
I raised this not as a deployed solution most urban analytics stacks are nowhere near this but as the direction that serious infrastructure intelligence work needs to move toward.
Differentially Private Federated Learning Across Urban Sensor Networks
Urban data is politically and legally sensitive in ways that military data is sensitive operationally. A smart city sensor network aggregates information about the movement, behaviour, and patterns of civilian populations. Centralising that data for AI training creates privacy exposure, legal liability, and in authoritarian contexts, a surveillance infrastructure that outlasts its original purpose.
I discussed Differentially Private Federated Learning as the architecture that makes urban analytics viable without those costs. The federated component means models are trained locally at the sensor node, the district server, the utility substation — and only model updates, not raw data, are shared upward. The differential privacy component means those updates are mathematically protected: calibrated noise is added such that no individual data point can be reconstructed from the aggregated model.
The practical implication is that a city can run a shared infrastructure intelligence model across its transport, utilities, and public safety systems without any single entity including the city government itself holding a centralised dataset of resident behaviour. That is not a minor privacy nicety. In a world where urban data infrastructure is increasingly a target, both for criminal actors and for state-level adversaries, it is an operational security consideration.
Sovereign AI and Urban Infrastructure
A thread that ran through this session, and one I pushed on, was the question of sovereign AI models in the urban context. Most cities deploying AI-powered analytics are doing so through commercial platforms often built on models trained elsewhere, hosted on infrastructure they don't control, and updated on schedules set by vendors.
The dependency this creates is underappreciated. A city's infrastructure intelligence layer, if it runs on a foreign-hosted model, is a city whose understanding of its own infrastructure is mediated by someone else's system. In peacetime that is a procurement question. In a crisis, a cyberattack, a natural disaster, a period of geopolitical tension, it becomes something more serious.
Sovereign AI in this context doesn't mean every city builds its own foundation model. It means the critical analytical layer that interprets infrastructure data runs on systems that are nationally or regionally governed, auditable, and resilient to external interference. The conversation around this at GWF was notably more advanced among European participants than I'd expected there is genuine policy momentum here, driven in part by the EU AI Act's implications for critical infrastructure AI.
AI Security Threats in Urban Systems
I flagged AI security threats specifically in the urban analytics context because the attack surface is different from military systems but no less consequential. Urban AI systems make or inform decisions about infrastructure allocation, anomaly response, and resource deployment. An adversary who understands how those systems work has options.
The threat I spent the most time on was adversarial input manipulation crafting sensor data or environmental conditions that cause an urban AI system to misclassify a situation. A power grid anomaly misclassified as normal. A movement pattern misclassified as routine. These aren't hypothetical attack vectors; they are documented in research and increasingly relevant as urban systems become more automated.
Persuasive AI came up in a different register here. In urban planning and infrastructure investment decisions, AI-generated analysis increasingly shapes what decision-makers see and prioritise. A system that surfaces certain patterns, routes certain recommendations, or frames trade-offs in particular ways can subtly steer decisions without any single output being obviously wrong. I raised this not as a conspiracy framing but as a design responsibility: the people building urban analytics systems need to think carefully about how their outputs are presented, what they omit, and whose interests the framing serves. Algorithmic outputs in consequential civic decisions warrant the same scrutiny we'd apply to any other form of expert advice.
What the Session Left Open
The honest closing note I'd offer on this session is that urban analytics as a field is at an interesting and slightly uncomfortable moment. The technical capability is running ahead of the governance frameworks. Cities are deploying AI systems for infrastructure management under procurement timelines that don't allow for the kind of adversarial stress-testing, privacy auditing, or sovereign architecture review that the stakes warrant.
GWF brought some of the right people into the same room. Whether those conversations translate into procurement standards, policy frameworks, or architectural requirements at the city level is the harder question and one that won't be answered at a conference.
Series: Geospatial World Forum 2026, RAI Amsterdam | April 27 – May 1
.jpeg)
.jpeg)
