Route planning, built into the editor
The same feed you edit is the feed you analyze. Cost, coverage, equity, stop spacing, and demand — computed straight from your GTFS, with no GIS to set up and nothing uploaded anywhere. Methodology you can put in a board memo or a grant narrative, at a fraction of what a planning platform costs.
Operating cost estimates
Answer "what does this service cost?" directly from the schedule. GTFS·X reads every revenue hour in the feed, computes the peak vehicle count, and multiplies by a cost-per-revenue-hour you control — per-route and system-wide weekly and annual figures, with one-click CSV export. Set your own loaded labor rate (NTD operating expense per vehicle-revenue-hour is a defensible starting point) and a deadhead factor for platform time. Compare a proposed alternative against today's service with a saved snapshot.
Demographic coverage
Population, households, and workers within walking distance of your stops — from US Census ACS five-year data, apportioned by buffering each stop (quarter-mile bus, half-mile rail) and overlapping the Census block groups it touches. Per-route and system-wide totals, the kind of number FTA discretionary programs ask for.
Title VI equity analysis
Run an equity check while you're still designing the change. GTFS·X compares trips-per-capita in minority vs non-minority block groups (ACS B03002) and reports an equity ratio against the four-fifths (0.80) convention from FTA Circular 4702.1B, with green/amber/red banding. Run it on the current feed and the proposed feed and compare.
Stop analysis
Four stop-level diagnostics most agencies never pull from their feed: stop-spacing distribution (against APTA / TransitWiki benchmarks), consolidation candidates with a time-saving estimate each, service intensity per stop, and wheelchair-accessibility completeness. Every table exports to CSV; findings highlight on the map.
Rider propensity — Demand Dots Free
A nationwide map layer showing where transit demand concentrates: blue dots for high-propensity adults (renters, zero-vehicle households, ages 18–24), orange dots for jobs (LEHD LODES), one dot per five people or jobs. Toggle it on while sketching an alignment or sizing a flex zone. Free on every plan.
Defensible by design
Built for planners who have to defend a number: real Census vintages cited on every result (ACS 2022 5-year for coverage/Title VI; ACS 2020–2024 + LEHD LODES 2023 for Demand Dots); standards not guesses (FTA Circular 4702.1B four-fifths, conventional walk buffers, APTA stop spacing, NTD cost reference); and documentation that states plainly what each tool doesn't capture.
What's free vs. Agency
Free on every plan: the Demand Dots layer, the Service Summary (revenue hours, trips, peak vehicles, span), and the system-level headline figures for cost and coverage.
Agency: route-level cost and coverage depth, Title VI, stop analysis, scenario comparison, and team collaboration.