Description of content

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

The data in the Store shall be structured in the following way:
- service area location (characters, e.g. nation, region, city, state, area names(s), but may also include characters and/or numbers, e.g. GPS/Galileo data)
- inter-urban road identity if known (characters and number)
- number of entrances (number)
- number of exits (number)
- total number of spaces (number)
- float to take account of vehicles searching for spaces (numbers)
- owner/operator ID (number)
- owner/operator contact information (characters and/or numbers)
- charges (numbers - in currency)
- periods when they operate (time and date string)
- method of service area fee collection (characters)
- hours when operator present (time and date string)
- separate motorcycle spaces (number)

- number of disabled spaces (number)

- number of spaces for coach operators (number)
- number of spaces for HGV's (number)
- re-fuelling facility available (character indicating YES or NO)
- includes hotel(s) with number (character indicating YES or NO plus number)
- includes restaurant(s with number (character indicating YES or NO plus number)
- includes shop(s) with number (character indicating YES or NO plus number)

- display information in urban area (character indicating YES or NO)

- list of devices on which service area information is displayed with details about whether "state" or "spaces" is to be displayed (characters and/or numbers)

It shall be possible for the service area state calculation Function to calculate the current state of the service area using the following "live" data:

- number of vehicles entered service area (number)
- number of vehicles that have left the service area (number)

It shall be possible for this data to be replicated depending on the number of entrances and exits that a service area has and how the data that they collect is to be used.  For example it shall be possible for the service 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

DFD 3.1.5 Provide Management of Service Areas

Input dataflows

mt_load_service_area_data

Output dataflows

mt_read_service_area_data