A living ontology
for the urban infrastructure
beneath your feet.
Urban Atlas AI maps assets, projects, permits and policies into one connected layer, so cities can see what's happening, what's failing and what to do next.
The Coordination Gap
Different crews. Same block. Same year. Nobody knew.
Cities run infrastructure through disconnected systems. Public works, permitting and private utilities each work in their own silo, so the same street gets opened again and again.
64%
Road cuts
Share of DC's street grid cut open in 10 or more of the 11 years from 2016 to 2026. The same streets keep getting dug up.
288
Missed opportunities
Groups of 2026 permits within 25 m of each other that started less than 30 days apart, close enough to have shared one trench.
637
Near misses
Groups of 2026 permits within 25 m that started 30 to 180 days apart. Earlier planning could have lined them up.
Road-cut permits per cell
< 54
54–99
100–190
191–278
279+ · Hotspot
171,518 road-cut permits analysed · Source: DC Open Data and Urban Atlas analysis. Permit proximity indicates potential coordination opportunities, not confirmed avoidable work.
JanJ
FebF
MarM
AprA
MayM
JunJ
JulJ
AugA
SepS
OctO
NovN
DecD
Dig Once
One trench instead of five.
Take one block. Telecom, electric, gas, water and sewer all have work planned under it, each on its own schedule. Lined up into one shared trench, the street is opened once, restored once, and keeps more of its pavement life.
Five openings. Five restorations.
When the schedules miss each other, the street is cut open five times in a year. The American Public Works Association's review of pavement studies found a single utility cut can take 20 to 56% off a pavement's life.
One opening. One restoration.
Urban Atlas doesn't just flag nearby work. It reasons about which jobs belong in the same trench, and why. Five planned starts become one opening in June: one mobilization, one restoration, one disruption for the block.
The Engine
Nearby isn’t the same as related.
Every asset, permit, project, and policy is a node in a living knowledge graph. Proximity finds the candidates; the engine reasons over the graph to decide which are worth coordinating, and records why.
A permit is filed.
A contractor files a water service replacement: ROW-2026-01482, a 120 ft trench. The engine snaps it to the street centerline and normalizes it into a location, scope, and work window it can reason over.
The engine looks around.
A buffered corridor finds nearby permits and assets. PostGIS finds what is close; the knowledge graph decides which candidates actually connect to this work.
What relates, and why.
The water main is the permit's own scope. A filed electric duct bank shares the trench, and the storm sewer can be inspected while the street is open. A nearby street light is rejected. Accepted and rejected relationships are both recorded with reasons.
The timing lines up.
The duct bank's permit overlaps the same work window. Shared space and shared time clear the gate, and a draft coordination room opens for one trench.
An agent sees what’s next.
An AI agent watching condition trends sees the 1981 cast-iron main under the block cross its break-risk threshold. It proposes replacing the main in the same trench, for a planner to review, before anyone files a permit.
Coordination Room
Every stakeholder. One coordination room. The same information.
A shared, realtime workspace turns a coordination opportunity into a decision: friction and contiguity scores, AI briefs, cited plan context, schedules, commitments and a permanent record in one place.
Room brief
Every coordination room opens with an AI-written brief: what is being coordinated and why the work belongs together.
Comprehensive Plan alignment
Up to three relevant policies from your adopted plan, cited and linked back to the source text.
Capital Improvements Plan alignment
Matching CIP projects surface automatically, so planned capital work is part of the conversation from the start.
Project activities timeline
Excavation, utility work and restoration on one shared schedule, with each coordination's work in its own row. Drag or resize an activity to reschedule it.
Corridor map
Every coordinated asset and permit on one map, with the shared work area outlined.
Room chat
Stakeholders and AI in one thread. Mention a colleague or ask a question, and answers cite the plan.
Social Friction Index
Each work stream adds friction by type and duration. Coordinated work earns credit for overlapping in space and time, scored 0–100 fragmented vs coordinated.
Contiguity index
A 0–1 measure of how continuous shared work is, weighting each relationship by proximity, schedule overlap and match confidence.
Room history
Every meaningful scope, phase, schedule and alignment decision is kept as a revision, with who made it, in an append-only history.
One Engine, Three Entry Points
Three ways in. One engine.
Every coordination room starts the same way. A permit, a planner's sketch or an agent's background signal all run one pipeline: find what's nearby, decide how it relates, attach plan context, and open a coordination room.
Permit workflow
A permit is filed and snapped to the street it runs along. The engine searches a buffer around it for nearby permits and assets, keeps the work that truly relates, and can open a draft coordination room once it clears the gate.
Agentic workflow
Manual workflow
Staff draw an area on the map during a brainstorm or emergency planning session. That drawing becomes the origin geometry, the same scans run, and staff can open a coordination room if they choose to proceed.
Integrations
No migration. No new system of record. Just intelligence layered on top of what you already run.
Urban Atlas connects to the systems your city already runs, reading what it needs, computing what doesn't exist anywhere else, and surfacing intelligence at the moment it matters. Nothing is replaced. Nothing is disrupted.
Accela
Esri ArcGIS
Cityworks
Cartegraph
Lucity
Infor
CentralSquare
CivicPlus
Granicus
OpenGov
Tyler Technologies
VUEworks
PostGIS
Accela
Esri ArcGIS
Cityworks
Cartegraph
Lucity
Infor
CentralSquare
CivicPlus
Granicus
OpenGov
Tyler Technologies
VUEworks
PostGIS
Accela
Esri ArcGIS
Cityworks
Cartegraph
Lucity
Infor
CentralSquare
CivicPlus
Granicus
OpenGov
Tyler Technologies
VUEworks
PostGIS
Accela
Esri ArcGIS
Cityworks
Cartegraph
Lucity
Infor
CentralSquare
CivicPlus
Granicus
OpenGov
Tyler Technologies
VUEworks
PostGIS
One coordinated trench pays for the platform every year.
© 2026 urbanatlas.ai. All rights reserved.
Trust