D3.9 Urban Car Park Data

Header Image
Project:
D3.9 Urban Car Park Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:07
Modified: 10.09.2021 10:38:53
Project:
Advanced:
This Data Store shall be used within the Manage Traffic Functional Area. It shall contain information objects that provide the static data for the car parks that are accessed from the urban traffic road network managed by the System. <br/><br/>Each information object in the Store shall contain the following data objects: <br/>(1) Car park location and/or name (characters),<br/>(2) Number of entrances (number),<br/>(3) Number of exits (number),<br/>(4) Total number of spaces (number),<br/>(5) Float to take account of vehicles searching for spaces (number),<br/>(6) Owner/operator ID (number),<br/>(7) Owner/operator contact information (characters and/or numbers (characters),<br/>(8) Charges (numbers - in currency),<br/>(9) Periods when they operate (time and date string),<br/>(10) Method of car park fee collection (characters),<br/>(11) Hours when operator present (time and date string),<br/>(12) Separate cycle spaces (number),<br/>(13) Separate motorcycle spaces (number),<br/>(14) Number of disabled spaces (number),<br/>(15) Display information in inter-urban area (character indicating YES or NO),<br/>(16) List of devices on which car park information is displayed with details about whether "state" or "spaces" is to be displayed (characters and/or numbers),<br/>(17) Thresholds for car park status change, e.g. number of occupied spaces for "almost full" status to be achieved (characters + numbers).<br/><br/>It shall be possible for the Car Park State Calculation function to calculate the current state of the service area using the following "live" data objects:<br/><br/>(18) Number of vehicles entered car park (number),<br/>(19) Number of vehicles that have left the car park (number),<br/>(20) Car park status, e.g. "almost full", "full", "spaces" and "closed" (characters).<br/><br/>It shall be possible for these data objects to be replicated depending on the number of entrances and exits that a car park has and how the data that they collect is to be used.  For example it shall be possible for the car park area to have separate parking areas for different types of vehicle such as car, coaches and HGV's.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_read_car_park_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_load_car_park_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