Testing a feeder change before implementation

In one sentence

Both cases sit side by side in the same workspace.

Why it matters

What if feeder 2 is withdrawn? In case A neighbourhood 2 rides feeder 2 to the hub; in case B the route is withdrawn and travellers re-route — some walk to the trunk, some move to feeder 1, a few leave public transport. Higher trunk load, longer waiting at the feeder-1 stop, longer walking access and more transfers become visible before anything is implemented.

A network is more than its total demand: where the vehicle fills, where people wait, where a feeder change shifts transfers. Reading a line stop by stop, from one simulation run, is the difference between a forecast and a planning tool.

Sources

• Schematic illustration; values are illustrative

What you see

1. 00.0Case A: today
2. 04.0Case B: feeder 2 withdrawn
3. 07.0Re-routing on the map
4. 10.5Effects before implementation
5. 14.0Both cases side by side

Use this explainer

MP4 (1800×720) · GIF (1200 px) · Poster (PNG)

Embed: <iframe src="https://www.replan.city/explains/embed/feeder-change.html?lang=en" width="900" height="360" style="border:0;max-width:100%;aspect-ratio:5/2" loading="lazy" title="Testing a feeder change before implementation"></iframe> Copy
Paste into any page; the explainer plays as live SVG (no video file).

Licence: CC BY 4.0 — reuse freely with the line “Replan GmbH · replan.city/explains”. The Replan mark in the corner stays.