Municipal imagery is captured at different dates, angles, and resolutions
Smart Cities / Delivered project
Urban Infrastructure Intelligence Platform
A repeatable framework for turning aerial imagery into standardized evidence about roads, crossings, public assets, and change.
Explore the page ↓
Municipal asset inventories age quickly, and field surveys cannot economically maintain consistent coverage across rapidly changing areas.
Asset definitions vary across departments and districts
Change detection must distinguish real change from capture variation
From operating uncertainty to testable evidence.
The work was decomposed into four engineering decisions. Each one produced an artifact the customer could inspect, test, and carry into deployment.
Align imagery, boundaries, and asset definitions
City asset, district, and change taxonomy
Detect road and public-realm features
Imagery normalization and asset benchmark across districts
Normalize outputs into a reviewable city index
Change-detection precision study by capture condition
Track changes by location and acquisition date
Reviewable city index with field-verification queues
Deployed around the workflow—not beside it.
The system boundary includes where inference runs, how evidence reaches existing tools, and how people handle uncertainty after launch.
Cloud geospatial pipeline for imagery alignment, feature extraction, comparison, and versioned map publication.
Aerial imagery, district boundaries, asset registers, work orders, and GIS layers align to shared identifiers.
Each acquisition creates a versioned index; uncertain changes route to GIS or field teams before register updates.
What must be measured before the system earns trust.
Evaluation covers model behavior, workflow burden, and production performance. The metric defines the gate; the customer baseline and acceptance threshold define the target.
Asset detection F1
Precision and recall by asset class and district.
Sets which inventory classes can be updated from imagery.
Change precision
Verified real changes among surfaced candidates.
Controls field-verification workload.
Coverage completeness
District area with comparable, usable, current imagery.
Separates capture gaps from asset gaps.
Verification efficiency
Field or GIS review time per accepted update.
Measures improvement over broad manual surveys.
Value has to appear in the customer’s operating day.
The index should prioritize where field verification matters and show the imagery and acquisition date behind every mapped change.
Tools follow the system—not the other way around.
Final architecture depends on data quality, operating conditions, integrations, risk, and evaluation criteria established during discovery.

