D8.6 Road Network Data Store

Header Image
Project:
D8.6 Road Network Data Store : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 16.08.2021 20:40:45
Modified: 21.12.2021 15:05:16
Project:
Advanced:
This Data Store shall contain information objects that provide details of the design, layout and physical characteristics of the road network in which the system has to operate.  The static data covers the actual layout and configuration of the urban road network.  Each information object in the Store shall comprise, but bot be limited to, the following data objects:<br/>(1) Road type (numbers and characters),<br/>(2) Type of data (numbers and characters),<br/>(3) Link:<br/>      (3a) ID (number),<br/>      (3b) Type (characters),<br/>      (3c) Start location (characters and/or numbers, e.g. GNSS data),<br/>      (3d) End location (characters and/or numbers, e.g. GNSS data),<br/>      (3e) Length (number),<br/>      (3f) Number of lanes/carriageways (number),<br/>      (3g) Lane/carriageway width(s) (number(s)),<br/>      (3h) Vehicle type usage restrictions (numbers and characters),<br/>      (3i) Vehicle parking restrictions (numbers and characters),<br/>      (3j) Speed limit(s) (numbers in kph or mph),<br/>      (3k) Presence of other objects, e.g. tunnels/bridges (numbers and characters),<br/>      (3m) Obstructions, e.g. narrow road/lanes, bridges/tunnels giving low clearance, bridges with weight restrictions (characters),<br/>(4) Junction:<br/>       (4a) ID (number),<br/>       (4b) Type (characters) - location (characters and/or numbers, e.g. GNSS data),<br/>       (4c) Equipment installed (numbers and characters):<br/>              (4ca) ID (number),<br/>              (4cb) Type (characters),<br/>              (4cc) Configuration (phases/durations/turning movements) (numbers and characters),<br/>              (4cd) Available methods of management (numbers and characters),<br/>              (4ce) Non-available vehicle movements (numbers and characters),<br/>             (4cf) Next up-stream junction (numbers and characters),<br/>             (4cg) Next down-stream junction (numbers and characters),<br/>(5) Date of last update (date string).<br/><br/>These data objects shall be used by a variety of Functions to enable traffic in the urban network to be managed.  It shall also be provided to functionality in the Manage Public Transport Operations Functional Area so that its service routes and schedules can be planned.  It shall be possible for some of the data objects to also be provided to Vehicles to enable driver guidance and information to be provided.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mffo_read_road_network_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mffo_load_road_network_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Tag Value
DataStore_SecurityLevel None
Details:
Default: None
isUnlimited false
Details:
Values: true,false
Default: false
itemKind Information
Details:
Values: Physical,Information
Default: Information
Maximum acceptable request times per application and/or service 1000
Details:
Default: 1000
Number of Users supported 1
Details:
Default: 1
Physical Capacity 1 Byte
Details:
Default: 1 Byte
Planned data storage duration over time 1 Year
Details:
Default: 1 Year
Planned Service level per application and partner None
Details:
Default: None
transaction numbers over time 10
Details:
Default: 10
Property Value
isControlType: false
ordering: FIFO