Route Monitoring Tools

Track real-time traffic conditions on strategic route corridors. Search your monitored routes to find delays, then drill into segment-level analysis to pinpoint exactly where bottlenecks form.

Documentation: Route Monitoring
Uses TOMTOM_MOVE_PORTAL_KEY

Recommended workflow: Use tomtom-route-search first to discover route IDs, then pass them to tomtom-route-monitoring-details for segment-level analysis.

tomtom-route-search

Search and filter all monitored routes by name, status, delay, or other properties.

Parameters

Parameter	Type	Required	Description
`sql_queries`	object	Yes	Named SQL queries

SQL Tables

routes: One row per monitored route

Column	Type	Description
`route_id`	number	Unique route identifier
`route_name`	string	Route name
`route_status`	string	`NEW`, `ACTIVE`, `UPDATING`, `FAILED`, `ARCHIVED`
`travel_time`	number	Current travel time in seconds
`typical_travel_time`	number	Typical travel time in seconds
`delay_time`	number	Delay in seconds
`passable`	number	0 (blocked), 1 (passable), or NULL
`route_length`	number	Route length in meters
`completeness`	number	Completeness percentage
`typical_travel_time_coverage`	number	Coverage percentage

Example SQL Queries

1-- Find routes by name
2SELECT route_id, route_name, delay_time FROM routes WHERE route_name ILIKE '%A10%'
3
4-- Most delayed routes
5SELECT route_id, route_name, delay_time,
6       ROUND(delay_time * 100.0 / NULLIF(travel_time, 0), 1) as delay_percent
7FROM routes
8WHERE route_status = 'ACTIVE' AND delay_time > 0
9ORDER BY delay_percent DESC
10
11-- Status summary
12SELECT route_status, COUNT(*) as count FROM routes GROUP BY route_status

tomtom-route-monitoring-details

Get detailed segment-level traffic analysis for routes. Supports up to 20 routes per request for cross-route comparisons.

Parameters

Parameter	Type	Required	Description
`routeIds`	string[]	Yes	Route IDs to query (1–20). Data is merged for cross-route SQL
`sql_queries`	object	Yes	Named SQL queries

SQL Tables

route_info: Route-level summary (one row per route)

Column	Type	Description
`route_id`	number	Route identifier
`route_name`	string	Route name
`route_status`	string	`NEW`, `ACTIVE`, `UPDATING`, `FAILED`, `ARCHIVED`
`travel_time`	number	Current travel time in seconds
`typical_travel_time`	number	Typical travel time in seconds
`delay_time`	number	Delay in seconds
`passable`	number	0, 1, or NULL
`route_length`	number	Route length in meters
`completeness`	number	Completeness percentage
`typical_travel_time_coverage`	number	Coverage percentage
`route_confidence`	number	Confidence level (0–1)

segments: Segment-level details (one row per segment)

Column	Type	Description
`route_id`	number	Route identifier
`segment_id`	number	Segment identifier
`segment_id_str`	string	Segment ID as string
`average_speed`	number	Average speed
`typical_speed`	number	Typical speed
`segment_length`	number	Segment length in meters
`open_lr_id`	string	OpenLR code
`current_speed`	number	Current speed
`relative_speed`	number	Speed relative to free flow
`confidence`	number	Confidence level (0–1)
`open_lr_length`	number	OpenLR length

Example SQL Queries

1-- Slowest segments (current speed well below typical)
2SELECT route_id, segment_id, current_speed, typical_speed,
3       (typical_speed - current_speed) as speed_drop
4FROM segments
5WHERE current_speed < typical_speed * 0.5
6ORDER BY speed_drop DESC
7
8-- Compare routes by delay percentage
9SELECT route_id, route_name, delay_time, travel_time,
10       ROUND(delay_time * 100.0 / NULLIF(travel_time, 0), 1) as delay_percent
11FROM route_info
12ORDER BY delay_percent DESC
13
14-- Low confidence segments
15SELECT route_id, segment_id, current_speed, confidence
16FROM segments
17WHERE confidence < 0.5
18ORDER BY confidence