Occasionally, differences can arise between a road’s actual posted speed, and EROAD’s electronic database of posted speeds, causing drivers to believe they’re traveling within a speed limit when they’re not. In these situations, you can notify EROAD to review a road’s posted speed.
Requesting a Posted Speed Review
Once you have selected an event on a road with what you believe is an incorrect posted speed:
-
Select the
menu in the Event pop-up, and then Request posted speed review. A review drawer opens.
-
In the drawer, fill in the relevant details. Use the comment field to explain why you view this posted speed is incorrect.
-
Submit.
Note: In-cab devices will only receive and act on this update from the time the individual device re-enters the map-tile containing that posted speed.
What happens when a request is made
EROAD gets its posted speed map data from various local and national government agencies, as well as 3rd party stakeholders.
3 days to change…
The above flow outlines what commonly happens:
-
An overspeed event occurs on a road where the driver believes they’re travelling to the posted speed, because that’s what the in-cab device says.
-
The company notifies EROAD of this discrepancy.
-
EROAD checks the appropriate national databases and systems, sends the customer the result of our validation process, and when appropriate, uploads the change to the cloud for distribution.
This process takes about 3 days.
BUT… Each device only updates when in cellular cover…
Your in-cab device is updated over the national cellular network. It might take several more days for an individual device to update its posted speed changes if:
-
your vehicle constantly operates in rural, shielded, or blackout areas
-
the device is unpowered
-
the cellular network suffers an outage
Your in-cab device starts using the new posted speed from the time it updates.
This change is NOT backdated from the date the review request was lodged.
… And devices might not update until you enter a map ‘tile’ a second time.
To reduce data traffic sent to each device, electronic maps are broken up into ‘tiles’ of fairly even data density. (Urban map tiles cover less area because they contain more points of interest, posted speeds and geofences.) When a vehicle enters a tile, that tile is loaded – not the country’s entire map – along with the tile’s posted speeds into the in-cab device.
However, if the vehicle travels through a revised tile, the in-cab device may be prompted to load the new tile, but the vehicle may already be traveling through the outdated posted speed zone before the tile has fully loaded.
How often a vehicle travels through that tile could determine how quickly that posted speed update takes effect.
Finding overspeed events
Posted speed challenges usually occur when drivers are warned – and therefore recorded – exceeding the posted speed limit.
You will be able to locate overspeed events and/or sessions in several ways:
-
Using the Overspeed Events or Overspeed sessions reports. Filtering by date range, vehicle and/or driver focuses your results, and by clicking
on the table of entries. This takes you to the event on the Activity map.
-
Select a vehicle (on the map, or under the Vehicles tab). The Details drawer appears.
-
Select the History tab. The vehicle’s journey history list appears.
-
Use the date filter to select the date/time when a vehicle got the overspeed event.
