Dublin City Council
Kerbside Asset Mapping — 2024/25
Under the EU H2020 SENATOR project, Inakalum surveyed kerbside assets along Dublin City Council’s footpaths and pavements — point, linear and polygon assets, every one walked, photographed, geotagged and categorised. The dataset was delivered into the CurbIQ kerbside platform. Most distinctively, the engagement included two full re-surveys of the network — a 2024 baseline and two refreshes in 2024 and 2025, proving change-detection at city scale.
- Customer
- Dublin City Council (SENATOR / CurbIQ)
- Engagement window
- Feb 2024 – June 2025
- Assets in current dataset
- 5,800+
- Re-surveys delivered
- 2 (Oct–Dec 2024, May–Jun 2025)
- Programme
- EU H2020 SENATOR — CurbIQ kerbside platform
“The unique approach of using locally-recruited agents with proprietary smartphone technology ensured that no street-level or overhead obstructions impeded data collection, offering superior coverage and accuracy compared to other methods.”
Every kerbside asset — point, linear and polygon.
Kerbside inventories are inherently multi-geometry. Discrete signs and bins are points; yellow lines and bus lanes are linear runs; parking bays and yellow boxes are polygons. Inakalum captured all three in one workflow, on one smartphone app, with one set of QA checks.
Point assets
Parking signs, traffic signals, pedestrian crossings, bins, hydrants, bus stops, lamp columns — each recorded as a discrete geotagged feature with type, category and photographs.
Linear assets — road markings
Single and double yellow lines, clearways, bus lanes, cycle lanes — recorded as linear geometries running along the kerb, with photographs at intervals along the run.
Polygon assets
Parking bays and yellow boxes — recorded as enclosed polygons captured on the ground rather than estimated from imagery, with type and photographs per area.
Delivered as KML to CurbIQ
The entire dataset was delivered as standard KML for ingestion into the CurbIQ kerbside platform. No custom integration, no bespoke export — just the standard GIS format every council and third-party platform already speaks.
The methodology proved at city scale.
The headline distinction of this engagement was not the initial survey — it was the two full re-surveys that followed. Because every original record was geotagged to its exact point and held under version control, assets can be easily re-verified if they are unchanged, edited if they have changed, or retired if they are no longer there. New assets can be added as they are found. That turns a snapshot into a programme.
“Each re-survey re-walked every asset to detect change — the geotagged, photograph-backed method underpins every kind of asset-management programme that depends on knowing what’s actually there, this year, not three years ago.” — Inakalum project record, June 2025
What two years of change actually looked like.
The May–June 2025 re-walk delivered a complete picture of how the kerbside inventory had changed since the initial 2024 baseline. Every asset re-verified, every removal cleaned out of the dataset, every new asset added with full attributes.
And: delivered on time despite one of the wettest periods on record falling in the middle of the project. Inakalum doesn’t routinely survey in wet or very cold weather, so completing on schedule called on careful project management — re-sequencing routes and redeploying agents around the weather windows we did get.
Locally-recruited agents. One app. One survey manual.
The Inakalum model: recruit agents who know the local geography, train them to a single survey manual, equip them with our proprietary smartphone capture app, run them through the same three-stage QA pipeline regardless of who they are. The result is consistency across hundreds of surveyors and tens of thousands of records.
Standardised capture
Every feature recorded against fixed drop-downs and mandatory fields for asset type and category — no free-text variation between surveyors.
In-field validation
The app rejects incomplete or out-of-range entries at source. The surveyor can’t walk away from a record that’s not finished.
Agent self-check before upload
Agents check and can edit data captured before uploading from the field — confirming each record is complete, categorised correctly and photographed properly before it leaves the kerb.