labs@atheron:~/industries/transit-mobility/data$ query --warehouse --dashboards

Ridership data

Passenger counts, fares and schedules in one set of numbers.

Every transit system counts riders differently. A warehouse that loads passenger counters, fare transactions, schedules and shared mobility trips every night, and checks them, gives planners and the board one set of ridership numbers to work from.

Start a project See the example projects

// what matters here

What is different in this industry.

Every source, every night

Passenger counters, fare systems, GTFS Realtime and GBFS feeds loaded on a schedule.

Checked, not averaged

Missing trips and counters that read zero are flagged before anyone sees a dashboard.

Open data out

Exports in the formats you publish, from the same numbers your staff use.

In your own account

The warehouse runs in a cloud account you own, set up as code and monitored.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Ridership data warehouse

Hypothetical. Not a client, not a result.

// The problem

A transit agency's passenger counters, fare transactions, GTFS schedules and on-time data live in separate systems, and every board report starts with a week of reconciling.

// What we would build

A data warehouse in the agency's own cloud account that loads passenger counts, fare data, GTFS Realtime and bike and scooter share trips from GBFS feeds every night, checks them and feeds dashboards for ridership by route and stop, on-time performance and crowding. Open data exports go out in the formats you publish.

// What is in it

Nightly loads from passenger counters, fare systems, GTFS Realtime and GBFS feeds
Quality checks that flag missing trips and counters that read zero
Dashboards for ridership by route, stop and hour, on-time performance and crowding
Open data exports in the formats you publish
Staff sign in with your organisation's accounts

// Stack

PostgreSQL
dbt
Metabase or Power BI
GTFS Realtime and GBFS
Terraform
AWS Canada

// estimate

Build: ≈ US$62,200 to US$95,200, delivered within 16 weeksCAD 88,600 to 135,500
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 2.4 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Access to your GTFS Realtime feeds: 1 to 4 weeks
Your IT security review and sign-on setup: 4 to 8 weeks

How it is paid

Deposit 20%: CAD 17,720 to 27,100
Discovery 7.7%: CAD 6,822.20 to 10,433.50
Design approved 7.7%: CAD 6,822.20 to 10,433.50
Core features 23.3%: CAD 20,643.80 to 31,571.50
Full build 15.5%: CAD 13,733.00 to 21,002.50
Testing and fixes 7.7%: CAD 6,822.20 to 10,433.50
Launch 8.1%: CAD 7,176.60 to 10,975.50
Holdback, 30 days after launch (10%): CAD 8,860 to 13,550

Start from this example

// questions

Questions we get about this.

Can bike share and scooter trips sit beside transit ridership?

Yes, from the operators' GBFS feeds and the trip data your agreements give you.

Our passenger counters miss trips. Does the ridership warehouse hide that?

No. Gaps are flagged and reported, so planners know which numbers to trust.

Which tool do transit planners see dashboards in?

Metabase or Power BI if you already use one, or dashboards we build into your staff portal.

Back to the industry: Transit and mobility About the service: Data and analytics

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call