Answers for planning a traffic data project.

Share locations, study dates, service type, classes, intervals, movement requirements and required outputs. A short brief is enough to begin the scoping conversation.

Typical scopes include classified counts, turning movements, pedestrian and cyclist counts, parking observations, queue studies, origin-destination work and video-based analysis.

Yes. Classes are agreed around the client brief, local authority requirements, country terminology and the quality of the source data.

Footage should clearly show the agreed observation area, approaches and movements for the defined periods. Suitability is confirmed before processing.

Large video files should not be sent through a standard website form. An approved secure-transfer workflow can be agreed after initial scoping.

Review checks focus on completeness, consistent class application, intervals, movements and adherence to the approved specification.

Deliverables are agreed in the brief and may include spreadsheets, turning-movement summaries, time intervals, charts, methodology notes and a quality record.

Yes. Existing footage can be assessed for visibility, coverage, timing and suitability before analysis is scheduled.

Yes. Country and language requirements are scoped with the project; the country directory helps align terminology before a request is submitted.

Timing depends on the number of sites, survey duration, footage volume, classification detail and reporting format. A confirmed programme follows scope review.

Use the enquiry form for project context only. Do not include passwords, private keys or unnecessary personal information; secure file transfer can be arranged separately.

The team reviews the brief, confirms any missing scope details and replies from the enquiry mailbox with the next practical step.