Road Network Inventory
Central registry for municipal road segments, cross-section profiles, appurtenances, traffic data, linear referencing, and dynamic segmentation — the foundational layer feeding all downstream road management modules.
Segment Search
GIS Layer
Data Complete
Traffic Flag
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
9Delegated to
5Centreline GIS, dynamic segmentation layers
Road/parcel adjacency
TCA registration for road segments
Field inventory data capture
Change logging
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
3 capability groups comprising 8 discrete capabilities — each with API surface, business rules, and data ownership.
Unique ID, road name, from/to intersections, functional class, ownership (municipal/regional/provincial/private/boundary), surface type, width, lanes, speed, AADT, jurisdiction, and urban/rural classification.
Classification
Arterial, Collector, Local, Lane with MMS classification (Class 1–6).
Ownership
Municipal, Regional, Provincial, Private, and Boundary road ownership tracking.
Surface Type
HMA, surface treatment, gravel, concrete, and interlocking surface types.
Assumed Status
Track assumption status: assumed, pending assumption, private, provincial.
Centreline linkage with offset-distance positioning. Dynamic segmentation overlaying surface type, condition, traffic, jurisdiction, and ward.
LRS
Centreline-based linear referencing system for precise location on road network.
Dynamic Segmentation
Overlay multiple attributes (surface, condition, traffic) on the same centreline.
Offset-Distance
Position features and events using distance from reference points.
Multi-Layer
Simultaneously display jurisdiction, ward, condition, and traffic overlays.
ROW width, curb & gutter (type/material/condition), sidewalks (left/right, width, material, AODA compliance), bike lanes, shoulders, ditches, and utility corridors.
Curb & Gutter
Type, material, and condition tracking for roadside infrastructure.
Sidewalks
Left/right with width, material, condition, and AODA compliance status.
Bike Lanes
Conventional, buffered, protected, and multi-use pathway types.
Utility Corridors
Underground utility corridor locations and types within the ROW.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
5 entities with 4 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
8 RESTful endpoints across 5 resource groups — plus 4 domain events for async integration.
/api/v1/roads/segments
Road segment registry
/api/v1/roads/segments/{id}
Segment detail with cross-section
/api/v1/roads/segments
Register new segment
Ecosystem
Products that depend on this module
2 Civic products consume Road Network Inventory — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Segment Search Response
GIS Layer Rendering
Data Completeness
Traffic Data Currency
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Road Network Inventory
Request an architecture brief, integration guide, or live demo environment for your team.