A live road incident map for a city, refreshed on your timetable
Closures, roadworks and other incidents on one map that redraws itself every hour or every 15 minutes, shared by link with the people who need it.
Part of the guide Location intelligence automation
A live road incident map is a single map of a city that shows its current road closures, roadworks and other incidents, each as a pin with its kind and street, and that redraws itself on a timetable so the page someone opens at 09:10 shows the roads as they were a few minutes earlier. You build it once, choose how often it refreshes, and share one link. Nobody has to copy anything from one screen to another.
This is for control rooms, dispatch desks, newsrooms, event organisers, hotel concierge teams and city departments that keep a wall screen or a browser tab open on the roads. It covers what to put on the map, how often to refresh it, an invented example for Seoul, what makes a map misleading, and the four or five blocks that keep it current. It is part of the guide to location intelligence automation.
What goes on the map
Start with what the Traffic incidents block finds: road closures, roadworks and other incidents, read live from online maps, each with a position to about 150 metres, its street and district for the first 40 of a run, and the small icon the original map uses. That icon shows in each pin's pop-up, so a viewer recognises a closure at a glance.
Then decide what else belongs beside them. A map with only incidents answers "where is it blocked?" A map that also shows your own places answers "which of ours is affected?", which is usually the more useful question:
- Your depots, stores, venues or hotels, so the eye goes straight to incidents near them.
- A drawn area of interest, so viewers see the edge of what was searched.
- Incidents split into layers by kind, so roadworks can be hidden on a day only closures matter.
The Show on a map block draws the results as points with the area searched, groups them into one layer per category with a legend you can click, and can show clusters or a heat view when a city is busy.
How often should it refresh?
The map is only as fresh as its last run. The Schedule block can run it every 5, 15 or 30 minutes, every hour, or at set times, and can limit runs to working hours. A few rules of thumb:
- A control room or dispatch desk: every 15 minutes during operating hours.
- An event team on the day: every 5 or 15 minutes from two hours before doors open.
- A weekly planning view: once each morning is plenty; it is a record, not a live screen.
Set the map to update the same map on each run rather than save a new one, so the shared link always shows the latest picture. Keep a separate weekly flow that saves a new map if you want a history to look back on.
An invented example: a delivery firm's wall screen in Seoul
The details here are made up. A grocery delivery company runs six micro-warehouses in Seoul. Its dispatch room wants one screen showing what could slow riders this hour.
- The flow searches the city every 15 minutes from 07:00 to 22:00.
- Each incident is matched to the nearest micro-warehouse and its distance.
- The map shows the six warehouses as squares, incidents within 3 km in strong colours, the rest faded into a second layer.
- The same link is open on the wall screen and on the shift lead's phone.
At 11:30 the screen shows two roadworks pins near the Mapo warehouse and nothing near the others. The shift lead asks riders from Mapo to avoid one street. Nobody had to read a list.
What makes an incident map misleading
- A stale screen that looks current. Show the time of the last run in the map's name or the page, so a viewer knows how old it is.
- An area too big to cover. A large area is searched in parts of about 24 km, centre first, up to 8 parts a run, and the step says when it was only partly covered. Split a metropolitan region into several areas.
- Reading pins as exact. About 150 metres is good for which road, not which lane.
- Expecting accidents as their own kind. They come back as road closures for now.
- Confusing incidents with slow traffic. A jammed road with no closure is not an incident. For speeds and the jam factor around your places, add Traffic Flow to the same flow.
The blocks behind the map
An AI employee in xMap Flows keeps the map fresh without anyone touching it:
- Schedule: every 15 minutes in operating hours.
- Area of interest: the city, or the districts you serve, drawn.
- Traffic incidents: searching the area.
- Find nearest (optional): your own sites, so each pin says how far it is from yours.
- Show on a map: update the same map each run.
- Optionally Only new and the Email block, so a short message goes out only when a new closure appears.
What you get is a link that stays the same and a picture that does not. Templates to start from: Road closures in my city, Road incidents around the race route for event weeks, and Traffic bulletin for the radio, which turns the same incidents into words every 30 minutes. See also the pages for events and venues and media and publishing.
Questions
How current is the map?
As current as its last run. On a 15-minute timetable the incidents shown are at most about 15 minutes old, plus the time online maps take to show them.
Can I embed the map on our intranet or website?
Yes. A saved map can be shared by link and embedded, and the shared view shows only plain fields for each point. Stop the link at any time.
Can it show only closures near our sites?
Yes. Add your sites, match each incident to the nearest one, and filter by distance before the map.
Does the map show traffic speed as well?
Not by itself. Incidents are closures and roadworks; for speeds and congestion around places, add the Traffic Flow block to the same flow.