hasadna/open-bus-map-search

A fake ride appear in singleLineMap

Open

#1,659 opened on Jun 14, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (125 forks)auto 404
data researchfrontendgood first issue

Repository metrics

Stars
 (95 stars)
PR merge metrics
 (PR metrics pending)

Description

Issue - singleLineMap falsely caught 2 vehicle for one ride.

How to reproduce:

https://open-bus-map-search.hasadna.org.il/single-line-map?date=2026-06-11&operatorId=3&lineNumber=480&routeKey=10480-1-%23&rideTime=24%3A10

Expected behavior:

  • If only one vehicle do a ride (and likely only one vehicle is planned to do the ride) - then the page should caught only the real ride.
  • The page supposed to order GPS pings by the actual time they were taken in.

Actual behavior:

  • The startTime picker show "2 vehicles" for that hour - but only one actually perform the ride.
  • The map show pings locations from 2 vehicles - one of them is clearly completely motionless.
  • The drawn "actual route" doesn't make sense anyway. The time spans of the real ride and the fake "ride" overlap - so I would expect the drawn route to be a mess but in fact it does group each vehicle separately - it just connect them afterwards for some reason.

Screenshots:

One vehicle at the end station, not moving:

Another vehicle actually ride along the route:

Contributor guide

Research direction
Examine the ride selection logic in the single line map component. Investigate how GPS pings are grouped by vehicle and why a stationary vehicle's pings are included in the displayed ride.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65