What the map is saying
These notes are for the workflows. They are the same numbers the agent cites on a Remaining box or a mark. Read them after you file, or before you argue with an engineer. No agent vocabulary here — it is planning.
Five words, in planning terms
| Workflow | One job on one street, the way you would get it on a Monday: a client, a conflict, a deliverable. Ten of them. Each takes 15–45 minutes. |
| Say the job | You type what you want built — “a main-network corridor between these two points, keep the parking”. You never draw. The agent puts it on the real street. |
| Remaining … m | The width left in the carriageway after the 3.00 m traffic lane. This is the number the standard checks, the number you take into coordination, and the number you will argue about. |
| Recommendation | The sentence you would say in coordination: keep the parking, drop it, wrong street. Filed with the metres and a GeoJSON. It goes to the engineers, not to a drawer. |
| Report | The button at the top. Something looked wrong, or you wanted something the agent did not offer. A good report counts on the board like a filed workflow, and an engineer ships the fix while the event runs. |
What the agent will not do
It will not draw a corridor until you name the job — a condition (“keep parking”) is not a job. It will not invent a width: every number is OpenStreetMap plus the Zurich standard, and it tells you which. It will not decide for you: it asks for your recommendation and files yours. It will not leave the district. If it does any of these, that is a bug — report it.
Leftover width
A marked cycle lane sits beside 3.00 m of mixed traffic (Velostandards §5.5). Leftover — the box labelled Remaining … m — is whatever remains of the carriageway after that lane. Table 1 then asks whether that remainder holds the cycle facility.
The green band is the cycle facility the standard wants. The Remaining box is the width you have. That box is the meeting. Magenta is below the absolute minimum. Yellow is below the standard and may be justified.
| Network | One-way leftover | Minimum (§2.4.2) | Two-way leftover |
|---|---|---|---|
| Priority cycle route | 2.50 m | 2.20 m | 4.80 m |
| Main network | 2.20 m | 1.80 m | 3.50 m |
| Base network | 1.80 m | 1.50 m | 3.00 m |
Adjacent parking adds 0.75 m to the Table 1 ask. Two-way main network plus parking is 4.25 m leftover beside the traffic lane.
§2.4.2
Below the standard measure you must derive and justify the deviation. Below the absolute minimum you may not. Yellow marks on this map are that middle band — not a free pass, not an automatic fail.
Source: City of Zurich Cycling Standards (2024), Table 1 §2.4.1–2.4.2 · VSS SN 640 060. City overview: stadt-zuerich.ch — Velos.
Ahead of the map
OSM leftover is a drawing from last year’s extract. You walked the street this morning. File street knowledge (measured leftover) or a policy override (the meeting overrules Table 1). That packet goes to the desk. It does not move the line.
Colours on this map
Magenta — below the absolute minimum, a building inside 20 m, a pump, or a tree too close to a facade.
Yellow — below the Table 1 standard, still above the minimum. Justify it.
Blue leftover box — Remaining holds the standard.
Green — cycle band or a valid tree disc.
Power lines — LeV Art. 38
20 m horizontal clearance from buildings always suffices. The cyan ribbon is that envelope. Magenta marks are building footprints inside it. Distance on the mark is metres to the facade, not leftover width.
Law: LeV (SR 734.31) Art. 38.
Gravity sewers
Practice for small pipes: prefer ≥ 0.5 % downhill (VSA / SN 592 000). Amber is the pipe. Magenta is a stretch that climbs enough to need a pump. Elevations are Copernicus DEM via Open-Meteo — not a cadastral long section.
Street trees
Typical City Parks rhythm on this map: 8 m grid, 2.5 m off facades. Green discs keep the setback. Magenta discs sit too close to a building polygon. Not a cadastral planting plan.
Talking to engineers
A filed workflow is not a drawing. What travels is the remaining width (or distance, or slope) + the recommendation you would make on Monday + the GeoJSON. Street knowledge and policy overrides land on the same desk. Flag a mark if the OSM width, building, or terrain looks wrong — that is a data bug, not a planning argument.
Engineers read /desk. Flags also roll up at /api/ops/learn.
How to report something, and what happens next
Tap Report at the top of the chat. Say whether it is a bug (a number or a line that is wrong for this street), an improvement (something a planner would need that the agent does not offer), or a comment. One sentence in your words is enough — you do not need to know why.
An engineer claims it on /desk, ships the fix without taking the site down, and the agent tells you in chat, by name, when it is done. Your workflow is kept. The report counts on the board, and “Reported a bug” and “Asked for a fix, got it” are badges.
What we learn from your 48 hours
Where each workflow loses people (which step, in which words). Whether planners say the job or click through it. Which tradeoff wins on which street. What you do this in today — CAD, GIS, Excel, paper, meetings — and whether you would use this on a live project. Every report is a line in the next build. None of it is a score on you.