Intersection Topology Format (ITF), Topology Guidelines

Datum besluit SC 21-06-2019
Topology Guidelines version 2.1.a

Disclaimer (NL):

Bij het gebruik en toepassen van de Landelijke iVRI standaarden is en blijft de gebruiker, te weten de wegbeheerder respectievelijk opdrachtnemer van de wegbeheerder, zelf aansprakelijk voor de mogelijke risicos die ontstaan of kunnen ontstaan uit het aanbieden of laten aanbieden van (combinaties van) diensten en producten die conform deze standaarden werken in de eigen organisatie of elders in de keten waarvoor de wegbeheerder verantwoordelijk is. Dit geldt in het bijzonder ten aanzien van het verzamelen, opslaan en delen van gegevens en meer specifiek indien daar waar al dan niet direct of indirect herleidbare persoonsgegevens worden verwerkt op grond van de AVG. Gebruikers zijn zelf verantwoordelijk om bij het gebruik van de standaarden telkens na te gaan of gebruik van standaarden, dan wel de combinatie van data vanuit de standaarden in de basis voldoet aan de wet- en regelgeving, in het bijzonder de AVG. Het gebruik conform de standaarden kan het risico op aansprakelijkheid van de wegbeheerder verkleinen, maar niet altijd wegnemen of geheel uitsluiten. Dit is mede afhankelijk van de wijze waarop de wegbeheerder zelf in haar eigen organisatie of bij gebruik van opdrachtnemers in de keten de data verwerkt en gebruikt. Het is dan ook een dringend advies zowel voorafgaand aan de implementatie en ingebruikname door de gebruiker van de standaarden als periodiek een risico-analyse (zoals Data Protection Impact Assessment (DPIA)) en controle van de keten op het gebruik van de standaarden en bijkomende individuele risico s bij de wegbeheerder en haar opdrachtnemers uit te laten voeren. Het doel van dergelijke analyses en controles is dat mogelijke risico s die onbedoeld kunnen optreden op voorhand gedentificeerd kunnen worden, zodat de wegbeheerder zelf de nodige beheersmaatregelen kan treffen om (alsnog) aan de wettelijke voorschriften te kunnen voldoen. CROW en de opstellers van de standaarden hebben deze documenten met de grootst mogelijke zorg en met aandacht opgesteld, maar kunnen geen aansprakelijkheid aanvaarden voor een mogelijke overtreding van wet- en regelgeving door de wegbeheerder respectievelijk opdrachtnemer van de wegbeheerder, door te verwijzen naar de standaarden als oorzaak van een mogelijke overtreding van de AVG of andere wettelijke voorschriften. CROW en de opstellers van de standaarden wijzen derhalve een aansprakelijkheid door gebruikers ten aanzien van het gebruik van de standaarden Landelijke iVRI standaarden van de hand.

Disclaimer (EN):

When using and applying the Landelijke iVRI standaarden the end user, being the road authority or its principal, remains solely responsible for the possible risks that emerge or can emerge from the provision of services and products that operate by these standards, either within the own organisation or elsewhere in the chain of the road authoritys responsibility. This especially applies to the activities where data is gathered, stored and shared, and more specifically in cases where, be it directly or by inference, private data of individuals are processed, based on the GDPR and/or its national implementation. The user of these standards are themselves responsible for ascertaining that either the use of these standards, or the combination of data that is processed from applying these standards, are legal, especially in terms of the GDPR and/or its national implementation. The use of these standards can reduce the risks for liability of road users, but they can not eliminate these risks; the beforementioned risks of violating privacy legislation are mainly dependent on the way in wicht the road authority uses and processes the data within the own organisation and in relation to contractors within the chain of responsibility. It is urgently advised that, not alone when preparing a project, but also when implementing and operating a service or product, the road authority performs a periodic risk analysis (like a Data Protection Impact Assessment (DPIA)) and a check on the whole chain of information in terms of compliance to standards and additional individual risks on behalf of the road authority and its contractors. The purpose of these analyses and checks is to identify the possible risks beforehand, in order to take preventive and controlling measures, so that the road authority (eventually) is compliant to the legal framework that is applicable. CROW and the authors of these standards have created this document with the utmost care, but will not accept liability for a possible violation of any legislation by the road authority or its contractors by referring to these standards as the root cause of a possible violation of the GDPR, its national implementation or any other legal prescription. CROW and the authors of the Landelijke iVRI standaarden therefore explicitly waive all responsibility for the use of these standards.

Contents

1 - Introduction

1.1 - Purpose of this document

1.2 - MapData (MAP)

1.3 - ITF Intersection Topology Format (ITF)

1.4 - Reading guide

1.4.1 - Background documents

1.4.2 - Relevant standards

2 - Identifiers

2.1 - StationID and TlcIdentifier

2.2 - Version numbers

3 - Reference example

3.1 - Properties of lanes

3.1.1 - Tracked vehicles1

3.2 - Nodes

3.2.1 - Absolute (ITF) versus relative (MAP) coordinates

3.2.2 - NodeList

3.2.3 - Connections

3.2.4 - Connection trajectory

3.3 - Restrictions5

4 - Specific intersection or lane configurations

4.1 - Bicycle box (bike box)

4.2 - Bicycle lanes

4.2.1 - Bicycle lane with continuous lane marking

4.2.2 - Bicycle lane with broken lane marking

4.2.3 - Bidirectional separated bicycle lanes

4.2.4 - Cyclist movement in two stages

4.2.5 - Bicycle street

4.3 - Intersection lanes

4.3.1 - Fan out

4.3.2 - Road Geometry

4.3.3 - Merging lanes

4.3.4 - Joining approach roads

4.4 - Public transport lane

4.5 - Dynamic lane configuration

4.6 - Multiple intersections for 1 TLC (and ITF or MAP file)

4.7 - Remote intersection

4.7.1 - Use of remoteIntersection, no egress lanes

4.8 - Double stop lines

4.9 - Connections

4.9.1 - Connection 1:2

4.9.2 - Connection 2:2

4.9.3 - Connection 2:3

4.10 - Crosswalk

4.10.1 - Safe island

4.10.2 - Multiple signal groups

5 - Control-data:

5.1 - Sensors

5.1.1 - Sensor allocation

5.1.2 - Sensor relation

5.2 - Signal group relations

Annex A: Bit string example

Annex B: Conversion code absolute – relative positions

Annex C: Members subWG NL profile

This chapter describes the use of all data frames and data elements of the MapData (MAP) data structure on the basis of a simply example. The intersection layout as shown in Figure 1 is used as a reference example to detail the configurations.

Figure 1 Intersection layout

MapData can describe the geometry of one or more intersections. In this example, there is only one intersection. Each intersection contains a reference point: the centre of an intersection (conflict area), see Figure 2.

Figure 2 Reference point of the intersection

The general configuration of the intersection are detailed in Table 1.

Table 1 General intersection configuration

A bit string is an arbitrarily long array of bits. Specific bits can be identified by parenthesized integers and assigned names. As an example, the bit string for the data element LaneSharing is shown in Figure .

Figure 38 Bit string example

The example shows the 10 bit sting 0001000100, where BIT3and BIT7 are set from left to right. This indicates that user types individualMotorizedVehicleTraffic and cyclistVehicleTraffic can access and use the respective lane.

//Copyright (c) 2017, Dynniq (www.dynniq.com)

//All rights reserved.

//

//Redistribution and use in source and binary forms, with or without

//modification, are permitted provided that the following conditions are met:

//

//1. Redistributions of source code must retain the above copyright notice, this

// list of conditions and the following disclaimer.

//2. Redistributions in binary form must reproduce the above copyright notice,

// this list of conditions and the following disclaimer in the documentation

// and/or other materials provided with the distribution.

//

//THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND

//ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

//WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

//DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR

//ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

//(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

//LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND

//ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

//(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

//SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE

package com.dynniq.geotools;

import java.text.DecimalFormat;

/**

* Class dealing with WGS84 locations

*

* @author eckoende(Eric Koenders, Dynniq)

*

*/

public class GeoPoint {

private doublelon;

private doublelat;

private static DecimalFormat df = new DecimalFormat("#.######");

public GeoPoint(double lon, double lat) {

this.lon = lon;

this.lat = lat;

}

public double getLon() {

return lon;

}

public void setLon(double lon) {

this.lon = lon;

}

public double getLat() {

return lat;

}

public void setLat(double lat) {

this.lat = lat;

}

public GeoPoint clone() {

return new GeoPoint(lon, lat);

}

public final static double EarthRadius = 6367000.0; // in meters

/**

* Calculate the distance between two points in meters.

*

* @param otherthe other GeoPoint

* @return the geographic distance between this point and the other in meters

*/

public double geodistance(GeoPoint other)

{

// convert to radians

double lon1 = Math.toRadians(this.lon);

double lat1 = Math.toRadians(this.lat);

double lon2 = Math.toRadians(other.lon);

double lat2 = Math.toRadians(other.lat);

// Haversine formula

double dlon = lon2 - lon1;

double dlat = lat2 - lat1;

double a = haversin(dlat) + Math.cos(lat1) * Math.cos(lat2) * haversin(dlon);

return EarthRadius * haverasin(a);

}

/**

* Calculate the longitude difference between two point in meters.

* A negative value is returned if the other point is to the west.

* @param otherthe other GeoPoint

* @return the geographic distance between this point and the other in meters

*/

public double geodistance_lon(GeoPoint other)

{

// convert to radians

double lon1 = Math.toRadians(this.lon);

double lat1 = Math.toRadians(this.lat);

double lon2 = Math.toRadians(other.lon);

// Haversine formula

double dlon = lon1 - lon2;

double a = Math.cos(lat1) * Math.cos(lat1) * haversin(dlon);

return EarthRadius * haverasin(a) * (dlon 0 ? -1 : 1);

}

/**

* Calculate the latitude difference between two point in meters.

* A negative value is returned if the other point is to the south.

* @param otherthe other GeoPoint

* @return the geographic distance between this point and the other in meters

*/

public double geodistance_lat(GeoPoint other)

{

// convert to radians

double lat1 = Math.toRadians(this.lat);

double lat2 = Math.toRadians(other.lat);

// Haversine formula

double dlat = lat1 - lat2;

double a = haversin(dlat);

return EarthRadius * haverasin(a) * (dlat 0 ? -1 : 1);

}

/**

* @brief Move the longitude by the given distance

* A negative value must be used when moving to the west.

* @param distance The distance to offset the longitude in meters

*/

public void geodisplace_lon(double distance) {

double reflat = Math.toRadians(this.lat);

double reflon = Math.toRadians(this.lon);

double cosreflat = Math.cos(reflat);

double dlon = haverasin(haversin(distance / EarthRadius) / cosreflat / cosreflat);

if (distance 0)

this.lon = Math.toDegrees(reflon - dlon);

else

this.lon = Math.toDegrees(reflon + dlon);

}

/**

* @brief Move the latitude by the given distance

* A negative value must be used when moving to the south.

* @param distance The distance to offset the latitude in meters

*/

public void geodisplace_lat(double distance) {

double reflat = Math.toRadians(this.lat);

double dlat = distance / EarthRadius;

this.lat = Math.toDegrees(reflat + dlat);

}

/**

* Haversine formula, see https://en.wikipedia.org/wiki/Haversine_formula

*

* @param a

* @returnthe haversine of a

*/

public static double haversin(double a)

{

return Math.pow(Math.sin(a / 2), 2);

}

/**

* Inverse Haversine formula, see https://en.wikipedia.org/wiki/Haversine_formula

*

* @param a

* @returnthe haverasine of a

*/

public static double haverasin(double a)

{

return 2 * Math.asin(Math.min(1, Math.sqrt(a)));

}

public String toString() {

return "[" + df.format(lon) + "," + df.format(lat) +"] ";

}

public static void main(String args[]) {

/* take a reference location */

GeoPoint refloc = new GeoPoint(5.420362, 52.173284);

/* take a point */

GeoPoint pnt = new GeoPoint(5.420022, 52.173569);

/* calculate the delta differences */

double deltax = pnt.geodistance_lon(refloc);

double deltay = pnt.geodistance_lat(refloc);

System.out.println("Refloc = " + refloc);

System.out.println("Point = " + pnt + " delta [x,y] = [" + deltax + ", " + deltay + "]");

/* take a point at the reference location */

GeoPoint node = refloc.clone();

/* move the point by a delta */

node.geodisplace_lon(deltax);

node.geodisplace_lat(deltay);

System.out.println("Node = " + node);

}

Jaap Vreeswijk MAPtm

Martijn Harmenzon MAPtm

Martin Barto Vialis

Eric Koenders Dynniq

Peter Luns Siemens

Eddy Verhoeven Siemens

Peter Smit Swarco

Jaap Zee Swarco

Kartik Mundaragi Shivakumar RHDHV

Klaas-Jan op den Kelder RHDHV

Wannes de Smet BeMobile

Arie Schreuders Sweco

Bram Schiltmans RWS