Changeset Second Opinion

Welcome. Changeset Second Opinion helps a volunteer reviewer with a flagged OpenStreetMap edit. It gathers the public evidence for one changeset, asks a small model ten yes or no questions about it, shows every answer, and suggests where the case belongs in your queue. If a reply to the mapper would help, it drafts one for you to edit. You can try it on demo data in a few minutes, with no OpenStreetMap account, no GPU and no AWS account. New here? Read what it is, then follow the quickstart.

What it will not do

• It never writes to OpenStreetMap. It reads public data. The one extra request to OpenStreetMap is the sign-in exchange, with read-only scope.
• Lanes only order the queue. Nothing is hidden, nothing closes by itself and nothing is posted by itself.

A case on the demo data: real changesets from October 2026, read by the Strands Decider 2B.

Find your path

Review a changeset

You look after the map and a flagged edit has landed in your queue. Review your first changeset.

Run a workspace

You invite people, set the tone and own the workspace. Set up the first admin.

Self-host it

You run it, keep it up and keep the cost capped. Install with Docker Compose.

Contribute

You fix a bug, add a question or write a community pack. Set up for development.

Check the claims

You are judging or studying it and want the answer in five minutes. How a verdict is made and what it cannot do.

How these docs are organised

Every page is one of four kinds, and its first line says who it is for. Tutorials teach by doing. How-to guides get one task done. Reference pages are complete and dry, and the ones for the API, the command line, the settings, the roles and the schemas are generated from the code. Explanations say why. The idea comes from Diátaxis.