The General Traffic Signal Specification (GTSS) provides a simple, open, and universal framework for traffic signal data, configuration and location. By defining a minimal set of four CSV files, GTSS makes it easy for cities, vendors, and developers to share, analyze, and develop signal systems reliably and consistently.
From these four files, agencies can power performance monitoring, mapping, visualization, and analytics, while enabling developers to build new tools and services without extra configuration or proprietary barriers.
Github: github.com/GTSS/
Discussions: github.com/GTSS/discussions
Mission
To create an open, practical standard for traffic signal systems that prioritizes safety, efficiency, interoperability, and innovation, while supporting the evolution toward smart, digitization of urban infrastructure.Core Concept: Four Files, Endless Possibilities
GTSS v1.0 is intentionally simple. With just four core text files, agencies can describe every intersection in a standardized way:- agency.txt — Basic agency information: name, contact, and operational metadata.
- signals.txt — Intersection locations, street names, and signal ID.
- phases.txt — Each signal’s phasing, movement details and posted speed.
- detectors.txt — Detection channels, types, and setback distance and lane assignments.
From these four files, agencies can power performance monitoring, mapping, visualization, and analytics, while enabling developers to build new tools and services without extra configuration or proprietary barriers.
History
GTSS was created to solve a fragmented traffic signal landscape, where incompatible systems and proprietary protocols caused inefficiencies and vendor bias.Get Involved
GTSS is an open specification, built with input from traffic engineers, city planners, technology companies, and safety advocates. Contributions are welcome from anyone interested in improving urban transportation systems.Github: github.com/GTSS/
Discussions: github.com/GTSS/discussions