New in GTFS·X: scenario planning, Fares v2, flex zones, flag stops, network walksheds & embeddable widgets

Can you add l Network Redesign & Day-to-Day Service Management — Plan major network changes or routine adjustments in one place Via Transportation.

On-Demand Planning — Design flexible, demand-responsive services that complement fixed routes Via Transportation.

Scheduling Algorithms — Optimize blocking, runcutting, and rostering for efficient operations Transportation.

Streets & Infrastructure Design — Data-driven street design to speed up infrastructure Transportation.

Data & Analytics
Demographic & GIS Analysis — Evaluate service impact on low-income and minority populations in real time Via Transportation+1.

Ridership Forecasting — Predict ridership to guide service decisions SoftwareSuggest.

Custom Stats & Geostats — Build and manage your own geospatial statistics for project estimates and Jane/NJANE Via Transportation.

Demand & Accessibility Analysis — Assess network performance and equity SoftwareSuggest.

GTFS & Fare Integration
Full GTFS Support — Import and manage routes, stops, and fares; assign rules and share with Google Maps,, etc.

Custom GTFS Fields — Route description, URL, continuous pickup/drop-off, trip short name .

Thanks Ephraim, this is a great checklist. Most of it maps directly onto what GTFS·X already does today, so here is a point-by-point with links into the docs. A few items are genuinely outside what we do, but most of what you've described is current functionality available to Agency tier subscribers.

Planning & operations

1. Network redesign & day-to-day service management. Yes. Save the routes you are viewing as named scenarios ("current", "proposed redesign") and switch between them from the header. Cost, Coverage, Title VI, and Stop analysis all re-scope to the active scenario, so you can compare a redesign against today's network without duplicating feeds. Routine edits (trips, calendars, stop times) live in the same editor. Docs: Scenario analysis

1. On-demand planning. Yes. Full GTFS-Flex authoring: draw polygon service areas (microtransit), build stop groups (dial-a-ride), generate deviation buffers off a fixed route, and set booking rules and service windows, all alongside your fixed routes in one feed. Docs: Flex zones & booking rules, with a primer at What is GTFS-Flex?

1. Scheduling. Partial, and worth being precise about. GTFS·X estimates stop times from the road network (Mapbox map-matching plus dwell and speed factors), duplicates trips on a headway, and manages vehicle blocks. It does not do runcutting or crew rostering. Those are operations-side tools that sit outside a GTFS authoring app. Docs: Timetables, trips & blocks

1. Streets & infrastructure design. Not something we do. We draw transit alignments with snap-to-road, but GTFS·X is a transit-data tool, not a streetscape or roadway-design tool. Docs (alignment drawing): Routes & shapes

Data & analytics

1. Demographic & GIS analysis. Yes. Census/ACS block-group coverage (population, households, workers) with an equity profile (minority, low-income, zero-vehicle, senior, youth vs the county baseline), plus an FTA Title VI service-equity analysis. Docs: Demographic coverage and Title VI analysis

1. Ridership forecasting. Not yet, and I would rather not overstate it. We show a demand-propensity layer (renters, zero-car households, ages 18 to 24, jobs from ACS plus LODES) to inform where to put service, but it is a display layer, not a boarding forecast. Honest ridership prediction needs APC or modeled OD data we do not synthesize. Docs (what the layer is and is not): Rider propensity

1. Custom stats & geostats. Not currently. The analysis modules use a fixed set of Census variables; there is no way yet to bring your own layers or define custom spatial metrics. The closest thing for project estimates is per-route cost modeling. Docs: Cost estimation

1. Demand & accessibility analysis. Partial, and useful. Coverage analysis (including network-distance walksheds on Agency plans), Title VI equity, and stop-level diagnostics (wheelchair-boarding completeness, spacing, service intensity). It is planning-grade demand and accessibility, not live ridership. Docs: Demographic coverage and Stop analysis

GTFS & fare integration

1. Full GTFS support. Yes. Import and edit the full spec (routes, stops, calendars, transfers, pathways, frequencies, fares, plus GTFS-Flex), validate as you go, then publish to a stable URL with automatic Mobility Database registration and a checklist for Google, Apple, and transit.land. Docs: Import & export, Hosted publishing, and Fares

1. Custom GTFS fields. Mostly. routedesc, routeurl, and continuous pickup/drop-off (route-level and per-stop, the flag-stop case) are all editable in the UI. tripshortname is preserved on import and export but does not have its own editor field yet. Docs: Routes & shapes and Flex zones & booking rules

Short version: the planning, GTFS authoring, and equity-analysis pieces are here today and free to try. The operations-scheduling and ridership-modeling items are not, and a couple (street design, custom geostats) are outside what GTFS·X aims to be. That said, if any of these are "must have" features for your agency, please do let me know—I'm always interested in suggestions for how to make the platform more useful.

DOSE IT ALLOW GTFS X ALLOW TO SIGN IN INTO REMIX VIA USA STATE

There's no direct integration between Remit and GTFS·X. The best workflow for switching from Remix is to export your existing Remix projects to GTFS which can be imported here.

Oh how could I get the all transit tools do I have to like contact you or something like that

Ephraim, I'll reach out to you directly via email!