Data Store
3.9 Urban Car Park Data


Description of content

This Data Store shall be used within the Manage Traffic Area. It shall contain the static data for the car parks that are accessed from the urban traffic road network managed by the System.

The data in the Store shall be structured in the following way: - car park location
- number of entrances (number)
- number of exits (number)
- total number of spaces (number)
- float to take account of vehicles searching for spaces (number)
- owner/operator ID (number)
- owner/operator contact information (characters and/or numbers (characters)
- charges (numbers - in currency)
- periods when they operate (time and date string)
- method of car park fee collection (characters)
- hours when operator present (time and date string)
- separate cycle spaces (number)
- separate motorcycle spaces (number)
- number of disabled spaces (number)
- display information in inter-urban area (character indicating YES or NO)
- 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)

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:

- number of vehicles entered car park (number)
- number of vehicles that have left the car park (number)

It shall be possible for this data 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.

Other data shall be used for trip planning purposes but will be stored within the Provide Traveller Journey Assistance Area.

Diagrams

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

Input dataflows

Output dataflows