Strategy · published
A repeatable evidence workflow from the student projects — which metrics to calculate, with which tool or method, and the decision it led to.
| Summary | Mapping where pedestrian routes cross truck routes, and counting the crossings, drives a site layout with separated flows. |
| Tool or method | manual / formula (crossings counted on the site flow plan) |
| Status | published |
The question it answers
Where do people and trucks cross, and which layout removes those crossings?
How it works
- Draw the routes of trucks, vans, staff, cars and the public on the existing site plan.
- Count the points where pedestrian routes cross vehicle routes, or the share of separated routes.
- Redesign the zoning, entrances or crossings (for example an underpass) and count again.
- Keep the layout with the fewest crossings.
In the student projects
- Natalie Žižková — manual / formula. Pedestrian–vehicle conflict points: existing 4 → proposed 0. Decision: “The crossing-point and flow analysis led to a strict two-zone layout (truck area vs public/staff area) with zero pedestrian–truck crossings.”
- Vladi Kostecki — manual / formula. Pedestrian–vehicle conflict points: original 3; new 0. Decision: “…add a pedestrian underpass to remove all pedestrian–truck crossings.”
- Sara Gani — manual / formula. Pedestrian–vehicle conflict points: share of separated routes before 30%; after 90%. Decision: “The L-shaped layout … was kept because it scored best across the KPI matrix while separating truck, car and pedestrian flows.”
- Eva Kažukolovaitė — manual / formula. Pedestrian–vehicle conflict points: not quantified; the proposal claims conflicts with pedestrians are eliminated. Decision: “Replace the temporary container depot with rearrangeable timber modules placed in a cross-dock pattern to separate van and cargo-bike flows, move the vehicle entrance to remove pedestrian collisions.”
Values and decisions as reported by the student; see each case study for the page in the portfolio.
Where it falls short
- The projects count crossings in two ways (number of points, or share of separated routes), so the results are not comparable.
- Worker safety incidents would need operational data; the projects assess safety only through the layout.
Where are the ambitions, metrics and tools?
They appear automatically below under Connections, and in Obsidian under the
auto_properties.
Connections
- Case studies: Natalie Žižková, Vladi Kostecki, Sara Gani, Eva Kažukolovaitė
- Metrics it calculates: Pedestrian–vehicle conflict points
- Ambitions (through its projects): Adaptable over time, Cargo bikes and light electric vehicles, Green and productive roofs, Habitat and ecological connectivity, Healthy workplaces, Logistics as part of the city, Micro-hub networks, Mixed use and function stacking, Modular and prefabricated architecture, Public access and community use, Rainwater kept on site, Reuse of existing buildings, Safe sites with separated flows, Screening with greenery and façades
Something wrong or missing? Suggest a correction