Specifications
Working proposals for quality, editorial data and meaningful vector output. The conformance framework remains unfinished.
About OTI
Open Transit Information is developing a common standard for clear, consistent, accessible transport information.
The aim is a coherent information language that people can recognise and understand across transport networks. Proposed studies compare legibility, symbols, hierarchy, sound and interaction in defined tasks. Their intended role is to inform shared quality requirements.
Maps, station displays, personal journeys and spoken information serve different contexts. Each should apply the same principles of clarity, reliability and accessibility. Open specifications, reusable data, software and research provide the foundations for that standard.
OTI is in an early development stage. Draft specifications and research documents sit alongside an experimental software implementation. Their maturity differs, so each area identifies its current status.
Working proposals for quality, editorial data and meaningful vector output. The conformance framework remains unfinished.
A published experimental npm library backed by a Rust/WebAssembly core. Its API and supported workflows continue to develop.
Questions and proposed methods for representation, perception, language and communication through different channels.
The project is currently maintainer-led. Its source credits Open Transit Information contributors, and its governance draft describes the initial maintainer's role and the recording of design decisions.
A multi-organisation steering group and a non-profit organisation are future governance proposals. The draft also calls for specification decisions to remain distinct from the priorities of a particular software implementation.
See the current responsibilities, documented proposals and decisions still needed.
Open resources, research and possible professional products and services share the OTI identity. Integration, information design and managed publication are areas to investigate through real needs and clearly scoped work.
Future paid offers must identify their provider and conditions. Shared formats should remain usable independently of purchasing a service, and improvements proposed to the common work should follow its review process.
Start with a specific question, a source or an example that can improve the shared work.
Project code is licensed under Apache-2.0. Specifications and documentation use CC-BY-4.0. Each resource keeps its own licence and attribution requirements.
Public Sans and its licence are included locally. The Bilbao network uses CTB / Metro Bilbao open data and OpenStreetMap geography. Source licences, dates and editorial decisions are recorded with the map.