A shared network model
Current software work normalises identifiers, ordered stop sequences, optional route geometry and provenance. Planar coordinates and geographical coordinates remain explicitly different.
Ecosystem
Data, specifications and experimental software
The proposed architecture connects service data, editorial decisions, draft formats and experimental software.
From sources to representations
An open architectureDescribe the network and its presentation
Service data describes routes, stops and journeys. Editorial data adds decisions such as short labels, hierarchy and the ordering of routes along shared sections. The proposed model records editorial decisions separately so their source and purpose can be inspected.
GTFS-Carto
A proposed editorial extension linked to GTFS identifiers. The draft describes cartographic fields, publication metadata and reusable network presentation choices.
Draft formats and quality requirements
OTI standard
Proposed requirements for the quality, accessibility, provenance and currency of passenger information. It is a working draft with an unfinished conformance process.
Semantic Transit SVG
A proposed convention connecting vector artwork to routes, stops and other meaningful objects, supporting reuse between print and interaction.
Software and publication
The experimental OTI library uses a Rust geometry core compiled to WebAssembly. Its integration layer imports supported inputs, measures labels, produces SVG and supplies a browser viewer with quality diagnostics.
A shared registry is a separate proposal. It would describe network packages, their publishers, licences, versions and validity. Distributed publication should let different tools consume compatible resources while keeping responsibility with identifiable publishers.
Explore the toolchain
See the current scope and the documentation available for the experimental software.
Registry and publication
A direction for reusable, traceable network resources. A public registry service is not operating in this release.
One initiative, several ways to apply it
The owner intends open resources, research and future professional products and services to share the OTI identity. Possible applications include information design, integration, quality review and managed publication. These are directions to evaluate through concrete needs.
Shared formats should remain usable independently of a paid service. A reusable improvement can return through the contribution process, while private project data stays under its own rights and permissions. Open licensing and maintenance responsibilities need to remain clear in either case.