DATEX II MST Traffic Data Interface configuration

The management of DATEX II MST Traffic Data interface requires some preparation steps.

The elements involved are automatically installed during Optima installation :

• Two DB tables:

  • VEHICLE_CLASS_TSYS
  • DATEX2_MEASUREMENT_SITE_TABLE

• The file:

  INSTALL_PATH\ptv-optima-as\standalone\deployments\datex2import.war

As indicated in → DATEX II MST Traffic Data Interface methodology > Loading anagraphic data you must previously fulfill some model constraints as shown in the table:

<measurementSiteTable id="NDW01_MT" version="1135">
    <measurementSiteRecord id="PZH01_MST_0687_01" version="8">
........
....

<measurementSiteTable id="NDW01_MT" version="1135">
    <measurementSiteRecord id="PZH01_MST_0687_01" version="8">
        <measurementSiteRecordVersionTime>2019-08-30T00:14:07Z</measurementSiteRecordVersionTime>
....
        <measurementSpecificCharacteristics index="1">
            <measurementSpecificCharacteristics>
                <accuracy>95</accuracy>
                <period>60</period>
                <specificLane>lane1</specificLane>
....
            </measurementSpecificCharacteristics>
........
....

It's necessary also to to fill the table VEHICLE_CLASS_TSYS, implementing the mapping between:

• The vehicle category
• The <specificVehicleCharacteristics tag of the file measurement_current.xml

<measurementSiteTable id="NDW01_MT" version="1135">
    <measurementSiteRecord id="PZH01_MST_0687_01" version="8">
....
            <measurementSpecificCharacteristics>
....
                <specificVehicleCharacteristics>
                    <lengthCharacteristic>
                        <comparisonOperator>lessThan</comparisonOperator>
                        <vehicleLength>5.6</vehicleLength>
                    </lengthCharacteristic>
                </specificVehicleCharacteristics>
            </measurementSpecificCharacteristics>
........
....

The <specificVehicleCharacteristics tag describes the vehicle category through a couple of tags:

• <vehicleType>
• <lengthCharacteristic>

For each <specificVehicleCharacteristics you can have one or two <lengthCharacteristic> that define a length range.

For example, for a vehicle with a length in the range [4,8], you can have:

<measurementSiteTable id="NDW01_MT" version="1135">
    <measurementSiteRecord id="PZH01_MST_0687_01" version="8">
....
            <measurementSpecificCharacteristics>
....
                <specificVehicleCharacteristics>
                    <lengthCharacteristic>
                        <comparisonOperator>greaterThanOrEqualTo</comparisonOperator>
                        <vehicleLength>4</vehicleLength>
                    </lengthCharacteristic>
                    <lengthCharacteristic>
                        <comparisonOperator>lessThanOrEqualTo</comparisonOperator>
                        <vehicleLength>8</vehicleLength>
                    </lengthCharacteristic>
                </specificVehicleCharacteristics>
            </measurementSpecificCharacteristics>
........
....

The table VEHICLE_CLASS_TSYS has the structure shown in the table:

It's necessary to have a mapping ( a record in the VEHICLE_CLASS_TSYS table) between these <specificVehicleCharacteristics> and one TSYS.

In the table, four examples of queries for setting a record of the table VEHICLE_CLASS_TSYS:

INSERT INTO vehicle_class_tsys (lmin, lmax, vehicle_type, tsys) VALUES (NULL, 5.600000, 'vehicle_type', 'CAR_TO_PCU_Traffic_Data');

INSERT INTO vehicle_class_tsys (lmin, lmax, vehicle_type, tsys) VALUES (5.600000, 12.200000, 'vehicle_type', 'LGV_TO_PCU_Traffic_Data');

INSERT INTO vehicle_class_tsys (lmin, lmax, vehicle_type, tsys) VALUES (12.200000, NULL, 'vehicle_type', 'HGV_TO_PCU_Traffic_Data');

INSERT INTO vehicle_class_tsys (lmin, lmax, vehicle_type, tsys) VALUES (NULL, NULL, 'ANY_VEHICLE', 'Equivalent_TO_PCU_Traffic_Data');