How are Posted (Real) Road Speed overspeed events generated

Real Road Speed Overview and Customer Validation Process

Smartrak's Real Road Speed functionality enables accurate monitoring of driver behaviour by comparing vehicle speed against the actual posted speed limit of the road being travelled—not just the general 100 km/h default. This allows for more precise identification of overspeed and underspeed events across all road types.

The system generates GPS-based timer events every 20 seconds, recording key data such as speed, time, and location.

When speed exceeds the posted limit plus a configurable threshold (default 5 km/h), an overspeed event is logged; a return to compliant speed triggers a corresponding "below speed" event.

Due to the 20-second interval between GPS readings, some overspeed events may be missed or slightly misrepresented in duration.

To ensure event validity and reduce false positives caused by GPS bounce or signal distortion, each event undergoes stringent validation checks based on satellite quality, speed change tolerances, and point-to-point speed consistency.

Customers should verify any flagged speeding events by checking that they occur on valid roadways (not off-road or in improbable locations), assessing surrounding environment (e.g., tall buildings or dense terrain), and reviewing event patterns for consistency.

Smartrak advises assessing driver behaviour trends over time rather than relying on isolated events, unless there are instances of extreme or dangerous speeding that warrant further investigation.

Additionally, when reviewing speeding near council-owned facilities, it's important to consider whether the roads are public or private, as this affects the enforceability of posted speed limits.

What is Real Road Speed?

In order to accurately report overspeed and monitor driver behaviour, Smartrak needs to calculate and report Real Road Speed.

Real Road Speed provides the ability to understand when and where drivers are speeding in relation to the road speed of the actual road they are travelling on and not just 100 km/hr roads.  It ensures more accurate reporting of driver behaviour and under / overspeed events.

How do we calculate Real Road Speed?

1. The tracking application detects a trip has started. (key on)

2. Every 20 seconds a location/timer event will be generated. This event contains information like:

   1. Location

   2. Speed

   3. Time

3. The system will perform a real road speed check

   1. If this event is above (or equal to) the posted speed limit + threshold (defaults to 5):

      1. Create overspeed event.

   2. If this event is below the posted speed limit + threshold and the previous event was an overspeed event:

      1. Create below speed event.

Limitations

Event Frequency

Each timer event is generated at a 20-second frequency. This frequency has an impact on a few things:

An overspeed period reports on:

• Start time

• End time

• Distance

• Min speed

• Max speed

Due to the fact that we are using events at 20-second intervals, an overspeed period can inaccurately be reporting an overspeed state for up to 18 seconds.  Periods will only ever be a maximum of 20 seconds inaccurate.

Missing overspeed events

Since we are only taking a snapshot of the speed every 20 seconds the is the possibility of missing an overspeed period entirely if it falls within the 20 seconds between pings.

Speed Validation / GPS Bounce

Every overspeed event undergoes the following speed validation (any events which do not pass all these checks are automatically invalidated):

• Satellite Quality - GPS position from a minimum of 4 satellites to ensure accuracy.

• Changes in speed - Checks GPS speed hasn't increased or decreased by more than 20km/h in the last second.

• Point to Point Speed - GPS speed is within +/- 9km/h of the calculated point-to-point speed, given the previous and current position.

NOTE: Despite all this validation, there is still the possibility for false-positives due to GPS bounce. Please ensure you check for false-positives as detailed later in this document.

Checking for False Positives

Due to the nature of GPS it is important to understand that speeds reported can be inaccurate on occasion. If the GPS satellite coverage is low or the vehicle is in conditions that can affect the signal, the speed can be miscalculated. Taking this into account we advise that people watch for trends in speeding patterns rather than singling out a specific event.

When singling out specific events, please consider the following to ensure their validity and that they aren't false-positives:

• Is the overspeed event on the road?
  If the event is half-way up a hill or on top of a house, then the event was subject to GPS bounce and is not correct.

• Is the overspeed event in a highly built-up area?
  Even if the event is on the road, sometimes a highly built up area will create GPS bounce off tall buildings, trees, canyons and gullies.

• Check the events immediately before and after the overspeed event
  If there is a large jump in speed in a small amount of time, this event may not be correct.

• Does the vehicle have a pattern of overspeeding or high g-force events compared to other vehicles
  Further investigation of vehicle history may be appropriate to ensure the unit is providing accurate data.

Again, Smartrak recommends that overspeed events are viewed as a trend for a driver, rather than individual events. Exceptions to this may include situations where a driver has dangerously exceeded acceptable limits.

If there is a pattern of overspending or high g-force events for individual drivers, further investigation may be appropriate.

A note about enforceability of speed limits on roads leading into council-owned facilities

In New Zealand, the enforceability of speed limits on roads leading into council-owned facilities like golf courses, cemeteries, public gardens, and similar areas depends on the classification and jurisdiction of the road.

1. Public Roads: If the road is a public road, even if it leads to a council-owned facility, it will generally be subject to the same speed limits as other public roads in the area, and those limits can be enforced by the Police or local authorities. Speed limits are typically indicated by traffic signs.

2. Private Roads: If the road is privately owned, such as those within a council-owned facility, the enforcement of speed limits can be more complex. These roads might not have the same legal standing as public roads, but if they are accessible to the general public or serve as an access way to public spaces, there may still be local by-laws or regulations in place to impose certain limits, although these may not always be enforceable in the same way as on public roads.

3. Local Council Bylaws: Local councils can enforce certain rules on their facilities or roads that serve as access ways to those facilities. For example, if a council has set a speed limit in a parking area or a road within a public park or cemetery, that speed limit can generally be enforced by local authorities, though in practice, it might depend on the specific area or situation.

Post speed updates - Australian customers only (June 2025)

We’re now updating posted road speed data every week. This means more accurate speed monitoring, fewer false positives for speed events, and up-to-date road information you can continue to rely on.