Not directly. The standard approach is a small ETL step that parses GTFS into a derived JSON or REST endpoint with the shape SleekRank expects (one record per route, with embedded stop arrays). Once the endpoint exists, SleekRank pulls from it like any other REST source.

Store the stops as an ordered array on the route record (derived from stop_times for a representative trip on the route). A list mapping renders the array as a vertical list with stop names, accessibility flags, and optional links to per-stop pages run as a separate page group.

Real-time prediction data (GTFS-RT) is too volatile for a cached page. The standard pattern is to embed a small client-side widget on the route page that fetches predictions from the agency's GTFS-RT endpoint on load. SleekRank renders the static reference; the widget overlays the live data.

Yes. The GTFS stops table includes a wheelchair_boarding flag. Pull that field into the stops array and render an accessibility icon next to each stop, plus a route-level summary on the route page. Accessibility is heavy SEO and a real user-trust signal.

Add an alerts array column for active service alerts affecting the route, sourced from GTFS-RT alerts or a separate agency CMS. Render the alerts as a banner at the top of the route page when the array is non-empty, with severity styling.

Combine GTFS feeds from multiple agencies into one derived endpoint and run a single page group, with an agency_code field on each route. The base template renders the agency name and color, and the URL pattern can include the agency for disambiguation (/routes/{agency}/{slug}/).

SleekRank does not generate maps. Most agencies have route-shape data in GTFS shapes.txt; render that as a static or interactive map via a selector mapping that injects the route shape ID into a map embed. Many agencies use Mapbox or a static-map provider for this.

Yes, and it pairs well with per-route. Stops get their own URLs (/stops/{slug}/) showing every route that serves the stop, accessibility info, nearby stops, and any departures display. Cross-link from each route page's stop list to the corresponding stop page.