Overview
When working with Hopthru Ridership, encountering missing or incomplete information can be frustrating. This guide will walk you through the most common reasons data may not be appearing as expected—and what steps you can take to troubleshoot and resolve the issue on your own.
The dip in the graph shows a sudden drop in ridership data
Common Causes and How You Can Troubleshoot
1. APC Data Is Not Updating
Automatic Passenger Counters (APCs) provide critical ridership insights, and if the data isn’t showing up, it usually falls into one of these categories:
✅ Check your APC Software
Make sure your APC provider is regularly sending data to Swiftly. Disruptions in the data pipeline or changes to system settings can interrupt the data flow. Contact your APC provider or system integrator to confirm everything is still connected and communicating with Swiftly.
🔧 Investigate your APC Hardware
Sometimes the issue is local. APC hardware can malfunction due to power issues, sensor failures, or physical damage. Ask a maintenance technician or IT team member to check the status of your APC units. A quick onsite inspection can often uncover a fix.
2. Your GTFS Feed Might Be Outdated
Hopthru uses GTFS to observe the scheduled service for a transit system. The GTFS needs to be up-to-date with the latest service schedule, so that the tool works correctly.
📅 Check the GTFS Version
Double-check the version and expiration date of your GTFS file. If it’s out of date, it may not be compatible with the system, leading to missing or inconsistent data. You may want to confirm with the individual who is in charge of sending us your GTFS file, that we have your most up-to-date GTFS.
📬 Send the Updated GTFS to Swiftly
If you already have an updated GTFS file or a link to a hosted version, email it to support@goswift.ly. Our team will ensure your data is updated promptly and accurately.
If you can’t pinpoint the issue, reach out support@goswift.ly
Comments
Article is closed for comments.