Description of content

This Data Store shall be used within the Manage Traffic Area.  It shall contain 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.

The data in the Store shall be structured in the following way:
- date (date string)
- time (numbers defining hours, minutes and seconds)
- location (characters and/or numbers, e.g. GPS/Galileo data)
- vehicle flow (number in vehicles per hour)
- vehicle speed (number in kph or mph)
- vehicle headway (number in seconds)
- road occupancy (number as a percentage)
- queue presence (number or character indicating YES or NO)
- vehicle count (number)

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.

The data in the Store for predicted data shall be structured in the following way:
- predicted date (date string)
- predicted time (numbers defining hours, minutes and seconds)
- location (characters and/or numbers, e.g. GPS/Galileo data)
- vehicle flow (number in vehicles per hour)
- vehicle speed (number in kph or mph)
- vehicle headway (number in seconds)
- road occupancy (number as a percentage)

There shall be three sets of predicted data, comprising short, medium and long term predictions.

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:

- rain present (number or character indicating YES or NO)
- temperature (number - in degrees Centigrade)
- fog present (number or character indicating YES or NO)
- vehicle skidding (number or character indicating YES or NO)
- reduced visibility (number or character indicating YES or NO)

In addition data shall be stored about each car park, comprising the following:
- date (date string)
- time (numbers defining hours, minutes and seconds)
- car park identity (number)
- location  (characters and/or numbers, e.g. GPS/Galileo data)
- car park status (number)
- car park occupancy (number as a percentage of the total number of spaces)
- number of available spaces (number)

Diagrams

The Diagram(s) below is (are) the Diagram(s) where you can find the Datastore

DFD 3.1.1 Provide Urban Traffic Management

Input dataflows

mt_load_urban_traffic_data

Output dataflows

mt_read_urban_traffic_data