Map Update System --> Center:
intersection geometry

Definitions

intersection geometry (Information Flow): The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.

Map Update System (Source Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.

Center (Destination Physical Object): This general physical object is used to model core capabilities that are common to any center.

Included In

This Triple is in the following Service Packages:

• SU04: Map Management

This triple is associated with the following Functional Objects:

• Center Map Management
• Map Management

This Triple is described by the following Functional View Data Flows:

• map_intersection_details_for_center
• map_intersection_lanes_for_center

This Triple has the following triple relationships:

Communication Solutions

• US: SAE Other J2735 - Secure Internet (ITS) (12)
• Data for Distribution (TBD) - Apache Kafka (44)
• Data for Distribution (TBD) - OMG DDS (44)
• Data for Distribution (TBD) - OASIS MQTT (50)
• Data for Distribution (TBD) - OASIS AMQP (61)

Selected Solution

Data for Distribution (TBD) - OASIS AMQP

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security