How are you inspecting GTFS feeds?

GTFS feeds are the backbone of public transit data - but actually seeing what's inside one has always been far harder than it should be.

The old workflow usually went something like: unzip the feed, write a script to parse routes.txt and stops.txt, spin up QGIS or another GIS tool, load the shapes, and spend 20 minutes configuring things - just to answer a basic question like "do these two routes actually overlap here?" That's a lot of friction for what should be a 10-second sanity check.

TransitLens removes all of that. Drop in a GTFS ZIP or paste a feed URL - and in seconds every route, stop, and service calendar is on an interactive map. Filter by agency, route, or transport type. Click any stop to inspect its metadata. No install, no account, no setup. And it's completely free. Beyond the map, there's a table view to easily browse, search, and sort all your stops and routes data - and powerful filters let you scope down to exactly what you need, whether that's a single agency, a specific transport type, or a subset of routes.

Now we want to hear from you - the people actually working with GTFS day to day. How were you handling feed inspection before? Custom scripts? QGIS? Something else entirely? And what would make TransitLens even more useful for your workflow - feed diffing, schedule validation, coverage analysis with your own polygons?

Every reply here directly shapes the roadmap. Drop your workflow below.