Skip to content

Traffic Designer

Traffic Designer is a tool for building transit and movement analysis projects from multiple processed locations. It helps combine ALPR results into one project workspace, then runs aggregation to produce movement-oriented outputs.

What Traffic Designer Does

  • Creates a new traffic project from selected locations
  • Lets you define project name and output directory
  • Allows selecting which locations are included in analysis
  • Runs aggregation workflow on selected locations
  • Stores results in a dedicated project folder

When to Use

Use Traffic Designer when you already have processed measurement locations and want to:

  • analyze movements between multiple points,
  • prepare transit-oriented summaries,
  • build one combined output from many locations,
  • organize ALPR-based cross-location analysis.

Input Requirements

Before starting:

  • At least one location must exist in the project.
  • Locations should contain processed data suitable for aggregation.
  • You should know which locations belong to the same traffic study.

Wizard Flow

Traffic Designer starts as a two-page wizard.

Page 1: Welcome

  • Shows introductory information about the tool.
  • Click Next to continue.

Page 2: Project Setup

  • Project name: default value is Traffic01
  • Project directory: default is based on the last location path
  • Location selection: choose locations from a checkable table

Click Next on the last page to confirm and start processing.

What Happens After Confirmation

After accepting the dialog:

  1. The application creates a project directory: projectLocation/projectName.
  2. Current media playback is stopped.
  3. Current configuration is saved.
  4. Aggregation action starts with selected locations.
  5. Progress is shown in a dedicated progress dialog.

If no locations are available or the dialog is canceled, the workflow exits without changes.

Output

Traffic Designer generates project outputs in the selected directory. The exact result set depends on input data and aggregation scope, but all artifacts are grouped inside the created project folder.

Practical Tips

  • Use clear project names, for example: Transit_Center_MorningPeak.
  • Select only locations that belong to one analysis scenario.
  • Keep one folder per study to simplify reporting and comparison.
  • Run ALPR/location processing first, then run Traffic Designer aggregation.
  • How-to workflow: wiki/en/howto/howto_traffic_designer.md
  • UI dialog implementation: aitracker_gui/Gui/DialogTrafficDesigner.py
  • Main window integration: aitracker_gui/Gui/MainWindowGui.py