GTFS, routes, and timetables: when a website stops being just a website

Some topics look purely technical until you bring them down to a real project decision. That is where they become interesting.

Data has shape

A transport website cannot treat routes and timetables as loose paragraphs. A line has directions, stops, journey patterns, departures, special dates, and maps.

When that content lives as text, maintenance becomes fragile. When it lives as data, the website can start reasoning.

GTFS as a starting point

GTFS helps because it brings a common structure for routes, trips, stop_times, calendar, and stops. But importing it is not enough. You need to turn it into a model the CMS can edit and the user can understand.

That means deduplicating journey patterns, grouping timetables, respecting directions, and preserving raw data for review.

The website as a data interface

In this kind of project, the public website is only the surface. Underneath, structured content allows timetables, next buses, and stops to be shown without writing everything by hand.

That is where a website starts to feel like a product.

Closing

In the end, most of it comes back to the same thing: build with intent, remove noise, and leave a base someone can use, understand, and maintain.