How to Conduct a Traffic Signal Feasibility Survey Before Installing a New Signal

How to Conduct a Traffic Signal Feasibility Survey Before Installing a New Signal

How to Conduct a Traffic Signal Feasibility Survey Before Installing a New Signal

A traffic signal feasibility survey is the traffic data collection that tells an authority whether a junction needs a new signal and which design inputs that signal should use. This guide provides a practical checklist for evaluating traffic data before approving a new signal, whether you are a traffic authority, municipal engineer or EPC contractor. It covers the technical parameters and data requirements that authorities should consider before approving a new traffic signal.

Why does a feasibility survey need verifiable traffic data?

A feasibility survey needs counts that a design or warrant review can use, so verify the data method before accepting any vendor’s output. Signal timings are set from those counts, so the decision is only as sound as the data behind it.

Traffic signal engineering principles describe fixed-time signals as operating with phase timings predetermined from traffic studies. A weak survey therefore becomes a fixed error that the signal carries for years. A fixed-time signal can run with heavy cross traffic and almost no traffic on the main road, which is the kind of mismatch a good survey should expose.

Manual traffic counts can capture vehicle volume, but a comprehensive traffic assessment should also consider lane-wise distribution, turning movements and vehicle composition. These parameters provide a clearer understanding of traffic behaviour at an intersection.

Two practical consequences follow. A survey that reports only total volume cannot answer a turning-movement question, however clear its charts look. And a vendor’s count should be compared with an in-house count on the same breakdown, not on the headline total.

Check 1: Does the data cover the counts your study needs?

Your survey must cover every count type that your local warrant or design format requires, and the scope must be written down before fieldwork begins. Confirm the list with the approving authority rather than with the vendor.

Ask for a written scope that lists:

  • Vehicle classes, such as two-wheelers, cars, buses and trucks, reported separately
  • Counts by approach and by lane
  • Turning movements at the junction
  • Pedestrian counts, if your format requires them
  • The output format and the file types the authority will accept

If the authority’s format is not written down, do not guess it. Ask for the format in writing and record the date of the answer, so the scope can be traced later.

The collected traffic data should provide sufficient detail to understand vehicle movements, lane-wise distribution and vehicle composition at the intersection. These parameters help engineers evaluate traffic demand, identify movement patterns and determine whether the available information meets the requirements of the feasibility study.

Check 2: How long should the survey run, and can video replace a manual survey?

The survey duration should be agreed with the traffic authority for each junction, based on local traffic patterns, study objectives and applicable requirements. Do not accept a vendor’s duration as the standard. Write the agreed period for each junction separately, so that a junction with different peak patterns is not assumed to match another.

Video-based traffic monitoring can support continuous and recurring traffic analysis, while manual surveys provide observations during defined study periods. The appropriate survey duration depends on traffic patterns, assessment objectives and the requirements of the approving authority.

Ask two questions before signing. First, does the sample cover the peak periods your study uses? Second, does the vendor’s continuous data replace the manual survey, or does it supplement a short manual count that the authority still requires? The answer affects the survey scope and approval process, so record it in writing.

Check 3: What accuracy condition applies, and how do you validate the counts?

Validate vendor counts against manual counts taken at the same junction before approving the data. A vendor’s accuracy figure applies only to the condition it names.

The accuracy of video-based vehicle counting and classification can vary depending on visibility, lighting conditions, camera positioning and traffic density. Therefore, traffic data should be validated under different operating conditions, including low-light periods and dense mixed traffic.

A proposed validation has four steps:

  1. Pick one junction that represents the study area, and record its lighting and camera conditions.
  2. Run the manual count and the video count for the same time windows, including the peak periods.
  3. Compare totals by class, lane and turning movement, then flag any difference that would change the signal design. Record the difficult cases too, such as low-light periods or heavy mixed traffic, so they are not left out of the comparison.
  4. Have a named officer sign off the result before the vendor’s data is used for the decision.

The last step matters most. A signed comparison creates a record that the authority can defend if the design is later reviewed.

Hypothetical buyer scenario: how would a two-week parallel test work?

Consider a hypothetical municipal engineer who must decide whether a four-leg junction justifies a new signal, with a tight approval window and a budget for only one video vendor. The proposed evaluation is a two-week parallel test at that single junction, manual count against video count, reviewed before the scope is approved. This is not a test that has been performed.

The tradeoff is time against coverage. A two-week test is short enough to fit the approval window, but it may miss seasonal or weekend patterns that the authority’s format requires. The engineer should first identify the vendor whose output matches the required counts, then check the validation results before expanding to other junctions. If the validation shows gaps, the engineer can extend the manual count at the same junction rather than accept the vendor’s headline figures.

Check 4: Do existing cameras, integration and exports fit your design work?

Confirm camera suitability on site, and make export and exit terms a go or no-go check before the contract is signed. Export terms decide whether the authority keeps its data if it changes vendors.

Existing CCTV and IP cameras may support traffic data collection when their resolution, mounting height, viewing angle and coverage meet the survey requirements. Data exports should also be available in formats that support traffic analysis, reporting and integration with relevant planning applications.

Integration with existing traffic management systems and smart city infrastructure should also be considered. Supported communication protocols, data compatibility and long-term access to collected traffic information are important technical considerations.

Ask the vendor to confirm in writing that you can take raw counts, reports and the data dictionary if you change vendors. Without that term, the authority may lose the baseline it needs for the next review.

Shortlisting criteria for any vendor

Use consistent technical criteria to assess the quality, accuracy and suitability of collected traffic data. Each criterion should be supported by documented evidence.

  • Scope match: The vendor’s written output covers every count type in the authority’s format.
  • Validation evidence: The vendor accepts a signed side-by-side comparison against manual counts at one junction.
  • Stated conditions: Every accuracy figure comes with the lighting, visibility and traffic conditions it applies to.
  • Site fit: The existing cameras at the junction have been checked for resolution, mounting height and viewing angle.
  • Data ownership and exit: Raw counts, reports and the data dictionary can be taken if the authority changes vendors.
  • Controller protocol: The supported signal controller protocols are listed in writing.

A vendor that meets most of these criteria with evidence is a stronger candidate than one with the most features on a brochure. A vendor that cannot answer a criterion in writing has not yet passed it, whatever its website says.

Documents to request from any vendor

Before completing the feasibility assessment, ensure that the following technical documents and records are available:

  1. A written scope that matches the authority’s count types and output format
  2. A sample export in each file type the authority will accept, including the data dictionary
  3. The accuracy condition for every figure the vendor quotes
  4. A validation report from a previous deployment, if one exists, and a statement of what it did not cover
  5. The list of supported signal controller protocols
  6. The export and exit terms for raw counts, reports and the data dictionary

A vendor that cannot supply a sample export or a data dictionary before the contract is signed should be treated as a risk to the authority’s data continuity, however capable its analytics appear.

Key Technical Parameters for a Traffic Signal Feasibility Survey

The following table highlights important technical parameters to consider when assessing traffic data for a signal feasibility study.

Decision parameter What should be assessed?
Lane-wise or turning-movement counts
Vehicle movements across individual lanes and turning directions.
Vehicle classification
Separate identification of two-wheelers, cars, buses, trucks and other vehicle categories.
Survey duration and sample period
Coverage of peak hours, off-peak periods, weekdays and weekends, as required by the study.
Data accuracy and validation
Comparison of collected traffic data with manual observations under different traffic and visibility conditions.
Existing cameras and data exports
Camera suitability, recording quality, data accessibility and compatibility with traffic analysis applications.

For an authority assessing a new traffic signal, lane-wise counts, turning movements and vehicle classification are important inputs for understanding intersection traffic conditions. The collected data should also be validated for accuracy, and its format and compatibility with relevant traffic planning systems should be checked before it is used for signal design.

Which questions remain unresolved?

Carry these open items into the written scope:

  1. Which count types and output formats the approving authority requires
  2. The sample period for each junction, agreed with the authority
  3. Accuracy under the lighting and traffic conditions at your site
  4. The supported signal controller protocols and the export format for design software
  5. The vendor’s written export and exit terms

Key Takeaways

  • Set the required counts, classes, lanes and turning movements in writing before comparing vendors.
  • Agree the survey duration with the traffic authority, since no source reviewed sets one for an Indian junction.
  • Validate any video count against a signed manual count at the same junction, and make export terms a go or no-go check.

Conclusion

A traffic signal feasibility survey is only as strong as the data it rests on. The four checks in this guide help traffic authorities establish a clear, measurable and verifiable scope for traffic signal feasibility studies.

A structured feasibility survey helps identify traffic patterns, assess intersection requirements and establish reliable inputs for traffic signal planning. Data validation and technical evaluation remain essential before making installation decisions.

Use the checklist before any vendor is shortlisted. Require a written scope, a parallel validation at one junction, and written export terms, and the authority will hold a signal decision that it can explain later.

Key Terms Glossary

Turning movement count: A count of vehicles moving from one approach to another through a junction, by direction.

Lane-wise flow: The number of vehicles recorded in each lane of an approach over a given period.

Fixed-time signal: A traffic signal whose phase timings are set in advance from traffic studies rather than changed by live demand.

Signal warrant: A set of traffic conditions that an authority checks before deciding whether a signal is justified at a junction.

EPC contractor: A contractor engaged to engineer, procure and construct a project under a single contract.

Q1. Do I need a feasibility survey before installing a new traffic signal in India?

A feasibility survey gives the traffic authority the data needed to judge whether a signal is justified and how it should be designed. Check the applicable IRC codes and local rules with the approving authority, because requirements may vary by project and location.

Ask for the count types, lane and turning-movement output, and the accuracy conditions in writing. Then run a side-by-side validation against manual counts at the same site and agree on the data export requirements before signing. Any accuracy claim should be supported by validation evidence.

A traffic signal feasibility survey may require vehicle volume, vehicle classification, lane-wise counts, turning movement counts and pedestrian movement data. The exact requirements depend on the intersection, study objectives and applicable authority guidelines.

Turning movement counts show how vehicles move from different approaches through an intersection. They help engineers understand traffic distribution, identify movement conflicts and evaluate the requirements for signal phases and timing plans.

Existing CCTV cameras may be used when their resolution, viewing angle, mounting height, coverage and recording quality meet the survey requirements. Engineers should assess camera suitability and validate the collected data before using it for traffic signal planning.

The choice between fixed-time and adaptive traffic signals depends on traffic patterns, intersection complexity, and operational requirements. Fixed-time systems are often suitable for locations with predictable traffic flows. Adaptive Traffic Control Systems (ATCS) can adjust signal timings based on detected traffic conditions and may be beneficial at intersections with changing traffic demand. Selection should consider integration requirements, technical capabilities, maintenance, and expected performance benefits.

Table of Contents

Leave a Comment

Your email address will not be published. Required fields are marked *