geo.qaA world, live · tenant: public
London, right now.
Compared with 3 hours ago, central London is quieter. On the 219 cameras within 5 km of Trafalgar Square that reported in both windows, objects per view went 21.5 → 15.8.
Counted on the 267 street cameras within five kilometres of Trafalgar Square, which is a slice of Greater London and not all of it. Every number on this page names the clip it came from and the detector that counted it. One of them is taken all the way to a signed receipt below, and checked.
One answer, all the way down
Ask. Read. Check.
This is what every geo.qa answer is built from. Here it is once, unabridged, for one place.
ask
How busy is Trafalgar Square right now?
answer
6 people and 9 cars in view of the Trafalgar Square camera — about usual for this hour (percentile 0.65, CI 0.57–0.72, from 161 earlier readings).
At this hour of day, that is higher than 99 of 161 previous readings at this camera at this hour of day, over the last 30 days.
counts are from ONE camera of 267 within 5000 m. That is an answer about this junction, not about the area.
evidence
- clip sha256
- d6b057f5bb38e28045574c53d279ad56503dfd654a63b068fb6d2a47ee5261dc
- frame
- 137 of 275, captured 9 min ago
- counted by
- cpu_detect_coco@4d9812b3db3df883 (fasterrcnn_mobilenet_v3_large_fpn)
- camera
- tfl_jamcam:tfl-JamCams_00001.06502
The clip is kept and hashed. Fetch it, hash it, decode that frame and run the same detector: the counts must reproduce.
check
not established — verifier unreachable; nothing was checked. Retry.. The check did not complete, so nothing was established either way — not a pass and not a failure. The receipt is shown so you can check it yourself.
Checked at 2026-11-03 19:08 UTC.
curl geo.qa/api/world-model/verify/by-cid/43c42e889ff9ace20618a0961be7d00e83f0246dcc79eadda16a376e711060d5
No key, no account. The same call from your terminal returns the same verdict, and the clip hash checks out on the verify page without a terminal at all.
Twelve places
What each camera saw.
One camera each, as fresh as its last kept clip. A camera showing an operator notice says so rather than counting the notice.
Aldgate
9 people and 13 cars
Canary Wharf
13 cars, 1 bus and 4 trucks
Elephant and Castle
15 people, 7 cars, 1 bus and 1 truck
Hammersmith Broadway
7 cars, 1 bus and 1 truck
Hyde Park Corner
1 person, 6 cars, 3 buses and 1 truck
Marble Arch
6 people and 15 cars
Old Street
3 people, 11 cars, 1 bus and 1 bicycle
Oxford Circus
28 people, 9 cars, 1 bus and 5 motorcycles
Piccadilly Circus
3 people, 4 cars and 1 bus
Tower Bridge
20 people and 7 cars
Trafalgar Square
6 people and 9 cars
Vauxhall Cross
8 people and 6 cars
What the cameras know jointly
Twelve cameras, and the ground underneath them.
Every camera above stands at a cell. At that same cell the open ledger already holds what the ground is: metres of road, land-surface temperature, particulates, canopy. The cameras say what is moving. Joined, they answer what neither half can — and the two questions people mean by “busy” turn out to have different answers.
Most in frame
Charing Cross Rd/Cranbourne St
22 objects counted
Counting alone. Needs one camera.
Most crowded street
Piccadilly/Whitehorse St
86.1 vehicles per 100 m seen
18 vehicles over 20.9 m of street the camera resolved. Needs the ranges the detector measured.
Charing Cross Rd/Cranbourne St has the most objects in frame; Piccadilly/Whitehorse St has the most vehicles per 100 m of street it can see. Counting answers 'where is there most', dividing answers 'where is it worst', and the second needs the ranges the detector measured. The divisor is the furthest object in each frame, so it is a lower bound on what each camera can see and the densities are upper bounds: some of this difference is where the traffic happened to stand, not how crowded the street is
Breathing it now
Shaftesbury Ave/High Holborn — 18 people counted, at 4.8 µg/m³ PM2.5.
The camera counts who is standing there; CAMS says what they are breathing. An instant at one junction, not a dose.
Nothing here is averaged into a score. A score hides which half moved. Every number names the two measurements it came from, and an agent reads the same object at /api/worlds/london.
What this page cannot tell you
One junction, not a city.
One camera is one junction
A count is what one camera saw in one frame. It is an answer about that junction, not about the area around it. The trend line at the top compares the same cameras with themselves, which is the only comparison that removes our own sampling.
A park is not a cell
Ask about a place with no camera on it and the honest answer is the distance to the nearest one, not a number. geo.qa says it cannot see rather than inventing a count.
Not everything here is evidence
The counts on the cards and in the answer above come from retained clips, so they can be recomputed; a count from a live frame cannot, once the frame is gone. The trend is different: it is computed over the observation series, and there is no receipt for a trend. What you can check there is its method and its paired-camera reasoning. The detector is named by a function id: only counts sharing one are comparable.
For agents
The same World, as a document.
Everything above, with nothing added, at one URL. No key. Rebuilt about every two minutes, and served from the last build while the next one runs — each panel carries its own age.
curl geo.qa/api/worlds/london curl geo.qa/api/world-model/verify/by-cid/<receipt cid>
The document also carries the derivation: each step, its inputs by address, who computed it, and how to re-run it without trusting us.
The twelve panels were read in full for this build.
not read this time: verify 43c42e88: backend-unreachable; verify cc9f60e4: backend-unreachable; verify d588465d: backend-unreachable; verify 30ef2908: backend-unreachable; verify 5c2c3c99: backend-unreachable; verify 1f3203a3: backend-unreachable; verify 05304c94: backend-unreachable; verify eda15532: backend-unreachable; verify d6b057f5: backend-unreachable; verify 064c546e: backend-unreachable; verify d95cf944: backend-unreachable; verify f5fe1307: backend-unreachable; verify ecc7f419: backend-unreachable
Generated 2026-11-03T19:08:27.113Z. Bring your own cameras, drones or phones and your World gets the same treatment, in its own namespace: write to us.