BUA_ROAD vs. URBAN - What's the Difference?
BUA_ROAD and URBAN Values Do Not Match for the Same Road Segment v1
====================================================================
KB ID: KB0025919
Classification: Expected Behavior
Decision: UPDATE
Summary
-------
If a road segment has different values for BUA_ROAD and URBAN, this is usually expected behavior and does not automatically indicate a map defect.
BUA_ROAD represents the legal and driving context of being inside or outside a built-up area, primarily based on official built-up area entry/exit signage and related attribution. URBAN represents the map's urban classification derived from Built-Up Area (BUA) polygons and supports urban-context use cases such as cartographic representation, road classification, analytics, routing, and, in some regions, speed-limit related logic.
Because the two attributes are generated from different sources and serve different purposes, they are not required to have the same value on the same road segment.
---
Customer Symptoms
-----------------
Customers may report one or more of the following:
* A road is classified as BUA_ROAD=Yes but URBAN=No.
* A road is classified as URBAN=Yes but BUA_ROAD=No.
* Intelligent Speed Assistance (ISA) behavior does not match the visible urban area on the map.
* Traffic Sign Recognition (TSR) indicates entry into a built-up area while the road appears outside the mapped urban area.
* Routing or speed behavior differs from expectations based solely on map visualization.
* Two nearby roads within the same settlement have different BUA_ROAD and URBAN values.
---
Answer
------
BUA_ROAD and URBAN are independent attributes that describe different aspects of the road environment.
* BUA_ROAD describes the regulatory and driving context associated with built-up area boundaries.
* URBAN describes whether a road is located within a Built-Up Area polygon representing urban development.
As a result, a road can legitimately have different values for these attributes.
---
Root Cause
----------
### BUA_ROAD (Built-Up Area Road)
BUA_ROAD identifies roads associated with a built-up area from a regulatory and driver-assistance perspective.
#### How it is determined
* Primarily based on official built-up area entry and exit signage.
* May use verified attribution where built-up area status has been confirmed through map data processes.
* Supports directional transitions when entering or leaving built-up areas.
* In some situations, attribution may be derived through supporting built-up area information when direct sign verification is not available.
#### Primary uses
* Intelligent Speed Assistance (ISA)
* Traffic Sign Recognition (TSR)
* Advanced Driver-Assistance Systems (ADAS)
* Driving-context interpretation
* Vehicle navigation logic that depends on regulatory road environment information
#### Expected characteristics
* Roads within the same signed built-up area generally maintain continuous BUA_ROAD attribution.
* Major roads and highways can carry BUA_ROAD values when passing through signed built-up areas.
* BUA_ROAD reflects regulatory boundaries and may not match the physical extent of urban development.
---
### URBAN
URBAN identifies whether a road falls within a mapped Built-Up Area polygon.
#### How it is determined
* Derived from Built-Up Area (BUA) polygons.
* Based on the distribution and concentration of buildings and developed land.
* Represents a geographic and cartographic interpretation of urban development.
#### Primary uses
* Map visualization and cartographic representation
* Urban link classification
* Routing and network analysis
* Traffic modeling
* Spatial analytics
* Urban-context applications
* Regional implementations that may use urban classification for speed-limit related logic
#### Expected characteristics
* Roads inside or intersecting a Built-Up Area polygon can be classified as URBAN.
* Urban polygon boundaries are based on development patterns and may not align with regulatory signage boundaries.
* URBAN classification represents urban geography rather than legal driving regulations.
---
Why the Values Can Differ
-------------------------
Differences between BUA_ROAD and URBAN are often expected.
### Scenario 1: BUA_ROAD = Yes, URBAN = No
The road is inside a signed built-up area from a regulatory perspective, but the surrounding development pattern does not place it within a Built-Up Area polygon.
### Scenario 2: BUA_ROAD = No, URBAN = Yes
The road is located inside an urbanized area polygon but is not subject to built-up area signage attribution.
### Scenario 3: Highways Through Urban Areas
A highway may carry built-up area attribution because of regulatory signage while the urban polygon boundary follows a different geographic extent.
### Scenario 4: Polygon-Based Attribution Differences
Where sign verification is unavailable, built-up area attribution and polygon-derived urban classification may not align perfectly because each attribute follows independent business rules.
---
Impact
------
Assuming that BUA_ROAD and URBAN must always match can result in:
* Incorrect defect submissions
* Misinterpretation of ADAS or ISA behavior
* Incorrect TSR investigations
* Routing analysis errors
* Misunderstanding of urban classification behavior
---
Recommended Actions
-------------------
When investigating a potential issue:
1. Verify the BUA_ROAD attribution and any associated verification information.
2. Confirm whether the road is located within a Built-Up Area polygon.
3. Identify whether the customer concern relates to:
* Regulatory driving behavior and vehicle systems, or
* Urban classification and geographic representation.
4. Evaluate BUA_ROAD and URBAN independently before concluding that a map defect exists.
5. Compare the observed behavior against the intended product use case (ADAS, ISA, routing, analytics, visualization, or classification).
---
Expected Behavior
-----------------
* BUA_ROAD and URBAN values differ on the same road segment.
* Built-up area signage boundaries do not match Built-Up Area polygon boundaries.
* ADAS, ISA, and TSR behavior relies on regulatory built-up area information.
* Routing, analytics, or classification workflows use URBAN-based context.
* Urban polygons extend beyond or fall short of signed built-up area limits.
---
Unexpected Behavior
-------------------
* Incorrect or missing built-up area attribution despite verified regulatory information.
* Urban classification that does not follow the applicable Built-Up Area polygon rules.
* Product behavior that contradicts documented use of BUA_ROAD or URBAN attributes.
* Data inconsistencies that violate the applicable map specification.
---
Products Affected
-----------------
* HERE Map Data
* Routing products
* Navigation products
* ADAS-enabled solutions
* Intelligent Speed Assistance (ISA)
* Traffic Sign Recognition (TSR)
* Traffic analytics solutions
* Spatial analytics products
* Map visualization applications
---
Conclusion
----------
BUA_ROAD represents the legal and driving context of being inside or outside a built-up area, primarily based on Start/End settlement signs and intended for ADAS, ISA, TSR, and driving-assistance functions.
URBAN represents the map's urban classification derived from Built-Up Area polygons and may be used for visualization, road classification, traffic modeling, analytics, routing, and other urban-context applications.
The two attributes are independent and are not expected to always have the same value for a given road segment.
---
Keywords
--------
BUA_ROAD, URBAN, Built-Up Area, BUA Polygon, Urban Classification, ISA, Intelligent Speed Assistance, TSR, Traffic Sign Recognition, ADAS, Routing, Traffic Modeling, Spatial Analytics, Urban Link Classification, Road Attributes, Built-Up Area Boundary, Settlement Sign, Navigation, Speed Limits, HERE Map Data
Updated 3 days ago