Overview

Automated Driving Zones (ADZ) lets you create and edit Operational Design Domain (ODD) maps that govern where and how automated vehicles can operate, including SAE Level 2+, Level 3, and Level 4 automated driving systems.

With HERE ADZ, automotive OEMs can define and manage in-vehicle ODD maps for Advanced Driver Assistance Systems (ADAS) and Automated Driving (AD) functionality.

ADZ provides map creation tools through a web application and HERE APIs. You can use these tools to create maps with layers based on static and dynamic HERE map content.

HERE ADZ supports the following use cases:

Manual and automated editing via both web app and API
Manage the full ODD creation workflow, from generating maps based on custom content to validating, reviewing, approving, and updating them.
Create custom ODDs for various AD functionalities, such as construction zones and cross-country regulations
Designate restrictions and guidance based on vehicle class (sedan, SUV, truck).
Distribute company-specific ODDs across vehicles of different types, automated capabilities, and software versions
Deliver ODDs based on up-to-date map content
Support AD function compliance with local, regional, and global regulations, including UN R171, UN R157, NHTSA, and GB/T 40000-2021.
Support for the Protobuf data format, with Zerio and NDS.Live scheduled for future releases

Key concepts

Action roles define which ADZ actions a user or application can execute. Depending on the assigned role, a user or application can read, write, modify, review, approve, or reject attribute sets.

Each ADZ space includes four user groups that control access to space resources:

Group Name	Description
space-users	Non-admin users and applications with access to the ADZ space. Users are added to this group automatically after their first login. Admins and Super Admins can assign action roles to users and applications in this group.
space-admin	A group created by HERE for the organization that contains the ADZ space. Members are Admins and Super Admins. By default, users in this group cannot modify content catalog resources unless they are assigned additional permissions.
space-manager	A group for users who need to access and modify catalogs in the space.
avb-service	A group for users and applications that need to access and modify the output catalog for AVB.

Terminology

Term	Description	Example
Action	A request created by a user or system which is executed by the ADZ application in order to modify the attributes of an ODD	Copy from proposed to final, Delete final, Reject proposed
Action role	A named role with permissions to execute certain kinds of actions	Editor, Reviewer, Viewer
Property	The fundamental form of information used in ADZ, represented by a strongly-typed key-value pair. Supported types are integers, strings, booleans, and doubles.	speedKph (integer), handsOffEnabled (boolean)
Attribute	A connected set of properties.	`Attribute( segmentId = 1345, (fromFromStart =0, toFromEnd=0, properties=Set(speed=10, userNote="My note"))`
Attribute set	A collection of attributes that apply to the entire scope of the space. Each attribute set is uniquely identified by an attribute set ID.	Hands-free driving for SUVs only on limited-access roads with FC1 and FC2 in the United States, independent of traffic.
Attribute set ID	A unique URN identifier for an attribute set. The first portion of the ID identifies the attribute set state.	`proposed:suv:v1, live:suv:v2`
Platform user ID	A unique identifier for a HERE platform user. User IDs are displayed when someone uses the ADZ GUI.	HERE-c5468340-7056-4584-bde6-000000000000
Platform app ID	A unique identifier for a HERE platform app that interacts with ADZ through APIs.	`y35LReplKabbm0A6K5bk-NrA`
User management role	A management role within team management which defines what permissions they can assign to other users. For more information, see the web app guide.	Super admin, Admin, User
Space user ID	A unique identifier for a user within an ADZ space.	space-user-id-example