On today’s roads, speed limits provide much more value than just regulating how fast vehicles drive. They are a vital component of traffic safety, environmental impact, and the smooth flow of mobility systems. As vehicles become more intelligent and road networks more complex, accurately modeling speed limits requires a precise approach.
Speeding remains a significant contributor to traffic incidents. In 2023, speeding was a factor in 29% of all traffic deaths in the US, resulting in 11,775 fatalities—averaging over 32 lives lost each day. High speeds not only increase the likelihood of crashes due to reduced reaction times and longer stopping distances but also increase the severity of collisions. For instance, a pedestrian struck at 50 km/h faces a 20% risk of fatality, which escalates to 75% at 80 km/h and nearly 92% at 100 km/h.
Developing and implementing appropriate speed limits for navigation systems has demonstrated its effectiveness in improving road safety. NDS.Live provides a robust framework for this purpose, allowing developers to represent both explicit speed limits, such as posted signs and dynamic signals, and region-specific default limits, known as admin speed limits. By integrating these data points, NDS.Live ensures that digital maps reflect real-world traffic regulations accurately, supporting safer and more efficient mobility systems.
Developers working with NDS.Live have two powerful strategies for modeling speed limits at the road or lane level: assigning exclusively explicit speed limits or combining explicit speed limits with admin speed limits. These approaches enable flexibility in how digital maps reflect real-world legal regulations and posted signs—ensuring accuracy across a range of road types, regions, and vehicle categories.
Option 1: Using explicit speed limits
The first strategy relies solely on explicit speed limits. In this approach, speed values—whether based on country-specific driving rules or posted signs—are directly assigned to all relevant road or lane segments. When multiple limits apply, the lowest valid value prevails.
For example, if a country’s default urban speed limit is 50 km/h, this value can be explicitly assigned to all urban roads using the Country Driving Rules attributes. However, if a school area has a posted speed limit of 30 km/h, this lower value would be the priority for navigation system to apply this speed limit. Developers can model this simply by adding the 30 km/h limit to that road section. The system ensures that drivers always adhere to the safest applicable limit.
Another use case involves high-speed buses, considering a motorway where the general speed limit for buses and trucks is 80 km/h. However, special high-speed buses may be allowed to travel at 110 km/h. This can be modeled using special conditions: the 110 km/h limit is applied only when the vehicle type chosen as highspeed bus, while the standard 80 km/h applies in all other cases. On the other hand, heavy trucks receive the 80 km/h limit under any conditions. On motorways without any special use cases, the system simply applies a universal speed limit for buses.
This strategy ensures that all exceptions, special vehicle types, and regional defaults are explicitly handled, allowing precise, context-aware routing and safety assistance to the driver.
Option 2: Combining explicit and admin speed limits
While assigning explicit speed limits across all road segments ensures full clarity, a more efficient approach can be achieved by combining explicit speed limits with admin speed limits. This method reduces redundancy by using admin speed limits—default values based on regional regulations—for standard cases and applying explicit speed limits only where deviations appear.
For instance, if the default urban speed limit in a region is 50 km/h, this value can be set as an admin speed limit in the Region Rules Layer. It applies universally to all urban roads unless explicitly overridden. In the case of a school zone with a posted limit of 30 km/h, this lower value is modeled using an explicit speed limit. Since the system always considers the lowest valid value, the 30 km/h restriction is applied to that road segment.
This strategy supports efficient maintainability and scalability in digital map databases, especially when managing large, region-specific datasets.
A more complex scenario involves high-speed buses. Consider a motorway where the admin speed limit is set at 80 km/h for all buses and trucks. However, special high-speed buses are legally permitted to drive up to 110 km/h. In this case, the 80 km/h limit is treated as a hard admin speed limit, while the 110 km/h limit is applied explicitly with the appropriate vehicle condition: Highspeed public bus.
By leveraging the flexibility of admin speed limits with selective explicit overrides, developers can create precise and efficient speed limit models that reflect real-world driving rules—without overloading the map data.
In some traffic scenarios, fixed speed limits aren’t enough. To manage congestion, reduce noise, or limit emissions, dynamic speed limit signs are increasingly used—especially on major motorways. These signs can adjust permitted speeds in real time based on conditions such as traffic density, weather, or environmental targets.
Let’s look at a practical example based on Austrian road regulations. On Austrian motorways, the default speed limits are:
Now imagine a motorway segment equipped with a dynamic sign that temporarily reduces the speed limit to 100 km/h for all vehicles to cut down on noise and pollution. In this case:
NDS.Live supports modeling these dynamic adjustments by allowing developers to set explicit dynamic speed limits with a Dynamic lifetime layer. This allows us to represent real-time traffic control policies with accuracy. When the dynamic sign is active, its value applies—even if it’s higher than the posted limit. If the dynamic system is inactive, the posted or admin limit acts as a fallback.
This scenario slightly deviates from the general rule that the lowest applicable speed limit always wins. Dynamic signs can legally override posted signs, even if they allow a higher value, highlighting the need for flexible and intelligent modeling that reflects real-world usage.
With these capabilities, NDS.Live makes it easier for developers to handle modern, adaptive traffic systems, ensuring the digital map reflects the reality on the road with precision.
Option 1: Modeling without admin speed limits
In cases where admin speed limits are not used, developers rely solely on explicit speed limits to define valid values for each vehicle type. This approach works well in scenarios where posted or dynamic speed limits are sufficient to represent real-world driving rules, and where simplicity or tight control over the data is prioritized.
Let’s return to the Austrian motorway example with a dynamic sign temporarily lowering the speed to 100 km/h. Even without a posted sign or admin-defined defaults, NDS.Live enables accurate modeling through explicit speed limits. Here’s how the limits would be assigned per vehicle type:
To systematically apply these defaults across a network of roads, NDS.Live lets developers define an attribute map within the Road Rules Layer. For example, in 100 motorway segments, the system explicitly encodes the relevant speed limits for trucks, buses, and other vehicles, ensuring consistent interpretation of legal and contextual speed rules across the digital map.
This approach ensures clarity and full control over how speed limits are defined, without relying on hierarchical admin defaults. Although it may add more data, it gives developers the accuracy they need in areas where road rules are complicated or change often.
Option 2: Admin speed limits combined with explicit speed limits
In more refined implementations, developers can model both admin speed limits and explicit speed limits together to deliver comprehensive and compliant road data. In this approach, admin speed limits define the default legal constraints for different vehicle types, while explicit speed limits are used to capture special conditions, such as dynamic signs or specific road configurations.
Let’s take our example with motorways that have the following admin speed limits:
Now consider that a dynamic speed limit of 100 km/h is displayed on a motorway to reduce noise or emissions. This dynamic speed is assigned as an explicit speed limit. However, because the explicit limit does not include the attribute property, it cannot override any admin-defined lower limit.
As a result, the lowest applicable value for each vehicle type remains valid:
This configuration ensures that legal compliance is respected for all vehicles, while still allowing contextual adaptations via dynamic signs. An attribute map for a particular region in the Region Rules Layer stores these admin defaults, serving as a baseline across all motorway segments.
The dynamic speed limit for the road is provided using the Road Rules Layer. To indicate that this layer contains dynamic speed limits, the lifetime of this layer is explicitly set to Dynamic.
As we see from the examples, NDS.Live provides a robust and flexible framework for modeling speed limits through two main strategies: using only explicit speed limits or combining them with admin speed limits to optimize data efficiency. By supporting region-specific defaults, posted signs, and dynamic limits—along with the ability to model exceptions for vehicle types or road conditions, NDS.Live enables precise and scalable representation of real-world traffic regulations. This ensures that map data remains accurate, up-to-date, and adaptable to diverse mobility applications, from navigation to automated driving systems.
To explore these concepts in more depth and stay aligned with best practices, join the NDS.Live Developer Portal.
Back to news →