User:Bicycle tourer/Confluence Types Reference

Id	Image	Properties	Explanation
1		Carriageways in merging road: Single Links from merging road: 0 Carriageways in receiving road: Single Connection between receiving carriageways: <na>	Type 1: Simple confluence (single carriageways road merging into single carriage road, no link) K 7041 (tertiary, white) merging into L13 (secondary, yellow), no highway links. K 7041 is just one way; L13 one way (could be two ways starting/ending at merging node) Example located between Gülitz and Pirow, Brandenburg, Germany, 2018-09. Difference to generic highway link rules: None
1a		Carriageways in merging road: Single Links from merging road: 0 Carriageways in receiving road: Single Connection between receiving carriageways: <na>	Type 1a: Bending confluence (single carriageways road merging into single carriage road, no link) K 7016 (tertiary, white) merging into bending L 103 (secondary, yellow) Wrong interpretation: Intuitively it looks like the road coming from south is merging into a road going west-east. Right interpretation: Road coming from west (K 7016) is merging into the road coming from south going east (L 103, íncluding bend) Example located near Guhlsdorf, Brandenburg, Germany, 2018-09. Difference to generic highway link rules: None
2	Image tbd	Carriageways in merging road: single Links from merging road: leaving Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 2: Confluence with single carriageway road merging into single carriageway road, single link on leaving side tbd
3		Carriageways in merging road: single Links from merging road: entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 3: Confluence with single carriageway road merging into single carriageway road, single link on entering side Bremer Straße (tertiary, white) merging into B 51 (primary, orange) The northern link of Bremer Straße should be a tertiary link (according to case distinction table) (preferred, because it's a link with oneway and there is other entering traffic on another carriageway), in fact it is mapped as tertiary (not really wrong, but not preferred) The southern part of Bremer Straße is classified tertiary (complying with case distinction table), classification as tertiary link would be not wrong, but also not preferred, because it contains the complete leaving traffic. Example located north of Bassum, Niedersachsen, Germany, 2018-09 Difference to generic highway link rules: With generic rules the link would have been classified as primary, which makes this junction awkward.
4	Image tbd	Carriageways in merging road: single Links from merging road: leaving + entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 4: Confluence with single carriageway road merging into single carriageway road, links on leaving and entering side tbd
5	Image tbd	Carriageways in merging road: dual common Links from merging road: 0 Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 5: Confluence with dual carriageways road merging into single carriageway road, no links at all tbd
6	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 6: Confluence with dual carriageways road merging into single carriageway road, single link on leaving side tbd
7		Carriageways in merging road: dual common Links from merging road: entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 7: Confluence with dual carriageways road merging into single carriageway road, single link on entering side L 623 (secondary, yellow) merging into B 3(primary, orange, reference not visible) Northern carriageway of L 634 is simple secondary, southern part has to be two secondary links at least near B 3 (both are mapped secondary w/o link), where the two destinations are on separate carriageways. More eastern the southern part is a secondary as expected. Interpretation: Mapping the links as non links allowed to keep these parts on secondary level, while treating them as links would have forced them to be primary with the generic rules. Difference to generic highway link rules: With generic rules the links would have been classified as primary, which makes this junction awkward.
8	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving + entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 8: Confluence with dual carriageways road merging into single carriageway road, links on leaving and entering side tbd
9	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 9: Confluence with dual carriageways road merging into single carriageway road, no links at all tbd
10	Image tbd	Carriageways in merging road: dual separated Links from merging road: leaving Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 10: Confluence with dual carriageways road merging separated into single carriageway road, single link on leaving side tbd
11	Image tbd	Carriageways in merging road: dual separated Links from merging road: entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	Type 11: Confluence with dual carriageways road merging separated into single carriageway road, single link on entering side tbd
12		Carriageways in merging road: dual separated Links from merging road: leaving + entering Carriageways in receiving road: single Connection between receiving carriageways: <na>	K 10 (tertiary, white) merging into B 4 (primary, orange) Traffic merging from K 10 into B 4: Separate carriageways (i.e. link) in K 10 for northeast and southwest direction, B 4 single carriageway. Traffic leaving B 4 towards K 10: Coming from northwest or southeast means entering first a separate carriageway (i.e. link) Links are treated as part of K 10, because if there were only one carriageway (as in simple confluence above) it would be obviously part of K 10. Therefore the links inherit the classification of K 10. Please note that neither the cycleways nor the small street merging into K 10 from east bothers the confluence from K 10 and B 4 (the small street is together with K 10 a separate confluence --- not discussed here) Example located near Bienenbüttel, Niedersachsen, Germany, 2018-09. Difference to generic highway link rules: With generic rules the links would have been classified as primary (and gotten ref=B 4), which makes this junction awkward.
13		Carriageways in merging road: single Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: single	"El Santo Road" being residential with single carriageway, merging "Country Club Drive" being tertiary with dual carriageways, receiving Single connection between the two carriageways of Country Club Drive classified like merging road as highway=residential, complying with case distinction table --- it is treated as part of merging road Example located in Plano, Texas, USA, 2018-09 Difference to generic highway link rules: None
14	Image tbd	Carriageways in merging road: single Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: single	Type 14: Confluence with single carriageway road merging into dual carriageways road with single connection, single link on leaving side tbd
15	Image tbd	Carriageways in merging road: single Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: single	Type 15: Confluence with single carriageway road merging into dual carriageways road with single connection, single link on entering side tbd
16	Image tbd	Carriageways in merging road: single Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: single	Type 16: Confluence with single carriageway road merging into dual carriageways road with single connection, links on leaving and entering side tbd
17	Image tbd	Carriageways in merging road: single Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 17: Confluence with single carriageway road merging into dual carriageways road with connected connection, no links at all Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
18	Image tbd	Carriageways in merging road: single Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 18: Confluence with single carriageways road merging into dual carriageways road with connected connection, leaving link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
19	Image tbd	Carriageways in merging road: single Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 17: Confluence with single carriageways road merging into dual carriageways road with connected connection, entering link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
20	Image tbd	Carriageways in merging road: single Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 20: Confluence with single carriageways road merging into dual carriageways road with connected connection, leaving and entering links Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
21	Image tbd	Carriageways in merging road: single Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 21: Confluence with single carriageways road merging into dual carriageways road with separated connections, no links at all Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
22	Image tbd	Carriageways in merging road: single Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 22: Confluence with single carriageways road merging into dual carriageways road with separated connections, leaving link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
23	Image tbd	Carriageways in merging road: single Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 23: Confluence with single carriageways road merging into dual carriageways road with separated connections, entering link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
24	Image tbd	Carriageways in merging road: single Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 24: Confluence with single carriageways road merging into dual carriageways road with separated connections, leaving and entering links Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
25	Image tbd	Carriageways in merging road: single Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 25: Confluence with single carriageways road merging into dual carriageways road with separated connections, no links at all Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
26	Image tbd	Carriageways in merging road: single Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 26: Confluence with single carriageways road merging into dual carriageways road with separated connections, leaving link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
27	Image tbd	Carriageways in merging road: single Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 27: Confluence with single carriageways road merging into dual carriageways road with separated connections, entering link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
28	Image tbd	Carriageways in merging road: single Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 28: Confluence with single carriageways road merging into dual carriageways road with separated connections, leaving + entering link Merging road not split into separate carriageways until it hits the first carriage way of receiving road Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
29		Carriageways in merging road: dual common Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: single	Uelzener Straße (Residential, white, smaller) merging into K 7 (tertiary, white, broader) Separate carriageways in receiving road K 7, separate links into every direction from Uelzener Straße All links are {{tag|highway|residential]] according to case distinction table, even road pieces crossing different carriageways of Munstermannskamp Example located near Lüneburg, Niedersachsen, Germany, 2018-09 Difference to generic highway link rules: With generic rules the links would have been classified as tertiary (and gotten ref=K 7), while the connection between the two carriageways of K 7 would have stayed residential: A really awkward junction.
30	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: single	Type 30: Confluence with dual carriageways road merging into dual carriageways road with single connection, leaving link tbd
31	Image tbd	Carriageways in merging road: dual common Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: single	Type 31: Confluence with dual carriageways road merging into dual carriageways road with single connection, entering link tbd
32	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving and entering Carriageways in receiving road: double Connection between receiving carriageways: single	Type 32: Confluence with dual carriageways road merging into dual carriageways road with single connection, leaving and entering links tbd
33	Image tbd	Carriageways in merging road: dual common Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 33: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
34	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 34: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
35	Image tbd	Carriageways in merging road: dual common Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 35: Confluence with dual carriageways road merging into dual carriageways road with separated connection, entering link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
36	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 36: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving and entering link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in a single node There is high probability that this junction is a roundabout and not a confluence
37	Image tbd	Carriageways in merging road: dual common Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 37: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
38	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 38: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
39	Image tbd	Carriageways in merging road: dual common Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 39: Confluence with dual carriageways road merging into dual carriageways road with separated connection, entering link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
40	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 40: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving and entering links Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction (e.g. because of an island), which connect with second carriageway in different nodes There is high probability that this junction is a roundabout and not a confluence
41	Image tbd	Carriageways in merging road: dual common Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 41: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, no links at all Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
42	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 42: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, leaving link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
43	Image tbd	Carriageways in merging road: dual common Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 43: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, entering link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
44	Image tbd	Carriageways in merging road: dual common Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 44: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, leaving + entering link Merging road hits first carriageway of receiving road in one node and then splits again for connection to other carriageway. Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
45		Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Chapel Creek Parkway (Residential, white, name not visible) merging into Parkwood Boulevard (secondary, yellow) Separate carriageways in merging residential Separate carriageways in receiving secondary Please note the service road coming from west adds another confluence: It does not keep this junction from being a confluence between merging residential and Parkwood Boulevard It makes this junction being two confluences in parallel The connection between the two carriageways of Parkwood Boulevard are classified as the higher one from the two roads merging at this place --- residential, not service Probably the existence of the service road force the carriageways of merging residential to join into one node when merging into second carriageway of receiving secondary (which makes this example different from example 6) Example located near Frisco, Texas, USA, 2018-09 Difference to generic highway link rules: With generic rules the links would have been classified as secondary, which makes this junction awkward.
46	Image tbd	Carriageways in merging road: dual separated Links from merging road: leaving Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 46: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving link Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in common node.
47	Image tbd	Carriageways in merging road: dual separated Links from merging road: entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 47: Confluence with dual carriageways road merging into dual carriageways road with separated connection, entering link Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in common node.
48	Image tbd	Carriageways in merging road: dual separated Links from merging road: leaving + entering Carriageways in receiving road: double Connection between receiving carriageways: dual connected	Type 48: Confluence with dual carriageways road merging into dual carriageways road with separated connection, leaving + entering links Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in common node.
49	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 49: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in separate nodes.
50	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 50: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in separate nodes.
51	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 51: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in separate nodes.
52	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual separated	Type 52: Confluence with dual carriageways road merging into dual carriageways road with separated connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, connecting to second carriageway in separate nodes.
53	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 53: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
54	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 54: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
55	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 55: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.
56	Image tbd	Carriageways in merging road: dual separated Links from merging road: 0 Carriageways in receiving road: double Connection between receiving carriageways: dual reverse	Type 56: Confluence with dual carriageways road merging into dual carriageways road with dual reverse connection, no links at all Connection to other carriageway of receiving road by separate ways for each direction, with traffic from R to M leaving R before traffic from M to R merges.