15. -15-
高精度地图数据及应用
自动驾驶与高精地图标准组织和协议标准
标准组织 标准协议
OADF SIP-adus Dynamic Map Specifications for Dynamic Map
Field Operational Tests
NDS Navigation Data Standard
Open Lane Model 1.0
ADAIS Advanced Driver Assistance Systems Interface Specification
TISA Traffic Message Channel （TMC）
Transport Protocol Experts Group（TPEG）
SENSORIS Sensor Ingestion Interface Specification
TN-ITS TN-ITS CEN TS 17268
ISO ISO/TC204 22726：Dynamic events and map database specifications for applications of
automated driving systems, cooperative ITS, and advanced road/traffic management
systems
20524 :Geographic Data Files – GDF5.1
21. -21-
(一)基本概念
数据架构
ROOT
Product Databases
Update Regions
Building Blocks
Levels
Contents
An NDS database may consist of several product databases, and each product database may be
divided further into update regions. This concept supports a flexible and consistent versioning
concept for NDS databases and makes it possible to integrate databases from different database
suppliers into one NDS database. The inner structure of databases complying with NDS is further
characterized by building blocks, levels and the content itself.
Each product database is delivered by one database supplier, has its own version control and can
therefore be updated independently from other product databases.
The geographic area of a product database is partitioned into one or more update regions. An
update region is a geographic area of a product database that may be subject to a regional update.
The geographic area of an update region can be further divided into several update areas.
All navigational data is regarded as belonging to a specific building block. Each building block
addresses specific functional aspects of NDS, such as names for location input or map display data.
The data of some building blocks is partitioned into different levels. The higher the level, the larger
are the partitions in terms of spatial size, which is at least partly compensated by lower spatial
density or reduced content.
The following types of data contents are distinguished in the database:
• Features: All real-world objects relevant for a navigation system are represented by one or
more features and can be represented on one or more levels.
• Attributes: Attributes describe the specifics of the different features.
• Metadata: Metadata contains information on variable database content and database
properties. It can refer to data of a specific product database, a building block, or the
complete database.
25. -25-
(一)基本概念
分幅/层级(Partitioning/Levels)
Features are assigned to exactly one tile. They do
not cross tile borders.
Features have geometries that extend over more
than one tile. NDS uses a clipping mechanism to
describe the geometry of these features.
26. -26-
(一)基本概念
数据内容（Database Contents）
数据库中存着三种类型的数据内容：
■ Features（要素）: All real-world objects relevant for a navigation
system are represented by one or more features and can be represented
on one or more levels.
■ Attributes（属性）: Attributes describe the specifics of the different
features.
■ Metadata（元数据）: Metadata contains information on variable
database content and database properties. It can refer to data of a
specific product database, a building block, or the complete database.
Fixed attributes are mandatory
information that describe and
define a feature. They are
stored with each feature and
always store a value. Fixed
attributes are coded compactly
because the attribute-value
structure is predefined within
the feature class. An example
of a fixed attribute is the link
type.
Flexible attributes are additional or exceptional
information about a feature. They are stored as
attribute maps with a tile and may be assigned
to one or multiple features in the tile.
■ Optional information is available in the source
data. The compiler may use flexible attributes to
assign this information to features. An example
of an optional flexible attribute is a speed limit.
■ A real-world situation requires additional
information. To model the situation, a flexible
attribute must be assigned to a feature. An
example of such a mandatory flexible attribute is
the transition mask of an intersection if there is
at least one turn restriction.
Attributes
(属性)
Fixed Attributes
(固定属性)
Flexible Attributes
(灵活属性)
Attribute Groups
(属性组)
组合为
分为
Attribute Maps
(属性映射)
Features
(要素)
拥有
含有
关联
27. -27-
(一)基本概念
灵活属性和属性映射（Flexible Attributes and Attribute Maps）
Attribute Type Reference:
1) Attribute Type Codes
2) Reference Type
Attribute Map
1) Attribute Map Type
• VALUES_TO_ONE_FEATURE
• VALUES_TO_MANY_FEATURES
• VALUES_TO_ALL_FEATURES
2) Attribute Map
• Attribute Values
• Feature Reference
28. -28-
(一)基本概念
属性组（Attribute Group）
Traffic Regulation
A lane is only allowed to be used by school busses, public busses, and bicycles from Monday to Friday between
7:30 am and 9:30 am and between 4:30 pm and 6:30 pm. At all other times, the lane is open for all traffic.
PRIMARY Attributes
Attributes that may be used standalone or as the leading attributes of
an attribute group. The leading attribute represents the regulation that
the attribute group describes.
SECONDARY Attributes
Attributes that must be grouped with a primary attribute. Secondary
attributes specify the conditions under which the regulation applies.
Within one attribute group, the list of secondary attributes shall be
ordered by the numeric value of the attribute type code.
isInclusive
NDS uses the isInclusive flag to invert
a condition expressed in a secondary
attribute.
Rules for Attribute Groups
■ The primary attribute shall
be the first attribute within a
group. The list of secondary
attributes shall be ordered by
the numeric value of the
attribute type code.
■ Conditions expressed by
secondary attributes shall
evaluate to TRUE or FALSE.
■ The truth values of attribute
groups are combined with OR.
Within an attribute group,
the truth values of the
secondary attributes are
logically combined with AND
after the isInclusive flag has
been applied. The result is the
truth value of the group.
■ Attribute groups shall not be
nested.
29. -29-
(一)基本概念
形状点、属性点及有效区间（Shape Points、Attribute Points and Validity Ranges）
VALIDITY_RANGE
An attribute group shall not contain more than one
VALIDITY_RANGE attribute. Because the truth values of
secondary attributes are logically combined with AND, a shape
point would have to lie within all specified validity ranges.
30. -30-
(一)基本概念
可加载数据（Loadable data）
Loadable data
• To support features that require high-volume data, NDS provides the loadable data concept. The high-volume data is stored as an NDS product in the cloud.
Only small parts of the data are transferred to the navigation system on demand. The navigation system can cache loadable data to avoid redundant transfer
over the air and to bridge connection gaps.
• Loadable data shall not modify or update preinstalled NDS data. Preinstalled map data shall only be modified by NDS updates.
• Loadable data shall not be used for continuously or temporarily changing information, for example, fuel prices or short-term speed limits related to moving
construction sites. NDS provides the volatile data concept for continuously changing data.
32. -32-
(二)Volatile Data Building Block
功能场景
The Volatile Data building block contains volatile data, which is subject to frequent changes. For example,
fuel prices at gas stations or variable speed limits change many times a day.
Due to the frequent changes, volatile data needs to be updated at shorter intervals than with regular
updates. Volatile data is not versioned, but contains a start time, time stamp, and expiration date.
Navigation systems can use this information to determine whether a volatile item is still valid.
Example: Volatile Speed Limits
35. -35-
(三)Routing Building Block
功能场景
■ Route calculation
The Routing building block contains a topological representation of the road network for route calculation. Route
calculation has to find a route from a given start position to a given destination position using the data structures of
the Routing building block.
■ Map matching
The Routing building block contains road geometry data for map matching. Map matching derives the current
vehicle position from a raw position that is delivered by GPS or other sensors. The position is then matched to the
digital map represented in the Routing building block.
■ Route guidance
Road topology and road geometry data is necessary for route guidance. Route guidance checks the current vehicle
position against the calculated route and derives maneuver descriptions.
■ Advanced driver assistance (ADAS)
ADAS is supported by an additional attribute layer within the Routing building block. The layer contains an
extended set of attributes, such as curvature, road width, and slope. Additional attribute points attach attributes
with high positional accuracy to road geometry.
The Routing building block is a core building block. There shall be
only one instance of the Routing building block in an update region.
37. -37-
(三)Routing Building Block
内容（Contents）
1
Routing tiles
Contains data that is relevant for route
calculation.
For example: intersections, and routing-
relevant attributes, such as transition
masks.
Routing geo tiles
Contains data that is not relevant for
route calculation, but only relevant for
route guidance, map display, and map
matching.
For example: Z level information, road
geometry lines, shape point lists,
references from links to road map lines.
truckAttributeLayer
Contains attributes for traffic restrictions for
truck vehicle types.
For example: limitations of vehicle height and
road width.
guidanceAttributeLayer
Contains attributes for maneuvers, right-of-way,
and traffic lights. It also contains
signpost attributes, lane attributes, and toll
attributes required for route guidance
applications. This layer is only used on level 13
and it is stored in the routing geo tile.
nameAttributeLayer
Contains attributes for assigning names to
routing features.
adasAttributeLayer
Contains attributes for geometric properties of
roads and lanes, such as curvature, slope, road
width, and lane width.
volatileAttributeLayer
Contains attributes for volatile data, such as
volatile speed limits.
38. -38-
(三)Routing Building Block
Link、Base Link和Routing Link
(一) A link describes a road segment between
two intersections. It represents a road or a
carriageway. Carriageways of a controlled
access road or other dual-carriageway roads
are represented by a separate link for each
carriageway.
(二) Splitting Links: Road features intersecting
tile borders shall be split according to the NDS
tiling scheme and according to the rules that
apply to routing features.
39. -39-
(三)Routing Building Block
Base Link存储结构
RoutingTileTable RoutingAuxTileTable
Tile:545555100 Tile:545555100
shapePointType
Indicates whether a link is a
route link or a base link with or
without geometry
information.
shapePoints
Defines the geometry of a base
link by a list of shape points.
Geometry information is not
stored in a shape point list if
the base link consists only of a
start and an end point
connected by a straight line.
scaleSublevel
Specifies the recommended
scale sublevel for rendering the
base links.
attrSource
Specifies the recommended
scale sublevel for rendering the
base links.
40. -40-
(三)Routing Building Block
Route Link存储结构
RoutingTileTable RoutingAuxTileTable
Tile:545554860 Tile:545554860
Tile:545554855 Tile:545554855
A route link is always stored in the tile
that contains the link's start point.
Road Geometry Line Feature
If the link is a route link, then the
road geometry of the link is defined
in the road geometry lines. Road
geometry lines are also stored in the
routing geo tile.
41. -41-
(三)Routing Building Block
Link固定属性 (Fixed Attributes of Link Features)
Data structure Description
priorityRoadClass Classification of a road.
Lower values stand for higher road classes. 0 is always the highest road
class, for example, motorway. The meaning of the individual values 0...15 is
country-specific. A company compiling a database is responsible for
mapping the classification scheme of the data provider to the 15 classes.
linkType Properties of a link or road geometry line that are used for guidance
purposes.
For example: ramp, part of a roundabout, part of a road parallel to a
controlled access road, a traffic square, or a pedestrian zone.
travelDirection Indicates whether the road represented by the link or road geometry line is
traversable and in which direction.
If the travel direction is set to IN_NO_DIRECTION, the road is
either closed or conditionally closed in one or both directions.
ferry
tunnel
bridge
Indicates whether the link or road geometry represents:
■ Part of a ferry connection
■ Part of a tunnel or a bridge
toll Indicates if the link or road geometry line represents a toll road or has a toll
booth.
The attribute contains the direction for which toll must be paid.
controlledAccess Indicates if the link or road geometry line represents a controlled access
road, for example, a motorway or freeway.
serviceArea Indicates if the link or road geometry line represents a road that leads to or
from a service area or is part of a service area. Examples of service areas:
motorway rest area, parking facility, golf course.
To distinguish between parking and non-parking areas, the flexible attribute
PARKING is assigned to links that contain parking facilities.
Data structure Description
functionalRoadCl
ass
Importance of a road within the network. Lower numbers indicate higher
importance. Higher numbers indicate lower importance.
urban Indicates whether a road is located in an urban, built-up area. For example,
applications can use this information to determine the legal speed limit or to
calculate routes that avoid city areas.
complexIntersecti
on
Indicates whether the link or road geometry line belongs to a complex
intersection. A complex intersection is composed of connected links that
the application shall handle as one unit for guidance and routing. Every
route between two complex intersections shall contain at least one link with
the fixed attribute complexIntersection set to FALSE.
pluralJunction Indicates that a maneuver may require different guidance than implied by
the geometry
motorway Indicates that the link or road geometry line is part of a motorway.
Data structure Description
averageSpeed Average speed of cars in normal traffic flow.
The compiler calculates the value for the average speed based on
information from the input data.
startAngle
endAngle
Angle for the start and end of a link.
The angles are stored in 64 sectors, with the first sector starting from north
in clockwise direction. This attribute is used to calculate costs for turns in
route calculation.
length Length of a link in centimeters
The value shall be greater than zero.
(1)Fixed attributes for links and road geometry lines in nds.common.fixedattributes >
SharedRoadAttributes
(2)Fixed attributes for links and road geometry lines in nds.common.fixedattributes >
RoutingRoadAttributes
(3)Additional fixed attributes of link features in nds.routing.link > Link
42. -42-
(三)Routing Building Block
Link类型举例（1）
Pedestrian Zone
■ linkType = PEDESTRIAN_ZONE
describes a zone that is mainly used by pedestrians. Access for
cars is modeled by the fixed attribute travelDirection and
the flexible attribute PROHIBITED_PASSAGE
Link for Pedestrian Use Only
■ linkType = PEDESTRIAN
describes a link for pedestrian use only.
The flexible attributes PEDESTRIAN_LINK_TYPE and
PEDESTRIAN_LINK_LOCATION may be used to model detailed
link properties.
If access for cars is permitted under specific conditions, then
prohibited passage is modeled by the fixed attribute
travelDirection and the flexible attribute PROHIBITED_PASSAGE.
Paved Area
■ linkType = SQUARE
describes paved areas where cars are allowed to drive, but
which do not have legally defined traffic patterns.
Roundabout
■ linkType = ROUNDABOUT
describes a circular intersection with traffic flow into one
direction only and a central island.
Special Traffic Figure
■ linkType = SPECIAL_TRAFFIC_FIGURE
describes a closed circular, ellipsoidal, or rectangular
construction of roads that is not recognized as a roundabout
because one or more roads are located inside or run through
the construction and are accessible for personal cars.
The travel direction may differ from that of a roundabout, for
example, clockwise for righthand traffic, or even partly in both
directions.
Controlled-Access Road (not Motorway)
■ linkType = NO_SPECIAL
■ controlledAccess = TRUE
■ motorway = FALSE
describe roads with regulated traffic flow and entries/exits that
are not officially classified as motorways.
43. -43-
(三)Routing Building Block
Link类型举例（2）
Motorway
■ linkType = NO_SPECIAL
■ controlledAccess = TRUE
■ motorway = TRUE
describe motorways with regulated traffic flow and regulated
entries and exits.
This link type shall not be used for entries, exits, or roads
parallel to motorways.
Ramp between Two Motorways
■ linkType = RAMP
■ controlledAccess = TRUE
■ motorway = TRUE
describe roads that connect entries and exits between
motorways. In Asian navigation systems, this type of
interchange is called JC.
Ramp between Different Grades and between
Controlled-Access Road and Non-
Controlled-Access Roads
■ linkType = RAMP
■ controlledAccess = FALSE
■ motorway = FALSE
describe roads that connect two roads at different grades or
that represent entries and exits between controlled-access
roads and non-controlled-access roads. In Asian navigation
systems, this type of entry/exit from controlled-access roads
is called IC.
Road Parallel to a Motorway
■ linkType = PARALLEL
■ controlledAccess = TRUE
■ motorway = TRUE
describe roads that start or end at a motorway or run
parallel to a motorway.
Slip Road
■ linkType = SLIP_ROAD
■ controlledAccess = FALSE
■ motorway = FALSE
describe roads that connect two roads at the same grade.
Service Area
■ linkType = NO_SPECIAL
■ serviceArea = TRUE
■ controlledAccess = FALSE
■ motorway = FALSE
describe roads that lead to or from a service area or are
part of a service area. Examples of service areas:
motorway rest area, parking facility.
44. -44-
(三)Routing Building Block
Link类型举例（3）
Service Road
■ linkType = SERVICE_ROAD
describes roads that run parallel to a major road that usually
has a higher priority road class.
Service roads can be used for access to the areas around
the major road. Also known as frontage roads.
Link Defining Borders or Boundaries
■ linkType = BOUNDARY
■ priorityRoadClass =0
■ travelDirection = IN_NO_DIRECTION
be used to model a link that defines the border of a region
or the boundary around an area, for example, a country or a
parking area. The compiler adds these links to the routing
data. They do not correspond to roads in the real
world or in the source data.
45. -45-
(三)Routing Building Block
路口（Intersection Feature Class）
⚫ An intersection represents a road junction where two or more roads meet or cross.
An intersection is also used to model the end point of a dead-end road. Two roads
that cross each other but are not connected topologically do not form an intersection.
⚫ Intersections may connect multiple base links and route links. An intersection is
represented by exactly one point in the road network.
⚫ Intersections are characterized by the following main properties:
• Position：Each intersection has a pair of coordinates defining the intersection's
geographic position relative to the center of its tile.
• Transitions：NDS uses the concept of transitions to model the way from one
link to another through an intersection. Transitions represent the topological
connection of links through intersections.
• Number of links：This property specifies how many base links and/or route
links are connected to an intersection.
• Fixed and flexible attributes：Examples of flexible attributes for intersection
features are the TRANSITION_MASK_* attributes that indicate allowed and not
allowed driving maneuvers at intersections. Also, name references are modeled
by flexible attributes.
• References to other routing features：An intersection always references at least
one base link or route link that is connected to it. The intersection represents
either the link's start or end point, depending on the link direction.
46. -46-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(1) Using Transition Masks
TRANSITION_MASK_2_4_VAL is assigned
Allow the transition between
fromLink 2 and toLink 2
The left turn maneuver on link 3 is not allowed between 4 pm and 6 pm.
■ Bit in transition mask is set to 0 (CLOSED).
■ The transition mask attribute TRANSITION_MASK_2_4_VAL with
value 63487 is assigned to the intersection (binary representation:
1111011111111111).
■ The conditionally not allowed left turn maneuver ("Left turn not
allowed between 4 pm and 6 pm") is modeled by an attribute group
with the flexible attributes PROHIBITED_PASSAGE and
TIME_RANGE_OF_DAY, which is assigned to the respective
transition of the intersection. The attribute reference type is
ROUTING_SIMPLE_INTERSECTION_TRANSITION.
47. -47-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(2) Using Special Transition Codes
■ One road that splits up into two or more roads, where the main road
bends slightly and a side road of minor importance leaves the intersection
straight ahead. Because the side road is of minor importance, the guidance
instruction may be suppressed. The driver would consider the main road to
go straight ahead and expect a turn instruction for the side road.
■ To enable guidance instructions for such cases, the compiler shall assign
the flexible attribute SPECIAL_TRANSITION_CODE to the transition. If a
guidance instruction applies to a sequence of several links, then the
compiler shall assign the flexible attribute
SPECIAL_TRANSITION_CODE_PATH to the first link of the sequence.
■ Shows a transition for which an application cannot easily derive a
guidance instruction. Because of the small angle between links 3 and 4,
which leave the intersection, the transitions 2 > 3 and 2 > 4 are difficult to
distinguish.
■ For a vehicle on path 1 > 2 > 3 along the main road, the guidance
instruction for the second transition can be suppressed by storing a special
transition code for the complete path. The compiler shall assign
SPECIAL_TRANSITION_CODE_PATH with specialTransitionCode =
ALONG_MAIN_ROAD to link 1.
48. -48-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(3) Using Turn Penalties for Transitions
■ On level 13 of the Routing building block, the application can evaluate the
properties of links and intersections, such as angle and transitions, to determine the
route costs. However, not all of this information is available on upper levels, so that
the penalty for routes on upper levels could be different.
■ To avoid that routes calculated on upper levels of the Routing building block differ
from routes calculated on level 13 due to different costs, NDS provides the flexible
attribute TRANSITION_DURATION. The attribute defines the average duration in
seconds that a vehicle needs to drive the transition between two links. The attribute
may be assigned to links, simple intersections, and simple intersection transitions.
■ When the compiler assigns the attributes to features on upper levels, it shall sum
up the transition durations from all corresponding lower-level features. In this way,
the information about penalties is available on the upper levels as well and can be
considered in route calculation.
49. -49-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(4) Modeling Turn Restrictions
■ Prohibited turn maneuvers across an intersection, also called turn restrictions, may
cross tile borders. To enable the application to find the links that belong to a turn
restriction, NDS provides the flexible attributes CONTINUED_TURN_RESTRICTION
and BACKWARDS_CONTINUED_TURN_RESTRICTION.
■ These flexible attributes are used to model prohibited turn maneuvers for three or
more consecutive links. The attributes contain a list of directed references to links that
must not be traveled in the given sequence. CONTINUED_TURN_RESTRICTION is
provided for forward routing; BACKWARDS_CONTINUED_TURN_RESTRICTION for
backward route searches.
■ The attributes are assigned to the first and the last link of a sequence of links with a
turn restriction. The following rules apply:
• CONTINUED_TURN_RESTRICTION shall be assigned to the first link of the
sequence.
• BACKWARDS_CONTINUED_TURN_RESTRICTION shall be assigned to the
last link of the sequence.
• The reference direction shall be identical in both lists of directed link
references. The directed link to which the turn restriction attribute is assigned
shall not be contained in the list of link references.
50. -50-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(5) Modeling Right Turns on Red
In Germany，turning right
on red is prohibited by default
In USA，turning right
on red is permitted by default
■ The flexible attribute TURN_ON_RED_ALLOWED may be used to model regulations
for turning right at a traffic light showing a red signal.
■ In countries, where turns on red are permitted by default, the attribute is set to TRUE in
the region metadata. To prohibit turns on red at specific intersections, the flexible
attribute is assigned to the corresponding transitions with the value FALSE.
■ In countries, where turns on red are prohibited by default, the attribute does not need
to be set in the region metadata. Absence of this attribute means that turns on red are
prohibited by default. To permit turns on red at specific intersections, the flexible attribute
is assigned to the corresponding transition with the value TRUE.
51. -51-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(6) Modeling Permitted U-Turns
■ To allow applications to consider permitted U-turns in route cost calculation, NDS provides the flexible attributes PREFERRED_U_TURN_FLAG,
PREFERRED_U_TURN_PATH, and BACKWARDS_PREFERRED_U_TURN_PATH.
■ For turns protected by traffic lights: NDS provides the flexible attributes PROTECTED_TURN_TRAFFIC_LIGHT, PROTECTED_TURN_TRAFFIC_LIGHT_PATH, and
BACKWARDS_PROTECTED_TURN_TRAFFIC_LIGHT_PATH.
■ For unprotected turns that need to be announced: NDS provides the flexible attributes ANNOUNCE_UNPROTECTED_TURN and
ANNOUNCE_UNPROTECTED_TURN_PATH.
■ The compiler shall assign PREFERRED_U_TURN_FLAG to a link or transition at which a Uturn is permitted by signposts or road markings.
■ To model permitted U-turn maneuvers across complex intersections:
• PREFERRED_U_TURN_PATH shall be assigned to the first link of the sequence. The attribute contains the sequence of links forming the U-turn path as directed
link references. The first link of the sequence shall not be listed in the attribute.
• BACKWARDS_PREFERRED_U_TURN_PATH shall be assigned to the last link of the sequence. The attribute contains the sequence of the links forming the U-
turn in reverse order as directed link references. The last link of the sequence shall not be listed in the attribute.
52. -52-
(三)Routing Building Block
路口过渡和转向（Modeling Transitions and Turns）
(7) Modeling Roundabouts with Middle Traversal
■ For roundabouts that offer the possibility to drive through the middle, the flexible attribute
ROUNDABOUT_INTERIOR can be assigned to the link traversing the roundabout.
Flexible attribute assigned to the:
Solid line: ROUNDABOUT
Dotted line: ROUNDABOUT_INTERIOR
53. -53-
(三)Routing Building Block
复杂路口和汇合处（Complex Intersections and Plural Junctions）
(1) 概念
Complex intersection Plural junction
Composed of connected links that the application shall handle as one
unit or guidance and routing
Attribute of links
Multiple links that belong to one real-world complex intersection, for
example, a controlled access intersection.
Guidance attribute in order to suppress guidance instructions at a
transition from one link to another. If the destination link has a plural
junction attribute assigned, then the application aggregates or
suppresses guidance instructions according to the plural junction type.
54. -54-
(三)Routing Building Block
复杂路口和汇合处（Complex Intersections and Plural Junctions）
(2) 汇合处类型
■ pluralJunctionType=INTERSECTION_INTERNAL: Indicates that a link should not
be treated as an individual part of the road, but as a part of the intersection.
guidance announcement is only given beforethe first link flagged as
INTERSECTION_INTERNAL and suppressed for all following links flagged in the
same way.
■ pluralJunctionType=MANOEUVRE: Indicates that only one guidance
announcement is given right before the link is entered, but not when leaving the link,
because there is only one legal possibility to leave the link.
■ linkType=ROUNDABOUT, pluralJunctionType=INTERSECTION_INTERNAL:
Indicates that a link should not be treated as an individual part of the road, but as a
part of the roundabout.
■ linkType=NO_SPECIAL, pluralJunctionType=MAGIC_ROUNDABOUT: Indicates
that a link connects inner roundabouts within a complex roundabout.
55. -55-
(三)Routing Building Block
复杂路口和汇合处（Complex Intersections and Plural Junctions）
(3) 汇合处类型
■ pluralJunctionType=INDESCRIBABLE: Indicates a maneuver that cannot be
explained in one guidance announcement or at all. Examples: Indirect left or right
turns.
56. -56-
(三)Routing Building Block
复杂路口和汇合处（Complex Intersections and Plural Junctions）
(4) 复杂路口和复杂封闭路口
■ complexIntersection=TRUE, COMPLEX_INTERSECTION_TYPE is not assigned: standard complex intersection
■ complexIntersection=TRUE, COMPLEX_INTERSECTION_TYPE=CONTROLLED_ACCESS_INTERSECTION: controlled-access complex intersection
■ complexIntersection=TRUE, COMPLEX_INTERSECTION_TYPE=COMBINED_INTERSECTION: A combined intersection is a controlled-access intersection that
contains one or more standard complex intersections.
• A complex intersection that contains parts marked as combined intersections can be used to provide guidance on different levels of detail. For example, an
application can use the flag CONTROLLED_ACCESS_INTERSECTION to provide a single guidance advice across the whole intersection in a guidance
overview.
• Links with the flag COMBINED_INTERSECTION are part of the controlled-access intersection and additionally a separate standard complex intersection. The
application can provide detailed guidance advice when driving through the separate complex intersection.
57. -57-
(三)Routing Building Block
更新区域边界Link和转向处理方式(Handling Links and Transitions at Update Region Borders)
(1) Duplicate Features at Update Region Borders
■ If a real-world feature, such as a road or an intersection, is located on the update region border, then the compiler shall ensure that this feature is represented by
corresponding NDS features in each update region. Example: A road on the update region border shall be represented by two links, one in each update region. Duplication
of features enables routing and guidance across update region borders.
■ Intersections at update region borders are also duplicated and stored in both update regions because gateways are represented by intersections.
■ The duplicate features shall be assigned the flexible attribute GATEWAY. Intersections or links representing the same junction or road in reality shall have the same
gateway ID. In this way, applications can identify the features that belong to each other and merge them at runtime.
■ At the start and end of duplicate links, there shall be intersection gateways.
■ If a link is located on an update region border, then each of its flexible attributes is split. The compiler shall assign the flexible attributes to each duplicate link in travel
direction only. The duplicate links may be assigned different attribute values in the update regions. Examples are the values for the attributes
NAMED_OBJECT_REFERENCE, HOUSE_NUMBER_RANGE, or TMC_LOCATION.
58. -58-
(三)Routing Building Block
更新区域边界Link和转向处理方式(Handling Links and Transitions at Update Region Borders)
(2) Modeling Transitions across Intersections at Update Region Borders
■ To support guidance across intersections at update region borders,
the compiler creates stubble links at intersections to indicate that the
transition continues in the neighboring update region.
■ The stubble links are placeholders for the links that are connected
to the intersection, but are located in the neighboring update region.
The links connected to an intersection are modeled completely in one
update region only. The stubble link enables applications to find the
fully modeled link in the other update region and to provide guidance
across the intersection. To model a stubble link, the compiler
proceeds as follows:
• The compiler duplicates the links that belong to an
intersection at an update region border, but are located in one
update region only. Links that are completely located and
modeled in the neighboring update region are created as
stubble links in the current update region.
• Stubble links are assigned the flexible attribute STUBBLE.
Stubble links shall have the same geometry as the original
links. Shape points, start and end intersections shall be
identical.
• The completely modeled link and the corresponding stubble
link are assigned the flexible attribute GATEWAY with the
same gateway ID. No additional flexible attributes are
assigned to the stubble links.
59. -59-
(三)Routing Building Block
更新区域边界Link和转向处理方式(Handling Links and Transitions at Update Region Borders)
(3) Modeling Path-dependent Transitions at Update Region Borders
■ To enable guidance for path-dependent transitions at update
region borders, the compiler creates a network of stubble links and
intersection gateways. This network indicates that the transition
continues in the neighboring update region.
■ The stubble links are placeholders for the links that are part of
the complex intersection, but are located in the neighboring update
region. The links connected to an intersection are modeled
completely in one update region only.
■ The network of stubble links and intersection gateways enables
applications to find the fully modeled features in the other update
region and to provide guidance across the intersection.
■ Features of a complex intersection that are completely located
and modeled in the neighboring update region are treated as
follows:
• Links are created as stubble links in the current update
region.
• Intersections are created as gateways in the current
update region.
60. -60-
(三)Routing Building Block
路标建模(Modeling Signposts)
(1) Flexible Attributes for Signposts:
Flexible Attributes
for Signposts
SIGNPOST VALIDITY_RANG LANE_MASK
SIGNPOST
contains all information about
the signpost, such as the
reference to the base link or
road geometry that must be
passed in order to reach a
destination displayed on the
signpost, the color definitions
for text and background, exit
numbers and names.
VALIDITY_RANGE
indicates the location of the
signpost along the base link or
road geometry line.
LANE_MASK
model information that is
relevant for specific lanes.
61. -61-
(三)Routing Building Block
路标建模(Modeling Signposts)
(2) Information in SIGNPOST:
Information in SIGNPOST Value
baseRouteLinkId 42
hasSignpostBackgroundIcon FALSE
backgroundColor 23 (blue) Color definitions are stored in the color Table of
the product database.
hasName FALSE
hasNumber TRUE
signpostNumberRef 99
junctionType 2 (EXIT)
horizontalNumber 2
verticalNumber 3
signpostElements Signpost elements
■ baseRouteLinkId: Link that has to be passed in order to reach
one of the destinations on the signpost.
■ hasSignpostBackgroundIcon and
signpostBackgroundIconId: Information about the background
icon of the signpost.
■ backgroundColor and textColor: Color of the signpost
background and the text on the signpost.
■ hasName, hasNumber, signpostNameRef, and
signpostNumberRef: Exit or interchange information to be
displayed on the signpost.
■ junctionType: Defines the type of the junction, such as
interchange or exit.
■ horizontalNumber and verticalNumber: Defines a grid for
positioning the individual signpost elements on the signpost. The
elements themselves are described in signpostElements.
■ signpostElements: Contains the individual signpost elements.
Each element is defined in a separate structure of type
SignpostElement. Signpost elements shall be ordered by their
position in the signpost grid. The first entry in the SignpostElement
sequence represents the upper-left corner. The rest of the elements is
sorted by row, from left to right grid position.
62. -62-
(三)Routing Building Block
路标建模(Modeling Signposts)
(3) Signpost Elements:
Data in signpostElements sequence:
Grid position 0 1
0 Signpost element 0
type = TOWARD_INFO
info = "Salzburg"
Signpost element 1
type = FILL
1 Signpost element 2
type = TOWARD_INFO
info = "Nürnberg"
Signpost element 3
type = FILL
2 Signpost element 4
type = DIRECTIONAL_INFO
info = reference to the named
object for motorway 8. This
named object has the named
object class SIGNPOST; the
name string shall have the name
format ROAD_NUMBER.
Signpost element 5
type = DIRECTIONAL_INFO
info = reference to the named
object for motorway 9. This named
object has the named object class
SIGNPOST; the name string shall
have the name format
ROAD_NUMBER.
Entries in the signpostLayoutTable:
63. -63-
(三)Routing Building Block
停车设施 (Modeling Parking Facilities)
NDS provides the flexible attribute PARKING to define parking
facilities along a base link or road geometry line. An application
can use the attribute to distinguish between parking and non-
parking areas.
The attributes that are assigned to the link representing
the ramp in order to model this real-world situation:
64. -64-
(三)Routing Building Block
号牌限行 (Modeling License Plate Restrictions)
■ LICENSE_PLATE_RESTRICTION
– LicensePlateRestrictionRule > isLastDigitRule = TRUE
– lastDigitRuleType = SPECIAL_DIGIT
– numLastSpecialDigits: 2
– specificPlates: relevant number plate endings
■ DAYS_OF_WEEK: Booleans for the weekdays set to TRUE for the relevant
days
■ TIME_RANGE_OF_DAY: startTime = 7:30, endTime = 20:00,
isInclusive = FALSE
In order to ease traffic congestion, some cities apply
traffic restrictions based on license plates. The
restrictions may apply to specific factors or a
combination of factors:
■ Vehicle types
■ Local or non-local vehicles
■ Vehicles with permit
■ Numbers on the license plate
■ Areas within the city
The areas with restricted traffic do not necessarily
correspond to administrative areas.
■ Weekdays, times of the day, public holidays
License plate restrictions are updated frequently. Also,
there may be temporary restrictions.
NDS provides the flexible attribute
LICENSE_PLATE_RESTRICTION for modeling such
regulations. The attribute contains structures for storing
the type of restriction and the exact rules regarding the
license plates. The compiler may assign the attribute to
routing and BMD features.
65. -65-
(三)Routing Building Block
Use of Bypasses, Side Streets, or Shortcuts as Routing Options
The flexible attribute SHORTCUT may be assigned to links that are part
of an alternative route that is faster than the main road. An example of a
shortcut is a road that is not as well known as the main road. The links
are classified by the data supplier based on local knowledge.
The flexible attribute BYPASS may be assigned to links that bypass city
centers or for smaller mountain roads. In Japan, for example, the links of
bypass roads are classified by the government.
The flexible attribute SIDE_STREET may be assigned to links that are
part of a minor road in a metropolitan area between major locations
with heavy traffic. An example of a side street is a link that is longer
than the main link but with less traffic. The links are classified by the
data supplier based on local knowledge.
66. -66-
(三)Routing Building Block
Further Use Cases with Flexible Attributes
Grade change of ramps compared to previous link
GRADE_TYPE = DOWN
GRADE_TYPE = UP
Modeling warning Sign
If a road has two sides that are
separated by a road divider,
then it may be digitized as two
links.
Modeling Multi-Digitized Road
Modeling Enforcement Cameras Modeling Roads as Start or End Point Modeling Stationary Objects along the road
START_OR_DESTINATION_ROAD_ONLY
67. -67-
(四)Routing: Advanced Driver Assistance (ADAS)
ADASIS v3 map attribution profiles
Profile Description
Intersection profile Node The node profile is used to describe intersections.
Basic geometry
profile
Heading
change
This profile represents the heading angle change of the path at the points of a polyline representation of the
path.
Basic geometry
profile
Curvature This profile represents the curvature of the path.
Basic geometry
profile
Slope This profile represents the slope information of a path.
Road model profile Road
geometry
This profile provides the geometry of the road reference line, usually as a polyline. Typically, the road reference
line is the road centerline, but this is dependent on the underlying road map.
Road model profile Lane model A lane is part of a carriageway that is designated for use by a single line of vehicles, to control and guide drivers,
and reduce traffic conflicts. A lane is usually a laterally delimited area as part of a carriageway.
Road model profile Linear objects Linear objects describe various kinds of real and virtual objects that can be represented by a line roughly in the
direction of the lane: lane boundaries, lane markings, lane center lines, physical lane dividers, curbs, guard rails,
fences, walls
Road model profile Lane
geometry
A lane geometry description defines the geometry of all lanes for a section of a path (a section being defined as
a range of offsets).
Road model profile Lane
connectivity
The lane connections between one road segment and the following road segment are described by the
LaneConnectivity Profile.
68. -68-
(四)Routing: Advanced Driver Assistance (ADAS)
ADASIS v3 map attribution profiles
Profile Description
Road model profile # Lanes (per
direction)
This profile represents the number of lanes on a specific path in a specific relative driving direction.
Road model profile Lane width The lane width profile provides the width of the drivable area on a lane in centimeters.
Road model profile Location object This profile provides information on objects near the road that can be used to precisely locate the ego vehicle.
Speed profiles Effective speed
limit
The effective speed limit describes the speed limit that currently applies to the ego vehicle.
Speed profiles Extended speed
limit
The extended speed limit profile can describe speed limits that might apply to a road (or set of lanes), possibly
depending on a variety of conditions.
Other profiles Complex
intersection
This is a Boolean flag marking a part of a path that is inside an intersection.
Other profiles Link identifier This profile gives the ID of the map database link to which a specific part of the path belongs to.
Other profiles Traffic sign The traffic sign profile conveys information about roadside traffic signs.
Other profiles Traffic light The traffic light profile describes traffic lights along a path.
Other profiles Road
accessibility
This profile represents the information about which classes of actors can access the path.
Other profiles Tunnel The road is in a tunnel.
Other profiles Divided road There is a division between the lanes of opposite driving directions.
69. -69-
(四)Routing: Advanced Driver Assistance (ADAS)
ADASIS v3 map attribution profiles
Profile Description
Other profiles Functional road
class
This is a classification of the road with respect to its importance for routing. Lower values correspond to higher
importance. The actual range of numbers is dependent on the map provider, as is their exact definition.
Global data profiles Driving side The legal driving side (righthanded or left-handed traffic).
Other profiles Form of way This profile represents the type or form of a path; a path can be a tunnel, a bridge, a divided road, etc.
Other profiles Access
restriction
Driving restrictions for a path.
Other profiles Overtaking
restriction
Overtaking restrictions for a path.
70. -70-
(五)Routing: Modeling Toll
Toll Systems
NDS supports the following toll systems:
■ Fixed-fee toll system
Toll fees are charged at toll plazas on the mainline of a toll road, for example, on a motorway. In most fixed-fee toll
systems, different payment methods are available, for example, paying in cash or via electronic toll collection (ETC).
Fixed-fee toll systems are also known as open toll collection systems.
■ Distance-based toll system
Toll fees are charged at the entry or exit of a toll road, and depend on the distance traveled on the toll road. In most
distance-based toll systems, different payment methods are available, for example, paying in cash or via electronic toll
collection (ETC). Distance-based toll systems are also known as closed toll collection systems.
■ Vignette-based toll system
The driver purchases a toll vignette for a defined period of time before entering a country.
71. -71-
(五)Routing: Modeling Toll
Modeling Toll Roads
The fixed attribute toll indicates whether toll must be paid for a specific
road (DataScript location: nds.common.fixedattributes >
SharedRoadAttributes). To store detailed toll information, the fixed
attribute toll shall be set.
72. -72-
(六)Routing: Eco Routing
Modeling Toll Roads
In addition to the shortest distance and shortest duration routes, eco routing offers another option for route calculation. This option is
economic and eco-friendly because it minimizes fuel consumption and emissions.
The following infrastructural factors influence the calculation of eco routes and have to be taken into account for eco routing in NDS:
■ Consumption Speed Curve (CSC)
The CSC describes the speed-dependent fuel or energy consumption for a car driving at a constant height and at a distinct average speed.
The CSC takes fluctuations of normal traffic speed into consideration. Specific consumption effects, however, which could also be
derived from a map, are modeled separately by means of the factors for speed
variation and slope. NDS models the Consumption Speed Curve by means of the flexible attribute
CONSUMPTION_SPEED_DEPENDENCY.
■ Speed variation
Transitions, intersections, and curves on a route cause speed variations and thus impact consumption. The speed variation factor for
transitions describes how acceleration and deceleration affect consumption due to functional road class transitions, speed limits, right
of way regulations, and sharp bends at nodes and intersections. The speed variation factor for curves describes acceleration and
deceleration effects on consumption due to speed reduction at curves along links. To store the calculated consumption factor for speed
variation, NDS provides the flexible attribute CONSUMPTION_SPEED_VARIATION.
■ Slope
Road slope above a specific threshold causes excessive consumption due to a higher energy effort during uphill driving and an energy
waste due to braking when driving downhill. NDS provides several attributes to store slope values
73. -73-
(七)Lane Building Block
车道属性（Attributes for Lanes）
■ LANE_GROUP
Groups all lanes that have the same travel
direction and feature references
■ LANE_RANGE_MASK
Assigns flexible attributes to lanes or parts of
lanes
■ LANE_GROUP_FEATURE_REFERENCE
Defines a reference to a lane group that
belongs to several links
■ LANE_GROUP_ASSOCIATION
Defines relations between lane groups. An
application can use lane group associations
to assess the traffic situation
■ LANE_BOUNDARY_MARKINGS_DEFAULTS
Specifies the default settings for lane
boundaries
■ LANE_CONNECTION_TYPE
Specifies whether a lane splits or merges
74. -74-
(七)Lane Building Block
LaneTileTable存储内容
Defines a reference to a
lane group that belongs to
several links
Groups all lanes that have the
same travel direction and
feature references
Link’s attribute point list
Defines relations between
lane groups
LANE_GROUP属性所包含的信息有：
■ Lane group ID
The lane group ID shall be unique per tile.
■ References to other features
■ Connected lanes
■ Lane geometry
■ Lane boundaries
75. -75-
(七)Lane Building Block
切分车道组(Cutting of Lane Groups)
The compiler shall start a new lane group when the number of
lanes changes. Lane groups are cut in the following situations:
■ Lane starts forming
Examples:
– An exit lane starts to emerge from the main carriageway of a
motorway.
– A lane starts forming inside an intersection.
■ Lane ends merging into another lane
Examples:
– An entry lane of a motorway is completely merged with the
main carriageway.
– A lane ends inside an intersection.
■ New maneuver is possible
Example: An intersection starts and different transitions to
other links are possible.
■ Adjacent lanes are physically separated from each other for
a significant distance. Every lane in the lane group shall be
accessable via a paved surface.
Examples:
– A lane group is not cut for small traffic islands between the
lanes within an intersection.
– A lane group is cut if two lanes are separated by a longer
guardrail.
76. -76-
(七)Lane Building Block
Clipping Lane Groups that Cross Tile Borders
The lane connectivity describes possible maneuvers between lanes.
Lane connectivity is modeled with lane connector IDs, which shall be
unique within a group of 9 tiles (3x3 tile matrix).
If a lane group extends over more than a 3x3 tile matrix, then it shall
be clipped at a 90° angle in one of the tiles to ensure the uniqueness of
lane connector IDs. The compiler does not need to clip the lane group
directly at the tile border. The individual parts of the lane group are
assigned to the corresponding tiles.
If a lane group or only one of its lanes extends into the neighboring tile,
then the compiler does not need to clip the lane group.
If the lane groups have splitting or merging lanes close to the tile
border, cutting directly at the tile border is unfavorable. Instead, the
lane groups may be cut at an arbitrary position inside a tile.
79. -79-
(七)Lane Building Block
车道类型赋值(Flexible Attributes to Lane Types)
Flexible attributes for lane types:
• IS_REGULATED_ACCESS_LANE: Describes a holding zone that is used to regulate traffic using time intervals.
Lanes of this type are used to regulate truck access to tunnels or bridges.
• IS_BICYCLE_LANE: Describes a bicycle lane.
• IS_BUS_LANE: Describes a bus lane.
• IS_TRAM_LANE: Describes a tram lane.
• IS_PARKING_LANE: Describes a lane on the roadbed that is parallel to the driving lanes. Lanes of this type are
typically used for parking. Sometimes, vehicles may temporarily use them as driving lanes.
• IS_TRUCK_PARKING_LANE: Describes a lane on the roadbed that is parallel to the driving lanes. Lanes of this type
are typically used by trucks for parking. Sometimes, vehicles may temporarily use them as driving lanes.
83. -83-
(七)Lane Building Block
车道组间关系(Relations between Lane Groups)
NDS provides the flexible attribute
LANE_GROUP_ASSOCIATION to model relations
between lane groups.
SAME_DIRECTION
OPPOSITE_DIRECTION
INTERSECTION
84. -84-
(七)Lane Building Block
车道几何 (Lane Geometry)
The geometry of a lane is defined by a center line and lane boundaries at the curbside and the middle
side of the road. Lane boundaries can either be physical boundaries or markings on the street. An
application can use the center lines for path planning and the lane boundaries for car positioning.
Lane geometry information is optional. However, applications only support autonomous driving
functionality on roads with lane geometry information. To indicate that lane geometry information
is available for a routing feature, the compiler may assign the flexible attribute
HAS_LANE_GEOMETRY to the routing feature.
The Lane building block supports two options for storing high-precision lane geometry:
■ Internally: Within the LANE_GROUP attribute
The sequence laneBoundaryGeometry defines the lane geometry data of lane boundaries. The
sequence laneAdvancedGeometry defines the lane geometry data of center lines.
The compiler shall set the geometryInternal flag in the LANE_GROUP attribute to TRUE.
■ Externally: Outside the LANE_GROUP attribute
The lane geometry is stored in lane geometry tiles. The compiler shall set the geometryInternal
flags in the LANE_GROUP attribute to FALSE.
85. -85-
(七)Lane Building Block
车道边线 (Lane Boundary)
Filling of first
LaneBoundaryGroupParallelElements
at the curbside with multiple
LaneBoundaryParallelElement and
their sequentialElements
88. -88-
(七)Lane Building Block
Lane boundary shared within lane group
To model shared lane boundaries, the compiler only fills the
second boundary element. For the first boundary element,
laneBoundarySource is set to INTERNAL_SHARED to
indicate that the shared boundary is stored in the next
element.
89. -89-
(七)Lane Building Block
Lane boundary shared across lane groups
Example: The shared lane boundary is stored in lane group 1
and reused in lane group 0.
Lane boundaries shall only be shared across lane
groups if the group of boundary elements belongs to
the complete length of both lane groups. This means
that both lane groups shall either have the same
spatial extent or apply to the complete routing
feature.
If a boundary is shared between two lane groups on
the same link, then the compiler shall store the
shared geometry in the lane group in positive link
direction. The digitization direction of the shared
geometry shall correspond to the digitization
direction of the link.
91. -91-
(七)Lane Building Block
Modeling Lanes along a Road
（一）Attribute LANE_GROUP
（二）Attribute LANE_GROUP_FEATURE_REFERENCE
Example: Exit lanes of a motorway
92. -92-
(七)Lane Building Block
Assigning Lane Groups to Features with High Precision
Forming Shoulder Lane: Intersection before Position where Lanes Split
94. -94-
(七)Lane Building Block
Modeling Lanes at Intersections
(1)Assigning Lane Groups to Intersecting Links
Each of the base links has at least 3 lane groups, one lane group
each for:
■ Set of lanes in positive link direction
■ Set of lanes in negative link direction
■ Part of the base link that brings traffic into the intersection
The compiler shall assign the following attribute group to
each base link within the intersection:
■ LANE_GROUP: Defines the lane group and provides
information about connectivity between lanes
■ VALIDITY_RANGE
■ LANE_GROUP_ASSOCIATION: To define the relation
between the 4 lane groups within the intersection, the
compiler assigns the flexible attribute
LANE_GROUP_ASSOCIATION
95. -95-
(七)Lane Building Block
Modeling Lanes at Intersections
(2) Defining Relations of Lane Groups at Intersections
LANE_GROUP_ASSOCIATION attribute for lane group 0
assigned to link 348:
■ associationType = INTERSECTION
■ numFeatureReferences = 3
■ featureReference (Base link, Lane group ID):
(345,3); (346,1); (347, 2)
96. -96-
(七)Lane Building Block
Modeling Lanes at Intersections
(3) Assign attribute groups consisting of
LANE_GROUP_FEATURE_REFERENCE and VALIDITY_RANGE
to the connected directed base links
97. -97-
(七)Lane Building Block
Modeling Lanes at Intersections
(4) Modeling Connectivity of Lanes Across Intersections LANE_GROUP settings for base link 348
98. -98-
(七)Lane Building Block
Modeling Lanes at Intersections
(5) Modeling Connectivity of Lanes Across Complex
Intersections
Sample settings for link 321
99. -99-
(七)Lane Building Block
Modeling Lane Boundaries along a Road (1)
【Sound Barrier】
【Solid Line】
【Travel Direction】
【Dashed Line】
【Link Direction】
102. -102-
(七)Lane Building Block
Modeling Lane Boundaries for Gores
(1) Ramp without Gore Area
There is a start point of the gore, but no gore area. Therefore, the compiler does not define a lane boundary for the gore.
105. -105-
(七)Lane Building Block
Modeling Road Areas
(1) Modeling Road Areas in Intersections (2) Modeling Road Areas with Gore
Intersections can contain open areas that are not covered
by the lane model but are still of interest for highly
automated driving. For example, the application wants to
know where other vehicles or pedestrians can be expected
or where the vehicle can go in an emergency.
To model drivable and non-drivable areas in intersections,
the compiler assigns the flexible attribute ROAD_AREA to
a link or road geometry line adjacent to the road area.
To model drivable and non-drivable gore areas, the
compiler assigns the flexible attribute ROAD_AREA to a
link or road geometry line adjacent to the gore.
106. -106-
(七)Lane Building Block
Modeling Areas for Public Transport
(1) Tramway Tracks beside and on the Road
The tramway tracks are stored in public transport lane
groups, the lanes drivable by car are stored in road lane
groups.
The lane that is bordered by a dashed line on the curbside
and a double solid line on the middle side is stored as lane
1 of road lane group 1. The lane with the tramway tracks
on the road is stored as lane 0 of public transport lane
group 1. It overlaps with lane 1 of road lane group 1, but
has a different geometry.
An example of a tramway track on the road and a tramway
track located beside the road.
107. -107-
(七)Lane Building Block
Modeling Areas for Public Transport
(2) Merging Tramway Tracks
a tramway track beside the road that crosses one road lane
and merges into another tramway track on the road. The
tramway tracks are stored in three public transport lane
groups. tramway track on the road and a tramway track
located beside the road.
108. -108-
(七)Lane Building Block
Modeling Areas for Public Transport
(3) Modeling Public Transport Stops
Bus Stop on the Road
To model the bus stop, the compiler stores the following road
area types:
■ PUBLIC_TRANSPORT_STOP for the area on lane 0 of road
lane group 1 where the bus stops.
■ WAITING_AREA for the waiting area beside the road.
Tramway Stop with Passengers Crossing the Road
The tramway stop is modeled by means of the following structures:
■ Three public transport lane groups: One public transport lane
group with lane connectivity element type TRAIN_STOP for the
area where the tram stops and two public transport lane groups
with lane connectivity element type TRAIN_TRACK for the other
parts of the tramway tracks.
■ One road area of type WAITING_AREA for the waiting area and
the area where passengers cross the road.
109. -109-
(七)Lane Building Block
Modeling Lane Prohibitions
(1) Lane Change Prohibitions
To determine whether a change to an adjacent lane is allowed, the application shall consider the flags
openToCurbSide and openToMiddleSide in the LaneBoundaryElement sequence, as well as the
prohibitions modeled with PROHIBITED_PASSAGE.
The following rules apply:
■ If the openTo* flag is set to FALSE, then the vehicle is never allowed to change to the adjacent lane.
■ If the openTo* flag is set to TRUE, then the application shall check the prohibitions on the adjacent lane before
changing the lane.
110. -110-
(七)Lane Building Block
Modeling Lane Prohibitions
(2) Lanes with Time-Dependent Prohibitions
To model the prohibitions for lane 1, the compiler assigns two lane groups:
■ Lane group 0 defines lane 0 and lane 1 in positive link direction.
■ Lane group 1 defines lane 0 and lane 1 in negative link direction.
To define that lane 1 may be used in both directions, the compiler assigns
the attribute LANE_USED_IN_BOTH_DIRECTIONS in positive link
direction.
For optimization purposes, the compiler stores the lane boundaries for lane
1 only in lane group 0, which contains the lane in positive link direction.
111. -111-
(七)Lane Building Block
Modeling Lane Prohibitions
(3) Modeling Dynamic Shoulder Lanes
Some shoulder lanes are drivable at certain times. To model
dynamically drivable shoulder lanes, the compiler groups the
flexible attribute PROHIBITED_PASSAGE with a an attribute for
time periods and assigns it to the shoulder lane. The lane
boundary type of the lane marking between shoulder lane and
middle lane is set to open to both sides.
112. -112-
(七)Lane Building Block
Modeling Lane Prohibitions
A high-occupancy vehicle lane (HOV lane, also called carpool
lane) is reserved for vehicles with a specific minimum number
of occupants.
To indicate that a lane or a road is reserved for high-occupancy
vehicles, NDS provides the following flexible attributes:
■ IS_CARPOOL_LANE
This flexible attribute is a lane attribute and is assigned to base
links or road geometry lines on level 13.
■ IS_COMPLETE_CARPOOL_ROAD
This flexible attribute is used for route guidance and routing
options, for example, to avoid or prefer HOV lanes. The
attribute is assigned to links or road geometry lines on all
levels. If the attribute value is TRUE, then the feature
represents an HOV road, meaning that it only consists of HOV
lanes. If the attribute value is FALSE, then the road
represented by the respective feature has both HOV lanes and
normal lanes. If the attribute is not assigned to a feature, then
no HOV lanes exist or the HOV status is unknown.
(4) High-Occupancy Vehicle Lanes
113. -113-
(七)Lane Building Block
Modeling Lane Prohibitions
(5) Lanes Reserved for Special Vehicles
Lanes can be reserved for special vehicle types, such as busses or trucks. For example, the following attribute group
defines a lane reserved for trucks:
■ LANE_RANGE_MASK
■ PROHIBITED_PASSAGE
■ FREQUENTLY_USED_VEHICLE_TYPES
Bit set to TRUE for the required vehicle type, such as isTruck, and to FALSE for isInclusive. This means
that driving on this lane is prohibited for all vehicles except trucks.
Lanes can be reserved for vehicles with a special equipment, such as autonomous cars, hybrid cars, or cars with
trailers. For example, the following attribute group defines a lane reserved for cars with autonomous driving
functionality:
■ LANE_RANGE_MASK
■ PROHIBITED_PASSAGE
■ EQUIPMENT
Bit set to TRUE for the equipment type isAutonomouslyDriven and to FALSE for isInclusive. This
means that driving on this lane is prohibited for all vehicles except cars with autonomous driving functionality.
114. -114-
(七)Lane Building Block
Modeling Traffic Lights
NDS provides the following primary flexible attributes for modeling traffic lights:
■ TRAFFIC_LIGHTS
Indicates that one or more traffic lights exist on a feature. Applications can use this information for route guidance.
■ TRAFFIC_LIGHTS_LONGTERM
Indicates that one or more traffic lights with a very long switching cycle exist on a feature. Examples are traffic lights
blocking tunnels and bridges. Applications can use this information for route guidance.
■ NUM_TRAFFIC_LIGHTS
Indicates the number of traffic lights on a link. Applications can use this information for routing and route guidance.
■ TRAFFIC_LIGHT_GROUP
Specifies additional information on sets of traffic lights, for example, traffic light type and switching cycle.
Applications can use this information for car positioning and driver assistance.
To define properties of a traffic light, the compiler may group TRAFFIC_LIGHTS and
TRAFFIC_LIGHTS_LONGTERM with the following secondary flexible attributes:
■ TRAFFIC_LIGHT_DETAILS
Specifies details of a traffic light, such as the construction type and the color set.
■ VALIDITY_RANGE
Defines the position of a traffic light on a routing feature.
115. -115-
(七)Lane Building Block
Modeling Traffic Lights
(1) Traffic Light Groups
A traffic light group is a set of one ore more traffic lights that are valid for the same travel direction and that have the
same switching cycle. To define traffic light groups for a base link or road geometry line, the compiler shall assign the
flexible attribute TRAFFIC_LIGHT_GROUP to the feature.
Traffic light groups contain the following information:
■ Traffic light group ID
Shall be unique within a group of 9 tiles (3x3 tile matrix).
■ Number of traffic lights in the group
■ Traffic light type
■ References to traffic light definitions
■ References to switching cycles
■ Bounding boxes for the group
If one traffic light group is valid for lanes on multiple features, then the compiler shall store the traffic light group on one
of the features only. On the other features, the traffic light group shall be referenced using the flexible attribute
TRAFFIC_LIGHT_GROUP_REF.
116. -116-
(七)Lane Building Block
Modeling Traffic Lights
(2) Traffic Light Groups at An Intersection
Sample settings for TRAFFIC_LIGHT_GROUP_REF attribute on base link 319
121. -121-
(七)Lane Building Block
Modeling Traffic Lights
(7) Modeling Additional Traffic Lights for Specific Maneuvers
Vehicles that enter the intersection from base link 321 must
give way to the oncoming traffic before turning left. After the
traffic lights of traffic light group 3 have turned red, the
traffic light of traffic light group 4 signals a protected turn to
the waiting vehicles inside the intersection.
The "Räumpfeil" may be modeled as a traffic light group with
only one lens and a stop location inside the intersection. The
compiler assigns the following attributes:
■ TRAFFIC_LIGHT_GROUP on base link 325
■ TRAFFIC_LIGHT_STOPPING_LOCATION on base link
325 (line position 1)
■ TRAFFIC_LIGHT_PATH on base link 321
Stores the sequence of base links 323 and 325.
122. -122-
(七)Lane Building Block
Modeling Traffic Lights
(8) Modeling Traffic Lights for Lane Control
The figure illustrates traffic lights for lane control on a
motorway. Each of the traffic lights can display three
different signals.
This real-world situation is modeled as follows:
■ Each traffic light is stored in an own group.
■ Each traffic light definition contains three possible inlays.
■ The traffic light type is set to LANE_CONTROL.
123. -123-
(七)Lane Building Block
Modeling Traffic Lights
(9) Modeling Crossing Areas
Applications for highly automated driving must be aware of
areas where vulnerable road users, such as pedestrians or
cyclists, frequently cross the road. To model such areas,
NDS provides the flexible attribute
TRAFFIC_LIGHT_CROSSING_AREA. The compiler shall
assign the attribute to the base link or road geometry line
on which the traffic light group is stored.
The TRAFFIC_LIGHT_CROSSING_AREA attribute on
base link 324.
124. -124-
(七)Lane Building Block
Further Use Cases
(1) Passing Lanes
Applications for highly automated driving must be aware of
areas where vulnerable road users, such as pedestrians or
cyclists, frequently cross the road. To model such areas,
NDS provides the flexible attribute
TRAFFIC_LIGHT_CROSSING_AREA. The compiler shall
assign the attribute to the base link or road geometry line
on which the traffic light group is stored.
The TRAFFIC_LIGHT_CROSSING_AREA attribute on
base link 324.
125. -125-
(七)Lane Building Block
Further Use Cases
(2) Modeling Stop Lines and Waiting Lines
Stop lines are road markings that are usually accompanied by stop signs or
traffic lights. If the sensor of a navigation system detects a stop line, then the
vehicle shall stop and give right of way to traffic on the main road.
To model stop lines, NDS provides the flexible attribute STOP_LINE that
can be grouped with LANE_RANGE_MASK.
Waiting lines are road markings used to regulate right of way at intersections
where multiple roads of the same road class meet. Waiting lines are not
accompanied by stop signs. If the sensor of a navigation system detects a
waiting line, then the vehicle shall slow down and watch for traffic on the
intersecting roads. To model waiting lines, NDS provides the flexible attribute
WAITING_LINE that can be grouped with LANE_RANGE_MASK.
126. -126-
(七)Lane Building Block
Further Use Cases
(3) Modeling Staggered or Diagonal Stop Lines In intersections, the lanes in one lane group may end at
different positions. To avoid multiple cutting of lane groups,
the following rules apply to such scenarios in addition to
the rules for cutting lane groups:
■ A lane group shall be cut at the earliest point where
overlapping or incoming traffic is possible. If stop lines are
available, then the compiler may use the first stop line as an
indication of incoming traffic.
■ A lane group shall be cut when the intersection starts. The
intersection starts at the position where the compiler sets
LANE_GROUP_ASSOCIATION to INTERSECTION.
■ Stop lines shall not influence the cutting of lane groups
unless they indicate the first occurrence of incoming traffic
(see first rule above).
■ Stop lines shall not be taken as indication for the lane
group cutting rule "New maneuver is possible".
Explanation: In case of staggered or diagonal stop lines, the
maneuvers on the different lanes start within a very short
distance from each other. The corresponding lane group
shall not be cut multiple times at the stop line positions.
127. -127-
(七)Lane Building Block
Further Use Cases
(4) Modeling Express Roads and Express Lanes
The information whether a lane is an express lane, or whether a
road is an express road, is relevant for routing and for route
guidance. For route calculation, express lanes must be identified
to either avoid or prefer them when calculating a route. If a road
has express and normal lanes, then it can be used in both cases.
The flexible attribute IS_COMPLETE_EXPRESS_ROAD belongs
to the routing layer and can be assigned to links on all levels. If
the attribute value is TRUE, then the link is an express road,
meaning that it only consists of express lanes and the complete
road is physically separated from the normal road. If the
attribute value is FALSE, then the road represented by the
respective link has express lanes and normal lanes. If the
attribute is not assigned to a link, then no express lanes exist.
In the route guidance layer, the flexible attribute
IS_EXPRESS_LANE may be grouped with the attributes
LANE_RANGE_MASK to indicate that a lane or part of a lane is
an express lane.
An express lane is a traffic lane, or, in case of an
express road, a set of lanes with a limited number of
entrance and exit points. Express lanes or roads are
physically separated from normal lanes or roads.
131. -131-
(七)Lane Building Block
Further Use Cases
(8) Modeling Lanes with Opposing Traffic
To model a road with two overlapping lanes in opposite
driving direction, the compiler assigns two lane groups to
the feature. Each lane group contains one lane that
overlaps the lane of the other lane group. The compiler
assigns the flexible attribute LANE_OPPOSING_TRAFFIC
with a lane range mask to the overlapping lanes.
132. -132-
(八)Localization Landmark Building Block
Concept
Localization landmarks represent real-world objects, such as signs, road markings, or road-side furniture like posts and
poles. If the sensors of a vehicle detect localization landmarks along the road, then the system can use these to
determine the vehicle’s position.
To model relations between routing features and localization landmarks, the compiler defines feature references
between the base links or road geometry lines and the landmarks.
The height of a landmark position is relative to the base height of its tile that is defined in LandmarkMetadata >
baseTileHeight. The landmark position in Landmark > position is encoded as an offset to the tile anchor and
height. All geometries inside the landmark are encoded relative to this anchor point.
A localization landmark consists of a type and type-specific details. The Localization Landmark building block supports
the following types of localization landmarks:
■ SIGN
■ POLE
■ PERPENDICULAR_WALL and LANDMARK_OVERHEAD
■ TRAFFIC_LIGHT
■ MARKING
■ BARRIER
133. -133-
(八)Localization Landmark Building Block
SIGN
■ Traffic signs
Signs that are positioned along the
road with regulatory or informational
content.
Examples: Warning sign, highway
location marker.
■ Signposts
Signs that are positioned alongside or
above the road with informational
content.
Examples: Overhead signs on gantries
and overpasses, informational signs
by the side of the road, road-side
billboards.
■ Markers
Signs that are based on special labels
used for positioning only.
Examples: QR codes in parking garages.
134. -134-
(八)Localization Landmark Building Block
POLE
The Localization Landmark building block provides the landmark type POLE to model poles and pole-like objects. Poles
are characterized by an upward extent and may be part of road barriers.
Examples: Street light pole, signpost pole, guardrail post, reflector post, utility poles.
Landmarks of type POLE are stored in the landmarkPoleTileTable and have properties such as pole type, ground
position, top position, and height. The compiler shall use the flexible attribute LANDMARK_POLE to assign landmarks of
type POLE to base links or road geometry lines.
135. -135-
(八)Localization Landmark Building Block
WALL LANDMARK
Walls that are
tilted to the
vertical in
reality shall
also be
represented as
perpendicular
polygons.
a tunnel entrance
that is split into
three landmarks,
which are each
represented by a
polygon
The Localization Landmark building block provides landmark types to model vertical structures, such as walls. These landmarks are
planar objects that are positioned approximately perpendicular next to or above the road. The following types are available:
■ PERPENDICULAR_WALL for walls next to the road to which they are assigned, for example, the walls at the sides of a tunnel entrance.
Perpendicular walls shall not be positioned above the road surface in driving direction.
■ OVERHEAD_STRUCTURE for perpendicular walls above the drivable road surface to which they are assigned, for example, a wall above
a tunnel entrance. Overhead structures may extend the road surface and they may overlap with perpendicular walls.
The following rules apply to perpendicular walls and overhead structures:
■ Objects must not be parallel to the road, but they do not need to be strictly perpendicular to the road center line. The angle may deviate
for a maximum of 30°, resulting in a range from 60° to 120° relative to the road center line.
■ Perpendicular walls should have a width greater than one meter.
136. -136-
(八)Localization Landmark Building Block
Traffic Light Landmarks
The Localization Landmark building block provides the landmark type TRAFFIC_LIGHT to model the size and location
of traffic signals along the road.
Examples: Traffic light with or without pole.
Landmarks of type TRAFFIC_LIGHT are stored in the landmarkTrafficLightTileTable. They are defined by a
3D bounding box, which is placed around the entire signal head. The compiler shall use the flexible attribute
LANDMARK_TRAFFIC_LIGHT to assign landmarks of type TRAFFIC_LIGHT to base links or road geometry lines.
Traffic light details, such as colors or the layout of the signal head, are not stored in the Localization Landmark building
block because landmarks are only intended for localization purposes. The compiler shall define all traffic light details in
the Lane building block.
137. -137-
(八)Localization Landmark Building Block
Marking Landmarks
The Localization Landmark building block provides the landmark type MARKING to model road markings, such as lines,
arrows, or text.
Examples: Line marking, arrow, text marking on the road.
Landmarks of type MARKING are stored in the landmarkMarkingTileTable. They are defined by one of the
following properties:
■ 3D bounding box
Is placed around the entire road marking.
■ Center line
Represents the approximated center line of the road marking. The compiler shall use the flexible attribute
ANDMARK_MARKING to assign landmarks of type MARKING to base links or road geometry lines.
DataScript location: nds.landmark.main > landmarkMarkingTileTable
138. -138-
(八)Localization Landmark Building Block
Barrier Landmarks
The Localization Landmark building block provides the landmark type
BARRIER to model longitudional objects that are parallel to the road, for
example, fences, guardrails, or tunnel walls.
Landmarks of type BARRIER are stored in the
landmarkBarrierTileTable. The compiler shall use the flexible
attribute LANDMARK_BARRIER to assign landmarks of type BARRIER to
base links or road geometry lines.
Barrier landmarks have types that are defined in
LandmarkObjectBarrierType.
Examples of types are WALL_FLAT, BARRIER_CABLE, and FENCE.
The shape of a barrier is defined by one or multiple 3D polylines. The
polylines are stored in LandmarkObjectShape. The following rules
apply:
■ Each barrier shall be modeled with at least one polyline.
■ The polylines shall be ordered from top to bottom. The first polyline is the
upper edge of the barrier. The last polyline corresponds to the lower edge of
the barrier, which may correspond to the ground where the barrier starts.
■ The polylines shall not cross each other in height.
Explanation: When projected to a 2D surface as seen from the road, the
polylines shall not intersect.
139. -139-
(八)Localization Landmark Building Block
Use Cases
■ Standalone warning sign
Represented by two localization landmarks: One landmark of type POLE
and one landmark of type SIGN.
■ Traffic light
Represented by two localization landmarks: One landmark of type POLE
and one landmark of type TRAFFIC_LIGHT.
■ Standalone warning sign
Represented by two localization landmarks: One landmark of type POLE
and one landmark of type SIGN.
■ Signboard
Represented by five localization landmarks: Two landmarks of type POLE
and three landmarks of type SIGN.
The landmarks are stored in different flexible attributes and attribute layers. Landmarks of type POLE are stored in the pole attribute layer, landmarks
of type TRAFFIC_LIGHT are stored in the traffic light attribute layer, and landmarks of type SIGN are stored in the sign attribute layer.
140. -140-
(九) Obstacles Building Block
Concept
Obstacles are simplified localization objects. An obstacle is represented by a baseline that describes a longitudional
structure next to the road, for example, a guardrail. For positioning, the first obstacles next to the road are important.
Obstacles are represented in the map as follows:
■ 2-dimensional polyline
■ Height indicator above road level
The height indicator is used for filtering purposes. It is assigned to the entire obstacle and stored with a resolution of 10
cm. The data supplier may freely choose the reference point on the obstacle surface for the height indicator.
141. -141-
(九) Obstacles Building Block
Linking Obstacles to Routing Features
Obstacles are grouped in obstacle lists, which are stored in
tiles. Each obstacle list in the map is associated with the
base link or road geometry line from which the obstacle is
observed.
An obstacle list shall be assigned to one link only. Within
one link, obstacle lists can be cut and may be grouped with
a validity range.
If two or more obstacles are separated by less than 15 cm,
then the obstacles shall be represented as a single obstacle.
Figure above shows how multiple objects are represented as
one obstacle.
143. -143-
(九) Obstacles Building Block
Vertical Edges
Vertical edges can be any detectable vertical structure, for
example, poles, house corners, or corners of windows.
Vertical edges are stored in vertical edge lists in the vertical
edge layer. For each vertical edge, the compiler shall store a
3-dimensional point and a height.
The application uses vertical edges for positioning
purposes in urban scenarios.
Vertical edges are represented in the map as follows:
■ 3-dimensional point
Used to indicate the position of a vertical edge.
■ Height
Used to indicate the height of a vertical edge in centimeters,
that is, the vertical length of the object.
Figure above shows a real-world scenario with lampposts,
which are marked with blue lines. The compiler can store
the lampposts as vertical edges.
144. -144-
(十) Using POIs for Parking Facilities
Concept
If parking facilities are stored in a
separate product database, then the
compiler uses poiExt*AccessTables
to connect the parking POIs with the
routing network.
The Figure shows how to connect a
parking facility POI to a base link of the
routing network.
145. -145-
(十) Using POIs for Parking Facilities
Modeling Structured Parking Facilities
Structured parking facilities have parking
spots with predefined outlines. The
geometry of each parking spot is fixed,
but the occupancy changes frequently and
may be updated by volatile data.
To model the structured parking facility,
the compiler uses the following POI
standard categories:
■ POICAT_PARKING_ROW
Defines a parking row containing a set of
adjacent parking spots.
■ POICAT_PARKING_SPOT
Represents a parking spot within a
parking row.
146. -146-
(十) Using POIs for Parking Facilities
Modeling Unstructured Parking Facilities
Unstructured parking facilities are typically
located on the curbside of roads in urban
residential areas. The facilities represent
areas where vehicles may park, but which do
not have individual parking spots.
147. -147-
(十) Using POIs for Parking Facilities
Modeling Access Points in Parking Facility Maps
Parking facility maps contain map features that
are related to parking facilities. To model access
points to parking features, the compiler shall use
internal or external POI access tables, depending
on whether the parking features are stored in an
integrated or in a separate product database.
Parking facilities can contain the following access
points:
■ Access from parking facility map to base map
■ Access to parking section in parking facility
■ Access to parking row
■ Access to parking spot
Accesses to parking facility map and parking section
148. -148-
(十) Using POIs for Parking Facilities
Modeling Access Points in Parking Facility Maps
Parking facility maps contain map features that are related to parking facilities. To model access points to parking features,
the compiler shall use internal or external POI access tables, depending on whether the parking features are stored in an
integrated or in a separate product database.
Parking facilities can contain the following access points:
■ Access from parking facility map to base map
■ Access to parking section in parking facility
■ Access to parking row
■ Access to parking spot
Accesses to parking facility map and parking section Accesses from links and lanes to parking rows and parking spots
149. -149-
(十) Using POIs for Parking Facilities
Modeling Sections of Parking Facilities
A parking section is a space within a parking facility
that groups parking rows, drivable areas, lanes, and
links. The compiler shall assign the flexible attribute
PARKING_SECTION_ID with the same value to all
links or road geometry lines that belong to the same
parking section.
The figure shows a parking facility with two parking levels
that are connected by a transition section.
The POIs 2, 3, and 4 have a part-of relation to POI 1. The POIs
2 and 3, and the POIs 3 and 4 have a connected-to relation.
The compiler generates the following POIs:
■ POI 1: Access to parking facility map
POI category = POICAT_ACCESS_POINT
Secondary POI attribute: POIATTR_PARKING_SECTION_TYPE
■ POI 2: Access to parking level 1a
POI category = POICAT_ACCESS_POINT
Secondary POI attribute:
POIATTRVAL_PARKING_SECTION_TYPE_PARKING_LEVEL
■ POI 3: Access to transition between parking sections
POI category = POICAT_ACCESS_POINT
Secondary POI attribute:
POIATTRVAL_PARKING_SECTION_TYPE_TRANSITION
■ POI 4: Access to parking level 1b
POI category = POICAT_ACCESS_POINT
Secondary POI attribute:
POIATTRVAL_PARKING_SECTION_TYPE_PARKING_LEVEL
150. -150-
(十) Using POIs for Parking Facilities
Parking level with included rental zone
The figure shows a rental zone that is part of a larger
parking level in a parking facility.
The compiler generates the following POIs:
■ POI 1: Access to parking facility map
POI category = POICAT_ACCESS_POINT
Secondary POI attribute: POIATTR_PARKING_SECTION_TYPE
■ POI 2: Access to parking level 1
POI category = POICAT_ACCESS_POINT
Secondary POI attribute:
POIATTRVAL_PARKING_SECTION_TYPE_PARKING_LEVEL
■ POI 3: Access to rental zone
POI category = POICAT_ACCESS_POINT
Secondary POI attribute:
POIATTRVAL_PARKING_SECTION_TYPE_RENTAL_ZONE
152. -152-
GDF 5.1
ISO GDF Revision
Intelligent transport systems — Geographic
Data Files (GDF) GDF5.1 — Part 1:
Application independent map data shared
between multiple sources
Intelligent transport systems — Geographic
Data Files (GDF) GDF5.1 — Part 2: Map data
used in automated driving systems,
Cooperative ITS, and multi-modal transport
