Showcase
The Stage
The Stage shows a question travelling through GeoAI, act by act, next to a live map. It is built for demos, training and explaining to decision makers why an answer can be trusted. Nothing on it is invented: each act starts only when the real pipeline reaches that stage.
The eight acts
| Act | On the field | On the map |
|---|---|---|
| Route | Three doors: chat, catalogue, spatial. One lights up. | The deployment’s territory. |
| Analysis | Words in the question light up; concepts rise into the field; conditions are pinned. | The named place is drawn inside the territory. The camera stays wide, so you see where the place sits. |
| Retrieval | Candidate datasets fall in, sized by match, linked to the concept that found them. For a named place, only datasets with data in that municipality are searched. | Every candidate’s measured coverage appears; the camera only tilts into a survey view, it does not move away. |
| Selection | Roles light up: target, constraint, join partner. The rest fades. | Coverage turns into role rings. Solid means real coverage; dashed means a few features spilling over a border. |
| Dataset | Rival datasets fan out with their measured overlap; the combine-or-choose verdict plays out; specialist verdicts appear as chips. | A combination extends coverage to the extra municipalities. |
| Plan | The analysis family appears on the target, with labelled links to its constraints. | The camera makes its one move in, from the territory to the scope, and goes flat. It never pulls back out. Everything outside the scope fades. |
| Execute | A counter runs up to the result. In a multi-part question the part’s count is also written on its chapter strip. | Result features ripple out inside their evidence. |
| Merge | Only for a multi-part question: each part’s count and register, then the sum. | The parts land one at a time, each in its own colour. The legend names each kind with its count, and says how many are drawn when not all are. |
| Summary | The answer and scope note stream in. | Areas without evidence are greyed. The answer stays on the flat map as points, lines and areas, in its own colour. |
A question with several parts
When a message asks for two kinds of thing, the route act shows the split. Each part then plays analysis to execute as its own chapter, exactly as the pipeline runs it. A chapter strip above the map names the part being played (“Part 1 of 2”) and keeps its count once it is known. A Merge act follows: every part’s count and dataset and the total, while the parts’ results land on the map one at a time, each in its own colour, so you can see which result belongs to which kind. A part that could not be answered says so in its chapter and in the merge.
When the answer is a refusal
The field greys out and an Honest stop card shows the reason. The execute act states that nothing was executed, because a refusal has no number to inflate. It is often the most convincing part of a demo.
Ways to use it
Live
Type a question and press Run. Each act waits for the real pipeline and stays on screen long enough to read.
Replay
Drop a saved test-run file on the page and step through recorded questions without a model or database. Useful offline and for rehearsals.
Record
The Rec button records the tab to a video file for presentations (current Chrome or Edge, secure page).
Themes
Cool, Warm and Ink. Step, scrub, pause, and play at 1×, 1.6× or 2.5× speed.
Access
The website around the Stage (home page, this reference and the blog) is open to everyone. The Stage itself needs a personal Stage account:
- Request access. Visitors fill in their name, organisation and email on the request-access page. The request appears in the administration console.
- Account and invitation. An administrator creates the account from the request and sends the ready-written invitation, with the sign-in link, username and password, from their own mailbox.
- Sign in. Opening the Stage while signed out leads to the sign-in page and back to the Stage afterwards. A sign-in lasts until the browser has been idle for a while, the visitor signs out, or the application restarts.
A Stage account opens the Stage only, never the administration console. Disabling or deleting an account, or giving it a new password, signs it out on its next request.
Technical noteA browser sign-in is a random session token in an HttpOnly cookie, held in memory on the server. Scripts can still call the Stage endpoints with HTTP Basic credentials. Sign-in and request-access are rate-limited, and the request form carries a hidden field that catches bots.
Current limitsReplays carry no geometry, so the map stays schematic in replay mode. Very large results stay flat in the closing shot: more than 5,000 shapes, or more than 1,500 points.