Model demand-responsive transit service using GTFS-Flex

domain: gtfs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm the feed version: GTFS-Flex was merged directly into core GTFS in 2024, so current authoritative reference lives under the google/transit repo and gtfs.org, not the deprecated standalone MobilityData/gtfs-flex repo
  2. Look for flex-specific files such as booking_rules.txt and location_groups.txt/locations.geojson alongside standard GTFS files
  3. Identify stop_times.txt rows referencing flexible service via start_pickup_drop_off_window/end_pickup_drop_off_window instead of fixed times
  4. Read booking_rules.txt to determine how far in advance a rider must request a trip and by what mechanism
  5. Note that GTFS-Flex is static-only — it models business rules for demand-responsive service, not live vehicle location or real-time booking availability

Known gotchas

Related routes

evaluate gtfs-flex as a complement to gbfs/mds for demand-responsive microtransit trip planning
gtfs.org · 5 steps · unrated
Model fare products and rider pricing using GTFS-Fares v2
gtfs.org · 5 steps · unrated
model virtual station and dockless parking capacity per vehicle type in gbfs 3.0
gbfs.org · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans