Documentation
Complete guide to implementing and working with the General Traffic Signal Specification (GTSS).
GTSS Overview
Welcome to the comprehensive documentation for the General Traffic Signal Specification. Whether you’re a traffic engineer, system integrator, or city planner, this guide will help you understand and implement GTSS-compliant traffic signal information. GTSS Consits of 6 text (.txt) files each with their own set of parameters seperated by a comma.
agency.txt
agency.txt identifies the agency information associated with the traffic signals defined in the other GTSS files. Parameters include the agency ID, name, web address, timezone and email contact.
signals.txt
signals.txt lists signal ID, latitude and longitude information for the center of the intersection, and street names associated with each direction.
approaches.txt
approaches.txt defines the physical approaches to an intersection, including street names, compass bearing, and posted speed limits. Approaches represent real-world geometry with associations with one or more phases in phases.txt.
phases.txt
phases.txt defines phases and the lane and movement type through the intersection, number of lanes, and links to an approach ID as defined in approaches.txt.
detectors.txt
detectors.txt defines channels associated with phases for a specific signal, where these detection areas are in relation to stop bar and size, and expected objects to be detected.
basic_timings.txt
basic_timings.txt defines core signal timing parameters for each phase, including minimum green, yellow, all-red, pedestrian timings, and leading pedestrian intervals (LPIs).