Docstoc

NTCC_DATEXII

Document Sample
NTCC_DATEXII Powered By Docstoc
					TCC-TIH-0049                   NTCC DATEX II Service                          Version 2


                       National Traffic Control Centre
                                  DATEX II Service
1          Introduction
The TIH Community publishes a set of Principles on the TIH website at http://www.tih.org.uk
for exchanging traffic and travel1 information. One of the Principles recommends that data be
exchanged using XML-based services and the National Traffic Control Centre (NTCC) has
developed a DATEX II Publisher conforming to these Principles. Details of the specification
and supporting information, including schema, can be found at http://datex2.eu. The DATEX
II service makes Highways Agency data, covering the motorway and trunk road network in
England, available to third parties.

1.1        Overview
NTCC has installed a Traffic Control Centre Interface at required Police Control Offices and
Regional Control Centres in order to interface with the various subsystems of the Control
Office Base System (COBS). This equipment provides access to MIDAS traffic data and High
Occupancy Alerts (HIOCC), the ability to set Variable Message Signs and also to receive
VMS and Matrix Signal settings via the Message Sign and Signals Subsystems of COBS.
Traffic data is also collected from Traffic Monitoring Units and travel data from Automatic
Number Plate Recognition cameras located at strategic locations on the HA network. Both
categories of data are collected at 5-minute intervals. Once processed, the data is made
available to TIH recipients.

1.2        Purpose
This document describes the NTCC DATEX II Publisher to help potential subscribers’ Project
Managers and engineers to develop an interface and start using the data.
Although every endeavour has been made to ensure accuracy of documentation, the
specification is complex and there may be omissions or inaccuracies. Further assistance can
be sought using the contact details provided in the section ‘Help and Assistance’.




1
   The terms Traffic and Travel are used interchangeably throughout this document but Traffic
information generally refers to the data determined by loops in the road surface measuring actual
speeds, vehicle flows and occupancy whilst Travel information refers to travel times between two
locations determined by ANPR cameras. However, Traffic Data is used to refer to a publication of
combined Traffic and Travel data.


                                            Page 1
 TCC-TIH-0049                                  NTCC DATEX II Service                                               Version 2


1.3                Table of Contents
 1      Introduction .......................................................................................................................1
      1.1    Overview ....................................................................................................................1
      1.2    Purpose......................................................................................................................1
      1.3    Table of Contents.......................................................................................................2
      1.4    Abbreviations .............................................................................................................3
 2      Information Products .........................................................................................................4
      2.1    Event Product ............................................................................................................4
      2.2    Variable Message Sign Product.................................................................................4
      2.3    Matrix Signal Product.................................................................................................4
      2.4    Traffic Data Product ...................................................................................................4
      2.5    Predefined Locations Product....................................................................................5
      2.6    Service Status............................................................................................................5
      2.7    Access .......................................................................................................................6
 3      Event Product....................................................................................................................8
      3.1    Event Format .............................................................................................................8
      3.2    Event Locations .......................................................................................................12
 4      Variable Message Sign Product......................................................................................18
      4.1    VMS Format.............................................................................................................18
 5      Matrix Signal Product ......................................................................................................21
      5.1    Matrix Signal Format................................................................................................21
 6      Traffic Data Product ........................................................................................................24
      6.1    Traffic Data Format ..................................................................................................24
 7      Predefined Location Product...........................................................................................29
      7.1    Predefined Location Format.....................................................................................29
 8      Help and Assistance .......................................................................................................31
      8.1    TIH Technical Authority............................................................................................31
      8.2    Helpdesk ..................................................................................................................31
 9      Appendix A – Example XML ...........................................................................................32
      9.1    Event Product ..........................................................................................................32
      9.2    Variable Message Sign Product...............................................................................34
      9.3    Matrix Signal Product...............................................................................................34
      9.4    Traffic Data Product .................................................................................................35
      9.5    Predefined Location Product....................................................................................37




                                                                  Page 2
TCC-TIH-0049                 NTCC DATEX II Service                        Version 2


1.4        Abbreviations
ANPR         Automatic Number Plate Recognition
ATM          Active Traffic Management
CCTV         Closed Circuit Television
COBS         Control Office Base System
DATEX II     Data Exchange 2 – European specifications for language independent
             exchange of traffic information
GZIP         GNU Zip is a compression algorithm
HA           Highways Agency
HTTP         Hyper Text Transfer Protocol
ID           Identifier (unique NTCC database reference)
MIDAS        Motorway Incident Detection and Automatic Signalling
NMCS National Motorway Communication System
NTCC         National Traffic Control Centre
PCO          Police Control Office
RCC          Regional Control Centre
SOAP         Service Oriented Architecture Protocol
TCC CS       Traffic Control Centre Central System (referred to as TCC Instation software)
TCCI         Traffic Control Centre Interface
TIH          Travel Information Highway
TiS          Traffic Information Services (TiS) Limited
TMU          Traffic Monitoring Unit
TPEG         Transport Protocol Experts Group
URL          Uniform Resource Locator
VMS          Variable Message Sign
WGS84        World Geodetic System, 1984
XML          Extensible Markup Language




                                          Page 3
TCC-TIH-0049                   NTCC DATEX II Service                         Version 2



2          Information Products
NTCC provides information in the form of “information products”. Each information product
will consist of two XML files; one containing the payload (content.xml) and the other
containing the service status (metadata.xml). Two levels of service will be provided – Premier
and Standard, offering the same Information Products at differing delivery frequencies.

The following table lists the information products provided, their update frequencies and
estimated payload file size.

    Information Product        Premier Update        Standard Update            Estimated
                                 Frequency              Frequency              Payload Size
   Current Roadworks              2 minutes             10 minutes               1 M bytes
   Future Roadworks                 6 hours               6 hours                2 M bytes
 Current Planned Events           2 minutes             10 minutes               10 K bytes
 Future Planned Events              6 hours               6 hours               200 K bytes
   Unplanned Events               2 minutes             10 minutes               50 K bytes
 Variable Message Signs           2 minutes             10 minutes               3 M bytes
      Matrix Signals              2 minutes             10 minutes               9 M bytes
       Traffic Data               5 minutes             10 minutes              30 M bytes
  Predefined Locations          On occurrence       On occurrence within        25 M bytes
                               within 5 minutes          5 minutes

Note that the estimated file sizes for the Variable Message Signs and Matrix Signal products
are “worse case” assuming all current devices are set. Under normal circumstances these
products will not include devices that are not set except where faults are reported. It should
also be noted that sizes of files could increase as more infrastructure, including traffic
monitoring equipment, is installed on the road network.

2.1   Event Product
The Event information product will contain details of all current or future Events known to
NTCC. The payload file will contain every NTCC Event as a Situation object. The structure of
the Event information product is defined in section 3.

2.2   Variable Message Sign Product
The Variable Message Signs (VMS) information product will contain the status of all currently
set or faulty VMS on the HA network. If the next publication no longer contains a particular
VMS, then either the message or fault has been cleared. The payload file will contain
VariableMessageSignSetting elements. The structure of the VMS information product is
defined in section 4.

2.3   Matrix Signal Product
The Matrix Signal information product will contain the status of all currently set or faulty
Matrix Signals on the HA network. If the next publication no longer contains a particular
Matrix Signal, then either the setting or fault has been cleared. The payload file will contain
MatrixSignSetting elements. The structure of the Matrix Signal information product is defined
in section 5.

2.4   Traffic Data Product
The Traffic Data1 information product will contain both loop-based (flow, speed, occupancy)
and ANPR-based (travel times – actual, ideal, expected) data on per Link and per Journey
Time Section basis respectively. A Link is a stretch of road on the HA network having
constant geometry i.e. consistent number of lanes, gradient, speed limit. A Journey Time


                                           Page 4
TCC-TIH-0049                    NTCC DATEX II Service                         Version 2


Section is a continuous stretch of road on the HA network having ANPR cameras at each
end to determine vehicle travel times.

The payload file will contain ElaboratedDataPublication elements. The structure of the Traffic
Data information product is defined in section 6.

2.5       Predefined Locations Product
The Predefined Location information product will contain location references for every Link,
Journey Time Section, Variable Message Sign and Matrix Signal on the HA network. To
reduce the size and complexity of other publications, they may refer to entries in this product
rather than fully describe a location. This product can therefore be used as a lookup table
from other information products.

The payload file will contain a PredefinedLocationsPublication element. The structure of the
Predefined Locations information product is defined in section 7.

2.6       Service Status
A service status file (metadata.xml) will be updated at least every three minutes, giving TIH
Receivers confidence that the DATEX II service is operational and providing up to date
information.

The service status file comprises two attributes in a single meta-data object, providing the
following:

      •    confirmationTime    the date/time that the service status file was last updated. This
                               confirms that the service is providing up to date and valid
                               payload files.
      •    confirmedTime       the date/time that the payload file was last updated, allowing
                               clients to determine when the payload file last changed.

The service status file will take the following form:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by NTCC -->
<MetaData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="metadata.xsd"
        confirmationTime="2007-06-15T13:12:52+01:00"
        confirmedTime="2007-06-15T13:09:52+01:00"
/>

Note that this file references an XML schema that defines the MetaData “element” and its
“attributes”. The service status file should be downloaded by TIH Receivers as part of their
‘poll-cycle’ in order to confirm that the service is still operational and to decided whether the
payload file has been updated. The Receiver’s poll frequency should be appropriate to the
update frequency of the service status file. If the service status “confirmationTime” has not
changed for at least five minutes then the client must assume that the DATEX II service is
unavailable.

TIH Receivers can disregard the service status file by using a “conditional” GET request
directly on the payload file. This is performed by setting the “If-Modified-Since” value in the
HTTP header to the “last-modified” value received previously in a HTTP response. The web
server will respond with a HTTP Response 304 (Not Modified) if the file has not changed
since the last request for it. This would make the client implementation easier but the clients
will not be able to determine if the information product is up-to-date.




                                              Page 5
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2


2.7        Access
A web server supporting HTTP 1.1 protocol will be used to serve the NTCC DATEX II
information products and will be accessible by TIH Receivers via the Internet on port 80 (note
this may be proxied). The web server will respond to both HTTP GET and POST requests in
the same way.

Access to the information products will be protected by basic authentication and will require
that Gzip and Deflate compression methods be requested. Failure to request compression
will result in a HTTP Response 400 or 406 (Bad Request).

NTCC does not currently support subscription management – all information is provided for
England.

In order to be interoperable with clients using Web Services, NTCC has wrapped all
information products with a static SOAP wrapper as described in the DATEX II Software
Developers Guide v1.0 available from the official DATEX II website.

For the Standard service, the information products will be available from the following URLs:
   1. Unplanned Events
       • http://datex2.tistrafficinfo.com/England/UnplannedEvent/metadata.xml
       • http://datex2.tistrafficinfo.com/England/UnplannedEvent/content.xml
   2. Current Planned Events
       • http://datex2.tistrafficinfo.com/England/CurrentPlanned/metadata.xml
       • http://datex2.tistrafficinfo.com/England/CurrentPlanned/content.xml
   3. Future Planned Events
       • http://datex2.tistrafficinfo.com/England/FuturePlanned/metadata.xml
       • http://datex2.tistrafficinfo.com/England/FuturePlanned/content.xml
   4. Current Roadworks
       • http://datex2.tistrafficinfo.com/England/CurrentRoadworks/metadata.xml
       • http://datex2.tistrafficinfo.com/England/CurrentRoadworks/content.xml
   5. Future Roadworks
       • http://datex2.tistrafficinfo.com/England/FutureRoadworks/metadata.xml
       • http://datex2.tistrafficinfo.com/England/FutureRoadworks/content.xml
   6. Variable Message Signs
       • http://datex2.tistrafficinfo.com/England/VariableMessageSign/metadata.xml
       • http://datex2.tistrafficinfo.com/England/VariableMessageSign/content.xml
   7. Matrix Signals
       • http://datex2.tistrafficinfo.com/England/MatrixSignals/metadata.xml
       • http://datex2.tistrafficinfo.com/England/MatrixSignals/content.xml
   8. Traffic Data
       • http://datex2.tistrafficinfo.com/England/TrafficData/metadata.xml
       • http://datex2.tistrafficinfo.com/England/TrafficData/content.xml
   9. Predefined Locations
       • http://datex2.tistrafficinfo.com/England/PredefinedLocation/metadata.xml
       • http://datex2.tistrafficinfo.com/England/PredefinedLocation/content.xml




                                           Page 6
TCC-TIH-0049             NTCC DATEX II Service                  Version 2


For the Premier service, the information products will be   available from host
datexii.tistrafficinfo.com using the same path.




                                   Page 7
TCC-TIH-0049                       NTCC DATEX II Service                               Version 2



3           Event Product
This section defines the format of the Event publication generated by NTCC, and defines the
meaning of the variable parts within the publication.

3.1         Event Format
Each Event publication comprises zero or more DATEX II situations representing a single
NTCC Event. Each such situation is a block of XML with structure given below. A DATEX II
publication for a particular Event is generated whenever the event details change.

NTCC Events are split up into Event Parts where a SituationRecord will represent each part.
In addition, each Event Part has associated affected links, which are the links that contain
traffic congestion caused by the event. Where affected links exist in an Event Part a
SituationRecord of type AbnornalTraffic will be used to describe the resultant effects.

The following template shows those parts that are common to all SituationRecords. It does
not show the specific parts of each type of Event (e.g. details of accidents, obstructions,
activities, etc.). DATEX II placeholders are shown enclosed within {}, and are explained later.

3.1.1       Event Message Template
<situation id="GUID{DATEX2_EVENT_EVENT_ID}">
     <relatedSituation>{DATEX2_EVENT_RELATED_SITUATION}</relatedSituation>
      <headerInformation>
          <areaOfInterest>regional</areaOfInterest>
          <confidentiality>restrictedToAuthoritiesTrafficOperatorsAndPublishers</confidentiality>
          <informationUsage>broadcast</informationUsage>
          <informationUsage>internet</informationUsage>
          <informationStatus>real</informationStatus>
     </headerInformation>
     <situationRecord xsi:type="{DATEX2_EVENT_TYPE}" id="GUID{DATEX2_EVENT_EVENT_PART_ID}">
          <situationRecordCreationReference>{DATEX2_EVENT_EVENT_NAME}</situationRecordCreationReference>
          <situationRecordCreationTime>{DATEX2_EVENT_CREATION_TIME}</situationRecordCreationTime>
          <situationRecordVersion>{DATEX2_EVENT_VERSION}</situationRecordVersion>
          <situationRecordVersionTime>{DATEX2_EVENT_VERSION_TIME}</situationRecordVersionTime>
          <situationRecordFirstSupplierVersionTime>{DATEX2_EVENT_FIRST_SUPPLIER_VERSION_TIME}
           </situationRecordFirstSupplierVersionTime>
          <probabilityOfOccurrence>{DATEX2_EVENT_PROBABILITY_OF_OCCURRENCE}</probabilityOfOccurrence>
          <sourceInformation>
                 <sourceCountry>gb</sourceCountry>
                 <sourceName>
                      <value lang="en">{DATEX2_EVENT_SOURCE}</value>
                 </sourceName>
          </sourceInformation>
          <validity>
                 <validityStatus>definedByValidityTimeSpec</validityStatus>
                 <validityTimeSpecification>
                      <overallStartTime>{DATEX2_EVENT_OVERALL_START_TIME}</overallStartTime>
                      <overallEndTime>{DATEX2_EVENT_OVERALL_END_TIME}</overallEndTime>
                      <validPeriod>
                            <startOfPeriod>{DATEX2_EVENT_START_PERIOD}</startOfPeriod>
                            <endOfPeriod>{DATEX2_EVENT_END_PERIOD}</endOfPeriod>
                            <recurringTimePeriodOfDay xsi:type="TimePeriodByHour">
                            {DATEX2_EVENT_TIME_PERIOD_OF_DAY}</recurringTimePeriodOfDay>
                      </validPeriod>
                 </validityTimeSpecification>
          </validity>
          <impact>
                 <impactOnTraffic>{DATEX2_EVENT_LEVEL_OF_DISRUPTION}</impactOnTraffic>
                 <impactDetails>
                      <capacityRemaining>{DATEX2_EVENT_CAPACITY_REMAINING}</capacityRemaining>
                      <numberOfLanesRestricted>{DATEX2_EVENT_RESTRICTED_LANES}</numberOfLanesRestricted>
                      <numberOfOperationalLanes>{DATEX2_EVENT_OPERATIONAL_LANES}</numberOfOperationalLanes>
                      <originalNumberOfLanes>{DATEX2_EVENT_ORIGINAL_LANES}</originalNumberOfLanes>
                      <trafficRestrictionType>{DATEX2_EVENT_RESTRICTION_TYPE}</trafficRestrictionType>
                 </impactDetails>
                 <delays>
                      <delayTimeValue>{DATEX2_EVENT_DELAY}</delayTimeValue>



                                                 Page 8
TCC-TIH-0049                        NTCC DATEX II Service                               Version 2

                 </delays>
            </impact>
            <nonGeneralPublicComment>
                 <comment>
                      <value lang="en"> {DATEX2_EVENT_COMMENT}</value>
                 </comment>
            </nonGeneralPublicComment>
            <groupOfLocations>{DATEX2_EVENT_LOCATION}</groupOfLocations>
      </situationRecord>
</situation>


3.1.2      Event Placeholders
This section defines the placeholders used in the NTCC Event publication.

3.1.2.1 {DATEX2_EVENT_EVENT_ID}
Each NTCC Event has a unique event identifier

3.1.2.2    {DATEX2_EVENT_EVENT_PART_ID}
Each NTCC Event may contain one or more Event Parts that map onto DATEX II
SituationRecords. Each Event Part has a unique event identifier preceded with an additional
sequence number defined as ‘GUID{sequence_number}-{event_part_id}’

3.1.2.3   {DATEX2_EVENT_EVENT_NAME}
Each NTCC Event has a unique event reference containing an indication of type, year,
month, day and incremental sequence number e.g. U-07-1031-0001.

3.1.2.4 {DATEX2_EVENT_TYPE}
NTCC Events map onto DATEX II Situation Record Types as follows.

 NTCC Event Reason /       DATEX II Situation Record         DATEX II Supplemental       DATEX II Supplemental
    Sub-Reason                       Type                      Enumeration Name           Enumeration Value
    Road Works                MaintenanceWorks                roadMaintenanceType             roadworks

Road Works / Resurfacing       MaintenanceWorks               roadMaintenanceType            resurfacingWork
     Road Works /              MaintenanceWorks               roadMaintenanceType               repairWork
    Barrier Repairs
     Road Works /              MaintenanceWorks               roadMaintenanceType              repairWork
     Bridge Repairs
     Road Works /              MaintenanceWorks               roadMaintenanceType             roadsideWork
     Gully Cleaning
     Road Works /              MaintenanceWorks               roadMaintenanceType           grassCuttingWork
     Grass Cutting
     Sports Event                   Activities                   publicEventType              sportsMeeting

      Sports Event /                Activities                   publicEventType              footballMatch
      Football Match
      Sports Event /                Activities                   publicEventType               cricketMatch
      Cricket Match
      Sport Event /                 Activities                   publicEventType          motorSportRaceMeeting
       Motor Sport
      Sport Event /                 Activities                   publicEventType          motorSportRaceMeeting
    British Grand Prix
   Entertainment Event              Activities                   publicEventType               majorEvent

  Entertainment Event /             Activities                   publicEventType                exhibition
        Exhibition
  Entertainment Event /             Activities                   publicEventType                  show
      Motor Show
  Entertainment Event /             Activities                   publicEventType                  show
       Boat Show
     Other Planned                  Activities                disturbanceActivityType             other

    Other Planned /            RoadsideAssistance            roadsideAssistanceType          vehicleRecovery
    Vehicle Recovery
       Accident                     Accident                       accidentType                  accident




                                                    Page 9
TCC-TIH-0049                        NTCC DATEX II Service                                 Version 2

        Accident /                  Accident                       accidentType                seriousAccident
    Serious Accident
        Accident /                  Accident                       accidentType              multivehicleAccident
  Multi-vehicle Accident
        Accident /                  Accident                       accidentType            jackknifedArticulatedLorry
    Jack Knifed Lorry
        Accident /             VehicleObstruction              vehicleObstructionType           vehicleOnFire
       Vehicle Fire
        Accident /             GeneralObstruction                 obstructionType          rescueAndRecoveryWork
    Vehicle Recovery
        Accident /                  Accident                       accidentType               overturnedVehicle
   Overturned Vehicle
        Congestion               AbnormalTraffic                abnormalTrafficType               slowTraffic

    Animals On Road        AnimalPresenceObstruction            animalPresenceType           animalsOnTheRoad

    People On Road             GeneralObstruction                 obstructionType             peopleOnRoadway

       Obstruction             GeneralObstruction                 obstructionType             objectOnTheRoad

     Obstruction /             VehicleObstruction              vehicleObstructionType           vehicleOnFire
      Vehicle Fire
     Obstruction /             GeneralObstruction                 obstructionType             objectOnTheRoad
        Debris
     Obstruction /             VehicleObstruction              vehicleObstructionType        brokenDownVehicle
  Broken down vehicle
       Spillage                GeneralObstruction                 obstructionType            spillageOnTheRoad

       Spillage /                   Accident                       accidentType            chemicalSpillageAccident
     Chemical Spill
       Spillage /              GeneralObstruction                 obstructionType                  shedLoad
      Shed Load
       Spillage /                   Accident                       accidentType              fuelSpillageAccident
     Oil Fuel Spill
       Flooding             EnvironmentalObstruction      environmentalObstructionType              flooding

           Ice             WeatherRelatedRoadConditio   weatherRelatedRoadConditionType               ice
                                       ns
        Security                   Activities                 disturbanceActivityType            securityAlert

    Other Unplanned                 Activities                disturbanceActivityType                other

 Miscellaneous Closure        NetworkManagement               networkManagementType               roadClosed

           Fog             PoorEnvironmentConditions           poorEnvironmentType                    fog

          Rain             PoorEnvironmentConditions           poorEnvironmentType                    rain

          Snow             WeatherRelatedRoadConditio   weatherRelatedRoadConditionType        snowOnTheRoad
                                       ns
       High Winds          PoorEnvironmentConditions           poorEnvironmentType               strongWinds

     Abnormal Load             VehicleObstruction              vehicleObstructionType           abnormalLoad

    Visibility Reduced     PoorEnvironmentConditions           poorEnvironmentType             visibilityReduced

* Emergency Roadworks          MaintenanceWorks                roadMaintenanceType                roadworks

* Emergency Roadworks /        MaintenanceWorks                roadMaintenanceType             resurfacingWork
      Resurfacing
* Emergency Roadworks /        MaintenanceWorks                roadMaintenanceType                repairWork
     Barrier repairs
* Emergency Roadworks /        MaintenanceWorks                roadMaintenanceType                repairWork
    Bridge Repairs


Notes:
   • For emergency roadworks, the attribute “urgentRoadworks” will be included and set
       to true
   • For repairWork, add the attribute “subjectTypeOfWorks” and set to a value from
       subjectTypeOfWorksEnum (e.g. crashBarrier, bridge etc…)



                                                    Page 10
TCC-TIH-0049                   NTCC DATEX II Service                          Version 2


3.1.2.5     {DATEX2_EVENT_CREATION_TIME}
This is the time that the Event was created in the NTCC system.

3.1.2.6     {DATEX2_EVENT_VERSION}
Throughout the lifecycle of an NTCC Event, the DATEX II Event publication will show details
of the latest version. As changes may occur more frequently than the publication interval, the
version may be incremented by more than one.

3.1.2.7     {DATEX2_EVENT_VERSION_TIME}
This is the time that the last modification was made to this Event at NTCC.

3.1.2.8 {DATEX2_EVENT_FIRST_SUPPLIER_VERSION_TIME}
As NTCC operational staff manually updates every NTCC Event, this will be the same as
{DATEX2_EVENT_VERSION_TIME}.

3.1.2.9   {DATEX2_EVENT_PROBABILITY_OF_OCCURRENCE}
Every NTCC Event is either active or inactive depending on the active times associated with
the event parts. The probability of an event occurrence is certain when the event is active
and probable at all other times.

3.1.2.10 {DATEX2_EVENT_SOURCE}
This is the source/supplier of information to NTCC, including for example, a Regional Control
Centre, the TCC System or as seen on CCTV.

3.1.2.11 {DATEX2_EVENT_OVERALL_START_TIME}
This is the earliest start time of all of the Event Parts associated with an NTCC Event.

3.1.2.12 {DATEX2_EVENT_OVERALL_END_TIME}
This is the latest end time of all of the Event Parts associated with an NTCC Event.

3.1.2.13 {DATEX2_EVENT_START_PERIOD}
This is the start time of the Event Part.

3.1.2.14 {DATEX2_EVENT_END_PERIOD}
This is the end time of the Event Part.

3.1.2.15 {DATEX2_EVENT_TIME_PERIOD_OF_DAY}
This is the start and end time of the ‘active’ period of the Event Part, for example, where
Roadworks are active overnight only.

3.1.2.16 {DATEX2_EVENT_LEVEL_OF_DISRUPTION}
This is an assessment of the impact on traffic conditions resulting from the Event as follows:

       unknown
       freeFlow – zero minutes delay
       heavy – less than 15 minutes delay
       congested – between 15 and 3600 minutes delay
       impossible – greater than 3600 minutes delay but also indicates road closures

3.1.2.17 {DATEX2_EVENT_CAPACITY_REMAINING}
This is percentage capacity remaining (excluding the hard shoulder), calculated using the
following formula:



                                           Page 11
TCC-TIH-0049                    NTCC DATEX II Service                         Version 2


        (Number of operational lanes / Number of original lanes) * 100

3.1.2.18 {DATEX2_EVENT_RESTRICTED_LANES}
This is the number of lanes (excluding the hard shoulder) in the primary location link that are
affected by the Event. Note that this is not the number of lanes closed unless the effect is
closure.

3.1.2.19 {DATEX2_EVENT_OPERATIONAL_LANES}
This is the number of remaining functional lanes (excluding the hard shoulder), calculated
using the following formula:
        (Number of original lanes – Number of restricted lanes)

Note that a value of zero will indicate a full closure.

3.1.2.20 {DATEX2_EVENT_ORIGINAL_LANES}
This is the number of lanes (excluding the hard shoulder) in the primary location link.

Note     that   the    four     placeholders (DATEX2_EVENT_CAPACITY_REMAINING,
DATEX2_EVENT_RESTRICTED_LANES, DATEX2_EVENT_OPERATIONAL_LANES and
DATEX2_EVENT_ORIGINAL_LANES) are only populated where the Event affects a section
of road and not where it affects an area.

3.1.2.21 {DATEX2_EVENT_RESTRICTION_TYPE}
This will be either “carriagewayBlocked” if the primary affected link has no operational lanes
otherwise “carriagewayPartiallyObstructed”.

3.1.2.22 {DATEX2_EVENT_DELAY}
Used in conjunction with {DATEX2_EVENT_LEVEL_OF_DISRUPTION}, this placeholder will
indicate the anticipated delay in seconds caused by the Event.

3.1.2.23 {DATEX2_EVENT_COMMENT}
A textual description of the Event, its effect and anticipated end time are provided.

3.1.2.24 {DATEX2_EVENT_RELATED_SITUATION}
Where Events are consequences of other Events, for example congestion on the opposite
carriageway due to onlookers, the secondary Event will refer to the primary Event using
GUID{DATEX2_EVENT_EVENT_ID}.

3.1.2.25 {DATEX2_EVENT_LOCATION}
Locations will be described using TPEG-Loc classes TPEGSimplePoint, TPEGFramedPoint
or TPEGGeometricArea. Points are defined by latitude/longitude in addition to road name,
intercept road and junction number where available. Areas are defined by a centre point and
radius of the extent of the Event.

Note that any components that will never be used by NTCC have been omitted from the
following template definitions, for example, NTCC only defines one intercept road for a given
junction, so that the second intercept road component is omitted from the templates.

3.2   Event Locations
Some guidance for the use of NTCC derived locations.




                                             Page 12
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2


3.2.1      Linear Locations
The following points need to be borne in mind when considering linear locations of Events as
they are coded in a DATEX II publication.

   1. A location consists of two parts – the “Location Links” and the “Affected Links”. When
      describing an Event within a DATEX II publication, the situation element representing
      the Event itself will have a location based on the Location Links, while the situation
      element representing the queue upstream of the Event will have a location based on
      the Affected Links.

   2. Human-readable locations will be expressed as definitions of upstream and
      downstream junctions in terms of junction numbers and / or intercept road names,
      together with the name of the principle link affected by the Event or by the queue. For
      the “Location Links” this is the primary link as selected by Control Room staff at
      NTCC; for the “Affected Links” (or the consequent queue) this is the link at the tail of
      the queue, i.e. the most upstream link in the set.

   3. The junctions reported in the upstream and downstream junctions are the
      “dissemination-capable” junctions. A junction is “dissemination-capable” if it satisfies
      the two criteria that:
          • It is easily recognised by motorists (i.e. it has a junction number or the
             intercept road is one motorists will recognise, a motorway or an A-road).
          • It is “usable” in the direction of approach. For a junction upstream of a
             location, this means that traffic may leave the road at this junction; for a
             junction downstream of a location, it means that traffic may rejoin the road at
             the junction.

   4. The machine-readable version of the principle Link is the WGS84 co-ordinates of the
      mid point of the link. The machine-readable version of an upstream or downstream
      junction is the WGS84 co-ordinates of a point within the junction being described by
      the human-readable location. The exact point within the junction that is used varies
      depending on the type of linear location.

   5. A consequence of the “dissemination-capable” junction is that the granularity of the
      upstream and downstream junction locations in the disseminated message is not as
      great as the granularity of the Link(s) containing the Event.

       For example, consider the following figure, showing the M62 eastbound between J21
       and J22. Links are shown as lines and Nodes are shown as dots.
                            A             B                             C
                                xxxxxxxx



                 J21                                                               J22

       The eastbound carriageway is split into two Links (AB and BC) because of a change
       in the number of lanes at Node B.

       An Event on Link AB will have the same upstream and downstream disseminated
       location as an Event on Link BC; that is the location in either case will be “M62
       eastbound between J21 and J22”, and the WGS84 co-ordinates will be of a point
       within junction J21 (actually node A) and a point within junction J22 (node C).



                                           Page 13
TCC-TIH-0049                       NTCC DATEX II Service                       Version 2


        However, in one case the principle Link described will be “Link AB”, with the WGS84
        co-ordinates of the middle of Link AB, while when the Event is in “Link BC”, the
        WGS84 co-ordinates will be the middle of Link BC.

    6. Where a direction is given it is the predominant direction of the road as a whole,
       rather than the local orientation of the particular link. Thus, for example, the M40 is
       considered to be a north-south road, and directions given will be either “northBound”
       or “southBound”, even for links at the southern end, which has a largely east-west
       orientation.

3.2.2       TPEGGeometricArea
This template is used when an Event covers an area rather than a specific section of the
road, for example, Weather.
<locationContainedInGroup xsi:type="Area">
     <tpegareaLocation xsi:type="TPEGGeometricArea">
          <tpegLocationType>largeArea</tpegLocationType>
          <radius>{DATEX2_EVENT_AREA_RADIUS}</radius>
          <centrePoint>
               <latitude>{DATEX2_EVENT_LATITUDE}</latitude>
                 <longitude>{DATEX2_EVENT_LONGITUDE}</longitude>
          </centrePoint>
          <name>
               <descriptor>
                     <value lang="en">{DATEX2_EVENT_AREA_DESCRIPTOR}</value>
               </descriptor>
               <tpegDescriptorType>areaName</tpegDescriptorType>
          </name>
     </tpegareaLocation>
</locationContainedInGroup>


3.2.2.1    {DATEX2_EVENT_AREA_RADIUS}
For Events affecting an area such as Weather, this is the radius in metres of the affected
area, centred on the defined location point.

3.2.2.2    {DATEX2_EVENT_AREA_DESCRIPTOR}
For Events affecting an area such as Weather, this is the textual description of the area
affected by the Event, for example, “The Vale of York”.




                                                 Page 14
TCC-TIH-0049                       NTCC DATEX II Service                                Version 2



3.2.3      TPEGSimplePoint
This template is used when the Event is at the intersection of two roads, rather than between
two intersections.
<locationContainedInGroup xsi:type="Point">
     <tpegpointLocation xsi:type="TPEGSimplePoint">
           <tpegDirection>{DATEX2_EVENT_DIRECTION}</tpegDirection>
          <tpegLocationType>intersection</tpegLocationType>
          <point xsi:type="TPEGJunction">
               <pointCoordinates>
                     <latitude>{DATEX2_EVENT_LATITUDE}</latitude>
                     <longitude>{DATEX2_EVENT_LONGITUDE}</longitude>
               </pointCoordinates>
               <name>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_SIMPLE_POINT_JUNCTION_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>junctionName</tpegDescriptorType>
               </name>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_ EVENT_SIMPLE_POINT_ROAD_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
               </ilc>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_ EVENT_SIMPLE_POINT_INTERCEPT_ROAD}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
               </ilc>
          </point>
     </tpegpointLocation>
</locationContainedInGroup>


3.2.3.1     {DATEX2_EVENT_DIRECTION}
This is the direction of the carriageway affected by the Event. Directions are encoded within
DATEX II messages according to the TPEG table loc02 direction type. Values used are:

        anticlockwise
        clockwise
        eastBound
        northBound
        southBound
        westBound
        unknown

3.2.3.2    {DATEX2_EVENT_SIMPLE_POINT_JUNCTION_NAME}
Where roads have junction numbers that are, in the opinion of the Highways Agency, in
public use they will be used.

3.2.3.3    {DATEX2_EVENT_SIMPLE_POINT_ROAD_NAME}
For point and linear locations, this is the road name of the primary link affected by an Event.

3.2.3.4  {DATEX2_EVENT_SIMPLE_POINT_INTERCEPT_ROAD}
Where roads and junctions numbers are not available, intercepting road names will be used.




                                                 Page 15
TCC-TIH-0049                      NTCC DATEX II Service                               Version 2



3.2.4      TPEGFramedPoint
This template is used when the Event is between two points on a section of road, such as on
a main carriageway between two intersections.
<locationContainedInGroup xsi:type="Point">
      <tpegpointLocation xsi:type="TPEGFramedPoint">
          <tpegDirection>{DATEX2_EVENT_DIRECTION}</tpegDirection>
          <tpegLocationType>framedPoint</tpegLocationType>
          <framedPoint>
               <pointCoordinates>
                     <latitude>{DATEX2_EVENT_LATITUDE}</latitude>
                     <longitude>{DATEX2_EVENT_LONGITUDE}</longitude>
               </pointCoordinates>
               <name>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_LINK_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>linkName</tpegDescriptorType>
               </name>
          </framedPoint>
          <to xsi:type="TPEGJunction">
               <pointCoordinates>
                     <latitude>{DATEX2_EVENT_LATITUDE}</latitude>
                     <longitude>{DATEX2_EVENT_LONGITUDE}</longitude>
               </pointCoordinates>
               <name>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_DS_JUNCTION_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>junctionName</tpegDescriptorType>
               </name>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_DS_ROAD_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
               </ilc>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_DS_INTERCEPT_ROAD}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
               </ilc>
          </to>
          <from xsi:type="TPEGJunction">
               <pointCoordinates>
                     <latitude>{DATEX2_EVENT_LATITUDE}</latitude>
                     <longitude>{DATEX2_EVENT_LONGITUDE}</longitude>
               </pointCoordinates>
               <name>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_US_JUNCTION_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>junctionName</tpegDescriptorType>
               </name>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_US_ROAD_NAME}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
               </ilc>
               <ilc>
                     <descriptor>
                           <value lang="en">{DATEX2_EVENT_FRAMED_POINT_US_INTERCEPT_ROAD}</value>
                     </descriptor>
                     <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
               </ilc>
          </from>
     </tpegpointLocation>
</locationContainedInGroup>




                                                Page 16
TCC-TIH-0049                   NTCC DATEX II Service                          Version 2


3.2.4.1    {DATEX2_EVENT_LATITUDE}
The latitude of a point expressed using WGS84.

3.2.4.2    {DATEX2_EVENT_LONGITUDE}
The longitude of a point expressed using WGS84.

3.2.4.3    {DATEX2_EVENT_FRAMED_POINT_US_JUNCTION_NAME} and
           {DATEX2_EVENT_FRAMED_POINT_DS_JUNCTION_NAME}
Where roads have junction numbers that are, in the opinion of the Highways Agency, in
public use they will be used.

3.2.4.4    {DATEX2_EVENT_FRAMED_POINT_US_ROAD_NAME} and
           {DATEX2_EVENT_FRAMED_POINT_DS_ROAD_NAME}
For point and linear locations, this is the road name of the primary link affected by an Event.

3.2.4.5  {DATEX2_EVENT_FRAMED_POINT_US_INTERCEPT_ROAD} and
         {DATEX2_EVENT_FRAMED_POINT_DS_INTERCEPT_ROAD}
Where roads and junctions numbers are not available, intercepting road names will be used.

3.2.4.6  {DATEX2_EVENT_FRAMED_POINT_LINK_NAME}
The name of the principle DATEX II predefined location link affected by the Event.




                                           Page 17
TCC-TIH-0049                       NTCC DATEX II Service                                Version 2



4           Variable Message Sign Product
This section defines the format of the DATEX II VMS publication.

4.1         VMS Format
Each DATEX II publication comprises zero or more DATEX II SituationRecords, each
representing the status of an active or faulty VMS with the following structure.

4.1.1       VMS Template
<situation id="GUID-VariableMessageSign">
      <headerInformation>
            <areaOfInterest>national</areaOfInterest>
            <confidentiality> restrictedToAuthoritiesTrafficOperatorsAndPublishers </confidentiality>
            <informationUsage>broadcast</informationUsage>
            <informationUsage>internet</informationUsage>
            <informationStatus>real</informationStatus>
      </headerInformation>
      <situationRecord xsi:type="VariableMessageSignSetting" id="GUID{DATEX2_VMS_EQUIPMENT_ID}">
            <situationRecordCreationTime>{DATEX2_VMS_SITUATION_RECORD_CREATION_TIME}
            </situationRecordCreationTime>
            <situationRecordVersion>{DATEX2_VMS_SITUATION_RECORD_VERSION}</situationRecordVersion>
            <situationRecordVersionTime>{DATEX2_VMS_SITUATION_RECORD_VERSION_TIME}
            </situationRecordVersionTime>
            <situationRecordFirstSupplierVersionTime>{DATEX2_VMS_SITUATION_FIRST_SUPPLIER_VERSION_TIME}
            </situationRecordFirstSupplierVersionTime>
            <probabilityOfOccurrence>certain</probabilityOfOccurrence>
            <sourceInformation>
                  <sourceCountry>gb</sourceCountry>
                  <sourceName>
                       <value lang="en">{DATEX2_VMS_SOURCE_NAME}</value>
                  </sourceName>
            </sourceInformation>
            <validity>
                  <validityStatus>active</validityStatus>
                  <validityTimeSpecification>
                       <overallStartTime>{DATEX2_VMS_OVERALL_START_TIME}</overallStartTime>
                  </validityTimeSpecification>
            </validity>
            <groupOfLocations>
                  <locationContainedInGroup xsi:type="LocationByReference">
                       <predefinedLocationReference>{DATEX2_VMS_LOCATION_REFERENCE}
                        </predefinedLocationReference>
                  </locationContainedInGroup>
            </groupOfLocations>
            <reasonForSetting>
                  <value lang="en">{DATEX2_IMP_REASON}</value>
            </reasonForSetting>
            <numberOfCharacters>{DATEX2_VMS_NUMBER_OF_CHARACTERS}</numberOfCharacters>
            <numberOfRows>{DATEX2_VMS_NUMBER_OF_ROWS}</numberOfRows>
            <vmsFault>{DATEX2_VMS_FAULT}</vmsFault>
            :
            <vmsFault>{DATEX2_VMS_FAULT}</vmsFault>
            <vmsIdentifier>{DATEX2_VMS_IDENTIFER}</vmsIdentifier>
            <vmsLegend>{DATEX2_VMS_LEGEND}</vmsLegend>
            :
            <vmsLegend>{DATEX2_VMS_LEGEND}</vmsLegend>
            <vmsType>{DATEX2_VMS_TYPE}</vmsType>
      </situationRecord>
</situation>

Note – ‘:’ indicates a repeated element.

4.1.2      VMS Placeholders
This section defines the placeholders used in the NTCC VMS publication.

4.1.2.1     {DATEX2_VMS_EQUIPMENT_ID}
This is a unique identifier assigned to the Variable Message Sign by NTCC.


                                                 Page 18
TCC-TIH-0049                   NTCC DATEX II Service                         Version 2


4.1.2.2     {DATEX2_VMS_SITUATION_RECORD_CREATION_TIME}
This is the first time the record has been created.

4.1.2.3    {DATEX2_VMS_SITUATION_RECORD_VERSION}
As VMS are set and cleared throughout their lifecycle, the DATEX II VMS publication will
show details of the latest version where the sign is either set or faulty. As changes may occur
more frequently than the publication interval, the version may be incremented by more than
one.

4.1.2.4     {DATEX2_VMS_SITUATION_RECORD_VERSION_TIME}
This is the time that the last modification was made to this VMS.

4.1.2.5 {DATEX2_VMS_SITUATION_FIRST_SUPPLIER_VERSION_TIME}
As NTCC is informed of Variable Message Sign status changes, this will be the same as
{DATEX2_VMS_SITUATION_RECORD_VERSION_TIME}.

4.1.2.6     {DATEX2_VMS_SOURCE_NAME}
This is the Control Office identifier of the Police or Highways Agency Regional Control Centre
that reported the VMS setting to NTCC via the TCCI and not necessarily that which
originated the setting. Valid values are:

       10      North East RCC
       20      North West RCC
       30      Eastern RCC
       40      West Midlands RCC
       45      West Midlands ATM
       50      East Midlands RCC
       60      South West RCC
       70      South East RCC
       71      Dartford PCO

4.1.2.7     {DATEX2_VMS_OVERALL_START_TIME}
This is the time that the VMS status update was received by NTCC.

4.1.2.8    {DATEX2_VMS_LOCATION_REFERENCE}
The location of the VMS will be a cross-reference to the Predefined Location publication,
which accurately describes the location using TPEG-Loc format.

4.1.2.9     {DATEX2_VMS_NUMBER_OF_CHARACTERS}
This is the number of characters that can be displayed on one row of the VMS.

4.1.2.10 {DATEX2_VMS_NUMBER_OF_ROWS}
This is the number of rows that can be displayed on the VMS.

4.1.2.11 {DATEX2_VMS_FAULT}
Where VMS are reported to NTCC as faulty, a row will be populated for each individual VMS
fault reported. It should be noted that there are many more possible faults than can be
expressed in DATEX II so different faults may result in more than one of the following values:

       communicationsFailure
       incorrectMessageDisplayed
       other



                                           Page 19
TCC-TIH-0049                  NTCC DATEX II Service                        Version 2


4.1.2.12 {DATEX2_VMS_IDENTIFER}
This is the geographic address of the VMS, which can be used to provide an approximate
location for the VMS.

4.1.2.13 {DATEX2_VMS_LEGEND}
A row will be populated to accommodate each individual row of a displayed message.

4.1.2.14 {DATEX2_VMS_TYPE}
This is the type of VMS using the following values:

            ContinuousSign          Fixed Plate Message Sign
            MonochromeGraphic       Variable Message Sign (excluding MS4 type)
            ColourGraphic           Variable Message Sign (MS4 type only)

4.1.2.15 {DATEX2_IMP_REASON}
The implementation reason is the cause associated with the setting of the VMS within the
Control Office. Valid values are:

   UpdateInitialisation                               Unconfirmed
   Clear                                              Fog
   PartClear                                          OncomingVehicle
   Accident                                           Test
   Congestion                                         ClosuresDiversions
   RoadWorksConing                                    Visibility
   Obstruction                                        Rain
   Debris                                             Other
   Incident                                           Ice
   Animals                                            Wind
   Pedestrians                                        Security
   LargeLoad                                          TidalSetting




                                           Page 20
TCC-TIH-0049                         NTCC DATEX II Service                                  Version 2



5            Matrix Signal Product
This section defines the format of the DATEX II Matrix Signal publication.

5.1          Matrix Signal Format
Each DATEX II publication comprises zero or more DATEX II SituationRecords, each
representing the status of an active or faulty VMS with the following structure.

5.1.1        Matrix Signal Template
<situation id="GUID-MatrixSignals">
      <headerInformation>
            <areaOfInterest>national</areaOfInterest>
            <confidentiality> restrictedToAuthoritiesTrafficOperatorsAndPublishers </confidentiality>
            <informationUsage>broadcast</informationUsage>
            <informationUsage>internet</informationUsage>
            <informationStatus>real</informationStatus>
      </headerInformation>
      <situationRecord xsi:type="MatrixSignSetting" id="GUID{DATEX2_MATRIX_EQUIPMENT_ID}">
            <situationRecordCreationTime>{DATEX2_MATRIX_CREATION_TIME}</situationRecordCreationTime>
            <situationRecordVersion>{DATEX2_MATRIX_VERSION}</situationRecordVersion>
            <situationRecordVersionTime>{DATEX2_MATRIX_VERSION_TIME}</situationRecordVersionTime>
              <situationRecordFirstSupplierVersionTime>{DATEX2_MATRIX_FIRST_SUPPLIER_VERSION_TIME}
            </situationRecordFirstSupplierVersionTime>
            <probabilityOfOccurrence>certain</probabilityOfOccurrence>
            <sourceInformation>
                   <sourceCountry>gb</sourceCountry>
                   <sourceName>
                        <value lang="en">{DATEX2_MATRIX_SOURCE_NAME}</value>
                   </sourceName>
            </sourceInformation>
            <validity>
                   <validityStatus>active</validityStatus>
                   <validityTimeSpecification>
                        <overallStartTime>{DATEX2_MATRIX_OVERALL_START_TIME}</overallStartTime>
                   </validityTimeSpecification>
            </validity>
            <groupOfLocations>
                   <locationContainedInGroup xsi:type="LocationByReference">
                   <predefinedLocationReference>{DATEX2_MATRIX_LOCATION_REFERENCE}
                   </predefinedLocationReference>
            </locationContainedInGroup>
              </groupOfLocations>
            <reasonForSetting>
                   <value lang=”en”>{DATEX2_IMP_REASON}</value>
            </reasonForSetting>
            <aspectDisplayed>{DATEX2_MATRIX_ASPECT_DISPLAYED}</aspectDisplayed>
            <matrixFault>{DATEX2_MATRIX_FAULT}</matrixFault>
            :
            <matrixFault>{DATEX2_MATRIX_FAULT}</matrixFault>
            <matrixIdentifier>{DATEX2_MATRIX_IDENTIFER}</matrixIdentifier>
      </situationRecord>
</situation>

Note – ‘:’ indicates a repeated element.

5.1.2      Matrix Signal Placeholders
This section defines the placeholders used in the NTCC Matrix Signals publication.

5.1.2.1     {DATEX2_MATRIX_EQUIPMENT_ID}
This is a unique identifier assigned to the Matrix Signal by NTCC.

5.1.2.2     {DATEX2_MATRIX_CREATION_TIME}
This is the first time the record has been created.




                                                   Page 21
TCC-TIH-0049                   NTCC DATEX II Service                          Version 2


5.1.2.3    {DATEX2_MATRIX_VERSION}
As Matrix Signals are set and cleared throughout their lifecycle, the DATEX II Matrix Signal
publication will show details of the latest version where the signal is either set or faulty. As
changes may occur more frequently than the publication interval, the version may be
incremented by more than one.

5.1.2.4     {DATEX2_MATRIX_VERSION_TIME}
This is the time that the last modification was made to this Matrix Signal.

5.1.2.5 {DATEX2_MATRIX_SITUATION_FIRST_SUPPLIER_VERSION_TIME}
As NTCC is informed of Matrix Signal status changes, this will be the same as
{DATEX2_MATRIX_VERSION_TIME}.

5.1.2.6     {DATEX2_MATRIX_SOURCE_NAME}
    This is the Control Office identifier of the Police or Highways Agency Regional Control
    Centre that reported the Matrix Signal setting to NTCC via the TCCI and not necessarily
    that, which originated the setting. See {DATEX2_VMS_SOURCE_NAME} for values.

5.1.2.7     {DATEX2_MATRIX_OVERALL_START_TIME}
This is the time that the Matrix Signal status update was received by NTCC.

5.1.2.8    {DATEX2_MATRIX_LOCATION_REFERENCE}
The location of the Matrix Signal will be a cross-reference to the Predefined Location
publication, which accurately describes the location using TPEG-Loc format.

5.1.2.9   {DATEX2_MATRIX_ASPECT_DISPLAYED}
The current aspect displayed on a Matrix Signal will have one of the following values:

          Aspect description                            DATEX II (AspectDisplayed)
               Undefined                                           UDF
                   Off                                              OFF
           Nation Restriction                                        NR
            Restriction End                                          RE
                  Stop                                             STOP
              Advisory 20                                            20
              Advisory 30                                            30
              Advisory 40                                            40
              Advisory 50                                            50
              Advisory 60                                            60
              Advisory 70                                            70
              Advisory 80                                            80
             Advisory 100                                           100
             Advisory 120                                           120
           Lane Divert Right                                        LDR
              Tidal Close                                          REDX
            Lane Divert Left                                        LDL
          Motorway Divert Left                                     MDVL
            Two way traffic                                       TWAY
           Lane 2 closed of 2                                        1T
           Lane 1 closed of 2                                        T1
         Lanes 1 & 2 closed of 3                                    TT1
           Lane 1 closed of 3                                       T11



                                            Page 22
TCC-TIH-0049                 NTCC DATEX II Service                        Version 2


         Lanes 2 & 3 closed of 3                                 1TT
           Lane 3 closed of 3                                    11T
               Lane Open                                         1(C)
          Motorway Divert Right                                 MDVR
                  Fog                                           FOG
                 Queue                                            Q
           Lane 4 closed of 4                                   111T
         Lanes 3 & 4 closed of 4                                11TT
        Lanes 2,3 & 4 closed of 4                               1TTT
           Lane 1 closed of 4                                   T111
         Lanes 1 & 2 closed of 4                                TT11
        Lanes 1,2 & 3 closed of 4                               TTT1
             Mandatory 20                                        20R
             Mandatory 30                                        30R
             Mandatory 40                                        40R
             Mandatory 50                                        50R
             Mandatory 60                                        60R
             Mandatory 70                                        70R
             Mandatory 80                                        80R
             Mandatory 100                                      100R
             Mandatory 120                                      120R
                 Test 1                                         TST1
                 Test 2                                         TST2
                 Test 3                                         TST3
                 Test 4                                         TST4
               MIDAS Off                                        MOFF
            Amber Flashers                                      AMB
            Tidal Divert Left                                    tDL
            Not yet allocated                                   None
               Undefined                                         UDF
            Not yet allocated                                   None
               Undefined                                         UDF

5.1.2.10 {DATEX2_MATRIX_FAULT}
NTCC only records the availability of Matrix Signals and not their faults so the only valid
value is:

       unknown

5.1.2.11 {DATEX2_MATRIX_IDENTIFIER}
This is the geographic address of the Matrix Signal, which can be used to provide an
approximate location for the signal.

5.1.2.12 {DATEX2_IMP_REASON}
The implementation reason is the cause associated with the setting of the VMS within the
Control Office. See previous explanation for {DATEX2_IMP_REASON} for values.




                                         Page 23
TCC-TIH-0049                          NTCC DATEX II Service                           Version 2



6             Traffic Data Product
This section defines the format of the Traffic Data publication generated by NTCC, and
defines the meanings of the variable parts within the publication.

6.1           Traffic Data Format
NTCC collects traffic data generated each minute from Traffic Monitoring Units and
Highways Agency’s MIDAS, in addition to travel data from ANPR cameras, at 5-minute
intervals. This data is processed on receipt to be used by Control Room staff and
applications at NTCC before being redistributed.

Loop-based data such as speed, flows and occupancy is reported on a per Link basis
whereas ANPR-based data is reported on a per Journey Time Section basis.

Each Elaborated Data publication comprises one or more instances of elaborated data to
provide:

      •   Current average travel times to traverse the Journey Time Section
      •   Expected travel times based on historic profiles
      •   Theoretical ideal travel times assuming free flowing traffic
      •   Current average vehicle flow rates for all vehicles and categorised by vehicle length
      •   Current average vehicle speeds per Link
      •   Current average occupancy per Link

6.1.1         Traffic Data Template
<periodDefault>300</periodDefault>
<headerInformation>
     <areaOfInterest>national</areaOfInterest>
     <confidentiality> restrictedToAuthoritiesTrafficOperatorsAndPublishers </confidentiality>
     <informationUsage>broadcast</informationUsage>
     <informationUsage>internet</informationUsage>
     <informationStatus>real</informationStatus>
</headerInformation>
<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_JOURNEY_TIME_SECTION_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TravelTimeValue">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                     <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                     </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <travelTime>{DATEX2_TRAFFIC_TRAVEL_TIME}</travelTime>
          <freeFlowTravelTime>{DATEX2_TRAFFIC_IDEAL_TRAVEL_TIME}</ freeFlowTravelTime>
          <normallyExpectedTravelTime>{DATEX2_TRAFFIC_EXPECTED_TRAVEL_TIME}</normallyExpectedTravelTime>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficFlow">




                                                     Page 24
TCC-TIH-0049                      NTCC DATEX II Service                                Version 2

          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <percentageLongVehicles>{DATEX2_TRAFFIC_PERCENT_OF_LONG_VEHICLES}</percentageLongVehicles>
          <vehicleFlow>{DATEX2_TRAFFIC_TOTAL_FLOW}</vehicleFlow>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficSpeed">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <averageVehicleSpeed>{DATEX2_TRAFFIC_AVERAGE_VEHICLE_SPEED}</averageVehicleSpeed>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficConcentration">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <occupancy>{DATEX2_TRAFFIC_OCCUPANCY}</occupancy>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}" xsi:type="ElaboratedData">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficFlow">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <vehicleCharacteristics>
               <lengthCharacteristic>
                    <comparisonOperator>lessThan</comparisonOperator>
                    <vehicleLength>5.2</vehicleLength>
               </lengthCharacteristic>
          </vehicleCharacteristics>
          <vehicleFlow>{DATEX2_TRAFFIC_FLOW_CATEGORY_1}</vehicleFlow>
     </basicDataValue>



                                                Page 25
TCC-TIH-0049                      NTCC DATEX II Service                                Version 2

</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}" xsi:type="ElaboratedData">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficFlow">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <vehicleCharacteristics>
               <lengthCharacteristic>
                    <comparisonOperator>greaterThan</comparisonOperator>
                    <vehicleLength>5.2</vehicleLength>
               </lengthCharacteristic>
               <lengthCharacteristic>
                    <comparisonOperator>lessThan</comparisonOperator>
                    <vehicleLength>6.6</vehicleLength>
               </lengthCharacteristic>
          </vehicleCharacteristics>
          <vehicleFlow>{DATEX2_TRAFFIC_FLOW_CATEGORY_2}</vehicleFlow>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}" xsi:type="ElaboratedData">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficFlow">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>
               </locationContainedInGroup>
          </affectedLocation>
          <vehicleCharacteristics>
               <lengthCharacteristic>
                    <comparisonOperator>greaterThan</comparisonOperator>
                    <vehicleLength>6.6</vehicleLength>
               </lengthCharacteristic>
               <lengthCharacteristic>
                    <comparisonOperator>lessThan</comparisonOperator>
                    <vehicleLength>11.6</vehicleLength>
               </lengthCharacteristic>
          </vehicleCharacteristics>
          <vehicleFlow>{DATEX2_TRAFFIC_FLOW_CATEGORY_3}</vehicleFlow>
     </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-{DATEX2_TRAFFIC_ID}" xsi:type="ElaboratedData">
     <sourceInformation>
          <sourceCountry>gb</sourceCountry>
          <sourceIdentification>{DATEX2_TRAFFIC_LINK_ID}</sourceIdentification>
          <sourceName>
               <value lang=”en”>NTCC</value>
          </sourceName>
     </sourceInformation>
     <basicDataValue xsi:type="TrafficFlow">
          <time>{DATEX2_TRAFFIC_TIME}</time>
          <affectedLocation>
               <locationContainedInGroup xsi:type="LocationByReference">
                    <predefinedLocationReference>{DATEX2_TRAFFIC_LOCATION_REFERENCE}
                    </predefinedLocationReference>



                                                Page 26
TCC-TIH-0049                       NTCC DATEX II Service                     Version 2

               </locationContainedInGroup>
          </affectedLocation>
          <vehicleCharacteristics>
               <lengthCharacteristic>
                    <comparisonOperator>greaterThan</comparisonOperator>
                    <vehicleLength>11.6</vehicleLength>
               </lengthCharacteristic>
          </vehicleCharacteristics>
          <vehicleFlow>{DATEX2_TRAFFIC_FLOW_CATEGORY_4}</vehicleFlow>
     </basicDataValue>
</elaboratedData>


6.1.2      Traffic Data Placeholders
This section defines the placeholders used in the NTCC Traffic Data publication.

6.1.2.1   {DATEX2_TRAFFIC_ID}
Each elaborated data record has a unique identifier preceded with an additional sequence
number defined as ‘GUID-{sequence_number}-{data_id}’ where data_id will be one of
{DATEX2_TRAFFIC_LINK_ID} or {DATEX2_TRAFFIC_JOURNEY_TIME_SECTION_ID}.

6.1.2.2     {DATEX2_TRAFFIC_LINK_ID}
This is the unique reference assigned to a Link in the NTCC network for the reporting of loop-
based data.

6.1.2.3     {DATEX2_TRAFFIC_JOURNEY_TIME_SECTION_ID}
This is the unique reference assigned to a Journey Time Section in the NTCC network for the
reporting of ANPR-based data.

6.1.2.4      {DATEX2_TRAFFIC_TIME}
Traffic data is collected by NTCC at 5-minute intervals and is then processed before
dissemination. This will be the time at which the data was collected at NTCC. The time taken
to collect, process and redistribute the data can be up to 15 minutes.

6.1.2.5    {DATEX2_TRAFFIC_LOCATION_REFERENCE}
The location of the Link or Journey Time Section will be a cross-reference to the Predefined
Location publication, which accurately describes the location using TPEG-Loc format.

6.1.2.6     {DATEX2_TRAFFIC_TRAVEL_TIME}
This will be the average time (in seconds) taken by a vehicle to travel the length of a Journey
Time Section. Delays can be calculated by subtracting
{DATEX2_TRAFFIC_IDEAL_TRAVEL_TIME} or
{DATEX2_TRAFFIC_EXPECTED_TRAVEL_TIME}.

6.1.2.7    {DATEX2_TRAFFIC_IDEAL_TRAVEL_TIME}
This will be the theoretical time (in seconds) taken by a vehicle to travel the length of a
Journey Time Section under ideal conditions.

6.1.2.8    {DATEX2_TRAFFIC_EXPECTED_TRAVEL_TIME}
This will be the expected time (in seconds) taken by a vehicle to travel the length of a
Journey Time Section based on historic conditions. Historic conditions are recorded and
averaged over the previous 6 weeks for all days of the week and special days such as Bank
Holidays.

6.1.2.9     {DATEX2_TRAFFIC_PERCENT_OF_LONG_VEHICLES}
This is the percentage of long vehicles monitored on a Link in any 5 minute period using the
following formula:


                                                 Page 27
TCC-TIH-0049                   NTCC DATEX II Service                          Version 2



({DATEX2_TRAFFIC_FLOW_CATEGORY_4} / {DATEX2_TRAFFIC_TOTAL_FLOW}) * 100

6.1.2.10 {DATEX2_TRAFFIC_TOTAL_FLOW}
This is the total vehicle flow (in vehicles per hour) monitored on a Link in any 5 minute period
and will be the sum of
{DATEX2_TRAFFIC_FLOW_CATEGORY_1}, {DATEX2_TRAFFIC_FLOW_CATEGORY_2},
{DATEX2_TRAFFIC_FLOW_CATEGORY_3} and
{DATEX2_TRAFFIC_FLOW_CATEGORY_4}.

6.1.2.11 {DATEX2_TRAFFIC_AVERAGE_VEHICLE_SPEED}
This is the average vehicle speed (in kilometres per hour) monitored on a Link in any 5-
minute period.

6.1.2.12 {DATEX2_TRAFFIC_OCCUPANCY}
This is the percentage occupancy monitored on a Link in any 5-minute period and is
determined by loops.

6.1.2.13   {DATEX2_TRAFFIC_FLOW_CATEGORY_1},
           {DATEX2_TRAFFIC_FLOW_CATEGORY_2},
           {DATEX2_TRAFFIC_FLOW_CATEGORY_3},
           {DATEX2_TRAFFIC_FLOW_CATEGORY_4}
The vehicle flows (in vehicles per hour) for individual vehicle lengths are determined by
loops. The vehicle length categories are:

       Category 1     <=5.2m
       Category 2     >5.2m and <=6.6m
       Category 3     >6.6m and <=11.6m
       Category 4     >11.6m

The DATEX II model supports operators lessThan, greaterThan and equalTo but not “less
than or equal to” so the service implements:

       Category 1     <5.2m
       Category 2     >5.2m and <6.6m
       Category 3     >6.6m and <11.6m
       Category 4     >11.6m

The accuracy of the loops when classifying vehicle lengths is 1% so measurements around
each breakpoint could fall into adjacent categories.




                                           Page 28
TCC-TIH-0049                             NTCC DATEX II Service                                     Version 2



7              Predefined Location Product
This section defines the format of the predefined location publication generated by NTCC,
and defines the meaning of the variable parts within the publication.

7.1            Predefined Location Format
The DATEX II PredefinedLocationsPublication class is used to describe the NTCC network.
This publication contains four data describing:
   • NTCC network Links
   • NTCC Journey Time Sections
   • Locations of VMS on HA roads
   • Locations of Matrix Signals on HA roads

7.1.1          Predefined Location Template
<payloadPublication xsi:type="PredefinedLocationsPublication" lang="en">
    <publicationTime>{DATEX2_LOCATION_PUBLICATION_TIME}</publicationTime>
    <publicationCreator>
         <country>gb</country>
         <nationalIdentifier>NTCC</nationalIdentifier>
    </publicationCreator>
    <headerInformation>
         <areaOfInterest>national</areaOfInterest>
         <confidentiality>restrictedToAuthoritiesTrafficOperatorsAndPublishers</confidentiality>
         <informationUsage>broadcast</informationUsage>
         <informationUsage>internet</informationUsage>
         <informationStatus>real</informationStatus>
    </headerInformation>

      <predefinedLocationSet id="GUID-NTCC-Links">
           <predefinedLocationSetName>
                <value lang="en">NTCC Network Links</value>
           </predefinedLocationSetName>
           <predefinedLocation id="{DATEX2_LOCATION_ID}">
                <predefinedLocationName>
                     <value lang="en">{DATEX2_LOCATION_DESCRIPTION}</value>
                </predefinedLocationName>
                <predefinedLocation xsi:type="{TPEG-TYPE}”>
                     {DATEX2_LOCATION_LINKS}
                </predefinedLocation>
           </predefinedLocation>
      </predefinedLocationSet>

      <predefinedLocationSet id="GUID-NTCC-JourneyTimeSections">
           <predefinedLocationSetName>
                <value lang="en">NTCC Journey Time Sections</value>
           </predefinedLocationSetName>
           <predefinedLocation id="{DATEX2_LOCATION_ID}">
                <predefinedLocationName>
                     <value lang="en">{DATEX2_LOCATION_DESCRIPTION}</value>
                </predefinedLocationName>
                <predefinedLocation xsi:type="{TPEG-TYPE}”>
                     {DATEX2_LOCATION_JOURNEY_TIME_SECTIONS}
                </predefinedLocation>
           </predefinedLocation>
      </predefinedLocationSet>

      <predefinedLocationSet id="GUID-NTCC-VariableMessageSignLocations">
           <predefinedLocationSetName>
                <value lang="en">NTCC Variable Message Sign Locations</value>
           </predefinedLocationSetName>
           <predefinedLocation id="{DATEX2_LOCATION_ID}">
                <predefinedLocationName>
                     <value lang="en">{DATEX2_LOCATION_DESCRIPTION}</value>
                </predefinedLocationName>
                <predefinedLocation xsi:type="{TPEG-TYPE}”>
                     {DATEX2_LOCATION_VARIABLE_MESSAGE_SIGNS}
                </predefinedLocation>
           </predefinedLocation>
      </predefinedLocationSet>



                                                         Page 29
TCC-TIH-0049                       NTCC DATEX II Service                      Version 2


     <predefinedLocationSet id="GUID-NTCC-MatrixSignalLocations">
         <predefinedLocationSetName>
              <value lang="en">NTCC Matrix Signal Locations</value>
         </predefinedLocationSetName>
         <predefinedLocation id="{DATEX2_LOCATION_ID}">
              <predefinedLocationName>
                   <value lang="en">{DATEX2_LOCATION_DESCRIPTION}</value>
              </predefinedLocationName>
              <predefinedLocation xsi:type="{TPEG-TYPE}”>
                   {DATEX2_LOCATION_MATRIX_SIGNALS}
              </predefinedLocation>
         </predefinedLocation>
     </predefinedLocationSet>
</payloadPublication>


7.1.2      Predefined Location Placeholders
This section defines the placeholders used in the NTCC Predefined Location publication.

7.1.2.1     {DATEX2_LOCATION_PUBLICATION_TIME}
This is the time that the Predefined Location publication was last updated.

7.1.2.2    {DATEX2_LOCATION_ID}
The location identifier will be a cross-reference to the location referenced in the Variable
Message Sign, Matrix Signal and Traffic Data publications and will be one of
{DATEX2_VMS_LOCATION_REFERENCE},
{DATEX2_MATRIX_LOCATION_REFERENCE} or
{DATEX2_TRAFFIC_LOCATION_REFERENCE}.

7.1.2.3    {DATEX2_LOCATION_DESCRIPTION}
A textual description of the location, for example, M6 northbound between J4 and J5.

7.1.2.4    {TPEG-TYPE}
One of either “Point” or “Linear” to reflect the class of TPEG-Loc referencing to be used.

7.1.2.5    {DATEX2_LOCATION_LINKS},
           {DATEX2_LOCATION_JOURNEY_TIME_SECTIONS}
Links and Journey Time Sections described using TPEGLinearLocation class of TPEG-Loc.

7.1.2.6   {DATEX2_LOCATION_VARIABLE_MESSAGE_SIGNS},
          {DATEX2_LOCATION_MATRIX_SIGNALS}
Variable Message Signs and Matrix Signals described using TPEGSimplePoint class of
TPEG-Loc.




                                                Page 30
TCC-TIH-0049                  NTCC DATEX II Service                        Version 2



8          Help and Assistance
NTCC can provide help and advice to anyone wishing to subscribe to the data services and
would encourage everyone considering this approach to discuss their requirements with us
before embarking on development. Individual subscriptions can also be created to tailor the
data to the users’ needs where required.

8.1        TIH Technical Authority
The TIH Technical Authority should be approached, through the helpdesk, for assistance
when interfacing to NTCC.
Subscriptions will be set up on an individual basis and all access to NTCC data will be
authorised and recorded. Specific connection details and user credentials will be provided as
part of the subscription process.

8.2        Helpdesk
24-hour support is available from the NTCC Helpdesk on 0121 245 4688 or by email to
helpdesk@tistrafficinfo.com.




                                          Page 31
TCC-TIH-0049                   NTCC DATEX II Service                         Version 2



9          Appendix A – Example XML
Each Information Product contains SOAP wrapper and header/footer as specified by the
specification and is detailed below.
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soapenv:Body>
        <d2LogicalModel modelBaseVersion="1.0" xmlns="http://datex2.eu/schema/1_0/1_0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://datex2.eu/schema/1_0/1_0
          http://datex2.eu/schema/1_0/1_0/DATEXIISchema_1_0_1_0.xsd">
             <exchange>
                 <supplierIdentification><country>gb</country>
                     <nationalIdentifier>NTCC</nationalIdentifier>
                 </supplierIdentification>
             </exchange>
             <payloadPublication xsi:type="SituationPublication" lang="en">
                 <publicationTime>2007-09-26T10:54:20+01:00</publicationTime>
                 <publicationCreator>
                     <country>gb</country>
                     <nationalIdentifier>NTCC</nationalIdentifier>
                 </publicationCreator>
:
                  Zero or more Situations are included here as specified in the following
                  examples.
:
             </payloadPublication>
        </d2LogicalModel>
    </soapenv:Body>
</soapenv:Envelope>


9.1        Event Product
<situation id="GUID271694016">
    <headerInformation>
        <areaOfInterest>national</areaOfInterest>
        <confidentiality> restrictedToAuthoritiesTrafficOperatorsAndPublishers
</confidentiality>
        <informationUsage>broadcast</informationUsage>
        <informationUsage>internet</informationUsage>
        <informationStatus>real</informationStatus>
    </headerInformation>
    <situationRecord xsi:type="AbnormalTraffic" id="GUID271721614-271694045">
    <situationRecordCreationReference>U-07-0925-0050</situationRecordCreationReference>
        <situationRecordCreationTime>2007-09-25T08:37:03+01:00</situationRecordCreationTime>
        <situationRecordVersion>5</situationRecordVersion>
        <situationRecordVersionTime>2007-09-25T11:20:06+01:00</situationRecordVersionTime>
        <situationRecordFirstSupplierVersionTime>2007-09-25T11:20:06+01:00
         </situationRecordFirstSupplierVersionTime>
        <probabilityOfOccurrence>certain</probabilityOfOccurrence>
        <sourceInformation>
            <sourceCountry>gb</sourceCountry>
            <sourceName>
                <value lang="en">TCC System</value>
            </sourceName>
        </sourceInformation>
        <validity>
            <validityStatus>definedByValidityTimeSpec</validityStatus>
            <validityTimeSpecification>
                <overallStartTime>2007-09-25T08:37:29+01:00</overallStartTime>
                <overallEndTime>2007-09-25T12:15:00+01:00</overallEndTime>
                <validPeriod>
                    <startOfPeriod>2007-09-25T08:37:29+01:00</startOfPeriod>
                    <endOfPeriod>2007-09-25T12:15:00+01:00</endOfPeriod>
                </validPeriod>
            </validityTimeSpecification>
        </validity>
        <impact>
            <impactOnTraffic>heavy</impactOnTraffic>
            <impactDetails>
                <capacityRemaining>100</capacityRemaining>
                <numberOfLanesRestricted>3</numberOfLanesRestricted>
                <numberOfOperationalLanes>3</numberOfOperationalLanes>
                <originalNumberOfLanes>3</originalNumberOfLanes>
                <trafficRestrictionType>carriagewayPartiallyObstructed
                 </trafficRestrictionType>
            </impactDetails>
            <delays>
                <delayTimeValue>600</delayTimeValue>



                                           Page 32
TCC-TIH-0049                 NTCC DATEX II Service                         Version 2

          </delays>
      </impact>
      <nonGeneralPublicComment>
          <comment>
              <value lang="en">On the M5 northbound between junctions J4 and J1, there are
               currently delays of 10 mins due to heavy traffic . Normal traffic conditions
               expected from 12:15 pm.

               Link to Multimap:
               http://www.multimap.com/map/browse.cgi ?pc=&#x26;GridE=398870&#x26;
               GridN=282600&#x26; scale=200000

               Link to Streetmap:
               http://www.streetmap.co.uk/newmap.srf?x=398870&#x26;y=282600&#x26;z=5

              Link to Disclaimer: http://www.highways.gov.uk/2299.aspx</value>
          </comment>
      </nonGeneralPublicComment>
      <groupOfLocations>
          <locationContainedInGroup xsi:type="Point">
              <tpegpointLocation xsi:type="TPEGFramedPoint">
                  <tpegDirection>northBound</tpegDirection>
                  <tpegLocationType>framedPoint</tpegLocationType>
                  <framedPoint>
                      <pointCoordinates>
                          <latitude>52.441382</latitude>
                          <longitude>-2.018044</longitude>
                      </pointCoordinates>
                      <name>
                          <descriptor>
                              <value lang="en">M5 northbound between J4 and J3</value>
                          </descriptor>
                          <tpegDescriptorType>linkName</tpegDescriptorType>
                      </name>
                  </framedPoint>
                  <to xsi:type="TPEGJunction">
                      <pointCoordinates>
                          <latitude>52.515889</latitude>
                          <longitude>-1.972777</longitude>
                      </pointCoordinates>
                      <name>
                          <descriptor>
                              <value lang="en">J1</value>
                          </descriptor>
                          <tpegDescriptorType>junctionName</tpegDescriptorType>
                      </name>
                      <ilc>
                          <descriptor>
                              <value lang="en">M5</value>
                          </descriptor>
                          <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
                      </ilc>
                      <ilc>
                          <descriptor>
                              <value lang="en">A41</value>
                          </descriptor>
                          <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
                      </ilc>
                  </to>
                  <from xsi:type="TPEGJunction">
                      <pointCoordinates>
                          <latitude>52.381984</latitude>
                          <longitude>-2.046519</longitude>
                      </pointCoordinates>
                      <name>
                          <descriptor>
                              <value lang="en">J4</value>
                          </descriptor>
                          <tpegDescriptorType>junctionName</tpegDescriptorType>
                      </name>
                      <ilc>
                          <descriptor>
                              <value lang="en">M5</value>
                          </descriptor>
                          <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
                      </ilc>
                      <ilc>
                          <descriptor>
                              <value lang="en">A38</value>
                          </descriptor>
                          <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
                      </ilc>
                  </from>
              </tpegpointLocation>
          </locationContainedInGroup>
      </groupOfLocations>
      <abnormalTrafficType>slowTraffic</abnormalTrafficType>



                                         Page 33
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2

    </situationRecord>
</situation>


9.2        Variable Message Sign Product
<situation id="GUID-VariableMessageSign">
:
    <situationRecord xsi:type="VariableMessageSignSetting" id="GUID30080104">
        <situationRecordCreationTime>2007-09-25T10:37:18+01:00</situationRecordCreationTime>
        <situationRecordVersion>1190719337</situationRecordVersion>
        <situationRecordVersionTime>2007-09-25T12:22:17+01:00</situationRecordVersionTime>
        <situationRecordFirstSupplierVersionTime>2007-09-25T12:22:17+01:00
         </situationRecordFirstSupplierVersionTime>
        <probabilityOfOccurrence>certain</probabilityOfOccurrence>
        <sourceInformation>
            <sourceCountry>gb</sourceCountry>
            <sourceName>
                <value lang="en">60</value>
            </sourceName>
        </sourceInformation>
        <validity>
            <validityStatus>active</validityStatus>
            <validityTimeSpecification>
                <overallStartTime>2007-09-25T12:22:17+01:00</overallStartTime>
            </validityTimeSpecification>
        </validity>
        <groupOfLocations>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>VMS30080104</predefinedLocationReference>
            </locationContainedInGroup>
        </groupOfLocations>
        <reasonForSetting>
            <value lang="en">Update/Initialisation</value>
        </reasonForSetting>
        <numberOfCharacters>18</numberOfCharacters>
        <numberOfRows>3</numberOfRows>
        <vmsIdentifier>M5/9618M</vmsIdentifier>
        <vmsLegend> TO M5 VIA A30</vmsLegend>
        <vmsLegend>     64 MILES</vmsLegend>
        <vmsLegend>     70 MINS</vmsLegend>
        <vmsType>monochromeGraphic</vmsType>
    </situationRecord>
:
</situation>


9.3        Matrix Signal Product
<situation id="GUID-MatrixSignals">
:
    <situationRecord xsi:type="MatrixSignSetting" id="GUID30200287">
        <situationRecordCreationTime>2007-09-25T05:53:54+01:00</situationRecordCreationTime>
        <situationRecordVersion>1190696034</situationRecordVersion>
        <situationRecordVersionTime>2007-09-25T05:53:54+01:00</situationRecordVersionTime>
        <situationRecordFirstSupplierVersionTime>2007-09-25T05:53:54+01:00
      </situationRecordFirstSupplierVersionTime>
        <probabilityOfOccurrence>certain</probabilityOfOccurrence>
        <sourceInformation>
            <sourceCountry>gb</sourceCountry>
            <sourceName>
                <value lang="en">10</value>
            </sourceName>
        </sourceInformation>
        <validity>
            <validityStatus>active</validityStatus>
            <validityTimeSpecification>
                <overallStartTime>2007-09-25T03:28:19+01:00</overallStartTime>
            </validityTimeSpecification>
        </validity>
        <groupOfLocations>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Signal30200287</predefinedLocationReference>
            </locationContainedInGroup>
        </groupOfLocations>
        <reasonForSetting>
            <value lang="en">Clear</value>
        </reasonForSetting>
        <aspectDisplayed>50</aspectDisplayed>
        <matrixFault>unknown</matrixFault>
        <matrixIdentifier>A1M/9438A</matrixIdentifier>
    </situationRecord>
:
</situation>




                                          Page 34
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2


9.4        Traffic Data Product

9.4.1      ANPR-based Travel times
<elaboratedData id="GUID-63281-10100">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>10100</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TravelTimeValue">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Section10100</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <travelTime>86</travelTime>
        <freeFlowTravelTime>80</freeFlowTravelTime>
        <normallyExpectedTravelTime>85</normallyExpectedTravelTime>
    </basicDataValue>
</elaboratedData>

9.4.2      Loop-based data

<elaboratedData id="GUID-3696908-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficFlow">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <percentageLongVehicles>0</percentageLongVehicles>
        <vehicleFlow>186</vehicleFlow>
    </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-3696909-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficSpeed">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <averageVehicleSpeed>57</averageVehicleSpeed>
    </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-3696910-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficConcentration">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <occupancy>1</occupancy>



                                          Page 35
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2

    </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-3696911-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficFlow">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <vehicleCharacteristics>
            <lengthCharacteristic>
                <comparisonOperator>lessThan</comparisonOperator>
                <vehicleLength>5.2</vehicleLength>
            </lengthCharacteristic>
        </vehicleCharacteristics>
        <vehicleFlow>162</vehicleFlow>
    </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-3696912-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficFlow">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <vehicleCharacteristics>
            <lengthCharacteristic>
                <comparisonOperator>greaterThan</comparisonOperator>
                <vehicleLength>5.2</vehicleLength>
            </lengthCharacteristic>
            <lengthCharacteristic>
                <comparisonOperator>lessThan</comparisonOperator>
                <vehicleLength>6.6</vehicleLength>
            </lengthCharacteristic>
        </vehicleCharacteristics>
        <vehicleFlow>6</vehicleFlow>
    </basicDataValue>
</elaboratedData>

<elaboratedData id="GUID-3696913-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficFlow">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <vehicleCharacteristics>
            <lengthCharacteristic>
                <comparisonOperator>greaterThan</comparisonOperator>
                <vehicleLength>6.6</vehicleLength>
            </lengthCharacteristic>
            <lengthCharacteristic>
                <comparisonOperator>lessThan</comparisonOperator>
                <vehicleLength>11.6</vehicleLength>
            </lengthCharacteristic>
        </vehicleCharacteristics>
        <vehicleFlow>18</vehicleFlow>
    </basicDataValue>
</elaboratedData>




                                          Page 36
TCC-TIH-0049                  NTCC DATEX II Service                         Version 2



<elaboratedData id="GUID-3696914-101000101">
    <sourceInformation>
        <sourceCountry>gb</sourceCountry>
        <sourceIdentification>101000101</sourceIdentification>
        <sourceName>
            <value lang="en">NTCC</value>
        </sourceName>
    </sourceInformation>
    <basicDataValue xsi:type="TrafficFlow">
        <time>2007-09-25T12:20:00+01:00</time>
        <affectedLocation>
            <locationContainedInGroup xsi:type="LocationByReference">
                <predefinedLocationReference>Link101000101</predefinedLocationReference>
            </locationContainedInGroup>
        </affectedLocation>
        <vehicleCharacteristics>
            <lengthCharacteristic>
                <comparisonOperator>greaterThan</comparisonOperator>
                <vehicleLength>11.6</vehicleLength>
            </lengthCharacteristic>
        </vehicleCharacteristics>
        <vehicleFlow>0</vehicleFlow>
    </basicDataValue>
</elaboratedData>


9.5        Predefined Location Product

9.5.1      Links
<predefinedLocationSet id="GUID-NTCC-Links">
    <predefinedLocationSetName>
        <value lang="en">NTCC Network Links</value>
    </predefinedLocationSetName>
:
    <predefinedLocation id="Link104036901">
        <predefinedLocationName>
            <value lang="en">A282 southbound within the A296/A225 junction</value>
        </predefinedLocationName>
        <predefinedLocation xsi:type="Linear">
            <tpeglinearLocation xsi:type="TPEGLinearLocation">
                <tpegDirection>clockwise</tpegDirection>
                <tpegLocationType>segment</tpegLocationType>
                <to xsi:type="TPEGNonJunctionPoint">
                    <pointCoordinates>
                        <latitude>51.435507</latitude>
                        <longitude>0.239161</longitude>
                    </pointCoordinates>
                    <name>
                        <descriptor>
                            <value lang="en">Node1040369</value>
                        </descriptor>
                        <tpegDescriptorType>pointName</tpegDescriptorType>
                    </name>
                </to>
                <from xsi:type="TPEGJunction">
                    <pointCoordinates>
                        <latitude>51.441569</latitude>
                        <longitude>0.238652</longitude>
                    </pointCoordinates>
                    <name>
                        <descriptor>
                            <value lang="en">1B</value>
                        </descriptor>
                        <tpegDescriptorType>junctionName</tpegDescriptorType>
                    </name>
                    <ilc>
                        <descriptor>
                            <value lang="en">M25</value>
                        </descriptor>
                        <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
                    </ilc>
                    <ilc>
                        <descriptor>
                            <value lang="en">A225</value>
                        </descriptor>
                        <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
                    </ilc>
                </from>
            </tpeglinearLocation>
        </predefinedLocation>
    </predefinedLocation>
:
</predefinedLocationSet>



                                          Page 37
TCC-TIH-0049                  NTCC DATEX II Service                          Version 2


9.5.2      Journey Time Sections
<predefinedLocationSet id="GUID-NTCC-JourneyTimeSections">
    <predefinedLocationSetName>
        <value lang="en">NTCC Journey Time Sections</value>
    </predefinedLocationSetName>
:
    <predefinedLocation id="Section11017">
        <predefinedLocationName>
            <value lang="en">Journey Time Section for M42 southbound from Jct 9 (A446) to M42
             Jct 5 (M6)</value>
        </predefinedLocationName>
        <predefinedLocation xsi:type="Linear">
            <tpeglinearLocation xsi:type="TPEGLinearLocation">
            <tpegDirection>northBound</tpegDirection>
            <tpegLocationType>segment</tpegLocationType>
                <to xsi:type="TPEGNonJunctionPoint">
                    <pointCoordinates>
                        <latitude>52.515269</latitude>
                        <longitude>-1.725507</longitude>
                    </pointCoordinates>
                    <name>
                         <descriptor>
                             <value lang="en">Node1261091</value>
                        </descriptor>
                        <tpegDescriptorType>pointName</tpegDescriptorType>
                    </name>
                </to>
                <from xsi:type="TPEGJunction">
                    <pointCoordinates>
                        <latitude>52.543741</latitude>
                        <longitude>-1.721629</longitude>
                    </pointCoordinates>
                    <name>
                         <descriptor>
                             <value lang="en">9</value>
                        </descriptor>
                        <tpegDescriptorType>junctionName</tpegDescriptorType>
                    </name>
                    <ilc>
                        <descriptor>
                             <value lang="en">M42</value>
                        </descriptor>
                        <tpegDescriptorType>tpegILCName1</tpegDescriptorType>
                    </ilc>
                    <ilc>
                        <descriptor>
                             <value lang="en">A446</value>
                        </descriptor>
                        <tpegDescriptorType>tpegILCName2</tpegDescriptorType>
                    </ilc>
                </from>
            </tpeglinearLocation>
        </predefinedLocation>
    </predefinedLocation>
:
</predefinedLocationSet>

9.5.3      Variable Message Signs
<predefinedLocationSet id="GUID-NTCC-VariableMessageSignLocations">
    <predefinedLocationSetName>
        <value lang="en">NTCC Variable Message Sign Locations</value>
    </predefinedLocationSetName>
:
    <predefinedLocation id="VMS30082775">
        <predefinedLocationName>
            <value lang="en">VMS M60/9084B</value>
        </predefinedLocationName>
        <predefinedLocation xsi:type="Point">
            <tpegpointLocation xsi:type="TPEGSimplePoint">
                <tpegDirection>anticlockwise</tpegDirection>
                <tpegLocationType>nonLinkedPoint</tpegLocationType>
                <point xsi:type="TPEGNonJunctionPoint">
                    <pointCoordinates>
                        <latitude>53.417181</latitude>
                        <longitude>-2.284734</longitude>
                    </pointCoordinates>
                    <name>
                        <descriptor>
                            <value lang="en">VMS M60/9084B</value>
                        </descriptor>
                        <tpegDescriptorType>pointName</tpegDescriptorType>
                    </name>
                    <name>



                                          Page 38
TCC-TIH-0049                  NTCC DATEX II Service                          Version 2

                       <descriptor>
                           <value lang="en">M60</value>
                       </descriptor>
                       <tpegDescriptorType>linkName</tpegDescriptorType>
                   </name>
               </point>
           </tpegpointLocation>
       </predefinedLocation>
   </predefinedLocation>
:
</predefinedLocationSet>

9.5.4      Matrix Signals
<predefinedLocationSet id="GUID-NTCC-MatrixSignalLocations">
    <predefinedLocationSetName>
        <value lang="en">NTCC Matrix Signal Locations</value>
    </predefinedLocationSetName>
:
    <predefinedLocation id="Signal30209741">
        <predefinedLocationName>
            <value lang="en">Matrix M6/7165K1</value>
        </predefinedLocationName>
        <predefinedLocation xsi:type="Point">
            <tpegpointLocation xsi:type="TPEGSimplePoint">
                <tpegDirection>northBound</tpegDirection>
                <tpegLocationType>nonLinkedPoint</tpegLocationType>
                <point xsi:type="TPEGNonJunctionPoint">
                    <pointCoordinates>
                        <latitude>53.487895</latitude>
                        <longitude>-2.654476</longitude>
                    </pointCoordinates>
                    <name>
                         <descriptor>
                             <value lang="en">Matrix M6/7165K1</value>
                        </descriptor>
                        <tpegDescriptorType>pointName</tpegDescriptorType>
                    </name>
                    <name>
                        <descriptor>
                             <value lang="en">M6</value>
                        </descriptor>
                        <tpegDescriptorType>linkName</tpegDescriptorType>
                    </name>
                </point>
            </tpegpointLocation>
        </predefinedLocation>
    </predefinedLocation>
:
</predefinedLocationSet>




                                          Page 39

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:10/27/2011
language:
pages:39