Drop a queue-geometry.json to begin.
queue-geometry.json here — and optionally a
preview-cloud.json for the 3D replay.Looking down, north up, equal scale. The corridor is coloured by where each lane width came from. It opens out at U-turns because the apex has no rail beside it — the ray runs on down the next lane.
Shaded spans are interpolated — no usable depth there, so the width is inferred from its neighbours.
Floor, rails and posts, reduced from the depth points as the walk progresses. Drag to orbit.
preview-cloud.json loaded. Generate one with
python -m queuewalk.preview <recording> --out preview-cloud.json, then drop it here.
The lane as a surface, its edges stood up as curbs, the line you walked, and where the
phone was with the direction it was pointing. Drag to turn, scroll or pinch to zoom,
two fingers or right-drag to move. Everything here is drawn from measurements in
queue-geometry.json and preview-cloud.json — nothing is invented.
Straight runs and turns, in walk order. Banks are groups of parallel runs.
The table view — every value in the charts above, readable without colour.
What the pipeline could and could not do at the time. This is how you tell months later whether a number can be trusted.