D3.13 Urban Traffic Data

Header Image
Project:
D3.13 Urban Traffic Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:06
Modified: 10.09.2021 10:38:52
Project:
Advanced:
This Data Store shall be used within the Manage Traffic Functional Area.  It shall contain information objects that provide traffic flow and other traffic related data for the urban road network.  The data in the Store shall be divided into two parts comprising, historic and current data.<br/><br/>Each information object in the Store for historic and current data shall contain the following data objects:<br/>(1) Date (date string),<br/>(2) Time (numbers defining hours, minutes and seconds),<br/>(3) Location (characters and/or numbers, e.g. GPS/Galileo data),<br/>(4) Vehicle flow (number in vehicles per hour),<br/>(5) Vehicle speed (number in kph or mph),<br/>(6) Vehicle headway (number in seconds),<br/>(7) Road occupancy (number as a percentage),<br/>(8) Queue presence (number or character indicating YES or NO),<br/>(9) Vehicle count (number).<br/><br/>There shall be one set of the above data for each location in the urban road network where some or all of the data shall have been obtained.  Within each set there shall be both current and historic data.<br/><br/>The data in the Store for predicted data shall be structured in the following way:<br/>(10) Predicted date (date string),<br/>11) Predicted time (numbers defining hours, minutes and second),<br/>(12) Location (characters and/or numbers, e.g. GPS/Galileo data),<br/>(13) Vehicle flow (number in vehicles per hour),<br/>(14) Vehicle speed (number in kph or mph),<br/>(15) Vehicle headway (number in seconds),<br/>(16) Road occupancy (number as a percentage).<br/><br/>There shall be three sets of predicted data, comprising short, medium and long term predictions.<br/><br/>It shall be possible for the following items of data to also be included in the Data Store with the data for each segment of the urban road network, if extended floating car data is available for collection:<br/><br/>(17) Rain present (number or character indicating YES or NO),<br/>(18) Temperature (number - in degrees Centigrade),<br/>(19) Log present (number or character indicating YES or NO),<br/>(20) Vehicle skidding (number or character indicating YES or NO),<br/>(21) Reduced visibility (number or character indicating YES or NO).<br/><br/>In addition data shall be stored about each car park, comprising the following:<br/>(22) D ate (date string),<br/>(23) Time (numbers defining hours, minutes and seconds),<br/>(24) Car park identity (number),<br/>(25) Location (characters and/or numbers, e.g. GPS/Galileo data),<br/>(26)Car park status (number),<br/>(27) Car park occupancy (number as a percentage of the total number of spaces),<br/>(28) Number of available spaces (number).<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_read_urban_traffic_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_load_urban_traffic_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