Norway/crossings

This is currently a working document.

Purpose of this documentation

The goals are:

• Homogenize the mapping of crossings and intersections in Norway
• Improve routing in general
• Add data necessary to allow wheelchair routing in Norway

This means that a clear and simple tagging scheme needs to be established which is easy to follow, practical to map, and yields favorable results for the above stated goals. An important aspect is to be complient with international tagging schemes, but where there are multiple possible methods - we will choose one to be the correct method for each real life case.

ᚫ It is also important to note that many situations that exist around the word do not necessarily exist in Norway. One example is the exclusive use of zebra markings. This means some data can be counted as implicit.

Types of intersection

It is easier to partition the types of intersection rather than trying to write one single table of instruction.

Car-Car intersections

The goal here is not not have multiple traffic signals in a row inside the same intersection.

Note: highway=traffic_signals is the base tag.

In many cases tags such as highway=stop or highway=give_way can be used where there are no traffic signals. However, these are less useful for routing and unnecessarily labour intensive to add (and maintain). For these reasons it is not recommended to add these on a large scale.

Type of intersection	Description	How to map	Map screenshot	Photo
+	1:1 intersecting roads. Two or more twoway roads meet and are controlled by traffic lights.	Add the tag highway=traffic_signals where the roads meet.
#	*:* intersecting roads. Multiple oneway roads intersect eachother at multiple points.	Add the tag highway=traffic_signals on the road-way where the stopping line is located.
⧺	1:* intersecting roads.	Add the tag highway=traffic_signals on the road-way where the stopping line is located. One the road that is not oneway, add direction tags on the traffic signal.

Car-Pedestrian intersections

The intersecting node

The goal here is to describe the infrastructure of the crossing for the pedestrians, and to indicate to cars that there maybe crossing pedestrians here, and whether this crossing has traffic lights.

Note: highway=crossing is the base tag.

...

The intersecting way

The footway (or cycleway) link which usually links two sidewalks while intersecting a road. It is not relevant do duplicate the information from the intersecting node.

The focus here should be on the road surface.

highway=footway/cycleway;footway/cycleway=crossing + surface + smoothness + lit is sufficient.

...

Kerb-intersections

This is an essential part of routing data. When a kerb is raised it can not be crossed (easily) by small wheel vehicles such as scooters, or by wheelchairs.

Therefor, whenever a pedestrian-accessible way crosses a kerb, a "barrier=kerb" node is required.

Type	Tag	Purpose	Comment
Base	barrier=kerb
Required addition	kerb=*	To specifcy the type of kerb intersection
Important addition	tactile_paving=yes/no	Useful information	This will likely duplicate information on the crossing node