Review application A.2

Web app

The website lets reviewers explore the published snapshot: where ATLAS and OpenStreetMap agree, where they differ and why. This chapter describes its pages and the shared mechanisms behind them.

Layer Technology
Browser Leaflet maps and plain JavaScript modules, Bootstrap; all libraries served locally (A3.4)
Server Flask: server-rendered pages and a JSON API (backend/blueprints/), of which only /api/lookup is public (A2.10)
Data PostgreSQL with PostGIS (A1)

Pages

Page Path Shows Details
Map / Every matched and unmatched stop of the viewport, with filters, search and a live summary A2.1, A2.2, A2.3
Problems /problems One problem at a time, by priority, with the stops involved on a map A2.4
Routes /routes, /routes/non-gtfs, /routes/gtfs-stop-id-sloid Matched and unmatched lines with their variants, OSM routes outside the timetable, and the GTFS identity map A2.6
Operators /operators For each ATLAS operator, how its matched OSM stops are tagged with operator and operator:wikidata, as a list of values with counts and map links, and a consistency status A2.7 for its colours
Data /data/analytics, /data/export Statistics of the published snapshot and the live pipeline timeline; CSV and PDF exports A1.2, A3.5, A2.5
Docs /docs This documentation A2.8

The map, Problems and Routes pages keep what they show in the address bar, so it can be shared as a link (A2.9). Scripts and AI agents read the same stops as JSON through the public lookup, /api/lookup, and learn how from /llms.txt (A2.10). Every page polls the pipeline status, so the navigation bar shows when a run is in progress. Which source labels and views appear is set by the review configuration and the active bundle's capabilities (A3).