Laurent Brand
← Case study
Browse all guides

CITA Traffic Platform / Documentation

Technical documentation

Run the prototype, trace its data, diagnose failures, and reproduce the A3 result.

Start with what you have

Select the input you have. The next step changes to match what you can actually verify.

Available input

Check the published A3 result

Start here with the files available on this site. You need Python 3; no source checkout, database, or university account.

What you can verifyCheck 48 hourly points, including 68.3 km/h on weekdays versus 101.2 km/h on weekends at 08:00. This checks the export; it does not recompute the original measurements.

Check the public export

Run the platform with a known input

Use the submitted source and its bundled A1 XML fixture. You need Docker, Compose, and a fresh local review database; no evaluation dump.

What you can verifyVerify migration, parsing, persistence, and duplicate handling: 37 A1 measurements and two fetches sharing one snapshot.

Start the fixture quickstart

Recompute every published A3 point

Use the corrected evaluation_hourly_profile.csv from the figure inputs. Python 3 is enough; no database is needed.

What you can verifyRebuild all 48 observation-weighted speeds and sample counts, then compare them with the public export.

Rebuild from the corrected CSV

Re-run the full evaluation queries

Use the archived dump from the thesis/university distribution, the application source, and PostgreSQL 17. Dump access is required and may need permission.

What you can verifyInspect the fixed dataset, export hourly profiles, and regenerate load windows. A complete archive restore was not verified here; raw XML reprocessing also needs the separate archive volume.

Open the archive workflow

Source access and other tasks

The public JSON and small verification tools are available here. The application source, corrected CSV, database dump, and raw archive are separate thesis materials; these docs do not supply a public source clone or institutional access.

Commands marked “Thesis source” run beside its compose.yaml. Source references are relative to that application unless marked Portfolio or Figures. The portfolio itself never connects to the database.

Verification scope

Verified on 6 November 2026: source image builds, migration and the fixture workflow with ephemeral PostgreSQL 17, 55 source tests, and all 48 A3 points reproduced from the corrected CSV.

A complete database restore and persistent-volume durability were not tested. Those steps remain explicitly marked in the guides. Requirements use version ranges; a fresh build can resolve newer packages than the original thesis environment.

Source files

Paths identify the relevant files and symbols in the inspected source distribution; they are not links to an assumed public repository. See access requirements.

README.md
Installation and evaluation prerequisites
compose.yaml
Services and volumes
Portfolio: docs/TRAFFIC-DATA.md
Aggregate provenance