API returns total_actual_rides: 0 for all operators on 2025-09-17 !

[Avri-Here]

Bug Description

The /gtfs_rides_agg/group_by endpoint returns total_actual_rides: 0 for ALL operators when querying data for 2025-09-17.

API Call

Expected Behavior

Should return realistic numbers for total_actual_rides based on SIRI real-time data.

Actual Behavior

All operators return total_actual_rides: 0, while total_planned_rides shows normal values.

Sample Response

[{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":2,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":1230,"total_planned_rides":1230,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":3,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":20057,"total_planned_rides":46608,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":4,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":3242,"total_planned_rides":4410,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":5,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":6328,"total_planned_rides":24385,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":6,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":1892,"total_planned_rides":4442,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":7,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":2285,"total_planned_rides":3271,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":8,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":744,"total_planned_rides":908,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":10,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":98,"total_planned_rides":98,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":14,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":7354,"total_planned_rides":12105,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":15,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":12618,"total_planned_rides":25872,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":16,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":8559,"total_planned_rides":21014,"total_actual_rides":0},{"gtfs_route_date":null,"gtfs_route_hour":null,"operator_ref":18,"day_of_week":null,"line_ref":null,"route_short_name":null,"route_long_name":null,"total_routes":14100,"total_planned_rides":26736,"total_actual_rides":0} ..

Impact

This causes the Open Bus Map Search application to display 0% completion rate for all operators.

Environment

• Date: 2025-09-18
• Query Date Range: 2025-09-17 to 2025-09-18
• All operators affected (2, 3, 4, 5, etc.)

[NoamGaash]

⚠️ AI-written comment. Drafted by an AI agent from hackathon materials. The
reproduction below was run against the live API on 2026-08-01, but please verify
independently before relying on it.

Confirming this is not specific to 2025-09-17, and not ingestion lag.

Two independent analyses during the hasadna Open Bus hackathon (July 2026) hit this,
across both /gtfs_rides_agg/list and /gtfs_rides_agg/group_by, on every date
sampled from 2025-11 to 2026-07, network-wide:

from openbus_hack import stride
for d in ["2026-07-01", "2026-06-15", "2026-04-01", "2025-11-01"]:
    rows = stride.get("/gtfs_rides_agg/group_by",
                      {"date_from": d, "date_to": d,
                       "group_by": "operator_ref,gtfs_route_date"})
    print(d, sum(r["total_planned_rides"] or 0 for r in rows),
             sum(r["total_actual_rides"] or 0 for r in rows))

Date	Σ total_planned_rides	Σ total_actual_rides
2026-07-01	121,420	0
2026-06-15	122,088	0
2026-04-01	53,260	0
2025-11-01	27,327	0

The control that rules out lag: line 2259 on 2026-07-29 reports
total_actual_rides = 0 in the aggregate, while /rides_execution/list for the same
line and date returns real actual_start_time values and zero cancellations. The
actuals exist at ride level — they are simply not being rolled into the aggregate.

num_planned_rides is populated normally and cross-checks well against the ride-level
endpoint (aggregate 123 vs 126 planned for that line/date), so the aggregate is still
usable as a planned-ride denominator. The actual column alone is the problem.

This has a live user-facing consequence. totalActualRides is consumed by five
pages in דאטאבוס (AllLinesChart, WorstLinesChart, DayTimeChart, OperatorGaps,
DataResearch), so the dashboard currently renders a confident chart showing that
essentially no bus in Israel ran. Tracked as
hasadna/open-bus-map-search#1770.

Method and full evidence:
https://github.com/hasadna/open-bus-hackathon-26/blob/main/algorithms/service-by-operator.md