xMap data

Traffic incidents

Traffic incidents finds road closures, roadworks and other incidents on online maps, live, where they are right now. Search the Area of interest before it, a list of cities or a circle around a point, and each incident comes back with its kind, its street and district, its position and its icon. Or check around each place that reaches it: every one of your sites gets how many incidents are nearby and the closest one.

In the editor: Road closures, roadworks and other incidents on online maps right now, with where they are. Find them in an area, or count those near each of your places.

Settings

Where

Pick one

Uses the Area of interest block before this one.

Area of interest
Cities Search the cities you type in the next setting.
Around a point Search a circle: a point and a radius.
Around each incoming place

Cities

A list you type

The cities to search, by name. Each one is searched within about 12 km of its centre.

Pick from 51 choices.

Center (latitude, longitude)

Text

The middle of the circle to search, as latitude, longitude.

Radius (m)

A number

How far to look, in metres: around the point, or around each place that comes in.

Needed before the flow can run.

Incidents

Pick one or more

Accidents are reported as road closures for now. A city takes about 2 searches; a big area is searched in up to 8 parts, centre first.

Road closures
Roadworks
Other incidents

What comes out

Each item that leaves the block carries these fields, to use in the blocks after it as {{field}}.

Each incident found

Where is the Area of interest, Cities or Around a point.

name: Its kind and, when known, its street.
category: Road closure, Roadworks or Incident.
street, district: Where it is, found from its position (up to 40 incidents a run).
city: The city or area it was found in.
lat, lng: Its position, to about 150 metres.
accuracy_m: How precise the position is, in metres.
incident_id: Its own ID, the same while it lasts.
image: Its small icon as the map shows it. Maps show it in the pop-up and emails attach it; downloads leave it out.

Around each incoming place

Where is Around each incoming place. Your places go on with two new fields.

incidents_nearby: How many incidents are within the radius.
nearest_incident: The closest one: its kind and how far, in metres.

How to use it

Logistics

Road closures in my city

Every morning, the closures and roadworks in the city before the drivers set off, by email and on a map with each incident’s icon.

Healthcare and emergency services

Nearest ambulance to each accident

Accidents come back as road closures for now, so the flow keeps closures and other incidents; Find nearest adds the nearest ambulance to each.

Delivery apps

Warn the drivers at each depot

A grocery delivery company has twelve depots across the city and wants each depot manager to know about any closure within 2 km before the vans leave at 06:00.

Before: Drivers found the closure when they reached it, and called the depot.

With the flow: At 05:30 each depot with a closure nearby gets a message naming it and how far it is.

Government and cities

A daily roadworks log for the city

A city’s roads department wants a record of every roadworks site seen each day, to compare with the permits it gave.

A large drawn area is searched in up to 8 parts, centre first; each site lands in the sheet with its street and district.

Field service

Closures near today’s appointments

Each job comes back with incidents_nearby and nearest_incident, so the dispatcher sees which visits may run late.

Real estate

Roadworks around our sites

Long roadworks next to a shop or a showroom cut its visitors; the weekly count shows which sites are affected.

Events and hospitality

Before the doors open

An events company wants to know, two hours before each show, whether roads near the venue are closed so it can warn ticket holders.

Before: Guests arrived late and blamed the organiser.

With the flow: The team posts a road update to ticket holders before they leave home.

Good to know

Incidents are read live from online maps, with a position to about 150 metres. Accidents are reported as road closures for now; a kind the map has no icon for comes back as Incident.
A city is about 2 searches. A large area is cut into parts of about 24 km and searched centre first, up to 8 parts a run; the step says when an area was only partly covered. Several smaller areas are better than one huge one.
Around each incoming place: places within about 25 km of each other share one search, and up to 5 such groups are checked in a run.
Street and district names are added to the first 40 incidents a run; the rest keep their kind as the name.
Put Only new after it to hear only about incidents that appeared since the last run (each keeps its incident_id while it lasts).
Credits: for each area searched, not for each incident, as shown at the top of the page.

Works well with

Area of interest: Sets where the flow looks: countries, cities or specific places, or areas you draw on a map.
Find nearest: For each place, finds the nearest of your own points from a CSV you upload, for example the nearest ambulance to each accident or the nearest branch to each new lead, and adds its name and the distance.
Filter: Keeps only the items that match a rule.
Only new: Lets through only the items this flow has not found before, so a daily flow sends only what is new.
Show on a map: Shows the results as points on a map, with the area of interest.
Email: Sends one email per run with all the items, or one email per item.
Slack: Channel-based messaging platform
My data: Brings in a table you uploaded or a list you saved on the My data page: your stores, customers, target accounts or sites.

Templates that use it

Nearest ambulance to each accident: Every accident in your city matched to the nearest of your ambulances, every hour.
Road closures in my city: Road closures and roadworks in your city, every morning.
Score every neighbourhood for a new branch: Every block of your city scored for a new supermarket, the 20 best on a map.
Monthly satellite pictures of my projects, with a site note: The latest satellite picture of each of your construction sites, every month.
Roadworks and closures near my projects: Road closures and roadworks near each of your sites, every morning.
Road closures near my depots, every hour: Closures and roadworks near each depot every hour, to dispatch on WhatsApp.
Incidents near my drivers’ zones: Incidents near your drivers' zones every 15 minutes, to dispatch.
Where to put micro-fulfilment hubs: Where to put micro-fulfilment hubs: most people per warehouse first.
Road and weather chat for my drivers: A chat for drivers: closures, roadworks, the weather and the nearest fuel or truck stop where they are going.
Weekly road disruption report: A weekly road disruption report across your cities, for ops managers.
Incidents and the people they affect: Road incidents and how many people live around each, every morning.
New roadworks and the residents affected: New roadworks this week and the residents affected.
Expansion committee pack, every month: A monthly expansion committee pack: every block scored, the best 20 investigated, approved, mapped.
Daily operations briefing for every hub: A daily operations briefing per hub, with a risk score and alerts for the risky ones.
Weekly city safety report: A weekly city safety report: incidents, people affected, hotspots investigated, actions.
Approved garage network for my claims team: Garages vetted by an AI agent and scored for your claims network, approved every month.
Storm and outage helpline chat for my customers: A chat that tells customers the weather and road incidents around them in a storm or outage.
Morning site briefing: weather and road closures: A morning briefing for each site: pours and lifts to avoid, heat precautions and road closures.
Tower field visits around weather and closures: A daily visit plan for every tower around closures and weather, sent to your work order system.
Road closures near my schools before the buses leave: Road closures near your schools sent to bus drivers before each run.
Where growers need a cold store: Grower areas with the fewest cold stores, scored for a packhouse, approved.
Road closures near the courts before hearings: Closures and roadworks around every court you attend, on WhatsApp at 6:30.
Accident hotspots for road safety awareness: Where road incidents cluster each week, with the people around them.
Traffic bulletin for the radio, every 30 minutes: A ready-to-read traffic bulletin every 30 minutes in the rush hours.

And 48 more in the template gallery.

Stories with it

Twelve fair routes before the officers leave (Microfinance)
Forty school buses, no surprise road closures (School transport)
Roadworks cleared before sixty thousand fans arrive (City traffic)
The council that answers residents in seconds (Local government)
Ask before every school trip, answered in Teams (Secondary school)
Every dialysis patient in the chair on time (Patient transport)
Trusting the road, not doubting the driver (Car insurance)
Every roadworks claim made on time (Insurance broking)
Five riders who never sit in a closed road (Courier services)
Three hundred farms, and no tanker turned back (Dairy cooperative)
Never driving into the wind again (Telecom field services)
No shift late, whatever the roads do at dawn (Airline ground handling)

Help articles

Traffic incidents and road closures: Closures and roadworks in an area or near each of your places.
The map: everything your AI employees found: Results, Map: every result as layers on one map, with filters, a time slider, a card for each result and Compare sites.

Guides and terms

How to monitor road closures near your sites: Every few minutes, the incidents that affect your sites or fleet.
Reverse geocoding: Turning coordinates into a street, district or address.

Try it

Build a flow with Traffic incidents on the home page, no account needed, or book a call. Try it live