Zetema
Edit
Web & mobile · A few weeksAnywhere· Source · Oct 2026

Riders who spot a wrong bus or train time in an app have no easy way to tell whoever publishes the data.

Transit riders who find wrong times or stops in trip-planning apps

Where it stands

  1. Sourced (done)
  2. Kit (done)
  3. Wanted (next)
  4. Building
  5. Solved

How this problem came to be

  1. Found2 sourcesgithub.com/public-transport
  2. Quoted3 claimseach checked against its page
  3. BriefWrittenand what solved looks like
  4. Market1 signals5 reactions on the issue
  5. Kit5 steps22 tools · 6 routes
  6. People0 want0 live it · 0 would test

The problem, broken down

Who it hurts
Riders using apps built on Transitous, a free, community-run public transport routing service, and the agencies whose timetables it shows.
The moment
When a rider waits at a stop the app says exists, or for a departure that never comes.
What people do today
Errors have to be reported to whoever makes each timetable feed, and riders rarely know who that is.
Why it's unsolved
Transitous combines many feeds from different publishers, and the right contact differs for each one.
What solved looks like
A small web service and form: given a Transitous trip id, it works out which feed the trip came from, returns the right contact (or says none is known) and a prefilled report. Tested on 20 trips from different feeds.

Evidence

Every claim is tied to the source it comes from
Transitous issue #751: data quality issue reporting form ↗
  1. 1The issue says Transitous depends on outside parties for timetable data, and errors like wrong times or stop positions should be reported to whoever creates each GTFS feed.
  2. 2It proposes a service that takes a trip id, matches it to its source feed, picks a contact address in a set order of preference, and lets an app ask the user to send a prefilled email.
  3. 3The issue is labelled ‘good first issue’ and ‘help wanted’, and was still open on 2026-10-09.

Written from the cited sources. Anything they don't say is left as a question, not a guess.

Sources

From a public page with a citation.

  1. [1]GTFS Schedule reference
  2. [2]Transitous issue #751: data quality issue reporting form
What the source says, in short

The issue says Transitous depends on outside parties for timetable data, and errors like wrong times or stop positions should be reported to whoever creates each GTFS feed. It proposes a service that takes a trip id, matches it to its source feed, picks a contact address in a set order of preference, and lets an app ask the user to send a prefilled email. The issue is labelled ‘good first issue’ and ‘help wanted’, and was still open on 2026-10-09.

Forks 0

Nobody has forked this yet. Be the first.

Market read

How big this is, from the evidence

  • GitHub ↗Builders' pull · Medium confidence5 reactions on the issue

How these were measured: Total reactions on the GitHub issue, read from its API.

For whoever takes this up

The builder's path for this problem

Five steps, each with the tools that fit this problem and a word to carry with you. A starter prompt is ready to paste into any assistant.

Open the path

Discussion 0

No comments yet.