---
title: "T Junctions (50)"
created: 2026-07-01
updated: 2026-07-01
type: concept
status: compiled
namespace: pattern-language
pattern_number: 50
pattern_name: "T Junctions"
source_repository: https://github.com/zenodotus280/apl-md
source_url: https://github.com/zenodotus280/apl-md/blob/master/Patterns/T%20Junctions%20%2850%29.md
license_note: Non-commercial reuse with attribution; see namespace README and source LICENSE.md.
related_patterns:
  - "Parallel Roads (23)"
  - "Looped Local Roads (49)"
  - "Road Crossing (54)"
---

# T Junctions (50)

> Source pattern from the abridged `apl-md` corpus. Use as a design reference and constraint seed; do not treat as commercial-clean training data.

### Problem
>Traffic accidents are far more frequent where two roads cross than at T Junctions.

### Solution
>Lay out the road system so that any two roads which meet at grade, meet in three-way T junctions as near to 90 degrees as possible. Avoid four-way intersections and crossing movements.

### Related Patterns
... if major roads are in position -- [[Parallel Roads (23)]], and you are in the process of defining the local roads, this pattern gives the nature of the intersections. It will also greatly influence the layout of local roads, and will help to generate their loop-like character -- [[Looped Local Roads (49)]].

At busy junctions, where pedestrian paths converge, make a special raised crossing for pedestrians, something more than the usual crosswalk -- [[Road Crossing (54)]] ...

---

> [!cite]- Alexander, Christopher. _A Pattern Language: Towns, Buildings, Construction_. Oxford University Press, 1977, p. 264.
> #APL/confidence/medium
>
> #APL/Town-Patterns/Local-Networking