DATEX II Interface – Event Dutch format

This interface is a custom HTTP REST Optima interface.

The DATEX II Event Dutch format is slightly different from the standard DATEX II format.

Requirements

To import such events, the following requirements must be fulfilled:

In the Optima database, the table PROVIDERS must have a record with the name NDWNL.
The Optima database must have authentication rules properly set according to the following script:

INSERT INTO auth_methods
            (idno,
             url_method,
             skip_auth,
             priority)
(SELECT Max(idno) + 1,
        '/talking-traffic-events-importer/.*',
        FALSE,
        1
 FROM   auth_methods);

INSERT INTO auth_methods_objects
(SELECT o.idno,
        Max(m.idno)
 FROM   auth_objects o,
        auth_methods m
 WHERE  o.code = 'OptimaADI'
 GROUP  BY o.idno);

As for the standard DATEX II event interface, remember to properly configure the configuration file vehicle_type_tsys.xml

Check that the Optima configuration.XML file contains the following two parameters in the route matching node configured as below:
<minValidPointsThreshold>0.8</minValidPointsThreshold>
<filterDistanceFromGraph>20</filterDistanceFromGraph>

The geolocatisation of the events is done by the Optima route matching algorithm using the shape of the events themselves. The parameter <minValidPointsThreshold> defines a threshold ratio (value between 0 and 1) for which the location will not be created and the related event will be skipped if the ratio of the valid points (i.e. not skipped by the route matching algorithm) is below this value.

All events posted at this service will update the events of the NDWNL provider already present in the Optima EVNT table. All events of the NDWNL provider that are in the database and not in the data feed will be closed.

To import the events the interface must be queried by a POST request. The the following example shows how this is done with the command line tool CURL:

Curl -X POST -H "Content-Type:application/octet-stream; Content-Encoding:gzip; Accept-Encoding: gzip, deflate" --data-binary @<event-file-name> http:// <hostname>:1800/talking-traffic-events-importer/stream?session=<session-id>

Where <event-file-name> is the file of the queried events in gzip format, <hostname> is the Optima root endpoint, and <session-id> is the Optima authentication token.

Important: Note that the header of the POST request must be:
Content-Type:application/octet-stream; Content-Encoding:gzip; Accept-Encoding: gzip, deflate