Swiftly understands that our operational, service planning, and scheduling customers often need to visualize Swiftly data in outside systems. This is why Swiftly makes it easy for our agency customers to export their data using CSV exports.
If you prefer to use the Swiftly API, please see the Swiftly API article.
Historical data
Swiftly historical data can be downloaded directly by following any of the guides below.
On-Time Performance Report
Find the download by going to Dashboard ➡️ Go to On-Time Performance ➡️ Select the Routes tab ➡️ Click Download.
Use this to:
- Compare early/late/on-time performance by route
- View stop-level adherence data
- Identify captured or missing stops
Why use it:
Quickly identify trends and improve schedule adherance across your system.
Run Times Report
Find the download by going to Dashboard ➡️ Go to Run Times ➡️ Click the Download button.
Use this to:
- Compare scheduled vs. actual run-times
- Identify trips running long or short
- See suggested runtime adjustments
Why use it?
Helps planners maximize on-time performance by finding opportunities to reduce or increase slack on the schedule.
Speed Map Report
Find the download by going to Dashboard ➡️ Go to Speed Map ➡️ Click Export CSV (bottom left).
Use this to:
- Identify slow segments, variability, and long dwell times
- Spot areas needing infrastructure or planning changes
Why use it:
Pinpoints reliability issues and helps guide investment decisions using live speed and dwell data.
Operator Reports (API Only)
Download Method: Only available via API
Why use it:
Understand individual operator performance over time — schedule adherence, performance trends, and morale-boosting insights.
🧾Hopthru Ridership Reports
Access the download by going to Dashboard ➡️ Open the “All Routes” or "All stops" dropdown ➡️ Select a report ➡️ Click the Download button (upper right corner)
Use this to:
- View ridership counts
- Compare ridership numbers by route/stop/vehicle/etc.
- Check average daily max loads and total boardings
Download Center Reports
In addition to historical data, Swiftly’s download center offers several valuable reports to help you meet your operational, service delivery, and service planning needs.
Missing trips
- Need to understand what trips are contributing to an incomplete data set? This report reveals your missed service and helps you identify problematic trips.
- Read more:
Service Metrics by stop/trip
- This holistic report offers a complete download of all captured, explained and missed service in your Swiftly data set.
- Use either report to troubleshoot issues at stop or trip level, as well to identify opportunities to improve the GTFS schedule.
- Read more:
Passenger Counts
- Is your agency using Swiftly’s manual passenger counter through the Onboard App? Service planning and scheduling can leverage this ridership data set to account for manually tallied boardings and alightings by stop.
- Read more:
Boardings by fare type
- This report shows you boarding and alightings by fare type (adult, child, senior, etc…).
- Unlike the report above, this report organizes data by boardings, and not by the sum of boardings/alightings by stop.
- Read more:
Pull out performance summary/Pull out events
- Has your agency implemented Cal-ITP’s Transit Operational Data Standard TODS in Swiftly, and looking for a report to track non-revenue service?
- This dataset includes a summary of pullout performance for a given date and time range. Data can be summarized by yard, vehicle, block, direction, or route. Key metrics include the number of scheduled pull-outs, number of observed pull-outs, and the percent of on-time pull-outs.
Please email support@goswift.ly if you:
1) Are looking to integrate with TODS.
2) Are already integrated with TODS, but do not see this report visible on your account.
Auto-Assigner Metrics by Stop Report
- Are you diagnosing missing data or irregularities in CAD/AVL or GTFS, or trying to identify gaps in assignment coverage by route, vehicle, or stop?
- This report adds visibility into the number and percentage of observed stops captured by Auto-Assigner so that you can validate the effectiveness of onboard hardware and assignment feeds.
- Read more:
Comments
Please sign in to leave a comment.